since updating to 5.9 a little while ago I find a load of these in /var/log/messages, which I've not seen before:
Jan 17 22:17:18 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument Jan 17 22:17:20 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument Jan 17 22:17:31 fcshome ntpd[4680]: sendto(129.70.132.37) (fd=22): Invalid argument Jan 17 22:34:22 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument Jan 17 22:34:23 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument Jan 17 22:34:37 fcshome ntpd[4680]: sendto(129.70.132.37) (fd=22): Invalid argument Jan 17 22:51:26 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument Jan 17 22:51:28 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument Jan 17 22:51:41 fcshome ntpd[4680]: sendto(129.70.132.37) (fd=22): Invalid argument Jan 17 23:08:32 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument Jan 17 23:08:33 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument Jan 17 23:08:46 fcshome ntpd[4680]: sendto(129.70.132.37) (fd=22): Invalid argument Jan 17 23:25:35 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument Jan 17 23:25:36 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument Jan 17 23:25:49 fcshome ntpd[4680]: sendto(129.70.132.37) (fd=22): Invalid argument Jan 17 23:42:38 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument Jan 17 23:42:39 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument Jan 17 23:42:53 fcshome ntpd[4680]: sendto(129.70.132.37) (fd=22): Invalid argument
Is ntp busted in 5.9?
Clues appreciated, thanks!
From: fred smith fredex@fcshome.stoneham.ma.us
since updating to 5.9 a little while ago I find a load of these in /var/log/messages, which I've not seen before: Jan 17 22:17:18 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument ... Is ntp busted in 5.9?
Dunno, but I upgraded to 5.9, rebooted and I do not have (yet) such errors... Do you also have the regular messages too when ntpd starts? Did you edit /etc/sysconfig/ntpd?
JD
On Fri, Jan 18, 2013 at 06:15:02AM -0800, John Doe wrote:
From: fred smith fredex@fcshome.stoneham.ma.us
since updating to 5.9 a little while ago I find a load of these in /var/log/messages, which I've not seen before: Jan 17 22:17:18 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument ... Is ntp busted in 5.9?
Dunno, but I upgraded to 5.9, rebooted and I do not have (yet) such errors... Do you also have the regular messages too when ntpd starts?
Here's what I see from rebooting last night after doing the updates. The first one appears to be during the shutdown, and the rest from the reboot:
messages:Jan 17 21:01:29 fcshome ntpd[5231]: ntpd exiting on signal 15 messages:Jan 17 21:03:34 fcshome ntpd[4679]: ntpd 4.2.2p1@1.1570-o Fri Nov 18 13:21:16 UTC 2011 (1) messages:Jan 17 21:03:34 fcshome ntpd[4680]: precision = 2.000 usec messages:Jan 17 21:03:34 fcshome ntpd[4680]: Listening on interface wildcard, 0.0.0.0#123 Disabled messages:Jan 17 21:03:34 fcshome ntpd[4680]: Listening on interface wildcard, ::#123 Disabled messages:Jan 17 21:03:34 fcshome ntpd[4680]: Listening on interface lo, ::1#123 Enabled messages:Jan 17 21:03:34 fcshome ntpd[4680]: Listening on interface eth0, fe80::21f:d0ff:fed9:53a2#123 Enabled messages:Jan 17 21:03:34 fcshome ntpd[4680]: Listening on interface lo, 127.0.0.1#123 Enabled messages:Jan 17 21:03:34 fcshome ntpd[4680]: Listening on interface eth0, 192.168.2.12#123 Enabled messages:Jan 17 21:03:34 fcshome ntpd[4680]: Listening on interface eth0:1, 192.168.1.2#123 Enabled messages:Jan 17 21:03:34 fcshome ntpd[4680]: kernel time sync status 0040 messages:Jan 17 21:03:35 fcshome ntpd[4680]: frequency initialized -99.461 PPM from /var/lib/ntp/drift messages:Jan 17 21:21:47 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument messages:Jan 17 21:21:49 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument messages:Jan 17 21:21:55 fcshome ntpd[4680]: sendto(129.70.132.37) (fd=22): Invalid argument messages:Jan 17 21:22:52 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument messages:Jan 17 21:22:53 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument
And there are a bazillion more of those errors continuing up to more or less the moment I write this.
Did you edit /etc/sysconfig/ntpd?
No. should I have?
On 01/17/2013 11:02 PM, fred smith wrote:
since updating to 5.9 a little while ago I find a load of these in /var/log/messages, which I've not seen before:
Jan 17 22:17:18 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument Jan 17 22:17:20 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument Jan 17 22:17:31 fcshome ntpd[4680]: sendto(129.70.132.37) (fd=22): Invalid argument Jan 17 22:34:22 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument Jan 17 22:34:23 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument Jan 17 22:34:37 fcshome ntpd[4680]: sendto(129.70.132.37) (fd=22): Invalid argument Jan 17 22:51:26 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument Jan 17 22:51:28 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument Jan 17 22:51:41 fcshome ntpd[4680]: sendto(129.70.132.37) (fd=22): Invalid argument Jan 17 23:08:32 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument Jan 17 23:08:33 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument Jan 17 23:08:46 fcshome ntpd[4680]: sendto(129.70.132.37) (fd=22): Invalid argument Jan 17 23:25:35 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument Jan 17 23:25:36 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument Jan 17 23:25:49 fcshome ntpd[4680]: sendto(129.70.132.37) (fd=22): Invalid argument Jan 17 23:42:38 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument Jan 17 23:42:39 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument Jan 17 23:42:53 fcshome ntpd[4680]: sendto(129.70.132.37) (fd=22): Invalid argument
Is ntp busted in 5.9?
Clues appreciated, thanks!
Everything I see on this issue says to restart the ntpd service when this happens. Does that help?
On Fri, Jan 18, 2013 at 09:06:32AM -0600, Johnny Hughes wrote:
On 01/17/2013 11:02 PM, fred smith wrote:
since updating to 5.9 a little while ago I find a load of these in /var/log/messages, which I've not seen before:
Jan 17 22:17:18 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument Jan 17 22:17:20 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument Jan 17 22:17:31 fcshome ntpd[4680]: sendto(129.70.132.37) (fd=22): Invalid argument Jan 17 22:34:22 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument Jan 17 22:34:23 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument Jan 17 22:34:37 fcshome ntpd[4680]: sendto(129.70.132.37) (fd=22): Invalid argument Jan 17 22:51:26 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument Jan 17 22:51:28 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument Jan 17 22:51:41 fcshome ntpd[4680]: sendto(129.70.132.37) (fd=22): Invalid argument Jan 17 23:08:32 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument Jan 17 23:08:33 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument Jan 17 23:08:46 fcshome ntpd[4680]: sendto(129.70.132.37) (fd=22): Invalid argument Jan 17 23:25:35 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument Jan 17 23:25:36 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument Jan 17 23:25:49 fcshome ntpd[4680]: sendto(129.70.132.37) (fd=22): Invalid argument Jan 17 23:42:38 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument Jan 17 23:42:39 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument Jan 17 23:42:53 fcshome ntpd[4680]: sendto(129.70.132.37) (fd=22): Invalid argument
Is ntp busted in 5.9?
Clues appreciated, thanks!
Everything I see on this issue says to restart the ntpd service when this happens. Does that help?
Johnny:
Dunno yet, just bounced it "/etc/rc.d/init.d/ntpd restart", so I'll watch it for a while and see what happens.
Fred
On Fri, Jan 18, 2013 at 1:39 PM, fred smith fredex@fcshome.stoneham.ma.us wrote:
On Fri, Jan 18, 2013 at 09:06:32AM -0600, Johnny Hughes wrote:
On 01/17/2013 11:02 PM, fred smith wrote:
since updating to 5.9 a little while ago I find a load of these in /var/log/messages, which I've not seen before:
Jan 17 22:17:18 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument Jan 17 22:17:20 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument Jan 17 22:17:31 fcshome ntpd[4680]: sendto(129.70.132.37) (fd=22): Invalid argument Jan 17 22:34:22 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument
[...]
After making sure ipv4 is correctly configured (!), try stopping ntpd and execute "ntpdate -d 216.230.228.211". If it succedes, I'd look into selinux issues ("setenforce 0" and restart ntpd [This won't solve your problem, just pospone it to the next reboot!])
-- Marcelo
"¿No será acaso que esta vida moderna está teniendo más de moderna que de vida?" (Mafalda)
-
fred smith -
John Doe -
Johnny Hughes -
Marcelo Roccasalva