[Devel] WARNING: set_timer called on a "detached" timer - OpenSER stops forwarding

[Martin Koenig]

Hi Bogdan,

I've increased the debug level to 7, now in addition I see a lot of

May 26 13:24:04 /sbin/openser[21881]: WARNING:vqm_resize: resize(0) called
May 26 13:24:04 /sbin/openser[21903]: WARNING:vqm_resize: resize(0) called
May 26 13:24:10 /sbin/openser[21885]: WARNING:vqm_resize: resize(0) called
May 26 13:25:07 /sbin/openser[21893]: WARNING:vqm_resize: resize(0) called
May 26 13:28:01 /sbin/openser[21903]: WARNING:vqm_resize: resize(0) called
May 26 13:28:02 /sbin/openser[21881]: WARNING:vqm_resize: resize(0) called
May 26 13:28:03 /sbin/openser[21898]: WARNING:vqm_resize: resize(0) called
May 26 13:28:03 /sbin/openser[21885]: WARNING:vqm_resize: resize(0) called 

Is this related?

Best regards,
Martin

> -----Original Message-----
> From: Bogdan-Andrei Iancu [mailto:bogdan at voice-system.ro] 
> Sent: Friday, May 26, 2006 9:38 AM
> To: Martin Koenig
> Cc: devel at openser.org
> Subject: Re: [Devel] WARNING: set_timer called on a 
> "detached" timer - OpenSER stops forwarding
> 
> Hi Martin,
> 
> the warning is due a race condition in timer processing. A 
> transaction 
> was detached from the timer list by the timer process which is 
> processing it for expire even; in the same time, another process was 
> computing the transaction (maybe a reply was received) and 
> it's trying 
> to place it back into timer....and this is the race.
> 
> Do you have any idea what scenario leads in your case to the race? we 
> can try to minimize the race window...
> 
> I will also try to add some more debug info when the race occurs.
> 
> Thanks and regards,
> Bogdan
> 
> Martin Koenig wrote:
> 
> >Hello all,
> >
> >now for the second time in two weeks, OpenSER stopped forwarding SIP
> >messages after the log message:
> >
> >WARNING: set_timer called on a "detached" timer -- ignoring: 
> 0xa80c7b40
> >
> >This is message is present more often:
> >
> >May 15 10:49:04 abc /sbin/openser[6552]: WARNING: set_timer 
> called on a
> >"detached" timer -- ignoring: 0xa80b4278
> >May 15 10:52:37 abc /sbin/openser[6552]: WARNING: set_timer 
> called on a
> >"detached" timer -- ignoring: 0xa80b1d38
> >May 15 10:58:46 abc /sbin/openser[6552]: WARNING: set_timer 
> called on a
> >"detached" timer -- ignoring: 0xa80c0548
> >May 15 11:01:17 abc /sbin/openser[6552]: WARNING: set_timer 
> called on a
> >"detached" timer -- ignoring: 0xa80abee8
> >May 15 11:07:13 abc /sbin/openser[6552]: WARNING: set_timer 
> called on a
> >"detached" timer -- ignoring: 0xa80bc870
> >May 15 11:27:06 abc /sbin/openser[6552]: WARNING: set_timer 
> called on a
> >"detached" timer -- ignoring: 0xa80b7410
> >May 15 12:05:13 abc /sbin/openser[6552]: WARNING: set_timer 
> called on a
> >"detached" timer -- ignoring: 0xa80bb358
> >May 15 12:31:43 abc /sbin/openser[6552]: WARNING: set_timer 
> called on a
> >"detached" timer -- ignoring: 0xa80c9480
> >May 15 13:01:30 abc /sbin/openser[6552]: WARNING: set_timer 
> called on a
> >"detached" timer -- ignoring: 0xa80c7b40
> >May 15 13:16:03 abc /sbin/openser[6552]: WARNING: set_timer 
> called on a
> >"detached" timer -- ignoring: 0xa80c3ac0
> >May 15 13:18:17 abc /sbin/openser[6552]: WARNING: set_timer 
> called on a
> >"detached" timer -- ignoring: 0xa80c6b10
> >
> >OpenSER is obviously not crashing every time it occurs. 
> Version is 1.0.0.
> >
> >Is this a known problem that can be solved by upgrading to 1.0.1?
> >
> >Best regards,
> >Martin
> >
> >
> >_______________________________________________
> >Devel mailing list
> >Devel at openser.org
> >http://openser.org/cgi-bin/mailman/listinfo/devel
> >
> >  
> >
> 
>