[asterisk-users] How to debug this specific issue?
tlesher at digium.com
Wed Aug 25 12:13:19 CDT 2010
On Wednesday 25 August 2010 11:38:27 Steve Davies wrote:
> On 25 August 2010 08:22, Matt Riddell <lists at venturevoip.com> wrote:
> > On 25/08/10 7:20 PM, Tilghman Lesher wrote:
> >>> I really thought that the canary should have sounded if Asterisk got in
> >>> a loop - or maybe that only happens with high priority?
> >> The canary only runs in high priority mode, and it's only able to do
> >> anything if high priority scheduling is the culprit. If it's something
> >> else, like memory swapping, there's nothing the canary can do to fix
> >> that.
> > Aha, explains why I've never seen the canary die :D
> ...and yes, I was running in high priority mode - I thought I was
> turning it off for testing, but looks like I left the setting in
> asterisk.conf so leaving '-p' off the command line was making no
> difference *sigh*
So in this case, the canary actually saved you from needing to reboot the
machine in order to recover from the lockup. The thread monitoring the canary
noticed within 60 seconds that the canary stopped updating the file and
deprioritized Asterisk, allowing the other processes to proceed.
Digium, Inc. | Senior Software Developer
twitter: Corydon76 | IRC: Corydon76-dig (Freenode)
Check us out at: www.digium.com & www.asterisk.org
More information about the asterisk-users