doktor5000 wrote:You should not need to restart any service on the client, the only one that is required is RPC portmapper and that one is socket-activated.
Would be helpful if you could at least post the fstab entry for this NFS mount. Did you add _netdev as an option to mark it as a remote filesystem ?
192.xxx.xxx.xxx:/ServerBackups /Backups/FileServers nfs rsize=8192,nosuid,wsize=8192,soft 0 0
doktor5000 wrote:Did you add _netdev as an option to mark it as a remote filesystem ?
192.xxx.xxx.xxx:/ServerBackups /Backups/FileServers nfs _netdev,rsize=8192,nosuid,wsize=8192,soft 0 0
KnightMB wrote:No, but I did read about adding the _netdev but never found any examples of where I should be putting this option. It might be that simple as adding it, but couldn't quite figure out the syntax of it.
KnightMB wrote:Save, (disable my cron work around), restart the system and it started it up again. Checked the file system and unfortunately, not mounted like before. I either have that _netdev in the wrong place perhaps? Or I have another issue I need to hunt down?
journalctl -ab | grep -iE "nfs|rpc|network.target|Backups.FileServers"
systemctl status Backups-FileServers.mount -al -n50
[root@skuld knightmb]# journalctl -ab | grep -iE "nfs|rpc|network.target|Backups.FileServers"
Jun 04 11:20:21 skuld systemd[1]: Listening on RPCbind Server Activation Socket.
Jun 04 11:20:21 skuld systemd[1]: Reached target RPC Port Mapper.
Jun 04 11:20:27 skuld systemd[1]: Starting RPC Bind...
Jun 04 11:20:27 skuld systemd[1]: Started RPC Bind.
Jun 04 11:20:32 skuld systemd[1]: Mounting /Backups/FileServers...
Jun 04 11:20:33 skuld kernel: RPC: Registered named UNIX socket transport module.
Jun 04 11:20:33 skuld kernel: RPC: Registered udp transport module.
Jun 04 11:20:33 skuld kernel: RPC: Registered tcp transport module.
Jun 04 11:20:33 skuld kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Jun 04 11:20:33 skuld kernel: FS-Cache: Netfs 'nfs' registered for caching
Jun 04 11:20:34 skuld kernel: NFS: Registering the id_resolver key type
Jun 04 11:20:34 skuld kernel: NFS4: Couldn't follow remote path
Jun 04 11:20:34 skuld mount[1082]: mount.nfs: Network is unreachable
Jun 04 11:20:34 skuld systemd[1]: Backups-FileServers.mount: Mount process exited, code=exited, status=32/n/a
Jun 04 11:20:34 skuld systemd[1]: Backups-FileServers.mount: Failed with result 'exit-code'.
Jun 04 11:20:34 skuld systemd[1]: Failed to mount /Backups/FileServers.
[root@skuld knightmb]# systemctl status Backups-FileServers.mount -al -n50
● Backups-FileServers.mount - /Backups/FileServers
Loaded: loaded (/etc/fstab; generated)
Active: failed (Result: exit-code) since Thu 2020-06-04 11:20:34 CDT; 2min 38s ago
Where: /Backups/FileServers
What: 192.xxx.xxx.xxx:/ServerBackups
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Jun 04 11:20:32 skuld systemd[1]: Mounting /Backups/FileServers...
Jun 04 11:20:34 skuld mount[1082]: mount.nfs: Network is unreachable
Jun 04 11:20:34 skuld systemd[1]: Backups-FileServers.mount: Mount process exited, code=exited, status=32/n/a
Jun 04 11:20:34 skuld systemd[1]: Backups-FileServers.mount: Failed with result 'exit-code'.
Jun 04 11:20:34 skuld systemd[1]: Failed to mount /Backups/FileServers.
KnightMB wrote:
- Code: Select all
Jun 04 11:20:34 skuld mount[1082]: mount.nfs: Network is unreachable
systemctl show -p Requires,Wants,Requisite,BindsTo,PartOf,Before,After,DefaultDependencies Backups-FileServers.mount
systemctl list-dependencies Backups-FileServers.mount --reverse
systemctl list-dependencies network.target --reverse
doktor5000 wrote:KnightMB wrote:
- Code: Select all
Jun 04 11:20:34 skuld mount[1082]: mount.nfs: Network is unreachable
I guess that's pretty self-explanatory, as already guessed it's trying to mount it too early during boot when network is not up yet.
Now to find out why the ordering is messed up. Do you use the classic network setup with net_applet, or do you use networkmanager ?
doktor5000 wrote:Also please post the output of
- Code: Select all
systemctl show -p Requires,Wants,Requisite,BindsTo,PartOf,Before,After,DefaultDependencies Backups-FileServers.mount
systemctl list-dependencies Backups-FileServers.mount --reverse
systemctl list-dependencies network.target --reverse
[root@skuld knightmb]# systemctl show -p Requires,Wants,Requisite,BindsTo,PartOf,Before,After,DefaultDependencies Backups-FileServers.mount
Requires=-.mount system.slice
Requisite=
Wants=network-online.target
BindsTo=
PartOf=
Before=umount.target remote-fs.target
After=remote-fs-pre.target -.mount systemd-journald.socket network-online.target network.target system.slice
DefaultDependencies=yes
[root@skuld knightmb]# systemctl list-dependencies Backups-FileServers.mount --reverse
Backups-FileServers.mount
● └─remote-fs.target
● ├─dracut-pre-pivot.service
● └─multi-user.target
● └─graphical.target
[root@skuld knightmb]# systemctl list-dependencies network.target --reverse
network.target
● ├─network-up.service
● └─network.service
KnightMB wrote:I think the networkmanager, is that the screen when you are finishing up an install of Mageia from DVD before the system reboots for the first time?
systemctl status network-up.service -al -n50
systemctl status network-online.target -al -n50
systemctl status network.service -al -n50
journalctl -ab > /tmp/journalctl.log
doktor5000 wrote:KnightMB wrote:I think the networkmanager, is that the screen when you are finishing up an install of Mageia from DVD before the system reboots for the first time?
No, that's the regular summary screen. You probably mean this one? https://doc.mageia.org/installer/7/en/c ... arams.html
So seems you're using the default net_applet.
doktor5000 wrote:Hmm, the rest doesn't provide much insight.
Could you add the output of
- Code: Select all
systemctl status network-up.service -al -n50
systemctl status network-online.target -al -n50
systemctl status network.service -al -n50
and maybe even the full log after a fresh boot of
- Code: Select all
journalctl -ab > /tmp/journalctl.log
then simply attach /tmp/journalctl.log here.
> systemctl status network-up.service -al -n50
● network-up.service - LSB: Wait for the hotplugged network to be up
Loaded: loaded (/etc/rc.d/init.d/network-up; generated)
Active: active (exited) since Thu 2020-06-04 23:00:07 CDT; 1min 46s ago
Docs: man:systemd-sysv-generator(8)
Process: 699 ExecStart=/etc/rc.d/init.d/network-up start (code=exited, status=0/SUCCESS)
Jun 04 23:00:07 skuld systemd[1]: Starting LSB: Wait for the hotplugged network to be up...
Jun 04 23:00:07 skuld network-up[699]: Waiting for network to be up[ OK ]
Jun 04 23:00:07 skuld systemd[1]: Started LSB: Wait for the hotplugged network to be up.
> systemctl status network-online.target -al -n50
● network-online.target - Network is Online
Loaded: loaded (/usr/lib/systemd/system/network-online.target; static; vendor preset: disabled)
Active: active since Thu 2020-06-04 23:00:09 CDT; 3min 24s ago
Docs: man:systemd.special(7)
https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget
Jun 04 23:00:09 skuld systemd[1]: Reached target Network is Online.
> systemctl status network.service -al -n50
● network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network; generated)
Active: active (running) since Thu 2020-06-04 23:00:09 CDT; 3min 56s ago
Docs: man:systemd-sysv-generator(8)
Process: 838 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=0/SUCCESS)
Tasks: 1 (limit: 3556)
Memory: 2.8M
CGroup: /system.slice/network.service
└─1016 /sbin/ifplugd -I -b -i enp3s8
Jun 04 23:00:08 skuld systemd[1]: Starting LSB: Bring up/down networking...
Jun 04 23:00:09 skuld network[838]: Bringing up loopback interface: [ OK ]
Jun 04 23:00:09 skuld ifplugd(enp3s8)[1016]: ifplugd 0.28 initializing.
Jun 04 23:00:09 skuld ifplugd(enp3s8)[1016]: Using interface enp3s8/00:16:76:9C:DE:2F with driver <e100> (version: 3.5.24-k2-NAPI)
Jun 04 23:00:09 skuld ifplugd(enp3s8)[1016]: Using detection mode: SIOCETHTOOL
Jun 04 23:00:09 skuld ifplugd(enp3s8)[1016]: Initialization complete, link beat detected.
Jun 04 23:00:09 skuld ifplugd(enp3s8)[1016]: Executing '/etc/ifplugd/ifplugd.action enp3s8 up'.
Jun 04 23:00:09 skuld network[838]: Bringing up interface enp3s8: [ OK ]
Jun 04 23:00:09 skuld systemd[1]: Started LSB: Bring up/down networking.
Jun 04 23:00:14 skuld NET[1404]: /etc/sysconfig/network-scripts/ifup-post : updated /etc/resolv.conf
Jun 04 23:00:14 skuld ifplugd(enp3s8)[1016]: Program executed successfully.
/sbin/ip a
Jun 04 23:00:07 skuld network-up[699]: Waiting for network to be up[ OK ]
Jun 04 23:00:07 skuld systemd[1]: Started LSB: Wait for the hotplugged network to be up.
[...]
Jun 04 23:00:09 skuld ifplugd(enp3s8)[1016]: ifplugd 0.28 initializing.
Jun 04 23:00:09 skuld kernel: e100 0000:03:08.0 enp3s8: NIC Link is Up 100 Mbps Full Duplex
Jun 04 23:00:09 skuld kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp3s8: link becomes ready
Jun 04 23:00:09 skuld ifplugd(enp3s8)[1016]: Using interface enp3s8/00:16:76:9C:DE:2F with driver <e100> (version: 3.5.24-k2-NAPI)
Jun 04 23:00:09 skuld ifplugd(enp3s8)[1016]: Using detection mode: SIOCETHTOOL
Jun 04 23:00:09 skuld ifplugd(enp3s8)[1016]: Initialization complete, link beat detected.
Jun 04 23:00:09 skuld ifplugd(enp3s8)[1016]: Executing '/etc/ifplugd/ifplugd.action enp3s8 up'.
Jun 04 23:00:09 skuld network[838]: Bringing up interface enp3s8: [ OK ]
[...]
Jun 04 23:00:11 skuld mount[1074]: mount.nfs: Network is unreachable
Jun 04 23:00:11 skuld kernel: NFS4: Couldn't follow remote path
Jun 04 23:00:11 skuld systemd[1]: Backups-FileServers.mount: Mount process exited, code=exited, status=32/n/a
Jun 04 23:00:11 skuld systemd[1]: Backups-FileServers.mount: Failed with result 'exit-code'.
Jun 04 23:00:11 skuld systemd[1]: Failed to mount /Backups/FileServers.
Jun 04 23:00:11 skuld systemd[1]: Dependency failed for Remote File Systems.
Jun 04 23:00:11 skuld systemd[1]: remote-fs.target: Job remote-fs.target/start failed with result 'dependency'.
doktor5000 wrote:You're welcome. Please don't forget to mark the thread solved
If you want a comparison of settings, I do have a backup of the entire /etc folder from the machine before I started tinkering with it today, just need to know which files to attach here (yesterday vs. today for example)
KnightMB wrote:If you want a comparison of settings, I do have a backup of the entire /etc folder from the machine before I started tinkering with it today, just need to know which files to attach here (yesterday vs. today for example)
diff -ur /etc /path/to/backup_of_etc
DEVICE=enp3s8
BOOTPROTO=static
IPADDR=192.xxx.xxx.xxx
NETMASK=255.255.252.0
GATEWAY=192.xxx.xxx.xxx
ONBOOT=yes
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes
DNS1=192.xxx.xxx.xxx
RESOLV_MODS=no
IPV6INIT=no
IPV6TO4INIT=no
ACCOUNTING=no
DEVICE=enp3s8
BOOTPROTO=none
IPADDR=192.xxx.xxx.xxx
NETMASK=255.255.252.0
GATEWAY=192.xxx.xxx.xxx
ONBOOT=yes
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes
DNS1=192.xxx.xxx.xxx
RESOLV_MODS=no
IPV6INIT=yes
IPV6TO4INIT=no
ACCOUNTING=no
KnightMB wrote:I set that BOOTPROTO=none, save and reboot, well it stopped working, set it back to BOOTPROTO=static and everything was fine again.
Users browsing this forum: No registered users and 1 guest