Hi Johan,
Thanks for the response I appreciate it. We do use radius for accounting and fire all the information to a central server, but it appears all that was fine and connectivity/configuration was good at the time of the issue. Anywhere in particular it could break things? I have seen it when opensips cant reach radius it starts to be none responsive, is that a scenario you have seen? Many thanks Jon ________________________________ From: Users <users-boun...@lists.opensips.org> on behalf of Johan De Clercq <jo...@democon.be> Sent: 30 October 2017 17:53 To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] opensips 2.2.5 stop responding/processing requests. - Centos 6.5 If you use acc with radius, check radius config. Br On 30 Oct 2017 18:33, "Jonathan Hunter" <hunter...@hotmail.com<mailto:hunter...@hotmail.com>> 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 Users@lists.opensips.org<mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
