Mauro writes:
> Here is ntp.conf
>
> statsdir /var/log/ntpstats/
Hm, mine's almost the same, except that I have statistics generation
turned off and am using different servers. Did you try the program I
wrote?
# /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help
driftfile /var/l
On 26 September 2012 15:57, lee wrote:
>
> What's in the configuration of your NTP daemon? Perhaps there's
> something wrong with that.
Here is ntp.conf
statsdir /var/log/ntpstats/
statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file
Mauro writes:
> PROBLEM!!
> System clock is gone one hour ahead, ntp stops to run with no messages
> logs and I now I'm in trouble because I don't know what to do.
Try the program below and see what it says. If it actually tells you
that the time is out of sync, you can write a script aroun
September 2012 22:20, Mauro wrote:
>> >>> On 20 September 2012 16:56, John Hasler wrote:
>> >>>> Someone who Stefan failed to identify wrote:
>> >>>>> ...ntpd crashes on my server. Time jumps forward one hour every time
>> >>>>
On Sep 23, 2012, at 6:13 AM, David L. Craig wrote:
On 12Sep23:0208-0700, Rick Thomas wrote:
On Sep 22, 2012, at 6:51 AM, Camaleón wrote:
Anyway, no NTP daemon should crash because of skewed time;
one thing is that it refushes to sync (which can be fine,
and should log this fact so the admin
El 2012-09-22 a las 12:42 -0700, unruh escribió:
(resending to the list)
> In linux.debian.user, you wrote:
(...)
> >> >> It seems not ntp problem but a kernel bug:
> >> >>
> >> >> http://my.opera.com/marcomarongiu/blog/2010/08/18/debugging-ntp-again-part-4-and-last
> >> >
> >> > You can try th
On Sun, 23 Sep 2012 02:08:19 -0700, Rick Thomas wrote:
> On Sep 22, 2012, at 6:51 AM, Camaleón wrote:
>
>> Anyway, no NTP daemon should crash because of skewed time; one thing is
>> that it refushes to sync (which can be fine, and should log this fact
>> so the admin can make the proper measures)
On 12Sep23:0208-0700, Rick Thomas wrote:
>
> On Sep 22, 2012, at 6:51 AM, Camaleón wrote:
>
> >Anyway, no NTP daemon should crash because of skewed time;
> >one thing is that it refushes to sync (which can be fine,
> >and should log this fact so the admin can make the proper
> >measures) but a di
On Sun, 23 Sep 2012, Neal Murphy wrote:
> I must agree that that was a somewhat braindead decision. 'Failure by design'
> is never an valid option.
>
> If a problem is important enough to require an admin's attention, a daemon
> should demand it via the console and the system logs. Nag repeatedl
On Sunday, September 23, 2012 05:08:19 AM Rick Thomas wrote:
> On Sep 22, 2012, at 6:51 AM, Camaleón wrote:
> > Anyway, no NTP daemon should crash because of skewed time; one thing
> > is
> > that it refushes to sync (which can be fine, and should log this fact
> > so the admin can make the proper
On Sep 22, 2012, at 6:51 AM, Camaleón wrote:
Anyway, no NTP daemon should crash because of skewed time; one thing
is
that it refushes to sync (which can be fine, and should log this fact
so the admin can make the proper measures) but a different thing is
completely killing the service.
Hi
hn Hasler wrote:
> >>>> Someone who Stefan failed to identify wrote:
> >>>>> ...ntpd crashes on my server. Time jumps forward one hour every time
> >>>>> this has happened.
> >>>>
> >>>> I doubt ntpd is crashing. Mo
On Fri, 21 Sep 2012 12:05:01 +0200, Mauro wrote:
> On 20 September 2012 22:20, Mauro wrote:
>> On 20 September 2012 16:56, John Hasler wrote:
>>> Someone who Stefan failed to identify wrote:
>>>> ...ntpd crashes on my server. Time jumps forward one hour eve
On 20 September 2012 22:20, Mauro wrote:
> On 20 September 2012 16:56, John Hasler wrote:
>> Someone who Stefan failed to identify wrote:
>>> ...ntpd crashes on my server. Time jumps forward one hour every time
>>> this has happened.
>>
>> I doubt ntpd i
On 20 September 2012 16:56, John Hasler wrote:
> Someone who Stefan failed to identify wrote:
>> ...ntpd crashes on my server. Time jumps forward one hour every time
>> this has happened.
>
> I doubt ntpd is crashing. Most likely something else is jumping the
> system cl
Someone who Stefan failed to identify wrote:
> ...ntpd crashes on my server. Time jumps forward one hour every time
> this has happened.
I doubt ntpd is crashing. Most likely something else is jumping the
system clock and ntpd is behaving as designed and exiting when it sees a
one hour
>>> with ntpd crashes on my server. Time jumps forward one hour every time
>>> this has happened. However I'm not convinced it's the hardware causing
>> Sounds like something is causing the one-hour jump, and that in turns
>> causes ntpd to go bonkers.
On 18 September 2012 15:51, Stefan Monnier wrote:
>> with ntpd crashes on my server. Time jumps forward one hour every time
>> this has happened. However I'm not convinced it's the hardware causing
>
> Sounds like something is causing the one-hour jump, and that
> with ntpd crashes on my server. Time jumps forward one hour every time
> this has happened. However I'm not convinced it's the hardware causing
Sounds like something is causing the one-hour jump, and that in turns
causes ntpd to go bonkers.
As for what causes this jump, I d
On 17 September 2012 21:47, Bob Proulx wrote:
> Mauro wrote:
>> I think ntpd crashes are because my server lost time.
>> I have ntpd in two server, now I've seen that in one of these ntp
>> crashes and the time of the server is 1 hour forward.
>> That's why
On 17 September 2012 19:33, Gerald Turner wrote:
> Mauro writes:
>> I think ntpd crashes are because my server lost time.
>> I have ntpd in two server, now I've seen that in one of these ntp
>> crashes and the time of the server is 1 hour forward.
>> That'
Mauro wrote:
> I think ntpd crashes are because my server lost time.
> I have ntpd in two server, now I've seen that in one of these ntp
> crashes and the time of the server is 1 hour forward.
> That's why ntp crashes: server time goes 1 hour forward and ntp can't
&g
Mauro writes:
> I think ntpd crashes are because my server lost time.
> I have ntpd in two server, now I've seen that in one of these ntp
> crashes and the time of the server is 1 hour forward.
> That's why ntp crashes: server time goes 1 hour forward and ntp can't
&g
On 16 September 2012 17:46, Camaleón wrote:
> Try by appending the "-x" argument at the "/etc/default/ntp" file from
> the server that crashes. If your thoughs are correct, this could mitigate
> the time difference.
I've uninstalled ntp and installed openntp from squeeze backports.
I hope this w
El 2012-09-16 a las 00:17 +0200, Mauro escribió:
(resending to the list)
> On 15 September 2012 16:47, Camaleón wrote:
> > On Sat, 15 Sep 2012 15:43:04 +0200, Mauro wrote:
> >
> >> I think ntpd crashes are because my server lost time.
> >
> > How can tha
On Sat, 15 Sep 2012 15:43:04 +0200, Mauro wrote:
> I think ntpd crashes are because my server lost time.
How can that be? If ntpd daemon is running, the server has to be synced
and showing the right time. And in the event the time is too much skewed,
ntpd shouldn't crash but left
I think ntpd crashes are because my server lost time.
I have ntpd in two server, now I've seen that in one of these ntp
crashes and the time of the server is 1 hour forward.
That's why ntp crashes: server time goes 1 hour forward and ntp can't
resynchronize so it crashes.
Now I do
Mauro wrote:
> What's the difference of running ntpdate instead ntp with cron?
'ntpdate' jumps the clock. It was intended for use at system boot
time when that is okay to do. 'ntpd' is a daemon that runs and makes
small clock adjustments as needed to keep time without "jumping" it.
The 'ntpdate
On Tue, 11 Sep 2012 22:54:50 +0200, Mauro wrote:
> On 11 September 2012 17:32, Camaleón wrote:
(...)
You can try a different approach: do not run ntpd as daemon but using
cron and see how it goes :-?
>>>
>>> What's the difference of running ntpdate instead ntp with cron?
>>
>> Well, A
On Tue, 11 Sep 2012 17:16:05 +0100, Chris Davies wrote:
> Camaleón wrote:
>> You can try a different approach: do not run ntpd as daemon but using
>> cron and see how it goes :-?
>
> Huh?
Yes, for testing purposes.
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-requ...@lis
On 11 September 2012 17:32, Camaleón wrote:
> On Tue, 11 Sep 2012 16:53:43 +0200, Mauro wrote:
>
>> On 11 September 2012 16:48, Camaleón wrote:
>>> On Tue, 11 Sep 2012 12:54:59 +0200, Mauro wrote:
>>>
On 11 September 2012 10:58, Chris Davies
wrote:
> Mauro wrote:
>> I think th
Camaleón wrote:
> You can try a different approach: do not run ntpd as daemon but using
> cron and see how it goes :-?
Huh?
Chris
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://li
Ralf Mardorf wrote:
> Does "jump the clock" mean that the time is synced hard, ignoring
> timestamps?
Yes.
Ntpdate is as likely to set the clock back as it is to put it
forward. Your applications might be able to cope with a second being
only 800ms long, but databases and the like get very upset
On Tue, 11 Sep 2012 16:53:43 +0200, Mauro wrote:
> On 11 September 2012 16:48, Camaleón wrote:
>> On Tue, 11 Sep 2012 12:54:59 +0200, Mauro wrote:
>>
>>> On 11 September 2012 10:58, Chris Davies
>>> wrote:
Mauro wrote:
> I think the best solution is uninstall ntp and use ntpdate with
>
On 11 September 2012 13:03, Ralf Mardorf wrote:
> On Tue, 2012-09-11 at 12:54 +0200, Mauro wrote:
>> On 11 September 2012 10:58, Chris Davies wrote:
>> > Mauro wrote:
>> >> I think the best solution is uninstall ntp and use ntpdate with cron.
>> >
>> > Not a particularly good solution for a numb
On 11 September 2012 16:48, Camaleón wrote:
> On Tue, 11 Sep 2012 12:54:59 +0200, Mauro wrote:
>
>> On 11 September 2012 10:58, Chris Davies
>> wrote:
>>> Mauro wrote:
I think the best solution is uninstall ntp and use ntpdate with cron.
>>>
>>> Not a particularly good solution for a number
On Tue, 11 Sep 2012 12:54:59 +0200, Mauro wrote:
> On 11 September 2012 10:58, Chris Davies
> wrote:
>> Mauro wrote:
>>> I think the best solution is uninstall ntp and use ntpdate with cron.
>>
>> Not a particularly good solution for a number of reasons. Mainly,
>> though, you need to be aware t
On Tue, 2012-09-11 at 12:54 +0200, Mauro wrote:
> On 11 September 2012 10:58, Chris Davies wrote:
> > Mauro wrote:
> >> I think the best solution is uninstall ntp and use ntpdate with cron.
> >
> > Not a particularly good solution for a number of reasons. Mainly, though,
> > you need to be aware
On 11 September 2012 10:58, Chris Davies wrote:
> Mauro wrote:
>> I think the best solution is uninstall ntp and use ntpdate with cron.
>
> Not a particularly good solution for a number of reasons. Mainly, though,
> you need to be aware that ntpdate is quite likely to jump the clock.
If ntp stop
Mauro wrote:
> I think the best solution is uninstall ntp and use ntpdate with cron.
Not a particularly good solution for a number of reasons. Mainly, though,
you need to be aware that ntpdate is quite likely to jump the clock.
Chris
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debia
On 11 September 2012 00:08, Gerald Turner wrote:
> Camaleón writes:
>
>> On Sat, 08 Sep 2012 13:31:16 +0200, Mauro wrote:
>>
>>> Hello I've two server with debian squeeze and in cluster with
>>> heartbeat+pacemaker.
>>> They run ntpd for time
Camaleón writes:
> On Sat, 08 Sep 2012 13:31:16 +0200, Mauro wrote:
>
>> Hello I've two server with debian squeeze and in cluster with
>> heartbeat+pacemaker.
>> They run ntpd for time synchronize.
>> I've noticed some ntpd crashes in random days and rando
pacemaker.
> >> They run ntpd for time synchronize.
> >> I've noticed some ntpd crashes in random days and random hour.
> >
> > Does restarting the service works?
>
> Yes.
Mmm, so it dies "gracefully" :-?
> >> Logs don't say
On Sat, 08 Sep 2012 13:31:16 +0200, Mauro wrote:
> Hello I've two server with debian squeeze and in cluster with
> heartbeat+pacemaker.
> They run ntpd for time synchronize.
> I've noticed some ntpd crashes in random days and random hour.
Does restarting the service works?
44 matches
Mail list logo
