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
    <[email protected]>:
    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
    [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

Reply via email to