We run 'ntpdate -q' once daily to check the ntpd sync status of the hosts in our network. On one host, this check is failing sporadically today: $ for i in `seq 1 10` ; do ntpdate -q 192.168.129.110 ; sleep 1 ; done server 192.168.129.110, stratum 4, offset -0.001034, delay 0.02693 24 May 10:11:16 ntpdate[3742]: adjust time server 192.168.129.110 offset -0.001034 sec server 192.168.129.110, stratum 4, offset -0.000997, delay 0.02701 24 May 10:11:17 ntpdate[3747]: adjust time server 192.168.129.110 offset -0.000997 sec server 192.168.129.110, stratum 4, offset 0.000000, delay 0.00000 24 May 10:11:18 ntpdate[3752]: no server suitable for synchronization found server 192.168.129.110, stratum 4, offset 0.000000, delay 0.00000 24 May 10:11:19 ntpdate[3757]: no server suitable for synchronization found server 192.168.129.110, stratum 4, offset -0.000162, delay 0.02878 24 May 10:11:20 ntpdate[3762]: adjust time server 192.168.129.110 offset -0.000162 sec server 192.168.129.110, stratum 4, offset 0.000000, delay 0.00000 24 May 10:11:21 ntpdate[3767]: no server suitable for synchronization found server 192.168.129.110, stratum 4, offset 0.000000, delay 0.00000 24 May 10:11:22 ntpdate[3772]: no server suitable for synchronization found server 192.168.129.110, stratum 4, offset 0.000000, delay 0.00000 24 May 10:11:24 ntpdate[3777]: no server suitable for synchronization found server 192.168.129.110, stratum 4, offset -0.001079, delay 0.02701 24 May 10:11:25 ntpdate[3782]: adjust time server 192.168.129.110 offset -0.001079 sec server 192.168.129.110, stratum 4, offset 0.000000, delay 0.00000 24 May 10:11:26 ntpdate[3787]: no server suitable for synchronization found It seems to fail 6/10 checks consistently, whereas normally it succeeds on all attempts. This is the ntpd configuration on 192.168.129.110: $ cat /etc/ntp.conf driftfile /var/lib/ntp/drift server 192.168.24.39 server 192.168.24.80 server 192.168.132.51 server 192.168.132.83 $ cat /etc/sysconfig/ntpd # Drop root to id 'ntp:ntp' by default. OPTIONS="-u ntp:ntp -p /var/run/ntpd.pid -x" The host is running F12, 2.6.32.10-90.fc12.x86_64. I was previously seeing this ntp sync problem on F12, 2.6.32.11-99, so I thought it was a problem with that kernel, but apparently not. - Kelvin -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
