[Asterisk-Users] Mutex problem in sip?

[Alex Zarubin]

Well, I think it is a problem because eventually mutex doesn't get released
and all the threads sit (in restart_monitor) forever. We've seen it several
times, along with the messages like

NOTICE[6151]: File sched.c, Line 209 (sched_settime): Request to schedule in
the past?!?
!
NOTICE[6151]: File sched.c, Line 209 (sched_settime): Request to schedule in
the past?!?
!

Anything we can do to help locate the problem?

Thank you.
Alex Zarubin

-----Original Message-----
From: Martin Pycko [mailto:martinp at digium.com]
Sent: Friday, August 01, 2003 2:28 PM
To: 'asterisk-users at lists.digium.com'
Subject: Re: [Asterisk-Users] Mutex problem in sip?


It doesn't look like a problem. It's that when you have so many calls ...
execution of some piece of code protected by mutex takes longer so it
happens that some calls wait for their time ..... I guess if you have too
many of those messages you should disable them.

regards
Martin

On Thu, 31 Jul 2003, Alex Zarubin wrote:

> Hello,
>
> CVS 07/31/03. Test with 130+ PSTN-to-SIP calls. Asterisk gets locked ...
>
> grep -e "Error" -e "eventually" p-console
>
> chan_sip.c line 1453 (sip_alloc): Error obtaining mutex: Device or
resource
> busy
> chan_sip.c line 1453 (sip_alloc): Got it eventually...
> chan_sip.c line 1453 (sip_alloc): Error obtaining mutex: Device or
resource
> busy
> chan_sip.c line 1453 (sip_alloc): Got it eventually...
> chan_sip.c line 1453 (sip_alloc): Error obtaining mutex: Device or
resource
> busy
> chan_sip.c line 1453 (sip_alloc): Got it eventually...
> chan_sip.c line 1453 (sip_alloc): Error obtaining mutex: Device or
resource
> busy
> chan_sip.c line 1453 (sip_alloc): Got it eventually...
> chan_sip.c line 1453 (sip_alloc): Error obtaining mutex: Device or
resource
> busy
> chan_sip.c line 1453 (sip_alloc): Got it eventually...
> chan_sip.c line 4980 (do_monitor): Error obtaining mutex: Device or
resource
> busy
> chan_sip.c line 4980 (do_monitor): Got it eventually...
> chan_sip.c line 4980 (do_monitor): Error obtaining mutex: Device or
resource
> busy
> chan_sip.c line 4980 (do_monitor): Got it eventually...
> chan_sip.c line 4980 (do_monitor): Error obtaining mutex: Device or
resource
> busy
> chan_sip.c line 4980 (do_monitor): Got it eventually...
> chan_sip.c line 4980 (do_monitor): Error obtaining mutex: Device or
resource
> busy
> chan_sip.c line 4980 (do_monitor): Got it eventually...
> chan_sip.c line 1453 (sip_alloc): Error obtaining mutex: Device or
resource
> busy
> chan_sip.c line 1453 (sip_alloc): Got it eventually...
> chan_sip.c line 1453 (sip_alloc): Error obtaining mutex: Device or
resource
> busy
> chan_sip.c line 1453 (sip_alloc): Got it eventually...
> chan_sip.c line 1453 (sip_alloc): Error obtaining mutex: Device or
resource
> busy
> chan_sip.c line 1453 (sip_alloc): Got it eventually...
> chan_sip.c line 1453 (sip_alloc): Error obtaining mutex: Device or
resource
> busy
> chan_sip.c line 1453 (sip_alloc): Error obtaining mutex: Device or
resource
> busy
> chan_sip.c line 1453 (sip_alloc): Error obtaining mutex: Device or
resource
> busy
> chan_sip.c line 1453 (sip_alloc): Got it eventually...
> chan_sip.c line 1453 (sip_alloc): Got it eventually...
> chan_sip.c line 1453 (sip_alloc): Got it eventually...
>
> .....
>
> chan_sip.c line 1453 (sip_alloc): Got it eventually...
> chan_sip.c line 4980 (do_monitor): Error obtaining mutex: Device or
resource
> busy
> chan_sip.c line 4980 (do_monitor): Got it eventually...
> chan_sip.c line 948 (sip_hangup): Error obtaining mutex: Device or
resource
> busy
> channel.c line 370 (ast_queue_frame): Error obtaining mutex: Device or
> resource busy
> chan_sip.c line 5044 (restart_monitor): Error obtaining mutex: Device or
> resource busy
> chan_sip.c line 5044 (restart_monitor): Error obtaining mutex: Device or
> resource busy
> chan_sip.c line 5044 (restart_monitor): Error obtaining mutex: Device or
> resource busy
> chan_sip.c line 5044 (restart_monitor): Error obtaining mutex: Device or
> resource busy
> chan_sip.c line 5044 (restart_monitor): Error obtaining mutex: Device or
> resource busy
> chan_sip.c line 5044 (restart_monitor): Error obtaining mutex: Device or
> resource busy
> chan_sip.c line 5044 (restart_monitor): Error obtaining mutex: Device or
> resource busy
> chan_sip.c line 5044 (restart_monitor): Error obtaining mutex: Device or
> resource busy
> chan_sip.c line 5044 (restart_monitor): Error obtaining mutex: Device or
> resource busy
> chan_sip.c line 5044 (restart_monitor): Error obtaining mutex: Device or
> resource busy
> chan_sip.c line 5044 (restart_monitor): Error obtaining mutex: Device or
> resource busy
> chan_sip.c line 5044 (restart_monitor): Error obtaining mutex: Device or
> resource busy
> chan_sip.c line 5044 (restart_monitor): Error obtaining mutex: Device or
> resource busy
> chan_sip.c line 5044 (restart_monitor): Error obtaining mutex: Device or
> resource busy
>
> Thank you.
>
> Alex Zarubin
> Webley Systems, Inc.
>
>
>

_______________________________________________
Asterisk-Users mailing list
Asterisk-Users at lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20030806/1429695c/attachment.htm