>See my next email. It is going backwards and forwards. Something has to >have rights, a driver, a cron job, etc to change your clock. Your system >time is being changed by something.
Do you mean the following message that you posted? >On Wed, 07 Jul 2010 12:44:33 -0500, Matthew Kitchin (public/usenet) wrote: > After looking a little more at the logfile, I noticed it then dropped back > an hour. You must have a cron job or something else interacting with the > system in some way that is changing the time. With you being the one that > has access to the system, I don't know how anyone here can help you anymore > until you can figure out what is changing your clock. I made note that the last time the problem happened was around 11:01. Notice that I started your test script to at 10:23, and it ended at 11:47. The output from that test shows that system time never went backwards. However, the sipregistrar.log show that it went backwards in time, during that same time, albeit, 5Hrs ahead UTC time. What other commands would there be that could change the times? And why doesn't it seem to change the system time, but only the sipregistrar.log times? Mike > Wed Jul 7 11:00:55 CDT 2010 > Wed Jul 7 11:00:56 CDT 2010 > Wed Jul 7 11:00:57 CDT 2010 > Wed Jul 7 11:00:58 CDT 2010 > Wed Jul 7 11:00:59 CDT 2010 > Wed Jul 7 11:01:00 CDT 2010 > Wed Jul 7 11:01:01 CDT 2010 > Wed Jul 7 12:00:57 CDT 2010 > Wed Jul 7 12:00:58 CDT 2010 > Wed Jul 7 12:00:59 CDT 2010 > Wed Jul 7 12:01:00 CDT 2010 > Wed Jul 7 12:01:01 CDT 2010 > Wed Jul 7 12:01:02 CDT 2010 > Wed Jul 7 12:01:03 CDT 2010 > Wed Jul 7 12:01:04 CDT 2010 > Wed Jul 7 12:01:05 CDT 2010 > Wed Jul 7 12:01:06 CDT 2010 > Wed Jul 7 12:01:07 CDT 2010 > Wed Jul 7 12:01:08 CDT 2010 > Wed Jul 7 12:01:09 CDT 2010 > Wed Jul 7 12:01:10 CDT 2010 > Wed Jul 7 12:01:11 CDT 2010 > Wed Jul 7 12:01:12 CDT 2010 > Wed Jul 7 11:01:18 CDT 2010 > Wed Jul 7 11:01:19 CDT 2010 > Wed Jul 7 11:01:20 CDT 2010 > Wed Jul 7 11:01:21 CDT 2010 > Wed Jul 7 11:01:22 CDT 2010 > Wed Jul 7 11:01:23 CDT 2010 > Wed Jul 7 11:01:24 CDT 2010 > Wed Jul 7 11:01:25 CDT 2010 > Wed Jul 7 11:01:26 CDT 2010 > Wed Jul 7 11:01:27 CDT 2010 > Wed Jul 7 11:01:28 CDT 2010 > Wed Jul 7 11:01:29 CDT 2010 > Wed Jul 7 11:01:30 CDT 2010 > Wed Jul 7 11:01:31 CDT 2010 > Wed Jul 7 11:01:32 CDT 2010 > Wed Jul 7 11:01:33 CDT 2010 > Wed Jul 7 11:01:34 CDT 2010 > > On 7/7/2010 12:41 PM, Matthew Kitchin (public/usenet) wrote: > I believe > this is evidence of your problem.... It jumped ahead 1 hour. Something is > still resetting your time. Sipx doesn't change the time on your OS. >> I would expect that to cause a lot of problems. >> >> From the logfile you attached: >> >> Wed Jul 7 11:00:58 CDT 2010 >> Wed Jul 7 11:00:59 CDT 2010 >> Wed Jul 7 11:01:00 CDT 2010 >> Wed Jul 7 11:01:01 CDT 2010 >> Wed Jul 7 12:00:57 CDT 2010 >> Wed Jul 7 12:00:58 CDT 2010 >> Wed Jul 7 12:00:59 CDT 2010 >> Wed Jul 7 12:01:00 CDT 2010 >> Wed Jul 7 12:01:01 CDT 2010 >> Wed Jul 7 12:01:02 CDT 2010 >> >> On 7/7/2010 12:30 PM, m...@grounded.net wrote: > On Wed, 7 Jul 2010 >> 12:53:47 -0400, Tony Graziano wrote: > Please check the >> sipregistrar.log for the microseconds fired message and tell us if you >> again see that message. >>> Yes, it is in there. I had rotated the logs when I started the test and >>> wasn't able to get past the merge-logs problem again. What is >>> interesting is that it happened around 11:01 or so and looking at the >>> sipregistry.log file, the times are totally weird as was identified >>> yesterday. I have ntpd turned off at the moment. Looking at the above >>> file, we see when we roll back the log that it goes from 17:02, to >>> 17:01 and then to 18:01 "2010-07- >>> 07T17:00:57.358701Z":KERNEL:WARNING:uc.sohologic.net:OsTimer- >>> 12:B6E76B90:SipRegistrar:"OsTimerTask::insertTimer timer to fire >>> 3041820306 microseconds in the past, queue length = 0" then to "2010-07- >>> 07T 17:00:58 "2010-07-07T 17:01:XX "2010-07-07T 16:01:XX--16:59:XX >>> "2010-07-07T 17:00:XX "2010-07-07T 17:00:00 "2010-07-07T 18:00:00-- >>> 18:01:12 "2010-07-07T 17:01:19 Yet again, the system hardware and >>> software time are dead on. sh check-time Wed 07 Jul 2010 12:29:03 PM >>> CDT -0.655495 seconds Wed Jul 7 12:29:03 CDT 2010 I have also attached >>> the output from the basic time check script which I ran. > >>> ============================ Tony Graziano, Manager Telephone: >>> 434.984.8430 Fax: 434.984.8431 Email: tgrazi...@myitdepartment.net >>> LAN/Telephony/Security and Control Systems Helpdesk: Telephone: >>> 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: >>> http://www.myitdepartment.net/gethelp/ ----- Original Message ----- >>> From: sipx-users-boun...@list.sipfoundry.org >>>> <sipx-users-boun...@list.sipfoundry.org> To: sipx-users <sipx- >>>> us...@list.sipfoundry.org> Sent: Wed Jul 07 12:32:02 2010 Subject: >>>> Re: [sipx-users] Random Dropped Registrations I am following >>>> everyone's suggestions. I am providing what ever output is required >>>> of me. Would be happy to send my snapshot to someone who may be >>>> able to check it as the merge-logs problem is one of the original >>>> issues. _______________________________________________ sipx- >>>> users mailing list sipx-users@list.sipfoundry.org List Archive: >>>> http://list.sipfoundry.org/archive/sipx-users Unsubscribe: >>>> http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP >>>> PBX -- http://www.sipfoundry.org/ >>> _______________________________________________ sipx-users mailing list >>> sipx-us...@list.sipfoundry.org List Archive: >>> http://list.sipfoundry.org/archive/sipx-users Unsubscribe: >>> http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- >>> http://www.sipfoundry.org/ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
