Re: NFS client names not mapping

2022-01-28 Thread Ed Greshko
On 29/01/2022 13:44, Gordon Messmer wrote: On 1/28/22 06:08, Robert Nichols wrote: Where does Fedora get its domain name? When I type "hostname --fqdn" I get "hostname: Name or service not known". The CentOS 8 VM apparently gets its domain name from the /etc/hostname file, which contains "cent

Re: heads up: node export service file has been renamed

2022-01-28 Thread Francois
On Fri, 28 Jan 2022 at 13:08, Barry Scott wrote: > > I just updated one of my servers and it failed to reboot. > > The reason is that I had: > > Requires=node_exporter.service > > in the default target and the update had installed a change to > the name of the node exporter service. It is not

Re: NFS client names not mapping

2022-01-28 Thread Ed Greshko
On 29/01/2022 11:44, Robert Nichols wrote: No change: [fedora ~]# hostnamectl hostname fedora.local [fedora ~]# hostnamectl  Static hostname: fedora.local    Icon name: computer-vm  Chassis: vm   Machine ID: 6e701e7fa0dc4996984b6509b40eb940  Boot ID: 256c0a3fa9dd4b88bd611

Re: NFS client names not mapping

2022-01-28 Thread Gordon Messmer
On 1/28/22 06:08, Robert Nichols wrote: Where does Fedora get its domain name? When I type "hostname --fqdn" I get "hostname: Name or service not known". The CentOS 8 VM apparently gets its domain name from the /etc/hostname file, which contains "cent9-vm.local". This does not appear to work in

Re: NFS client names not mapping

2022-01-28 Thread Robert Nichols
On 1/27/22 9:13 AM, francis.montag...@inria.fr wrote: Hi. On Thu, 27 Jan 2022 08:10:53 -0600 Robert Nichols wrote: On 1/26/22 7:15 PM, Gordon Messmer wrote: What does the entry for that filesystem in /proc/mounts look like?  It should have negotiated mount options that shed some light.

Re: NFS client names not mapping

2022-01-28 Thread Robert Nichols
On 1/28/22 8:53 AM, Ed Greshko wrote: On 28/01/2022 22:08, Robert Nichols wrote: On 1/28/22 1:03 AM, Ed Greshko wrote: On 26/01/2022 00:35, Robert Nichols wrote: In a Fedora 35 VM, all users and groups in an NFS mounted filesystem are mapped to "nobody" even though the names and numeric IDs a

Re: heads up: node export service file has been renamed

2022-01-28 Thread Patrick O'Callaghan
On Fri, 2022-01-28 at 14:52 +, Barry Scott wrote: > > > It is not called prometheus-node-exporter.service > > > > "Now called ..." I presume. > > Opsss. now called. > "Oops ..." I presume :-) poc ___ users mailing list -- users@lists.fedoraproject

Re: NFS client names not mapping

2022-01-28 Thread Ed Greshko
On 28/01/2022 22:53, Ed Greshko wrote: Example: For the host that I mentioned I used "hostnamectl f35ser.greshko.com" Correction. hostnamectl hostname f35ser.greshko.com Too late in my day. -- Did 황준호 die? ___ users mailing list -- users@lists.

Re: NFS client names not mapping

2022-01-28 Thread Ed Greshko
On 28/01/2022 22:08, Robert Nichols wrote: On 1/28/22 1:03 AM, Ed Greshko wrote: On 26/01/2022 00:35, Robert Nichols wrote: In a Fedora 35 VM, all users and groups in an NFS mounted filesystem are mapped to "nobody" even though the names and numeric IDs are the same on the server and client.

Re: heads up: node export service file has been renamed

2022-01-28 Thread Barry Scott
> On 28 Jan 2022, at 12:14, Patrick O'Callaghan wrote: > > On Fri, 2022-01-28 at 12:07 +, Barry Scott wrote: >> It is not called prometheus-node-exporter.service > > "Now called ..." I presume. Opsss. now called. Also watch out for prometheus.service changes as well. The way that you con

Re: NFS client names not mapping

2022-01-28 Thread Robert Nichols
On 1/28/22 1:03 AM, Ed Greshko wrote: On 26/01/2022 00:35, Robert Nichols wrote: In a Fedora 35 VM, all users and groups in an NFS mounted filesystem are mapped to "nobody" even though the names and numeric IDs are the same on the server and client. The messages logged are of the form: "

Re: heads up: node export service file has been renamed

2022-01-28 Thread Patrick O'Callaghan
On Fri, 2022-01-28 at 12:07 +, Barry Scott wrote: > It is not called prometheus-node-exporter.service "Now called ..." I presume. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedorapro

heads up: node export service file has been renamed

2022-01-28 Thread Barry Scott
I just updated one of my servers and it failed to reboot. The reason is that I had: Requires=node_exporter.service in the default target and the update had installed a change to the name of the node exporter service. It is not called prometheus-node-exporter.service Having been bitten I'm c

Re: firewalld restricts localhost - ?

2022-01-28 Thread lejeczek via users
On 28/01/2022 10:16, lejeczek via users wrote: Hi guys. I'm trying still not squared away Centos 9 firewalld and since closest to it is Fedora, here is a natural place to ask I thought - 'forward-port' if you use it for 'localhost', like here:     port=80:proto=tcp:toport=81:toaddr=127.0.0.1

firewalld restricts localhost - ?

2022-01-28 Thread lejeczek via users
Hi guys. I'm trying still not squared away Centos 9 firewalld and since closest to it is Fedora, here is a natural place to ask I thought - 'forward-port' if you use it for 'localhost', like here:     port=80:proto=tcp:toport=81:toaddr=127.0.0.1 does it work on Fedora, out-of-box? It used t