ntpd vs selinux

[Gene Heskett]

Tim wrote:
> Gene Heskett:
>>>> Jun 30 22:37:14 diablo ntpd[1936]: sendto(194.145.249.108): Invalid argument
>>>> Jun 30 22:38:01 diablo ntpd[1936]: sendto(194.102.249.64): Invalid argument
>>>> Jun 30 22:42:04 diablo ntpd[1936]: sendto(193.40.133.134): Invalid argument
> 
> Tim:
>>> For what it's worth, I'd see the same sort of thing if NTP was run
>>> twice.  Don't ask how that might happen, I've not figured it out.  If I
>>> checked the running processes, killed off all the NTPDs then restarted,
>>> it went away.
>  
> Gene Heskett:
>> I didn't kill any extra ntpd's. just a regular 'service ntpd restart'
> 
> Another thing that has that effect, that I'd forgotten about since
> leaving dial-up internet, was an interface going down that NTP was
> using.  I had to put an NTP restart script into my ifup post PPP script,
> to restart the NTP server after a new connection.  It just wouldn't keep
> on working by itself.
> 
That makes perfect sense now that I get 4 for an answer, Tim. :)  My 
dhcp lease was renewed in the middle of the night, giving me a different 
address in the 192.168 block.

I assume that would have the same effect.  For the rest of the system, 
it appears to be transparent and I have not rebooted.

 From the log, thats exactly what happened:

Jun 30 16:26:05 diablo dhclient: DHCPREQUEST on wlan0 to 192.168.1.1 port 67
Jun 30 16:26:05 diablo dhclient: DHCPNAK from 192.168.1.1
Jun 30 16:26:05 diablo dhclient: DHCPDISCOVER on wlan0 to 
255.255.255.255 port 67 interval 8
Jun 30 16:26:06 diablo dhclient: DHCPOFFER from 192.168.1.1
Jun 30 16:26:06 diablo dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 
port 67
Jun 30 16:26:06 diablo dhclient: DHCPACK from 192.168.1.1
Jun 30 16:26:06 diablo avahi-daemon[2046]: Withdrawing address record 
for 192.168.1.103 on wlan0.
Jun 30 16:26:06 diablo avahi-daemon[2046]: Leaving mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.103.
Jun 30 16:26:06 diablo avahi-daemon[2046]: iface.c: 
interface_mdns_mcast_join() called but no local address available.
Jun 30 16:26:06 diablo avahi-daemon[2046]: Interface wlan0.IPv4 no 
longer relevant for mDNS.
Jun 30 16:26:06 diablo avahi-daemon[2046]: New relevant interface 
wlan0.IPv4 for mDNS.
Jun 30 16:26:06 diablo avahi-daemon[2046]: Joining mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.105.
Jun 30 16:26:06 diablo avahi-daemon[2046]: Registering new address 
record for 192.168.1.105 on wlan0.
Jun 30 16:26:06 diablo dhclient: bound to 192.168.1.105 -- renewal in 
42563 seconds.

And at that point, those messages:

Jun 30 16:26:31 diablo ntpd[1936]: sendto(193.40.133.134): Invalid argument

started.

in other words, problem solved.  This avahi-daemon is a new item to me. 
  Should I bugzilla it for not restarting ntpd if it was found to be 
running?

-- 
Cheers, Gene