Ntpdate fails to start

[Tony Molloy]

On Tuesday 09 September 2008 10:30:34 Paul Smith wrote:
> On Tue, Sep 9, 2008 at 10:24 AM, Tony Molloy <tony.molloy at ul.ie> wrote:
> >> >> At booting, ntpdate fails to start, and also the following command
> >> >> fails:
> >> >>
> >> >> # /sbin/service ntpdate start
> >> >> ntpdate: Synchronizing with time server:                   [FAILED]
> >> >>
> >> >> The log messages are:
> >> >>
> >> >> Sep  7 12:50:50 localhost ntpdate[2908]: the NTP socket is in use,
> >> >> exiting
> >> >>
> >> >> Any ideas?
> >> >
> >> > Do you use NetworkManager to bring your network up?  If so, it's not
> >> > up in time for NTP to do its trick, and will be sort of running
> >> > (freewheeling without synchronising to external servers) and
> >> > preventing ntpdate from being usable.
> >>
> >> Thanks, Tim, but how can I check it out?
> >
> > # service NetworkManager status
> >
> > will tell you if NetworkManager is running
> >
> >
> > # service network status
> >
> > will tell you if the networkservice is running.
> >
> > You shouldn't have both running.
> >
> > Try the following and post the results
> >
> > # ntpq -p
>
> Thanks, Tony. The results:
>
> # /sbin/service NetworkManager status
> NetworkManager (pid 2319) is running...
> #

OK, as someone in a previous e-mail said if NetworkManager is running then 
ntpdate will fail to start at boot as NetworkManager will not have the 
network set up in time. 

ntpdate sets the  on your clock approx and then ntpd sets is accurately and 
maintains it. However if ntpdate doesn't run and your clock is off by more 
than a certain amount of time then ntpd will refuse to set it. I can't 
remember what amount of time is involved.

What was the result of

# service network status

>
> # ntpq -p
> bash: ntpq: command not found
> #

Do this as root or give the full path /usr/sbin/ntpq -p and post the results.


>
> but
>
> # /sbin/service ntpd status
> ntpd (pid 2049) is running...
> #

Ok it's running but not synhronising.

Tony
>
> Paul