[Dovecot] Time moved backwards ....
OK.. So I synced the clock.... and got ....
dovecot: Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. http://wiki.dovecot.org/TimeMovedBackwards
( The first time I did this the clock moved backwards 2 hours after a timezone change and dovecot suicided ) I think I understand the concept ... However a mail server should probably be synchronized to the local time .....
Suggestions ...???
Harry.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, Feb 18, 2009 at 05:17:18PM +0200, Harry Lachanas wrote:
OK.. So I synced the clock.... and got ....
dovecot: Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. http://wiki.dovecot.org/TimeMovedBackwards
( The first time I did this the clock moved backwards 2 hours after a timezone change and dovecot suicided ) I think I understand the concept ... However a mail server should probably be synchronized to the local time
You don't really mean what you are saying, I think. Anyway: what do you do with all those little file timestamps coming from the future?
Many servers dislike time jumping backwards. I've seen even cron killing itself. Above reaction of dovecot is indeed quite friendly.
FWIW -- if I have to turn back the clock of a server I don't want to reboot, I just slow down the clock and wait...
Regards
- -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFJnCoIBcgs9XrR2kYRAvaTAJwMsK2IcRN6WDJcnaVrvuALzrmQmACfVC9O HJzrzZZl3FLDq90AhgTimUk= =4PDz -----END PGP SIGNATURE-----
tomas@tuxteam.de wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, Feb 18, 2009 at 05:17:18PM +0200, Harry Lachanas wrote:
OK.. So I synced the clock.... and got ....
dovecot: Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. http://wiki.dovecot.org/TimeMovedBackwards
( The first time I did this the clock moved backwards 2 hours after a timezone change and dovecot suicided ) I think I understand the concept ... However a mail server should probably be synchronized to the local time
You don't really mean what you are saying, I think. Anyway: what do you
of course I do .....
The server I was talking about was a test server, fresh install, and I
corrected the time zone ....
So If U are offended, I am sorry ....
On the other hand if U have NOT something real to share .... please do
not answer .... at least with an empty answer ....
You will probably make other people tired + disappointed too,
searching the list trying to locate the answer to this question ....
do with all those little file timestamps coming from the future?
I haven't reached the point where a summer or winter time change happened ... :-) , yet ......... I would hate the moment that I would have to explain to my users that they have to wait for a couple of hours .... until the server wakes up again ...!!!! Also add that I tend not to explain in techno-mambo-jumbo-geek ( metaphorically ;-) ) terminology what is going on ....
Having said all of the above ...
My apologies to the list for the extra paragraphs and being of-topic ...
Cheers, Harry.
Many servers dislike time jumping backwards. I've seen even cron killing itself. Above reaction of dovecot is indeed quite friendly.
FWIW -- if I have to turn back the clock of a server I don't want to reboot, I just slow down the clock and wait...
Regards
- -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFJnCoIBcgs9XrR2kYRAvaTAJwMsK2IcRN6WDJcnaVrvuALzrmQmACfVC9O HJzrzZZl3FLDq90AhgTimUk= =4PDz -----END PGP SIGNATURE-----
On Wed, 18 Feb 2009, Harry Lachanas wrote:
OK.. So I synced the clock.... and got ....
dovecot: Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. http://wiki.dovecot.org/TimeMovedBackwards
Is this related to the leap second that occured yesterday?
Rob
on 2-18-2009 8:12 AM Rob Mangiafico spake the following:
On Wed, 18 Feb 2009, Harry Lachanas wrote:
OK.. So I synced the clock.... and got ....
dovecot: Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. http://wiki.dovecot.org/TimeMovedBackwards
Is this related to the leap second that occured yesterday?
Rob
There are no leap seconds planned for at least the first half of 2009. The next bulletin will be in July. The last leap second was in December 2008.
<quote>
INFORMATION ON UTC - TAI
NO positive leap second will be introduced at the end of June 2009. The difference between Coordinated Universal Time UTC and the International Atomic Time TAI is : from 2009 January 1, 0h UTC, until further notice : UTC-TAI = -34 s
Leap seconds can be introduced in UTC at the end of the months of December or June, depending on the evolution of UT1-TAI. Bulletin C is mailed every six months, either to announce a time step in UTC, or to confirm that there will be no time step at the next possible date.
</quote>
-- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't!!!!
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, Feb 18, 2009 at 06:08:04PM +0200, Harry Lachanas wrote:
tomas@tuxteam.de wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, Feb 18, 2009 at 05:17:18PM +0200, Harry Lachanas wrote:
OK.. So I synced the clock.... and got ....
dovecot: Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. http://wiki.dovecot.org/TimeMovedBackwards
( The first time I did this the clock moved backwards 2 hours after a timezone change and dovecot suicided )
That shouldn't happen: the clock of your server should be UTC and *independent* of the time zone! The time zone should be used to display times (I'm assumig an Unix-like server here -- no clue about other OSes).
I think I understand the concept ... However a mail server should probably be synchronized to the local time
You don't really mean what you are saying, I think. Anyway: what do you
of course I do ..... The server I was talking about was a test server, fresh install, and I corrected the time zone .... So If U are offended, I am sorry ....
No, I'm not, don't worry :-)
On the other hand if U have NOT something real to share .... please do not answer .... at least with an empty answer ....
See below: I did propose two ways of coping with this: rebooting (implicitly) and adjusting softly the clock.
I haven't reached the point where a summer or winter time change happened ... :-) , yet ......... I would hate the moment that I would have to explain to my users that they have to wait for a couple of hours .... until the server wakes up again ...!!!!
Well -- I tried to point out alternatives. See, this problem comes up in this list time and again, and I just wanted to say that dovecot *really can't do anything about it*. It's a general problem with servers.
And there seems to be more problems if you talk about changing time just because you need to change the time zone. And you shouldn't go about changing your clock when summer time comes.
Don't hesitate to ask if all this is mumbo-jumbo to you (but off-list, please, as it's quite off-topic by now)
Regards
- -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFJnDzgBcgs9XrR2kYRAoGbAJ0Zl3OAs3DpXBQURqSXRDyiLU/yFQCfVJbA 4MSDGlk42LuuyPiJa+T1E2g= =kbJM -----END PGP SIGNATURE-----
On February 18, 2009 6:08:04 PM +0200 Harry Lachanas grharry@freemail.gr wrote:
of course I do ..... The server I was talking about was a test server, fresh install, and I corrected the time zone ....
not possible. unix systems keep track of UTC time, not local time. you may have changed the time zone *and also* corrected the time.
I haven't reached the point where a summer or winter time change happened ... :-) , yet .........
again, irrelevant.
-frank
Words by Harry Lachanas [Wed, Feb 18, 2009 at 05:17:18PM +0200]:
OK.. So I synced the clock.... and got ....
dovecot: Time just moved backwards by 1 seconds. I'll sleep now until
we're back in present. http://wiki.dovecot.org/TimeMovedBackwards( The first time I did this the clock moved backwards 2 hours after a
timezone change and dovecot suicided ) I think I understand the concept ... However a mail server should probably be synchronized to the local time
.....Suggestions ...???
Configure ntpd, it syncs the time by micro adjusts. Or do I fail to see the problem ?
-- Jose Celestino | http://japc.uncovering.org/files/japc-pgpkey.asc
"One man’s theology is another man’s belly laugh." -- Robert A. Heinlein
On Feb 18, 2009, at 10:17 AM, Harry Lachanas wrote:
dovecot: Time just moved backwards by 1 seconds. I'll sleep now
until we're back in present. http://wiki.dovecot.org/TimeMovedBackwards( The first time I did this the clock moved backwards 2 hours after
a timezone change and dovecot suicided )
Dovecot tracks the UTC time, which doesn't change when you change
timezones..
on 2-18-2009 7:17 AM Harry Lachanas spake the following:
OK.. So I synced the clock.... and got ....
How are you syncing the clock? The preferred method is to run ntpd to keep the clock synced by nudging the timer faster or slower instead of doing large time corrections.
dovecot: Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. http://wiki.dovecot.org/TimeMovedBackwards
Daemons that work with timestamped logs and files don't like time to go backwards, especially when they are running. Dovecot is nice about it, while some others will either silently die, or corrupt something.
( The first time I did this the clock moved backwards 2 hours after a timezone change and dovecot suicided ) I think I understand the concept ... However a mail server should probably be synchronized to the local time .....
Suggestions ...???
Harry.
-- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't!!!!
participants (8)
-
Frank Cusack
-
Harlan Stenn
-
Harry Lachanas
-
Jose Celestino
-
Rob Mangiafico
-
Scott Silva
-
Timo Sirainen
-
tomas＠tuxteam.de