<div dir="ltr">So I'm thinking there has to be some sort of concurrent startup runlevel issue. Not really sure how to adjust this, but do you see any place in that init script that could cause this or something left out of the dependencies or something? Here's the first bit of the init.d again:<br>### BEGIN INIT INFO<br># Provides: ntp<br># Required-Start: $network $remote_fs $syslog<br># Required-Stop: $network $remote_fs $syslog<br># Default-Start: 2 3 4 5<br># Default-Stop: <br># Short-Description: Start NTP daemon<br>### END INIT INFO<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 8, 2015 at 7:23 PM, Tejeev Patel <span dir="ltr"><<a href="mailto:tejeevpatel@gmail.com" target="_blank">tejeevpatel@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>Hi all,<br></div><div>Thanks for your replies James and Hans. I've included some responses in the bellow email:<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
moin moin TJ,<br>
<br>
what James said in regards to debugging ntp :).<br></blockquote><div><font color="#3d85c6">Ill check on these step tickers, but my understanding was that the -g option should take care of that. Can I put in sdout's in the init script to log when stuff is being done so i can maybe trace where it quits? Any recommendations on where to put them in or how to do some debugging here?<br><br></font></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Here are some other things to check.<br>
<br>
Is there some ntp process already running?<br>
<br>
ps auxw | grep ntp<br>
<br></blockquote><div><font color="#ff0000"><span style="color:rgb(61,133,198)">No NTP process already running.</span><br></font> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Is there a config file in /etc/default/ that has an entry to not start<br>
ntp?<br>
<span style="color:rgb(11,83,148)"><br></span></blockquote><div><span style="color:rgb(61,133,198)">Only see an ntpdate config that basically says to look at the server list in ntp.conf rather than it's own and a ntp config that includes the option -g that I was originally looking to include here.<br></span><br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Is ntpdate installed and configured to prevent ntpd from starting?<br>
<span style="color:rgb(61,133,198)"><br></span></blockquote><div><span style="color:rgb(61,133,198)">ntpdate is apparently installed </span><br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
As James mentioned, ntp will refuse to change the time if it's off too<br>
much. Check to see if the systems are within a couple of minutes of the<br>
actual time.<br>
<br></blockquote><div><span style="color:rgb(61,133,198)">ntp will quit if the time is off by 1000 s or more but the -g option should override that.</span><br><div style="margin-left:40px"> <span style="color:rgb(61,133,198)">( -g Normally, ntpd
exits with a message to the system log if the offset exceeds the panic
threshold, which is 1000 s by default. This option allows the time to
be set to any value
without restriction; however, this can happen only once.
If the threshold is exceeded after that, ntpd will exit with a message
to the system log. This option can be used with
the -q and -x options.)</span><br></div><div style="margin-left:40px"><span style="color:rgb(61,133,198)"></span></div><span style="color:rgb(61,133,198)"><br></span></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Verify your hardware clock is set to UTC.<br>
<br>
Make sure your OS is set at the proper offset from UTC, e.g. you're set to<br>
now and AZ time zone, rather than now and eastern time zone.<br>
<br>
If the boxen are servers they should be set to UTC. Star date blah, blah,<br>
blah and all that.<br></blockquote><div><span style="color:rgb(61,133,198)">Both hardware and software are set to UTC on our servers.</span><br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
cioa,<br>
<br>
der.hans<br></blockquote><div><br> </div></div></div></div>
</blockquote></div><br></div>