Re: update not working correctly
On 12/7/19 9:09 PM, Tim via users wrote: The notion of only rebooting when you really need it has gone right out the window, to be replaced by the Windows-centric thinking that it's easier just to reboot rather than assess whether it's really necessary. Non-technical users don't need to run into weird issues when they do an update and they don't have the understanding to know what caused them or whether rebooting is necessary. For those that do have the technical understanding, there are easy ways to update without rebooting. ___ 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: update not working correctly
On Sat, 2019-12-07 at 09:14 -0500, John Mellor wrote: > As an aside, for some weird reason way beyond what makes sense on a > machine with an inode-based filesystem, the Gnome software tool has > a problem where it almost always wants to reboot to apply the > changes. That's an inconvenience that I assume that the Gnome people > are fixing some day I wouldn't believe that. There's been a hell of a lot of advocacy (that I don't agree with) that you should always reboot after updates. The notion of only rebooting when you really need it has gone right out the window, to be replaced by the Windows-centric thinking that it's easier just to reboot rather than assess whether it's really necessary. -- 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-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: usb thumb drive problem? [CLOSED]
(on Thursday, 12-05-2019, George said...) > From my experience, the drive has already lost or corrupted your data. > You may be able to recover some of the files, but attempts to "repair" > the filesystem risk destroying more data. You can try making a "clone" > of the USB drive using dd, etc. onto a new drive and use repair tools > on the copy. Thank-you, George. I tried finding a USB3 flash stick at the local walmart. (My workstation has USB3 ports as well as USB2 ports. The incremental back-ups are taking a lot of time using the USB2 sticks/ports.) They had USB2 sticks only. Once I've bought USB3 sticks in the right size range, I'll give that a try. I get the impression from the silence on my first question (better testing of the stick) that there is nothing. So I'm tagging this thread "CLOSED". Bill. ___ 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
Re: ASUS VivoBook Pro N705FD Notebook - boots to setup screen every time
On 12/7/19 12:15 AM, Ed Greshko wrote: On 2019-12-07 14:45, S.Bob wrote: I've managed to install Fedora 31 on a new ASUS VivoBook Pro N705FD Notebook. I've run a full dnf update. Every time I boot it boots to the setup screen (the one you see at first boot), then the mouse goes away and it hangs for like 2 minutes. Then it goes to the login screen and the mouse is back. Anyone have any ideas what this could be? how t debug it? I get the same results with Fedora 30 You are saying that after this happens you get to the login screen and can login and used the system, yes? Assuming that is the case, what is the output of systemctl status systemd-firstboot.service # systemctl status systemd-firstboot.service ● systemd-firstboot.service - First Boot Wizard Loaded: loaded (/usr/lib/systemd/system/systemd-firstboot.service; static> Active: inactive (dead) Condition: start condition failed at Sat 2019-12-07 02:52:51 MST; 7h ago └─ ConditionFirstBoot=yes was not met Docs: man:systemd-firstboot(1) Dec 07 02:52:47 F31-Host systemd[1]: Condition check resulted in First Boot > Dec 07 02:52:51 F31-Host systemd[1]: Condition check resulted in First Boot > Dec 07 02:52:51 F31-Host systemd[1]: Condition check resulted in First Boot > ___ 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: update not working correctly
On Sat, 2019-12-07 at 09:14 -0500, John Mellor wrote: > As an aside, for some weird reason way beyond what makes sense on a > machine with an inode-based filesystem, the Gnome software tool has a > problem where it almost always wants to reboot to apply the changes. > That's an inconvenience that I assume that the Gnome people are fixing > some day. I don;t know if there is a bug tracking that more minor issue. Last I heard that was a design choice so I wouldn't expect it to be "fixed". I use KDE and it doesn't affect me, but you can always update from the command line using dnf and avoid this. 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
update not working correctly
I update my desktop machine every few days, normally using the Gnome software tool from the updates tab. This is a fast i7 with a good SSD and 32GB of memory, and it normally boots to login in about 5 seconds. As an aside, for some weird reason way beyond what makes sense on a machine with an inode-based filesystem, the Gnome software tool has a problem where it almost always wants to reboot to apply the changes. That's an inconvenience that I assume that the Gnome people are fixing some day. I don;t know if there is a bug tracking that more minor issue. However, there is a more serious issue. Starting with Fedora 31, there are really good odds that the reboot does a grub hard stop with a message about a corrupt compressed file. I have to reboot manually several times, and eventually it comes up just as if nothing was wrong. This says to me that there is something either incorrectly async in the updater, or there is a missing state check in the update reboot sequence. Is anyone else having this issue? ___ 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: Grub.cfg not updating
On 12/6/19 3:22 PM, Robert McBroom via users wrote: On 12/6/19 5:41 PM, Samuel Sieb wrote: If this is an old install, you might need to update the bootloader bits that are stored in the mbr. It might too old to support BLS. That's why if it's not an EFI system, you should run grub2-install to make sure it's up to date. Updated with the update to f31. It's possible, but I don't think that updating the package updates the parts embedded on the hard drive. There should be some way to check the version from the boot menu to see if the version there matches the installed version. ___ 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
