Re: [Devil-Linux-discuss] ntp problem

[Heiko Z. <he...@zu...>]

On Sun, March 11, 2007 11:26, Bogdan Petrisor wrote:
> Hello all,
>
>
> Did anybody experienced problems with ntpd similar to this:
>
>
> Mar 11 11:55:38 src@esgaroth ntpdate[7253]: step time server
> 216.27.160.99 offset -0.019538 sec
> Mar 11 11:55:40 src@esgaroth jk_socketd[7512]: listening on socket
> /jail/NTPD/dev/log with rates
> [2048:4096]/10
> Mar 11 11:55:40 src@esgaroth ntpd[7515]: ntpd 4.2.4@1.1437-o Thu Mar  1
> 06:34:22 UTC 2007 (1)
> Mar 11 11:55:40 src@esgaroth ntpd[7515]: signal_no_reset: signal 13 had
> flags 4000000 Mar 11 11:55:40 src@esgaroth ntpd[7515]:
> set_process_priority: Leave priority alone: priority_done
> is <2> Mar 11 11:55:40 src@esgaroth ntpd[7515]: precision = 2.000 usec
> Mar 11 11:55:40 src@esgaroth ntpd[7515]: ntp_io: estimated max
> descriptors: 1024, initial socket
> boundary: 16
> Mar 11 11:55:40 src@esgaroth ntpd[7515]: Listening on interface #0
> wildcard, 0.0.0.0#123 Disabled Mar 11 11:55:40 src@esgaroth ntpd[7515]:
> bind() fd 17, family 10, port 123, scope 0, addr ::,
> in6_is_addr_multicast=0 flags=129 fails: Address already in use Mar 11
> 11:55:40 src@esgaroth ntpd[7515]: unable to bind to wildcard socket
> address :: - another process may be running - EXITING
>
>> From a couple of google searches it seems like this could be a ntp bug
>> but I just wanted to know
> if anybody has seen this problem and found any workaround.
>
> Best regards
>
>
>
> --------------------------------
> Being in the majority means that most people agree with you; it does not
> mean that you are right. --------------------------------

Do you get this message after you reboot the box?

What's the output of the following commands:
lsof -i tcp:123
lsof -i udp:123


-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org