It could mean your hardware clock is buggered or you have a very weird set of NTP servers. The time jumps are really big and all over the place.
Use NTP, and use a reliable source. Have a look at this thread: http://list.sipfoundry.org/archive/sipx-users/msg26255.html Some more information about time on Linux: http://www.linuxsa.org.au/tips/time.html Paul From: "Henry Dogger" <[email protected]> To: "Discussion list for users of sipXecs software" <[email protected]> Date: 20-05-2011 14:33 Subject: Re: [sipx-users] weird log problem on snapshots Sent by: [email protected] No one knows what this could mean? I’m still experiencing this problem… Henry From: [email protected] [ mailto:[email protected]] On Behalf Of Henry Dogger Sent: woensdag 18 mei 2011 16:24 To: Discussion list for users of sipXecs software Subject: [sipx-users] (no subject) Hi all, Earlier I made a snapshot for George to take a look at, at helping me with my problem. He noticed the following: >> Another weird thing I noticed in sipxproxy.log is that the log starts on May 15 >> >> "2011-05-16T07:34:26.697728Z":1:SIP:WARNING:sipxecs1.voip.office.caiw.intern:pid-32584:B0C26A30:SipXProxy:"SipXproxymain::proxy >> large default expires value: 300 NOT RECOMMENDED" >> >> then goes back to May 15 >> >> "2011-05-16T08:00:16.660772Z":3979:SIP:ERR:sipxecs1.voip.office.caiw.intern:SipRouter-11:42418940:SipXProxy:"SipUserAgent::send >> outgoing call 1" >> "2011-05-15T02:02:34.207922Z":927:KERNEL:NOTICE:sipxecs1.voip.office.caiw.intern:OsTimer-9:413F9940:SipXProxy:"OsMsgQShared::doSendCore >> message queue 'SipUserAgent-2' is over half full - count = 5919, max = >> 10000" >> >> then May 14 >> >> "2011-05-15T11:06:34.208194Z":5007:KERNEL:NOTICE:sipxecs1.voip.office.caiw.intern:OsTimer-9:413F9940:SipXProxy:"OsMsgQShared::doSendCore >> message queue 'SipUserAgent-2' is over half full - count = 9999, max = >> 10000" >> "2011-05-14T08:44:46.054707Z":9:KERNEL:NOTICE:sipxecs1.voip.office.caiw.intern:OsTimer-9:40A34940:SipXProxy:"OsMsgQShared::doSendCore >> message queue 'SipUserAgent-2' is over half full - count = 5001, max = >> 10000" >> >> then back to May 15 >> >> 2011-05-14T12:53:14.225172Z":8:SIP:NOTICE:sipxecs1.voip.office.caiw.intern:pid-643:17D43A30:SipXProxy:"BranchId::setSecret >> reset identifier key; previously generated branch ids will not be >> recognized as local." >> "2011-05-15T00:00:10.208192Z":9:KERNEL:NOTICE:sipxecs1.voip.office.caiw.intern:OsTimer-9:413F9940:SipXProxy:"OsMsgQShared::doSendCore >> message queue 'SipUserAgent-2' is over half full - count = 5001, max = >> 10000" >> >> Do you have any time synch mechanism / cron job running on the machine? I don’t have any cron jobs running or time synch which can cause this… Is this normal behavior? Kind regards, Henry Dogger Telecats BV _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
