[asterisk-users] Asterisk 1.2.12.1 dies after asterisk -rx and never comes up again

[Tzafrir Cohen]

On Wed, Oct 11, 2006 at 11:25:08AM +0200, Remco Barendse wrote:
> On Wed, 11 Oct 2006, Tzafrir Cohen wrote:
> 
> > On Wed, Oct 11, 2006 at 09:14:55AM +0200, Remco Barendse wrote:
> > > Hi list!
> > > 
> > > I recently upgraded to FreePBX 2.1.3 although I am not sure if this has 
> > > something to do with it.
> > > 
> > > I do a nightly restart of Asterisk, just in case. 
> > 
> > Why?
> 
> Sometimes the internet connection is dropped and asterisk doesn't do a dns 
> lookup and provider re-rest quickly enough so all calls are going out via 
> expensive ISDN.

So detect a connection change and then restart, by the way of 'asterisk
-rx restart now' (or 'restart when convinient', depending on whether you
care about local calls or remote calls). Assuming a restart is really
needed, rather than a reload.

A simple nightly restart means that on the avarage you'll be half a day
too late. 

How can you detect that both (a) DNS lookup failed with Asterisk and (b)
DNS lookup is already OK elsewhere?

> 
> Also I sometimes seem to have some trouble after re-loading FreePBX too 
> often I get things like extensions being marked as busy/not available.
> 
> > > = Parsing '/etc/asterisk/manager.conf': Found
> > > Oct 11 01:05:01 WARNING[6546] manager.c: Unable to bind socket: Address 
> > > already in use
> > 
> > Asterisk is already running.
> 
> I don't think so, asterisk -r will throw me an error that * is not 
> running. If * would be running I would get console I guess?

Maybe asterisk is in some sort of restart loop?

> 
>  
> > Probably the wonders , or a misuse of- safe_asterisk.
> > 
> > Alternatively, 
> > 
> > 
> > netstat -lntp | grep 5038
> 
> Thanks, I'll try that when the problem occurs again

-- 
Tzafrir Cohen         sip:tzafrir at local.xorcom.com
icq#16849755          iax:tzafrir at local.xorcom.com
+972-50-7952406          jabber:tzafrir at jabber.org
tzafrir.cohen at xorcom.com     http://www.xorcom.com