Hello!
I use opensips as a proxy. Its task is to convert SIP to SIP-I and vice versa.
During busy hours, the number of active dialogs reaches 200 per second and
everything worked perfectly
I had an accident. Moreover, at the time of occurrence there was no particular
load.
opensips stopped processing the load. And in the logs I saw these messages
Feb 26 22:03:58 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker:
timer task <ds-pinger> already scheduled for 88872160 ms (now 88902760 ms), it
may overlap..
Feb 26 22:03:59 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker:
timer task <ds-pinger> already scheduled for 88872160 ms (now 88903750 ms), it
may overlap..
Feb 26 22:04:00 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker:
timer task <ds-pinger> already scheduled for 88872160 ms (now 88904740 ms), it
may overlap..
Feb 26 22:04:01 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker:
timer task <ds-pinger> already scheduled for 88872160 ms (now 88905720 ms), it
may overlap..
Feb 26 22:04:02 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker:
timer task <ds-pinger> already scheduled for 88872160 ms (now 88906710 ms), it
may overlap..
Feb 26 22:04:03 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker:
timer task <ds-pinger> already scheduled for 88872160 ms (now 88907700 ms), it
may overlap..
if it helps, I use 64 mb for shared memory, 4 mb for pkg memory , and 4
children
--
Oleg Podguyko
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
