On Mon, Feb 21, 2005 at 03:27:09PM +0200, Gilad Ben-Yossef wrote: > Tzafrir Cohen wrote: > >Hi > > > >I have a strange problem here: the system clock of my server keeps > >changing. > > > >The following is from the output of 'date' run from the same shell about > >1 second apart: > > > > 12:13:37 > > 13:25:08 > > 12:13:34 > > > >As you can see, the clock occasionally loops back (it keeps in the range > >12:13:34-38) and occasionally decides to move about 72 minutes forward. > > > > OK, this is getting kind of weird... > > Just yesterday a client of mine asked me to help with a problem with an > Asterisk installation running on Xorcom's Rapid (that is debian sarge + > asterisk). The problem was that Asterisk seems to just exit for no > apperant reason from time to time.
Interesting. I'd like to get more information on that (possibly off-list). Next version of the Debian packages integrate safe_asterisk in the init.d script, but not as default. Not a fix, but will save you the manual restarts. > > Going over the config and logs the only thing I found was that the > system time seems to behave in a weird way, it seems that different > program have different notion of the system time. e.g.: > > # init q > > and > > # logger "test" > > will produce syslog entries which are 4 hours apart... Timezone issues? The timezone was set after the boot and init is not yet aware of the change? > > Such behaviour can surely explain sidden program shutdown (at least a > program that uses timers) > > I have no idea if this is related, but it sure is strange to hear about > a time drift related issue with sarge. What kernel did you use? The default of Rapid (as is the default of Sarge) is kernel 2.4.27-2-386 . -- Tzafrir Cohen | New signature for new address and | VIM is http://tzafrir.org.il | new homepage | a Mutt's [EMAIL PROTECTED] | | best ICQ# 16849755 | Space reserved for other protocols | friend ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
