Here are some patterns I'm noticing: 1. When adding my secondary servers back in sipXconfig I've noticed that replication of sipxsupervisor-config always seems to fail. All the services on these servers have green checkmarks and service control from the web interface works.
2. While devices are able to register to the secondary servers, these registrations are not being replicated to the primary server. Once these registrations drop off the main server they are unreachable from phones located on a different server. ________________________________ From: [email protected] [[email protected]] on behalf of Tony Graziano [[email protected]] Sent: Saturday, May 14, 2011 7:11 PM To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] 4.4 sipXrls dead is apache running? this is, i think an apache error message. can you grep your ports and see if httpd is listening on the correct ssl port (i.e. 8443 and not 443)? i would not think a cache server port should be configured, and have not seen this myself, so it still makes me think something else is the issue. if you were getting these when apache is not running, that might be "normal' as an error message i think. On Sat, May 14, 2011 at 7:38 PM, Josh M. Patten <[email protected]<mailto:[email protected]>> wrote: So I googled SSL23_GET_CLIENT_HELLO:unknown protocol and from what I can gather that means that something isn’t talking SSL correctly. Is there any way from those logs to figure out who the culprit is and give it a smack? Josh Patten Brazos County Network Engineer 979.361.4676<tel:979.361.4676> From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Tony Graziano Sent: Saturday, May 14, 2011 5:55 PM To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] 4.4 sipXrls dead with services stopped... remove all files in var/sipxdata/certdb Delete etc/sipxpbx/ssl (make copies or course) re-run the setup, then try to start services. On Sat, May 14, 2011 at 6:52 PM, Josh M. Patten <[email protected]<mailto:[email protected]>> wrote: Tony: from where? Josh Patten Brazos County Network Engineer 979.361.4676<tel:979.361.4676> From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Tony Graziano Sent: Saturday, May 14, 2011 5:50 PM To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] 4.4 sipXrls dead I would remove all certs first... On May 14, 2011 5:18 PM, "Josh M. Patten" <[email protected]<mailto:[email protected]>> wrote: > How about I just attach the log file ehh? > > This is the log file from when sipxrls starts up. Regarding the first > message, I verified with lsof that nothing was running on that port before > sipxrls started. > > Josh Patten > Brazos County Network Engineer > 979.361.4676<tel:979.361.4676> > > From: > [email protected]<mailto:[email protected]> > > [mailto:[email protected]<mailto:[email protected]>] > On Behalf Of Josh M. Patten > Sent: Saturday, May 14, 2011 4:13 PM > To: Discussion list for users of sipXecs software > Subject: Re: [sipx-users] 4.4 sipXrls dead > > Also seeing: > > "2011-05-14T21:09:03.135356Z":7:KERNEL:ERR:it.ippbx.co.brazos.tx.us:SipServerBroker-7:42107940:sipxrls:"OsSSLServerSocket > SSL_accept SSL handshake error:\n SSL error: 1 > 'error:00000001:lib(0):func(0):reason(1)'" > "2011-05-14T21:09:03.135398Z":8:KERNEL:ERR:it.ippbx.co.brazos.tx.us:SipServerBroker-7:42107940:sipxrls:"OsSSLServerSocket > SSL_accept SSL handshake error:\n SSL error: 336027900 'error:140760FC:SSL > routines:SSL23_GET_CLIENT_HELLO:unknown protocol'" > > Anyone here savvy on recreating SSL certs? > > Josh Patten > Brazos County Network Engineer > 979.361.4676<tel:979.361.4676> > > From: > [email protected]<mailto:[email protected]> > > [mailto:[email protected]<mailto:[email protected]>] > On Behalf Of Josh M. Patten > Sent: Saturday, May 14, 2011 4:05 PM > To: Discussion list for users of sipXecs software > Subject: Re: [sipx-users] 4.4 sipXrls dead > > Yeah full backup. I somehow don't think that will help, and I'll explain why: > Whenever Hoa was writing the fix for > http://track.sipfoundry.org/browse/XX-8474 the time values that were used to > "space out" requests were shortened slightly but not drastically in order to > help changes finish sooner. Well, I think Dale W shortened it down too much > for the final code and now if you have a huge RLS list (like I do) it will > fill up the buffers before it can finish processing them and crash. > > Could someone with a little insight into the code look into this and let me > know? > > > Josh Patten > Brazos County Network Engineer > 979.361.4676<tel:979.361.4676> > > From: > [email protected]<mailto:[email protected]> > > [mailto:[email protected]<mailto:[email protected]>] > On Behalf Of Tony Graziano > Sent: Saturday, May 14, 2011 3:58 PM > To: Discussion list for users of sipXecs software > Subject: Re: [sipx-users] 4.4 sipXrls dead > > > I normally perform reboots between upgrades. I find it helps. > > java "is" a four letter word you know... > > You hopefully got a full backup first in the case? > On May 14, 2011 4:47 PM, "Josh M. Patten" > <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> > wrote: >> No, I'll do that. It appears that it maxes out and then core dumps, as I >> have a fresh core dump in /var/log/sipxpbx right after this message in >> sipxrls.log (this is the last message that's sent. After that it's radio >> silence.): >> >> "2011-05-14T20:43:20.797258Z":272:KERNEL:NOTICE:it.ippbx.co.brazos.tx.us:SipSubscribeClient-28:40D8A940:sipxrls:"OsMsgQShared::doSendCore >> message queue 'ResourceListTask-29' is over half full - count = 99, max = >> 100" >> >> Josh Patten >> Brazos County Network Engineer >> 979.361.4676<tel:979.361.4676> >> >> From: >> [email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>> >> >> [mailto:[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>] >> On Behalf Of Tony Graziano >> Sent: Saturday, May 14, 2011 3:45 PM >> To: Discussion list for users of sipXecs software >> Subject: Re: [sipx-users] 4.4 sipXrls dead >> >> >> have you tried an actual reboot? >> On May 14, 2011 4:33 PM, "Josh M. Patten" >> <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>><mailto:[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>>> >> wrote: >>> Hmm it seems that more is unwell. All my services are now showing as >>> "undefined" on my main server (redundant proxies are OK). I'm not quite >>> sure where to begin my troubleshooting quest on this one. Anyone care point >>> me in the right direction? >>> >>> Josh Patten >>> Brazos County Network Engineer >>> 979.361.4676<tel:979.361.4676> >>> >>> From: >>> [email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>><mailto:[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> >>> >>> [mailto:[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>><mailto:[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>>] >>> On Behalf Of Josh M. Patten >>> Sent: Saturday, May 14, 2011 3:27 PM >>> To: >>> [email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>><mailto:[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> >>> Subject: [sipx-users] 4.4 sipXrls dead >>> >>> After upgrading sipX from 4.2.1 to 4.4 this afternoon sipXrls will not >>> respond to any requests and all that is in sipxrls.log when logging is set >>> to info is: >>> "2011-05-14T20:22:24.917670Z":3:RLS:INFO:it.ippbx.co.brazos.tx.us:pid-20269:07A69B40:sipxrls:"SIP_RLS_LOG_CONSOLE >>> : DISABLE" >>> "2011-05-14T20:22:24.917784Z":4:SIPDB:INFO:it.ippbx.co.brazos.tx.us:pid-20269:07A69B40:sipxrls:"initMutex.initialize >>> returns dbInitializationMutex::AlreadyInitialized" >>> >>> I've tried restarting the RLS service a couple times to see if that would >>> resolve it, as well as resending profiles to all servers with no luck. Is >>> there something I've not done properly? >>> >>> Thanks >>> >>> Josh Patten >>> Brazos County Network Engineer >>> 979.361.4676<tel:979.361.4676> >>> _______________________________________________ sipx-users mailing list [email protected]<mailto:[email protected]> List Archive: http://list.sipfoundry.org/archive/sipx-users/ -- ====================== Tony Graziano, Manager Telephone: 434.984.8430<tel:434.984.8430> sip: [email protected]<mailto:[email protected]> Fax: 434.326.5325<tel:434.326.5325> Email: [email protected]<mailto:[email protected]> LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426<tel:434.984.8426> sip: [email protected]<mailto:[email protected]> Helpdesk Contract Customers: http://support.myitdepartment.net Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 _______________________________________________ sipx-users mailing list [email protected]<mailto:[email protected]> List Archive: http://list.sipfoundry.org/archive/sipx-users/ -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected]<mailto:[email protected]> Fax: 434.326.5325 Email: [email protected]<mailto:[email protected]> LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected]<mailto:[email protected]> Helpdesk Contract Customers: http://support.myitdepartment.net <http://support.myitdepartment.net>Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
