[OpenSIPS-Users] CRITICAL:core:sig_alarm_abort: BUG - shutdown timeout triggered, dying...

[Bogdan-Andrei Iancu]

Hi Josip,

Please send me the sipp scripts and how exactly to use it (I know how to 
use sipp) in order to get your scenario.

Regards,
Bogdan

Josip Djuricic wrote:
> Hi Bogdan,
>
> yes, I have noticed in the trunk I've tested that even though registrations expires, and opensips removes it, and opensipsctl moni shows them under: usrloc:location-expires, and usrloc:location-contacts keeps getting lower by those usrloc:location-expires numbers. But usrloc:registered_users and usrloc:location_users keep rising constantly. And the memory usage also keeps rising constantly until I get out of shared memory.
>
> This only seams to happen when contact's expires, if re register comes in before timeout expires the memory stops rising.
>
> I've tested this with sipp and 100 000 users registering with 20 minutes expiration time, and 40-60 registrations per second. Going on and on...after few ours, no more shared memory available.
>
> I can send you any other detail you require? Also I can send you config and sipp scenario file?
>
> Best regards,
>
> Josip
>
>
>
> -----Original Message-----
> From: users-bounces at lists.opensips.org [mailto:users-bounces at lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu
> Sent: Tuesday, December 22, 2009 10:28 AM
> To: OpenSIPS users mailling list
> Subject: Re: [OpenSIPS-Users] CRITICAL:core:sig_alarm_abort: BUG - shutdown timeout triggered, dying...
>
> Hi Josip,
>
> So, what you are saying is that trunk has a problem (versus 1.6) - some 
> records do not expire .....
>
> Could you detail a bit the way I could reproduce this scenario ?
>
> Known bugs are listed on the tracker - 
> http://www.opensips.org/Development/Tracker
>
> Regards,
> Bogdan
>
> Josip Djuricic wrote:
>   
>> Hi Bogdan,
>>
>> I've had to swithch to v1.6 stable, so It's working now :)
>>
>> What I notice is that on trunk version I had this
>> UsrLoc Stats:
>> usrloc:registered_users = 387432
>> usrloc:location-users = 387432
>> usrloc:location-contacts = 12005
>> usrloc:location-expires = 375427
>>
>> but on stable 1.6 I have this:
>> UsrLoc Stats:
>> usrloc:registered_users = 12005
>> usrloc:location-users = 12005
>> usrloc:location-contacts = 12005
>> usrloc:location-expires = 375427
>>
>> And I can confirm that memory is now stable, I think it seg faulted because at that ime it has gone 10 times trough 100000users registration, what means usrloc:registered_users had more than 1 000 000 users, that could explain what happened. Somehow I think it was not clearing registered users no matter they expired and was deleted from db.
>>
>> Perhaps you can confirm that you can reproduce this problem?
>>
>> Also is there a possibility to get list of known limitations or perhaps bugs on v1.6 that I should be aware of (concerning stability issues before puttying the system in production use)? I know you mentioned release 1.6.1, so what should be important fixes you mentioned in that mail?
>>
>> Once again sorry for lot of questions.
>>
>> Thanks,
>>
>> Josip
>>
>>
>> -----Original Message-----
>> From: users-bounces at lists.opensips.org [mailto:users-bounces at lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu
>> Sent: Friday, December 18, 2009 1:26 PM
>> To: OpenSIPS users mailling list
>> Subject: Re: [OpenSIPS-Users] CRITICAL:core:sig_alarm_abort: BUG - shutdown timeout triggered, dying...
>>
>> Hi Josip,
>>
>> A key question - how many records do you have in usrloc?
>>
>> I'm asking because opensips is flushing the usrloc at shutdown and if 
>> you have too many records, this will take some time. Also, the shutdown 
>> time is control by an alarm (couple of seconds), so if the shutdown 
>> takes too long, the alarm will simply kill opensips.
>>
>> Regards,
>> Bogdan
>>
>> Josip Djuricic wrote:
>>   
>>     
>>> Hi,
>>>
>>> this is what happened tonight on trunk version of opensips. Any ideas?
>>>
>>> This is from log, I'm including backtrace also:
>>>