[asterisk-users] Asterisk just stops working...

[Steve Totaro]

Maybe you should play around with FreeSwitch.  It was written because
of deadlocks and the issues that have been around since the the
beginning....

http://www.freeswitch.org/node/117

"That's when I first heard it. That word. The one I can never forget, deadlock.

That was the first time, but it wasn't the last. I learned all about
the GNU debugger that day and it was just the first of many incidents.
Deadlock in the queue app. Deadlock in the manager, Avoiding Deadlock
on my console. It was starting to get to me a little but I kept going.
By this time I was also quite familiar with the term Segmentation
Fault another foe to the computer developer. After about a year's time
wrestling with bugs I found myself a lot more well-versed in the C
programming language than I even imagined and near Jedi caliber
debugging skills.

...We've all seen the infamous "Avoiding initial deadlock" message
which essentially is an attempt to lock a channel 10 times and if
still won't lock, just go ahead and forget about the lock."

Thanks,
Steve Totaro

On Thu, May 29, 2008 at 9:19 AM, Mark Hamilton <mark.h at cage151.com> wrote:
> You're right Steve.
> It's always been around.. and I think it's being ignored or simply can't be
> fixed, or I have no idea what it is. The bug is receiving trickles of
> response from the developers.
>
> It is so critical, I crash left and right every other day right now and I
> don't know where to turn to. There's no response, and my hands are getting
> sweaty.
>
> -----Original Message-----
> From: asterisk-users-bounces at lists.digium.com
> [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Steve Totaro
> Sent: May 28, 2008 11:46 AM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: Re: [asterisk-users] Asterisk just stops working...
>
> On Wed, May 28, 2008 at 10:44 AM, Nicolas Ross
> <rossnick-lists at cybercat.ca> wrote:
>>> The best approach is compile it with debug options, (make menuselect),
>>> set the compile to DEBUG on, then make clean, make, make install.
>>>
>>> THen, fire up under the debugger. When you're all locked up, use ^C to
>>> halt and leave the debugger in command, and do the "thread apply all bt"
>>> thing. That should be revealing.
>>
>> Thanks,
>>
>> I'm not that much a developper. So I'll recompile with DEBUG_CHANNEL_LOCKS
>> and DEBUG_THREADS.
>>
>> How do I start it up ? I curently start asterisk with redhat-style script
> in
>> /etc/rc.d, with safe_asterisk I think...
>>
>> Thanks,
>>
>> Nicolas
>>
>
> BTW, not sure what it is worth but this has been an issue in Asterisk
> since early 1.2.  I always just worked around it since it was a minor
> nuisance.
>
> Just an observation, but it seemed that if I did not issue reloads or
> keep a connection to the Asterisk CLI, the issue would not occur.  I
> don't know if that is fact or just imagination...
>
> Thanks,
> Steve Totaro
>
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>
>
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>