I know. I figured the when may possibly shed some light on the why and at least prove it is happening.
On 7/7/2010 10:03 AM, Tony Graziano wrote: > When, but not why. > > He is using a blade center, so the "chassis" is managing an aspect and the > two are fighting each other. > > I think we know where the problem lies. Let him get the chassis to play nice > and see what happens from there. > ============================ > 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@list.sipfoundry.org<sipx-users@list.sipfoundry.org> > Sent: Wed Jul 07 10:51:35 2010 > Subject: Re: [sipx-users] Random Dropped Registrations > > Maybe running a script like this will shed some light on your time issues. > > for i in {1..5000} > do > date>>/tmp/timecheck > sleep 1 > done > > This should output the time every second to a file for 5000 seconds. It > may give you an idea of when your clock is going haywire. > > On 7/7/2010 9:28 AM, Tony Graziano wrote: > >> How about fixing the timing on your blade center? I think lots of >> people will be happy to have that working properly! >> >> Once that is fixed let's wait to hear if you have anymore "lost" >> registrations. >> >> On Wed, Jul 7, 2010 at 10:23 AM, m...@grounded.net >> <mailto:m...@grounded.net> <m...@grounded.net >> <mailto:m...@grounded.net>> wrote: >> >> > You provided approximately 33 seconds of log data, and did not >> tell us >> > the time window during which the registrations disappeared. >> >> Didn't think you would want it because the relevant part seems to >> be when the problem occurs. It appears to be a timer related issue. >> I found some mentions of what I see in the error but haven't found >> a solution. >> >> > There is nothing useful in that data. >> >> Just prior to the problem being repeated, everything looked >> normal, we saw no errors anywhere. This is why I didn't post the >> entire log and only a few seconds prior. When we were able to >> duplicate the problem, we were watching wireshark, running tail -f >> on the sipregistrations.log and looking at the Active >> Registrations window. >> >> When the problem occurred, what we saw was that all phones in the >> Active Registrations screen appeared to go inactive. No phones >> were listed in that screen. At that same time, we noticed sipx >> throw a large number of errors, most of which were similarly >> repeated, all seemed to have something to do with timer, timing. >> >> >> "2010-07-07T06:00:47.560565Z":69042:KERNEL:WARNING:uc.mydomain.com:OsTimer-12:B6EF4B90:SipRegistrar:"OsTimerTask::insertTimer >> timer to fire 2846079116 microseconds in the past, queue length = 0" >> >> "2010-07-07T06:00:47.583583Z":70167:KERNEL:WARNING:uc.mydomain.com:OsTimer-12:B6EF4B90:SipRegistrar:"OsTimerTask::insertTimer >> timer to fire 479721900 microseconds in the past, queue length = 0" >> >> The above shows up repeatedly, the only difference being the >> microseconds so that seems to indicate a timing issue. >> >> The below is the other error which repeated many times. >> >> >> "2010-07-07T06:00:47.565994Z":69302:KERNEL:NOTICE:uc.mydomain.com:OsTimer-12:B6EF4B90:SipRegistrar:"OsMsgQShared::doSendCore >> message queue 'SipUserAgent-15' is over half full - count = 58, >> max = 100" >> >> Just seconds after this event occurred, we watched as phones >> slowly began showing up as active again in the Active >> Registrations screen. >> >> It seemed to me that these warnings are the crux of the issue and >> didn't see anything else in the log which seemed to indicate anything. >> If you feel the whole log should be posted, I can certainly do that. >> >> >> _______________________________________________ >> sipx-users mailing list sipx-users@list.sipfoundry.org >> <mailto: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/ >> >> >> >> >> -- >> ====================== >> Tony Graziano, Manager >> Telephone: 434.984.8430 >> sip: tgrazi...@voice.myitdepartment.net >> <mailto:tgrazi...@voice.myitdepartment.net> >> Fax: 434.984.8431 >> >> Email: tgrazi...@myitdepartment.net<mailto:tgrazi...@myitdepartment.net> >> >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> sip: helpd...@voice.myitdepartment.net >> <mailto:helpd...@voice.myitdepartment.net> >> Fax: 434.984.8427 >> >> Helpdesk Contract Customers: >> http://www.myitdepartment.net/gethelp/ >> >> Why do mathematicians always confuse Halloween and Christmas? >> Because 31 Oct = 25 Dec. >> >> >> _______________________________________________ >> 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-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/
