[asterisk-users] Asterisk just stops working...
Steve Totaro
stotaro at totarotechnologies.com
Fri May 30 09:49:08 CDT 2008
That is because they are busy with commas and pipes as delimiters and
deprecating things that "just work" the way they are....
You know, the things that really matter. The dealbreakers. The
things that make "Asterisk Ready".
Thanks,
Steve Totaro
On Fri, May 30, 2008 at 10:43 AM, Mark Hamilton <mark.h at cage151.com> wrote:
> Al,
>
> Either way, it doesn't matter. Because when the gdb is submitted afterall,
> there is still nothing going on Mantis to try and fix it.
>
> For example, look at my deadlock issue I've reported - definitely critical.
> And as you say it should be included in the "Next best thread that asks is
> asterisk ready?" because this critical bug that I've filed has hardly
> garnered any attention from the devels.
>
> Mark.
>
> -----Original Message-----
> From: asterisk-users-bounces at lists.digium.com
> [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Al Baker
> Sent: May 29, 2008 4:25 AM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: Re: [asterisk-users] Asterisk just stops working...
>
> Quote
>
> 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.
>
> If I may suggest , what would REALLY be 'Revealing' is if you could be
> just a bit more clear in your explanation and about 900% LESS in the
> techno babble.
> While the thought is in the Right Place do you REALLY expect anybody to
> know what the hell you mean by :
>
> 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
>
>
> *Just a thought*
>
> Sherwood McGowan wrote:
>> Steve Murphy wrote:
>>
>>> On Tue, 2008-05-27 at 14:31 -0400, Nicolas Ross wrote:
>>>
>>>
>>>>> On Tue, 27 May 2008 13:11:22 -0400, Nicolas Ross wrote
>>>>>
>>>>>
>>>>>> Now, when my server begin not to respond, when I do a sip show peers,
> I
>>>>>> only
>>>>>> see a subset of the users, and not the summary line. If I do other
>>>>>> commands
>>>>>> like "core show channels", it simply shows nothing at all. Not even a
> "0
>>>>>> active channels". Reload, or any other similar commands goes
> unansered.
>>>>>> The
>>>>>> "core" works as it still answers calls on the PRI, but sip extensions
>>>>>> can't
>>>>>> be reached, etc.
>>>>>>
>>>>>>
>>>>> I have had asterisk do this if its hanging on a DNS request.. you got
> any
>>>>> peers in there
>>>>> using DNS?
>>>>>
>>>>>
>>>> I don,t beleive it's the case. I beleive asterisk would still answer to
> the
>>>> "core show channels" command if it were the case...
>>>>
>>>>
>>> Not necessarily! If the channels are locked while the holdup occurred,
>>> then, you won't be able to even look at them.
>>>
>>>
>>>
>>>> The clients (phones) are configured to register with a fqdn domain. The
>>>> peers are type=friend, host-dynamic.
>>>>
>>>> I did change some changes to my dialplan so that I don't use queues and
>>>> agents anymore... We'll see if it happens again.
>>>>
>>>> By the way, my asterisk doesn't crash, I don't have a core dump. And
> since
>>>> core show locks doesn't provide anything when I'm in that situation, how
>
>>>> could I contribute ?
>>>>
>>>>
>>>>
>>> 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.
>>>
>>> murf
>>>
>>>
>>>
>>>> Thanks,
>>>>
More information about the asterisk-users
mailing list