Hi Guys
Running Rocky 9.2
cat /etc/redhat-release
Rocky Linux release 9.2 (Blue Onyx)
I got here by doing a migrate from Centos 8.5 across to Rocky 8.8 and using the standard scripts.
I then used Elevate from Alma to upgrade to Rocky 9.2 (i know in place upgrades are frowned upon - but i took an image of the hard drive to another drive using clonezilla before the upgrade) and surprisingly everthing came across without any issues - in the pre flight check it warned me that NFS was not support so i removed the NFS utils modules and then eveything went through.
I am now trying to reinstall NFS (to enable the system to share out some NFS folders) and am getting an error
Kernel is
uname -r
5.14.0-284.25.1.el9_2.x86_64
I installed NFS using
yum install nfs-utils
and it went through fine
This is what i see when i try to install again
yum install nfs-utils
Last metadata expiration check: 2:17:00 ago on Sat 26 Aug 2023 09:49:19.
Package nfs-utils-1:2.5.4-18.el9.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
So it appears to me that it is installed and working OK - but i am not able to mount any shares. I have a dedicated 10GB VLAN and have two ESXi hosts in my lab that wwre previously working fine (nothing has changed on them)
I am seeing Network manager errors in /var/log/messages that i feel are also somehow related as they point to that dedicated NIC.
Sep 12 14:05:36 mediastore8 systemd[1]: run-docker-netns-649b02bc11eb.mount: Deactivated successfully.
Sep 12 14:05:36 mediastore8 systemd[1]: var-lib-docker-overlay2-659742d6ad8a64d10bf45eacd34efed55bff4850b7f198e713bb7cbd4ba46ec9-merged.mount: Deactivated successfully.
Sep 12 14:05:36 mediastore8 kernel: nfsd: shutting down export module (net: f000085b).
Sep 12 14:05:36 mediastore8 kernel: nfsd: export shutdown complete (net: f000085b).
Sep 12 14:05:36 mediastore8 kernel: RPC: unregistering /proc/net/rpc
Sep 12 14:05:50 mediastore8 kernel: svc_age_temp_xprts
Sep 12 14:06:09 172.16.100.254 6610-Basement System: Interface ethernet 1/3/7, state down
Sep 12 14:06:09 172.16.100.254 6610-Basement System: Interface ethernet 1/3/7, state up
Sep 12 14:06:08 mediastore8 NetworkManager[1258]: <info> [1694491568.9865] device (enp1s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Sep 12 14:06:08 mediastore8 NetworkManager[1258]: <warn> [1694491568.9870] device (enp1s0): Activation: failed for connection 'Intel_10GB'
Sep 12 14:06:08 mediastore8 NetworkManager[1258]: <info> [1694491568.9873] device (enp1s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Sep 12 14:06:08 mediastore8 avahi-daemon[1260]: Withdrawing address record for fe80::23b4:a955:61cc:61b on enp1s0.
Sep 12 14:06:08 mediastore8 avahi-daemon[1260]: Leaving mDNS multicast group on interface enp1s0.IPv6 with address fe80::23b4:a955:61cc:61b.
Sep 12 14:06:08 mediastore8 kernel: nfsd_inet6addr_event: removed fe80:0000:0000:0000:23b4:a955:61cc:061b
Sep 12 14:06:08 mediastore8 avahi-daemon[1260]: Interface enp1s0.IPv6 no longer relevant for mDNS.
Sep 12 14:06:08 mediastore8 NetworkManager[1258]: <info> [1694491568.9905] dhcp4 (enp1s0): canceled DHCP transaction
Sep 12 14:06:08 mediastore8 NetworkManager[1258]: <info> [1694491568.9905] dhcp4 (enp1s0): activation: beginning transaction (timeout in 45 seconds)
Sep 12 14:06:08 mediastore8 NetworkManager[1258]: <info> [1694491568.9906] dhcp4 (enp1s0): state changed no lease
Sep 12 14:06:09 mediastore8 kernel: ixgbe 0000:01:00.0 enp1s0: detected SFP+: 5
Sep 12 14:06:09 mediastore8 kernel: ixgbe 0000:01:00.0 enp1s0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
Sep 12 14:06:09 mediastore8 NetworkManager[1258]: <info> [1694491569.4169] device (enp1s0): carrier: link connected
Sep 12 14:06:09 mediastore8 NetworkManager[1258]: <info> [1694491569.4171] device (Intel_10GB.200): carrier: link connected
Sep 12 14:06:28 mediastore8 kernel: svc_pool_stats_start, *pidx=0
There is nothing wrong with the link or cabling/NIC - i have succesfully rebooted to the older Centos 8 Boot drive and the NFS mounts are recognized at the ESXi end with no problems and there are no errors in the log files re NetworkManager
Craig