The time on nfs1 is drifing badly. It is currently 1m8s fast. root@mgt0:~# dsh.sh date -R | sort + dsh -M -c -f hostlist date -R download0: Sat, 07 Dec 2019 15:22:01 -0500 frontend-dev: Sat, 07 Dec 2019 15:22:00 -0500 frontend0: Sat, 07 Dec 2019 15:22:01 -0500 frontend1: Sat, 07 Dec 2019 15:22:01 -0500 internal0: Sat, 07 Dec 2019 15:22:01 -0500 mgt0: Sat, 07 Dec 2019 15:22:01 -0500 nfs1: Sat, 07 Dec 2019 15:23:09 -0500 vcs0: Sat, 07 Dec 2019 15:22:01 -0500 vcs1: Sat, 07 Dec 2019 15:22:01 -0500
root@mgt0:~# dsh.sh date +%s | sort + dsh -M -c -f hostlist date +%s download0: 1575750140 frontend-dev: 1575750139 frontend0: 1575750140 frontend1: 1575750140 internal0: 1575750140 mgt0: 1575750140 nfs1: 1575750208 vcs0: 1575750140 vcs1: 1575750140 In an NFS environment keeping system clock time in sync between client and servers is a critical requirement. Having them out of sync causes many very strange problems that are hard to debug. Been there. Done that. System clock time being out of sync is one of the things I routinely check now when I am looking at anything related to nfs. I can see in the logs that although ntp has been installed a few times that it always gets removed. I am installing it again. I'll mark it 'hold' so that it sticks around. Thanks! Bob
