[OpenSIPS-Users] Timer shift on dr-pinger
vladpaiu at opensips.org
Tue Mar 4 14:54:36 CET 2014
First of all, what kind of probing mode do you have defined ? (  )
Possible reasons are that either you are talking to your gateways via
TCP, and OpenSIPS is losing some time establishing new connections or
actually sending out SIP messages via TCP. You can set some thresholds
where OpenSIPS will warn you in case TCP gets slow, see .
Another possibility would be that you have your gateways defined as
FQDNs, and OpenSIPS is wasting lots of time doing DNS queries.You can
set some thresholds where OpenSIPS will warn you in case DNS gets slow,
On 02.03.2014 17:38, Remco wrote:
> Hi all,
> I'm experiencing timer shifts running OpenSIPS 1.9.
> The following message is in the logfile:
> Mar 2 06:49:15 [hostname] /usr/sbin/opensips:
> CRITICAL:core:timer_ticker: timer handler <dr-pinger> lasted (19910000
> us) for more than timer tick (1000000 us) -> potential timer shifting
> It seems that dr-pinger is experiencing some sort of delay which
> shifts the internal timer in the opensips process. Although the delays
> vary, they are not significantly increasing. After some time issues
> with processing traffic start to arise. Eventually some gateways are
> disabled by Drouting, although that takes a couple of hours.
> To me it seems that we have some sort of networking issue, what i
> cannot understand why drouting is causing the internal timers to
> shift. As the main function of the dr-pinger is to detect unreachable
> gateways and disable them. Perhaps someone has an idea what might be
> causing this behavior?
> Users mailing list
> Users at lists.opensips.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users