Re: NFS not connecting -
Tim: >> You might want to look at that file: >> >> /run/systemd/generator/nfs-server.service.d/order-with-mounts.conf Bob Goodwin: > [root@NFS-Server bobg]# cat > /run/systemd/generator/nfs-server.service.d/order-with-mounts.conf > # Automatically generated by nfs-server-generator > > [Unit] > RequiresMountsFor=/nfs4exports/home > > I'm not familiar with any of that? I see the same kind of thing in mine. It lists the directories to be exported. >>> # /home/egreshko >>> 192.168.0.0/16(rw,sync,insecure,no_root_squash,no_s > Above is an example provided by Ed, below is a similar line with my > address, just a trial to see if NFS might start with that in place, > it did not. >>> /home/bobg >>> 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) >> You're absolutely sure those filepaths are correct? And do you have >> line breaks in the file, as above? I've never seen an exports file >> like that. Again, are those line breaks in your exports file? Each entry should be one lone line. filepath allowed-address(options) e.g. /home/bobg 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) With no hash in front of it. -- uname -rsvp Linux 3.10.0-1062.9.1.el7.x86_64 #1 SMP Fri Dec 6 15:49:49 UTC 2019 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-08 18:58, Ed Greshko wrote: One more thing. Based on what commands were given to get this working I wonder if you didn't have a typo earlier when you created the directory. I would do an ls / to make sure you don't have a directory with a bad name. As well as ls /nfs4exports again to make sure you don't have directories you're not expecting. Such as "home1". . i don't see anything I can't account for ... But at the client I cam mount /media/nfs and create directories, cp stuff to them and it all appears in the server e.g. [root@NFS-Server bobg]# ls -al /nfs4exports/home/OOcalc total 40 drw-rw-r--. 2 root root 4096 Dec 8 20:10 . drw-rw-r--. 3 root root 4096 Dec 8 19:59 .. -rw-r--r--. 1 root root 15019 Dec 8 20:10 BOX86-Viasat-Usage-NOVEMBER-2019.ods -rw-r--r--. 1 root root 15075 Dec 8 20:10 BOX86-Viasat-Usage-NOVEMBER-2019.ots Now if all this stuff works when I boot it in the morning I will begin putting things back. Again thanks to all ... -- Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-09 07:52, Bob Goodwin wrote: > > On 2019-12-08 18:45, Ed Greshko wrote: >> OK, so your nfs-server is now starting. >> >> So, you should be able to fix things up now they way you want. >> >> Thanks, Samuel for catching that. > > . > > I thank you both, > Welcome One more thing. Based on what commands were given to get this working I wonder if you didn't have a typo earlier when you created the directory. I would do an ls / to make sure you don't have a directory with a bad name. As well as ls /nfs4exports again to make sure you don't have directories you're not expecting. Such as "home1". -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-08 18:45, Ed Greshko wrote: OK, so your nfs-server is now starting. So, you should be able to fix things up now they way you want. Thanks, Samuel for catching that. . I thank you both, Bob -- Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-09 07:14, Bob Goodwin wrote: > > On 2019-12-08 17:56, Ed Greshko wrote: >> That is extremely ODD. There should be no mention of /nfs4exports/home/bobg. >> >> I don't know why that shows up. >> >> But, can you post the contents of your "/etc/fstab"? > > . > > [root@NFS-Server bobg]# cat /etc/fstab > > OK, never mind. Based on what I'd seen, before Samuel caught the issue, I was concerned you were following instruction from a page which was showing configurations for "bind" mounts. -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-09 07:30, Bob Goodwin wrote: > > On 2019-12-08 18:03, Samuel Sieb wrote: >> >> He might not have tried starting nfs again after changing the file. That >> directory was in the exports file earlier. >> ___ > > . > > Crrrect, I did nothing more than he asked ... But restarting it changes the > result: > > > [root@NFS-Server bobg]# systemctl status nfs-server > ● nfs-server.service - NFS server and services > Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; > vendor preset: disa> > Drop-In: /run/systemd/generator/nfs-server.service.d > └─order-with-mounts.conf > Active: active (exited) since Sun 2019-12-08 18:22:18 EST; 9s ago > Process: 14041 ExecStartPre=/usr/sbin/exportfs -r (code=exited, > status=0/SUCCESS) > Process: 14042 ExecStart=/usr/sbin/rpc.nfsd (code=exited, status=0/SUCCESS) > Process: 14055 ExecStart=/bin/sh -c if systemctl -q is-active gssproxy; > then systemctl re> > Main PID: 14055 (code=exited, status=0/SUCCESS) > CPU: 52ms > > Dec 08 18:22:17 NFS-Server systemd[1]: Starting NFS server and services... > Dec 08 18:22:18 NFS-Server systemd[1]: Started NFS server and services. > lines 1-13/13 (END) > > > OK, so your nfs-server is now starting. So, you should be able to fix things up now they way you want. Thanks, Samuel for catching that. -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-08 18:03, Samuel Sieb wrote: He might not have tried starting nfs again after changing the file. That directory was in the exports file earlier. ___ . Crrrect, I did nothing more than he asked ... But restarting it changes the result: [root@NFS-Server bobg]# systemctl status nfs-server ● nfs-server.service - NFS server and services Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disa> Drop-In: /run/systemd/generator/nfs-server.service.d └─order-with-mounts.conf Active: active (exited) since Sun 2019-12-08 18:22:18 EST; 9s ago Process: 14041 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS) Process: 14042 ExecStart=/usr/sbin/rpc.nfsd (code=exited, status=0/SUCCESS) Process: 14055 ExecStart=/bin/sh -c if systemctl -q is-active gssproxy; then systemctl re> Main PID: 14055 (code=exited, status=0/SUCCESS) CPU: 52ms Dec 08 18:22:17 NFS-Server systemd[1]: Starting NFS server and services... Dec 08 18:22:18 NFS-Server systemd[1]: Started NFS server and services. lines 1-13/13 (END) -- Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-08 17:56, Ed Greshko wrote: That is extremely ODD. There should be no mention of /nfs4exports/home/bobg. I don't know why that shows up. But, can you post the contents of your "/etc/fstab"? . [root@NFS-Server bobg]# cat /etc/fstab # # /etc/fstab # Created by anaconda on Thu Dec 5 11:06:09 2019 # # Accessible filesystems, by reference, are maintained under '/dev/disk/'. # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info. # # After editing this file, run 'systemctl daemon-reload' to update systemd # units generated from this file. # /dev/mapper/fedora_localhost--live-root / ext4 defaults 1 1 UUID=8520e830-f869-4844-b29a-e0f02c39597b /boot ext4 defaults 1 2 /dev/mapper/fedora_localhost--live-home /home ext4 defaults 1 2 /dev/mapper/fedora_localhost--live-swap none swap defaults 0 0 [root@Workstation-1 /]# cat /etc/fstab # # /etc/fstab # Created by anaconda on Sat Nov 9 15:45:07 2019 # # Accessible filesystems, by reference, are maintained under '/dev/disk/'. # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info. # # After editing this file, run '' to update systemd # units generated from this file. # UUID=14dbd009-480a-48d1-9f45-a559ace50eda / ext4 defaults 1 1 UUID=8c8e7f0d-b772-4126-b437-6adf27abad99 /boot ext4 defaults 1 2 UUID=489E-FD83 /boot/efi vfat umask=0077,shortname=winnt 0 2 UUID=3f40f054-b5a2-4b08-96b6-25d17060f163 /home ext4 defaults 1 2 UUID=c8136f7f-651e-4696-a359-aa2c39f30522 none swap defaults 0 0 //192.168.2.8/smbBOX48 /mnt/box48/ cifs defaults,password= 0 0 192.168.2.128:/home /media/nfs nfs4 rw,soft,intr,fg,comment=systemd.automount 0 0 192.168.2.128:/nfs4exports/home /media/nfs nfs4 rw,soft,intr,fg,comment=systemd.automou nt 0 0 -- Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 12/8/19 2:56 PM, Ed Greshko wrote: On 2019-12-09 06:50, Bob Goodwin wrote: [root@NFS-Server bobg]# cat /etc/exports /nfs4exports/home 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) [root@NFS-Server bobg]# systemctl status nfs-server ● nfs-server.service - NFS server and services Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disa> Drop-In: /run/systemd/generator/nfs-server.service.d └─order-with-mounts.conf Active: failed (Result: exit-code) since Sun 2019-12-08 13:15:14 EST; 4h 25min ago Process: 13238 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=1/FAILURE) Process: 13239 ExecStopPost=/usr/sbin/exportfs -au (code=exited, status=0/SUCCESS) Process: 13240 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCESS) CPU: 13ms Dec 08 13:15:14 NFS-Server systemd[1]: Starting NFS server and services... Dec 08 13:15:14 NFS-Server exportfs[13238]: exportfs: Failed to stat /nfs4exports/home/bobg> That is extremely ODD. There should be no mention of /nfs4exports/home/bobg. I don't know why that shows up. He might not have tried starting nfs again after changing the file. That directory was in the exports file earlier. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-09 06:50, Bob Goodwin wrote: > > On 2019-12-08 15:19, Ed Greshko wrote: >> The command "/usr/sbin/exportfs -r" is still failing. >> >> Building on what others have already said. >> >> Execute the following commands one by one and then post the results. >> >> mv /etc/exports /etc/exports-HOLD >> mkdir -p /nfs4exports/home >> touch /nfs4exports/home/a-file >> echo "/nfs4exports/home >> 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check)" > >> /etc/exports >> exportfs -r > > . > > I'm not certain what to post but: Well, I'm asking if after the "exportfs -r" command was there any error? Or, any error prior to that? > > [root@NFS-Server bobg]# cat /etc/exports > /nfs4exports/home > 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) > > > [root@NFS-Server bobg]# systemctl status nfs-server > ● nfs-server.service - NFS server and services > Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; > vendor preset: disa> > Drop-In: /run/systemd/generator/nfs-server.service.d > └─order-with-mounts.conf > Active: failed (Result: exit-code) since Sun 2019-12-08 13:15:14 EST; 4h > 25min ago > Process: 13238 ExecStartPre=/usr/sbin/exportfs -r (code=exited, > status=1/FAILURE) > Process: 13239 ExecStopPost=/usr/sbin/exportfs -au (code=exited, > status=0/SUCCESS) > Process: 13240 ExecStopPost=/usr/sbin/exportfs -f (code=exited, > status=0/SUCCESS) > CPU: 13ms > > Dec 08 13:15:14 NFS-Server systemd[1]: Starting NFS server and services... > Dec 08 13:15:14 NFS-Server exportfs[13238]: exportfs: Failed to stat > /nfs4exports/home/bobg> That is extremely ODD. There should be no mention of /nfs4exports/home/bobg. I don't know why that shows up. But, can you post the contents of your "/etc/fstab"? -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-08 15:19, Ed Greshko wrote: The command "/usr/sbin/exportfs -r" is still failing. Building on what others have already said. Execute the following commands one by one and then post the results. mv /etc/exports /etc/exports-HOLD mkdir -p /nfs4exports/home touch /nfs4exports/home/a-file echo "/nfs4exports/home 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check)" > /etc/exports exportfs -r . I'm not certain what to post but: [root@NFS-Server bobg]# cat /etc/exports /nfs4exports/home 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) [root@NFS-Server bobg]# systemctl status nfs-server ● nfs-server.service - NFS server and services Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disa> Drop-In: /run/systemd/generator/nfs-server.service.d └─order-with-mounts.conf Active: failed (Result: exit-code) since Sun 2019-12-08 13:15:14 EST; 4h 25min ago Process: 13238 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=1/FAILURE) Process: 13239 ExecStopPost=/usr/sbin/exportfs -au (code=exited, status=0/SUCCESS) Process: 13240 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCESS) CPU: 13ms Dec 08 13:15:14 NFS-Server systemd[1]: Starting NFS server and services... Dec 08 13:15:14 NFS-Server exportfs[13238]: exportfs: Failed to stat /nfs4exports/home/bobg> Dec 08 13:15:14 NFS-Server systemd[1]: nfs-server.service: Control process exited, code=exi> Dec 08 13:15:14 NFS-Server systemd[1]: nfs-server.service: Failed with result 'exit-code'. Dec 08 13:15:14 NFS-Server systemd[1]: Stopped NFS server and services. -- Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 12/8/19 10:25 AM, Bob Goodwin wrote: The "/home/Media" part is what I need for my /etc/exports file, where, how, do I find that? Perhaps /home/bobg/Public? none of that matters if NFS does not run which is what I am seeing ... NFS will not run until you have a correct exports file, so yes, it does matter and is currently the most important part. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-09 00:11, Bob Goodwin wrote: > > On 2019-12-07 20:11, Bob Goodwin wrote: >> [root@NFS-Server bobg]# firewall-cmd --zone=public --add-service=mountd >> success >> [root@NFS-Server bobg]# etc]# firewall-cmd --zone=public >> --add-service=rpc-bind >> bash: etc]#: command not found >> >> Then this step fails? > > . > > I am still unable to get the NFS server to run - I do not know where you are at in the process based on other messages. So, let's take it from this point > > [root@NFS-Server bobg]# systemctl status nfs-server > ● nfs-server.service - NFS server and services > Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; > vendor preset: disa> > Drop-In: /run/systemd/generator/nfs-server.service.d > └─order-with-mounts.conf > Active: failed (Result: exit-code) since Sun 2019-12-08 10:07:27 EST; 1min > 43s ago > Process: 12686 ExecStartPre=/usr/sbin/exportfs -r (code=exited, > status=1/FAILURE) > That is telling you what command has failed. The command "/usr/sbin/exportfs -r" is still failing. Building on what others have already said. Execute the following commands one by one and then post the results. mv /etc/exports /etc/exports-HOLD mkdir -p /nfs4exports/home touch /nfs4exports/home/a-file echo "/nfs4exports/home 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check)" > /etc/exports exportfs -r -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On Sun, 2019-12-08 at 13:25 -0500, Bob Goodwin wrote: > On 2019-12-08 12:42, Patrick O'Callaghan wrote: > > On Sun, 2019-12-08 at 11:35 -0500, Bob Goodwin wrote: > > > I guess you mean exports? > > > > > > [root@NFS-Server bobg]# cat /etc/exports > > > # /nfs4exports/home > > > 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) > > Is that the actual file? If so, why is there a '#' at the start of the > > first line, and why is it split into two lines (unless that's an > > artefact of your email client)? > > . > > Why the #'s. to comment out the lines and limit it to just whatever was > uncommitted that I was trying at tat time. just a random collection of > things tried ... It's not really practical to debug what's going on unless you show what is actually in the /etc/exports file when you get the failure. And it's *very* important to show it as it really is, without any line breaks introduced by your mailer. > > This is my file: > > $ cat /etc/exports > > /home/Media 192.168.0.0/16(ro,all_squash,insecure) > > /home/poc/Stuff 192.168.122.0/24(rw) > > > > poc > > . > > The "/home/Media" part is what I need for my /etc/exports file, where, > how, do I find that? Perhaps /home/bobg/Public? none of that matters if > NFS does not run which is what I am seeing ... You don't "find" it. It's the server directory you want to access from the client(s). That just happens to be one I use. It could in principle be any directory that exists on the server. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-08 12:15, Tim via users wrote: On Sun, 2019-12-08 at 11:11 -0500, Bob Goodwin wrote: I am still unable to get the NFS server to run - [root@NFS-Server bobg]# systemctl status nfs-server ● nfs-server.service - NFS server and services Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disa> Drop-In: /run/systemd/generator/nfs-server.service.d └─order-with-mounts.conf You might want to look at that file: /run/systemd/generator/nfs-server.service.d/order-with-mounts.conf . [root@NFS-Server bobg]# cat /run/systemd/generator/nfs-server.service.d/order-with-mounts.conf # Automatically generated by nfs-server-generator [Unit] RequiresMountsFor=/nfs4exports/home I'm not familiar with any of that? Active: failed (Result: exit-code) since Sun 2019-12-08 10:07:27 EST; 1min 43s ago Process: 12686 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=1/FAILURE) Process: 12687 ExecStopPost=/usr/sbin/exportfs -au (code=exited, status=0/SUCCESS) Process: 12688 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCESS) CPU: 15ms Look at man exportfs: The -r option is about re-exporting directories, -au would be un-exporting all exported directories, the -f is about flushing the export tables. It also mentions other files used by the system: /var/lib/nfs/etab and /var/lib/nfs/rmtab (you could check if they're mangled, and possibly just erase them to wipe your slate clean). It does look like the restart ultimately succeeded. I've tried varying the exports - [root@NFS-Server bobg]# cat /etc/exports # /nfs4exports/home 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) # /nfs4exports/ 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) # /home/egreshko 192.168.0.0/16(rw,sync,insecure,no_root_squash,no_s Above is an example provided by Ed, below is a similar line with my address, just a trial to see if NFS might start with that in place, it did not. /home/bobg 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) You're absolutely sure those filepaths are correct? And do you have line breaks in the file, as above? I've never seen an exports file like that. I'm sure you don't have Ed's egreshko directory on your system. I'd try a simple test case, leave the home directory alone for a while, simplify your exports file. mkdir /testing touch /testing/testfile (even better make a testfile that has some content you can read) And inside your /etc/exports file, something simple like: /testing 192.168.0.0/16(rw,sync) That would allow anything with a 192.168 prefixed LAN IP address to connect. Your LAN is using those addresses? You'll need to allow NFS traffic through your firewalls, on the server and the clients. If you're on a safe network, you can disable your firewalls, otherwise enable the appropriate ports on your firewalls (ultimately, this is what you want to do). On my computer, I can test the server on itself. I can use NFS to access its own exports. That allows me to test the server, if a client is acting up. When you have a working NFS server, you can make any changes to your /etc/exports file take effect with this command, instead of simply restarting the NFS server: exportfs -ra After each change to exports I did systemctl restart nfs-server without success ... [root@NFS-Server bobg]# systemctl restart nfs-server Job for nfs-server.service canceled. What do you get from: systemctl stop nfs-server Hopefully it stops successfully. And, afterwards: systemctl status nfs-server And you should get a successful result about it being halted. You could try reversing the direction of your tests, share something from the other PC, instead. See if you get different results. Depending on what scheme you're using, to access something over NFS, your numerical User ID will have to be the same on the server and client (it's numerical numbers it cared about, not the username). Though world-readable directories and files shouldn't face that restriction. I'm running a mixed LAN with CentOS and Fedora, so my system may have some differences from a Fedora only LAN. -- Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-08 12:42, Patrick O'Callaghan wrote: On Sun, 2019-12-08 at 11:35 -0500, Bob Goodwin wrote: I guess you mean exports? [root@NFS-Server bobg]# cat /etc/exports # /nfs4exports/home 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) Is that the actual file? If so, why is there a '#' at the start of the first line, and why is it split into two lines (unless that's an artefact of your email client)? . Why the #'s. to comment out the lines and limit it to just whatever was uncommitted that I was trying at tat time. just a random collection of things tried ... This is my file: $ cat /etc/exports /home/Media 192.168.0.0/16(ro,all_squash,insecure) /home/poc/Stuff 192.168.122.0/24(rw) poc . The "/home/Media" part is what I need for my /etc/exports file, where, how, do I find that? Perhaps /home/bobg/Public? none of that matters if NFS does not run which is what I am seeing ... ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org -- Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On Sun, 2019-12-08 at 11:35 -0500, Bob Goodwin wrote: > I guess you mean exports? > > [root@NFS-Server bobg]# cat /etc/exports > # /nfs4exports/home > 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) Is that the actual file? If so, why is there a '#' at the start of the first line, and why is it split into two lines (unless that's an artefact of your email client)? This is my file: $ cat /etc/exports /home/Media 192.168.0.0/16(ro,all_squash,insecure) /home/poc/Stuff 192.168.122.0/24(rw) poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On Sun, 2019-12-08 at 11:11 -0500, Bob Goodwin wrote: > I am still unable to get the NFS server to run - > > [root@NFS-Server bobg]# systemctl status nfs-server > ● nfs-server.service - NFS server and services > Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; > vendor preset: disa> >Drop-In: /run/systemd/generator/nfs-server.service.d > └─order-with-mounts.conf You might want to look at that file: /run/systemd/generator/nfs-server.service.d/order-with-mounts.conf > Active: failed (Result: exit-code) since Sun 2019-12-08 10:07:27 > EST; 1min 43s ago >Process: 12686 ExecStartPre=/usr/sbin/exportfs -r (code=exited, > status=1/FAILURE) >Process: 12687 ExecStopPost=/usr/sbin/exportfs -au (code=exited, > status=0/SUCCESS) >Process: 12688 ExecStopPost=/usr/sbin/exportfs -f (code=exited, > status=0/SUCCESS) >CPU: 15ms Look at man exportfs: The -r option is about re-exporting directories, -au would be un-exporting all exported directories, the -f is about flushing the export tables. It also mentions other files used by the system: /var/lib/nfs/etab and /var/lib/nfs/rmtab (you could check if they're mangled, and possibly just erase them to wipe your slate clean). It does look like the restart ultimately succeeded. > I've tried varying the exports - > > [root@NFS-Server bobg]# cat /etc/exports > # /nfs4exports/home > 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) > > # /nfs4exports/ > 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) > > # /home/egreshko > 192.168.0.0/16(rw,sync,insecure,no_root_squash,no_subtree_check) > /home/egreshko > 2001:B030:112F:::/56(rw,sync,insecure,no_root_squash,no_subtree_check) > > /home/bobg > 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) You're absolutely sure those filepaths are correct? And do you have line breaks in the file, as above? I've never seen an exports file like that. I'm sure you don't have Ed's egreshko directory on your system. I'd try a simple test case, leave the home directory alone for a while, simplify your exports file. mkdir /testing touch /testing/testfile (even better make a testfile that has some content you can read) And inside your /etc/exports file, something simple like: /testing 192.168.0.0/16(rw,sync) That would allow anything with a 192.168 prefixed LAN IP address to connect. Your LAN is using those addresses? You'll need to allow NFS traffic through your firewalls, on the server and the clients. If you're on a safe network, you can disable your firewalls, otherwise enable the appropriate ports on your firewalls (ultimately, this is what you want to do). On my computer, I can test the server on itself. I can use NFS to access its own exports. That allows me to test the server, if a client is acting up. When you have a working NFS server, you can make any changes to your /etc/exports file take effect with this command, instead of simply restarting the NFS server: exportfs -ra > After each change to exports I did systemctl restart nfs-server > without success ... > > [root@NFS-Server bobg]# systemctl restart nfs-server > Job for nfs-server.service canceled. What do you get from: systemctl stop nfs-server Hopefully it stops successfully. And, afterwards: systemctl status nfs-server And you should get a successful result about it being halted. You could try reversing the direction of your tests, share something from the other PC, instead. See if you get different results. Depending on what scheme you're using, to access something over NFS, your numerical User ID will have to be the same on the server and client (it's numerical numbers it cared about, not the username). Though world-readable directories and files shouldn't face that restriction. I'm running a mixed LAN with CentOS and Fedora, so my system may have some differences from a Fedora only LAN. -- uname -rsvp Linux 3.10.0-1062.9.1.el7.x86_64 #1 SMP Fri Dec 6 15:49:49 UTC 2019 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-08 01:59, Samuel Sieb wrote: Right, you still haven't answered what is possibly the most important question. Where is the directory that you want to share located on your server filesystem? You can't just copy and paste an exports file from someone else. . I guess you mean exports? [root@NFS-Server bobg]# cat /etc/exports # /nfs4exports/home 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) # /nfs4exports/ 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) # /home/egreshko 192.168.0.0/16(rw,sync,insecure,no_root_squash,no_subtree_check) /home/egreshko 2001:B030:112F:::/56(rw,sync,insecure,no_root_squash,no_subtree_check) /home/bobg 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) # /nfs4exports/data 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) I lost all the data I had in NFS and can.t recover it, the replacement drive no longer gets up to operating speed, Bob . -- Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-08 01:59, Samuel Sieb wrote: Right, you still haven't answered what is possibly the most important question. Where is the directory that you want to share located on your server filesystem? You can't just copy and paste an exports file from someone else. . I guess you mean exports? [root@NFS-Server bobg]# cat /etc/exports # /nfs4exports/home 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) # /nfs4exports/ 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) # /home/egreshko 192.168.0.0/16(rw,sync,insecure,no_root_squash,no_subtree_check) /home/egreshko 2001:B030:112F:::/56(rw,sync,insecure,no_root_squash,no_subtree_check) /home/bobg 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) # /nfs4exports/data 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) I lost all the data I had in NFS and can.t recover it, the replacement drive no longer gets up to operating speed, Bob . -- Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-07 20:11, Bob Goodwin wrote: [root@NFS-Server bobg]# firewall-cmd --zone=public --add-service=mountd success [root@NFS-Server bobg]# etc]# firewall-cmd --zone=public --add-service=rpc-bind bash: etc]#: command not found Then this step fails? . I am still unable to get the NFS server to run - [root@NFS-Server bobg]# systemctl status nfs-server ● nfs-server.service - NFS server and services Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disa> Drop-In: /run/systemd/generator/nfs-server.service.d └─order-with-mounts.conf Active: failed (Result: exit-code) since Sun 2019-12-08 10:07:27 EST; 1min 43s ago Process: 12686 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=1/FAILURE) Process: 12687 ExecStopPost=/usr/sbin/exportfs -au (code=exited, status=0/SUCCESS) Process: 12688 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCESS) CPU: 15ms I've tried varying the exports - [root@NFS-Server bobg]# cat /etc/exports # /nfs4exports/home 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) # /nfs4exports/ 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) # /home/egreshko 192.168.0.0/16(rw,sync,insecure,no_root_squash,no_subtree_check) /home/egreshko 2001:B030:112F:::/56(rw,sync,insecure,no_root_squash,no_subtree_check) /home/bobg 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) After each change to exports I did systemctl restart nfs-server without success ... [root@NFS-Server bobg]# systemctl restart nfs-server Job for nfs-server.service canceled. i am still stuck ... Bob -- Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-08 14:59, Samuel Sieb wrote: > On 12/7/19 6:10 PM, Bob Goodwin wrote: >> [root@NFS-Server bobg]# exportfs -a >> exportfs: Failed to stat /nfs4exports/home: No such file or directory >> >> Ok, I have been able to get this far before another failure. It may be time >> to fix my /etc/exports. > > Right, you still haven't answered what is possibly the most important > question. Where is the directory that you want to share located on your > server filesystem? You can't just copy and paste an exports file from > someone else. I think he may be suffering from "typos". Note that in a previous post he mentioned his exports file contained: /nfs4exports/home1 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) I suspect he created the directory /nfs4exports/home1 and then subsequently edited his exports file and removed the "1". -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 12/7/19 6:10 PM, Bob Goodwin wrote: [root@NFS-Server bobg]# exportfs -a exportfs: Failed to stat /nfs4exports/home: No such file or directory Ok, I have been able to get this far before another failure. It may be time to fix my /etc/exports. Right, you still haven't answered what is possibly the most important question. Where is the directory that you want to share located on your server filesystem? You can't just copy and paste an exports file from someone else. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-07 18:55, Ed Greshko wrote: [root@f31k ~]# cat /etc/exports /home/egreshko 192.168.0.0/16(rw,sync,insecure,no_root_squash,no_subtree_check) /home/egreshko 2001:B030:112F:::/56(rw,sync,insecure,no_root_squash,no_subtree_check) [root@f31k ~]# exportfs -a . [root@NFS-Server bobg]# exportfs -a exportfs: Failed to stat /nfs4exports/home: No such file or directory Ok, I have been able to get this far before another failure. It may be time to fix my /etc/exports. [root@NFS-Server bobg]# exportfs -a exportfs: Failed to stat /nfs4exports/home: No such file or directory I will have to come back to this point in the morning and will report then. The help is very much appreciated, -- Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-08 09:11, Bob Goodwin wrote: > [root@NFS-Server bobg]# etc]# firewall-cmd --zone=public > --add-service=rpc-bind > bash: etc]#: command not found > > Then this step fails? You have copied/pasted in error. You pasted "etc]# firewall-cmd --zone=public --add-service=rpc-bind " You want firewall-cmd --zone=public --add-service=rpc-bind -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-07 18:55, Ed Greshko wrote: So.. [root@f31k etc]# firewall-cmd --zone=public --add-service=nfs success [root@f31k etc]# firewall-cmd --zone=public --add-service=mountd success [root@f31k etc]# firewall-cmd --zone=public --add-service=rpc-bind . Followed you to here: [root@NFS-Server bobg]# [root@NFS-Server bobg]# firewall-cmd --zone=public --add-service=nfs success [root@NFS-Server bobg]# firewall-cmd --zone=public --add-service=mountd success [root@NFS-Server bobg]# etc]# firewall-cmd --zone=public --add-service=rpc-bind bash: etc]#: command not found Then this step fails? -- Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 12/7/19 2:54 PM, Bob Goodwin wrote: On 2019-12-07 16:17, Samuel Sieb wrote: On 12/7/19 1:13 PM, Bob Goodwin wrote: Well it appears there must be something wrong with my server files installation. /nfs4exports does not lead to /home1 or /home? nfs4exports is part of /etc/exports: Being in the /etc/exports file doesn't make a directory exist. Where is the directory that you want to share located in the server filesystem? Are there any messages in the log from NFS? Try running "systemctl status nfs". . [root@NFS-Server bobg]# systemctl status nfs Unit nfs.service could not be found. Sorry, on my server (F30) nfs appears to be an alias. Just run "systemctl status nfs-server" instead. [root@NFS-Server bobg]# service rpcbind start Redirecting to /bin/systemctl start rpcbind.service [root@NFS-Server bobg]# service nfs-server start Redirecting to /bin/systemctl start nfs-server.service Job for nfs-server.service canceled. The "service" command is obsolete and shouldn't be used unless you have something really old running. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-08 07:17, Bob Goodwin wrote: > > On 2019-12-07 17:19, Patrick O'Callaghan wrote: >> Note that the GUI is not 100% reliable, i.e. it can misrepresent what >> is actually configured. >> >> Seehttps://bugzilla.redhat.com/show_bug.cgi?id=1773273 >> >> Also, try "firewall-cmd --get-active-zones" and "... --get-default- >> zone" to make sure you're looking at the right thing. >> >> poc > > . > > Did this: > > [root@NFS-Server bobg]# firewall-cmd --get-active-zones > public > interfaces: enp1s0 > > Dunno what to do with "... --get-default-zone" > > However enp1s0 connects to my LAN so I assume that is what is needed? > > I know I am late to the party. I have a new VM install of F31. So, with that in mind "f31K" is the server and "meimei" is the client. *BEFORE* [root@f31k etc]# firewall-cmd --get-active-zones public interfaces: enp1s0 [root@f31k etc]# firewall-cmd --info-zone=public public (active) target: default icmp-block-inversion: no interfaces: enp1s0 sources: services: dhcpv6-client mdns ssh ports: protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: I have no services enabled or running other than the default. (I will not use nfs3) So.. [root@f31k etc]# firewall-cmd --zone=public --add-service=nfs success [root@f31k etc]# firewall-cmd --zone=public --add-service=mountd success [root@f31k etc]# firewall-cmd --zone=public --add-service=rpc-bind success [root@f31k etc]# firewall-cmd --runtime-to-permanent success [root@f31k etc]# firewall-cmd --reload success *NOW AFTER* [root@f31k ~]# firewall-cmd --info-zone=public public (active) target: default icmp-block-inversion: no interfaces: enp1s0 sources: services: dhcpv6-client mdns mountd nfs rpc-bind ssh ports: protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: I entered what I need in "exports". So, here we go [root@f31k ~]# cat /etc/exports /home/egreshko 192.168.0.0/16(rw,sync,insecure,no_root_squash,no_subtree_check) /home/egreshko 2001:B030:112F:::/56(rw,sync,insecure,no_root_squash,no_subtree_check) [root@f31k ~]# exportfs -a [root@f31k ~]# Enable and start the nfs-server in one go. This will enable any other services needed by nfs-server [root@f31k ~]# systemctl --now enable nfs-server Created symlink /etc/systemd/system/multi-user.target.wants/nfs-server.service → /usr/lib/systemd/system/nfs-server.service. Then on the client. [root@meimei ~]# showmount -e f31k Export list for f31k: /home/egreshko 2001:B030:112F:::/56,192.168.0.0/16 [root@meimei ~]# mount f31k:/home/egreshko /mnt Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service → /usr/lib/systemd/system/rpc-statd.service. [root@meimei ~]# And. [root@meimei ~]# mount f31k:/home/egreshko /mnt [root@meimei ~]# ls /mnt Desktop Documents Downloads flash Music Pictures Public Templates Videos Done -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-07 17:19, Patrick O'Callaghan wrote: Note that the GUI is not 100% reliable, i.e. it can misrepresent what is actually configured. Seehttps://bugzilla.redhat.com/show_bug.cgi?id=1773273 Also, try "firewall-cmd --get-active-zones" and "... --get-default- zone" to make sure you're looking at the right thing. poc . Did this: [root@NFS-Server bobg]# firewall-cmd --get-active-zones public interfaces: enp1s0 Dunno what to do with "... --get-default-zone" However enp1s0 connects to my LAN so I assume that is what is needed? -- Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-07 16:17, Samuel Sieb wrote: On 12/7/19 1:13 PM, Bob Goodwin wrote: Well it appears there must be something wrong with my server files installation. /nfs4exports does not lead to /home1 or /home? nfs4exports is part of /etc/exports: Being in the /etc/exports file doesn't make a directory exist. Where is the directory that you want to share located in the server filesystem? Are there any messages in the log from NFS? Try running "systemctl status nfs". . [root@NFS-Server bobg]# systemctl status nfs Unit nfs.service could not be found. So I did these steps again: [root@NFS-Server bobg]# systemctl enable rpcbind [root@NFS-Server bobg]# systemctl enable nfs-server [root@NFS-Server bobg]# service rpcbind start Redirecting to /bin/systemctl start rpcbind.service [root@NFS-Server bobg]# service nfs-server start Redirecting to /bin/systemctl start nfs-server.service Job for nfs-server.service canceled. Looks like something is wrong here, job cancelled? [root@NFS-Server bobg]# systemctl status nfs Unit nfs.service could not be found -- Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On Sat, 2019-12-07 at 13:58 -0500, Bob Goodwin wrote: > On 2019-12-07 13:14, Patrick O'Callaghan wrote: > > You're not seeing anything that says "allow NFS", which means that it's > > blocked. The services line shows what should be let through. > > . > > Well I am lost in the Firewalld GUI with connections and zones, > permanent seems obvious, but I will have to learn more there. However > I've changed nothing in Firewalld in this computer and it did work > through the firewall just a few days ago, as I said I tried stopping it > and setting selinux to permissive, neither made any difference. Note that the GUI is not 100% reliable, i.e. it can misrepresent what is actually configured. See https://bugzilla.redhat.com/show_bug.cgi?id=1773273 Also, try "firewall-cmd --get-active-zones" and "... --get-default- zone" to make sure you're looking at the right thing. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 12/7/19 1:13 PM, Bob Goodwin wrote: Well it appears there must be something wrong with my server files installation. /nfs4exports does not lead to /home1 or /home? nfs4exports is part of /etc/exports: Being in the /etc/exports file doesn't make a directory exist. Where is the directory that you want to share located in the server filesystem? Are there any messages in the log from NFS? Try running "systemctl status nfs". ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-07 15:19, Samuel Sieb wrote: [bobg@Workstation-1 ~]$ showmount -e 192.168.2.128 clnt_create: RPC: Unable to receive Is that the IP address of the NFS server or Workstation-1? . 192.168.2.128 is the nfs server. As Tim said, this should be: mount 192.168.2.128:/nfs4exports/home1 /media/nfs . Well it appears there must be something wrong with my server files installation. /nfs4exports does not lead to /home1 or /home? nfs4exports is part of /etc/exports: [root@NFS-Server bobg]# cat /etc/exports /nfs4exports/home1 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) /nfs4exports/data 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) U followed an admin. Guide to installing NFS and this is what resulted. I think something went wrong and I may have to start over ... -- Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 12/7/19 8:30 AM, Bob Goodwin wrote: [bobg@Workstation-1 ~]$ showmount -e 192.168.2.128 clnt_create: RPC: Unable to receive Is that the IP address of the NFS server or Workstation-1? This computer's fstab has the line: 192.168.2.128:home1 /media/nfs nfs4 rw,soft,intr,fg,comment=systemd.automount 0 0 And at the server exports is: [bobg@NFS-Server ~]$ cat /etc/exports /nfs4exports/home1 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) My mount command: [root@Workstation-1 bobg]# mount 192.168.2.128:home1 /media/nfs As Tim said, this should be: mount 192.168.2.128:/nfs4exports/home1 /media/nfs Any firewall issues would be on the server, not the client side. On the server you could try running "systemctl firewalld stop" to test that. I don't know if NFS is default enabled, but probably not. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-07 14:09, Joe Zeff wrote: Were you getting SELinux alerts? If not, it wasn't the issue, so why did you think setting it to permissive would help? . I did not think it would help but there's always someone who suggests stopping selinux. I never see any problems with it since most of the things are in the realm of the ordinary. -- Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-07 12:51, Tim Evans wrote: Wouldn't this be? mount 192.168.2.128:/nfs4exports/home1 /media/nfs . No, that doesn't connect either but I can't make any sense of my server files, think I have something wrong there ... the home1 looks like the problem area. -- Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 12/07/2019 11:58 AM, Bob Goodwin wrote: Well I am lost in the Firewalld GUI with connections and zones, permanent seems obvious, but I will have to learn more there. However I've changed nothing in Firewalld in this computer and it did work through the firewall just a few days ago, as I said I tried stopping it and setting selinux to permissive, neither made any difference. Were you getting SELinux alerts? If not, it wasn't the issue, so why did you think setting it to permissive would help? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-07 13:14, Patrick O'Callaghan wrote: You're not seeing anything that says "allow NFS", which means that it's blocked. The services line shows what should be let through. . Well I am lost in the Firewalld GUI with connections and zones, permanent seems obvious, but I will have to learn more there. However I've changed nothing in Firewalld in this computer and it did work through the firewall just a few days ago, as I said I tried stopping it and setting selinux to permissive, neither made any difference. -- Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On Sat, 2019-12-07 at 12:20 -0500, Bob Goodwin wrote: > I'm not certain what to look for but I don't see anything I recognize > that says"no NFS" You're not seeing anything that says "allow NFS", which means that it's blocked. The services line shows what should be let through. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 12/7/19 11:30 AM, Bob Goodwin wrote: This computer's fstab has the line: 192.168.2.128:home1 /media/nfs nfs4 rw,soft,intr,fg,comment=systemd.automount 0 0 And at the server exports is: [bobg@NFS-Server ~]$ cat /etc/exports /nfs4exports/home1 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) /nfs4exports/data 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) My mount command: [root@Workstation-1 bobg]# mount 192.168.2.128:home1 /media/nfs Wouldn't this be? mount 192.168.2.128:/nfs4exports/home1 /media/nfs -- Tim Evans |5 Chestnut Court 443-394-3864|Owings Mills, MD 21117 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On 2019-12-07 12:02, Patrick O'Callaghan wrote: Could be a firewall issue. Check the output of: $ firewall-cmd --list-all IIRC it should include nfs, nfs3, mountd and rpc-bind. poc I should have said I tried stopping the firewall and selinux individually. I am seeing the following: [root@Workstation-1 bobg]# firewall-cmd --list-all public (active) target: default icmp-block-inversion: no interfaces: eno1 sources: services: dhcpv6-client mdns ssh ports: protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: And - [root@NFS-Server bobg]# firewall-cmd --list-all public (active) target: default icmp-block-inversion: no interfaces: enp1s0 sources: services: dhcpv6-client mdns ssh ports: protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: I'm not certain what to look for but I don't see anything I recognize that says"no NFS" -- Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: NFS not connecting -
On Sat, 2019-12-07 at 11:30 -0500, Bob Goodwin wrote: > . > > Due to failure of a 3TB Seagate hard drive (DOM 28 April 2019) i am > rebuilding the server again, this time with no backup to refer to. I am > trying to work from references found searching google, my notes were in > the server. I think what I have should work even if not optimal but /am > unable to get connected from this client which has always worked with > the NFS. > / > > /I have tried the various checks/rests and so far the only thing that > looks significant Is: > / > > [bobg@Workstation-1 ~]$ showmount -e 192.168.2.128 > clnt_create: RPC: Unable to receive > > This computer's fstab has the line: 192.168.2.128:home1 /media/nfs > nfs4 rw,soft,intr,fg,comment=systemd.automount 0 0 > > And at the server exports is: > > [bobg@NFS-Server ~]$ cat /etc/exports > /nfs4exports/home1 > 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) > > /nfs4exports/data > 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) > > My mount command: [root@Workstation-1 bobg]# mount 192.168.2.128:home1 > /media/nfs > > Also, ssh and sftp both work from this box and from the NFS box, both > are updated Fedora31 systems. i am uncertain of what should be in fstab > and exports but planned on refining that once things work. > > Help, suggestions please? Could be a firewall issue. Check the output of: $ firewall-cmd --list-all IIRC it should include nfs, nfs3, mountd and rpc-bind. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
NFS not connecting -
. Due to failure of a 3TB Seagate hard drive (DOM 28 April 2019) i am rebuilding the server again, this time with no backup to refer to. I am trying to work from references found searching google, my notes were in the server. I think what I have should work even if not optimal but /am unable to get connected from this client which has always worked with the NFS. / /I have tried the various checks/rests and so far the only thing that looks significant Is: / [bobg@Workstation-1 ~]$ showmount -e 192.168.2.128 clnt_create: RPC: Unable to receive This computer's fstab has the line: 192.168.2.128:home1 /media/nfs nfs4 rw,soft,intr,fg,comment=systemd.automount 0 0 And at the server exports is: [bobg@NFS-Server ~]$ cat /etc/exports /nfs4exports/home1 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) /nfs4exports/data 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check) My mount command: [root@Workstation-1 bobg]# mount 192.168.2.128:home1 /media/nfs Also, ssh and sftp both work from this box and from the NFS box, both are updated Fedora31 systems. i am uncertain of what should be in fstab and exports but planned on refining that once things work. Help, suggestions please? Bob -- Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
