[OpenSIPS-Users] WARNING:core:timer_ticker: timer task <ds-pinger>
Oleg Podguyko
podguiko at mail.ru
Tue Mar 3 12:36:34 EST 2020
Hi Bogdan
I used:
modparam("dispatcher", "ds_ping_interval", 30)
>Вторник, 3 марта 2020, 15:26 +03:00 от Bogdan-Andrei Iancu <bogdan at opensips.org>:
>
>Hi Oleg,
>
>OK, I see that slowly there is a progress on that timer task. Based on the numbers, I see a ~40sec overrun for the timer task. How often do you send the OPTIONS pings in dispatcher?
>
>Regards,
>Bogdan-Andrei Iancu
>
>OpenSIPS Founder and Developer
> https://www.opensips-solutions.com
>OpenSIPS Summit, Amsterdam, May 2020
> https://www.opensips.org/events/Summit-2020Amsterdam/
>
>
>On 2/28/20 1:48 PM, Oleg Podguyko wrote:
>>
>>It was just part of the log. Here is the whole log and scheduled value is changing
>>
>>
>>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..
>>Feb 26 22:04:04 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 88872160 ms (now 88908690 ms), it may overlap..
>>Feb 26 22:04:05 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 88872160 ms (now 88909690 ms), it may overlap..
>>Feb 26 22:04:06 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 88872160 ms (now 88910680 ms), it may overlap..
>>Feb 26 22:04:07 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 88872160 ms (now 88911670 ms), it may overlap..
>>Feb 26 22:09:37 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 89212210 ms (now 89241900 ms), it may overlap..
>>Feb 26 22:09:38 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 89212210 ms (now 89242810 ms), it may overlap..
>>Feb 26 22:09:39 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 89212210 ms (now 89243800 ms), it may overlap..
>>Feb 26 22:09:40 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 89212210 ms (now 89244790 ms), it may overlap..
>>Feb 26 22:09:41 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 89212210 ms (now 89245780 ms), it may overlap..
>>Feb 26 22:09:42 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 89212210 ms (now 89246770 ms), it may overlap..
>>Feb 26 22:09:43 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 89212210 ms (now 89247770 ms), it may overlap..
>>Feb 26 22:09:44 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 89212210 ms (now 89248760 ms), it may overlap..
>>Feb 26 22:09:45 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 89212210 ms (now 89249750 ms), it may overlap..
>>Feb 26 22:09:46 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 89212210 ms (now 89250740 ms), it may overlap..
>>Feb 26 22:09:47 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 89212210 ms (now 89251730 ms), it may overlap..
>>Feb 26 23:05:48 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 92582480 ms (now 92612090 ms), it may overlap..
>>Feb 26 23:05:48 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 92582480 ms (now 92613000 ms), it may overlap..
>>Feb 26 23:05:49 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 92582480 ms (now 92613990 ms), it may overlap..
>>Feb 26 23:05:50 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 92582480 ms (now 92614980 ms), it may overlap..
>>Feb 26 23:05:51 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 92582480 ms (now 92615970 ms), it may overlap..
>>Feb 26 23:05:52 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 92582480 ms (now 92616960 ms), it may overlap..
>>Feb 26 23:05:53 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 92582480 ms (now 92617950 ms), it may overlap..
>>Feb 26 23:05:54 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 92582480 ms (now 92618940 ms), it may overlap..
>>Feb 26 23:05:55 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 92582480 ms (now 92619930 ms), it may overlap..
>>Feb 26 23:05:56 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 92582480 ms (now 92620920 ms), it may overlap..
>>Feb 26 23:05:57 xx-spx-2 /usr/sbin/opensips[8379]: WARNING:core:timer_ticker: timer task <ds-pinger> already scheduled for 92582480 ms (now 92621920 ms), it may overlap..
>>
>>
>>
>>>Пятница, 28 февраля 2020, 14:12 +03:00 от Bogdan-Andrei Iancu <bogdan at opensips.org> :
>>>
>>>Actually, looking closer, I see that the "already scheduled" time reported by the ds-pinger never increases, it is stuck to 88872160 . Is this going for ever, with the same scheduled value, never changing, even if running for hours ?
>>>Bogdan-Andrei Iancu
>>>
>>>OpenSIPS Founder and Developer
>>> https://www.opensips-solutions.com
>>>OpenSIPS Summit, Amsterdam, May 2020
>>> https://www.opensips.org/events/Summit-2020Amsterdam/
>>>
>>>
>>>On 2/28/20 1:04 PM, Oleg Podguyko wrote:
>>>>Hi Bogdan,
>>>>
>>>>- my dispatcher table contains 167 lines
>>>>- all of them are defined as IPs
>>>>- 3 destinaitions via UDP and 163 via SCTP.
>>>>
>>>>>Пятница, 28 февраля 2020, 12:42 +03:00 от Bogdan-Andrei Iancu <bogdan at opensips.org> :
>>>>>
>>>>>Hi Oleg,
>>>>>
>>>>>The "ds-pinger" is the dispatcher's task for generating the probing pings to the destinations. And it seems it takes a lot of time to this task to do its job (and it has nothing to do with the traffic you have on your opensips).
>>>>>
>>>>>So, the destinations in dispatcher:
>>>>>- how many they are ?
>>>>>- are they defined as FQDN or IPs ?
>>>>>- are they via UDP or TCP/TLS ?
>>>>>
>>>>>Regards,
>>>>>Bogdan-Andrei Iancu
>>>>>
>>>>>OpenSIPS Founder and Developer
>>>>> https://www.opensips-solutions.com
>>>>>OpenSIPS Summit, Amsterdam, May 2020
>>>>> https://www.opensips.org/events/Summit-2020Amsterdam/
>>>>>OpenSIPS Bootcamp, Miami, March 2020
>>>>> https://opensips.org/training/OpenSIPS_Bootcamp_2020/
>>>>>
>>>>>
>>>>>On 2/27/20 12:14 PM, Oleg Podguyko via Users wrote:
>>>>>>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
>>>>>>Users at lists.opensips.org
>>>>>>http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>>
>>>>
>>>>
>>>>--
>>>>Олег Подгуйко
>>>>
>>
>>
>>--
>>Олег Подгуйко
>>
>>
--
Олег Подгуйко
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20200303/2c078263/attachment-0001.html>
More information about the Users
mailing list