Hi Guys,
Thanks for the responses,appreciate it! In the end it was an overloaded DNS server, which caused a delay in another SBC passing requests to the opensips server, so overloading it. Thanks for the advice everyone. It wasnt OpenSIPS! 😊 Jon ________________________________ From: Bogdan-Andrei Iancu <[email protected]> Sent: 31 October 2017 12:04 To: OpenSIPS users mailling list; Jonathan Hunter Subject: Re: [OpenSIPS-Users] opensips 2.2.5 stop responding/processing requests. - Centos 6.5 Hi Jonathan, It looks like you have kind on task inside OpenSIPS that is using a lot of time/process resources - shortly, this translate into "there are no available worker processes to handle new jobs". * do you have any threshold set to catch any DB/DNS delays ? * have you checked the CPU usage ? * have you monitor the "load:" statistics group ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com Home — OpenSIPS Solutions<http://www.opensips-solutions.com/> www.opensips-solutions.com OpenSIPS is a mature Open Source implementation of a SIP server. OpenSIPS is more than a SIP proxy/router as it includes application-level functionalities. On 10/30/2017 07:33 PM, Jonathan Hunter wrote: Hi Guys, Has anyone had the following behaviour with this release of opensips? It has been running fine for a number of months, and then suddenly today the server which was running as the primary suddenly stopped responding to SIP requests, or stopped processing them, or there was a long pause in a sequence completing. So in some cases, INVITES or REGISTER messages were ignored and the initial requests werent always logged in the opensips log file (even though we do this for all messages), however the SIP requests were hitting the server as I was tracing them. In the logs I can see the following warnings we havent seen before; Oct 30 13:31:25 sgw6 VU-SIP-Proxy[11159]: WARNING:core:utimer_ticker: utimer task <tm-utimer> already scheduled for 9639891650 ms (now 9639891850 ms), it may overlap. Oct 30 13:52:48 sgw6 VU-SIP-Proxy[11159]: WARNING:core:timer_ticker: timer task <nh-timer> already scheduled for 9640994180 ms (now 9641175280 ms), it may overlap.. Oct 30 13:52:48 sgw6 VU-SIP-Proxy[11159]: WARNING:core:timer_ticker: timer task <ul-timer> already scheduled for 9640980270 ms (now 9641175280 ms), it may overlap.. A restart of the opensips application didnt help, and service was only restored fully when I failed over to the secondary server. Has anyone had these issues before? There are no obvious server level issues, and as I mentioned the logs dont contain anything too unusual. Any help appreciated. Many thanks Jon _______________________________________________ Users mailing list [email protected]<mailto:[email protected]> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
