[asterisk-users] Permanent restart after upgrade

[Steve Totaro]

On Thu, Jun 9, 2011 at 7:32 PM, Steve Edwards <asterisk.org at sedwards.com> wrote:
> On Thu, 9 Jun 2011, Hans Witvliet wrote:
>
>> I went originally from a almost working machine running:
>> asterisk180-1.8.3.2-87.1
>>
>> To a machine that continuously restarts asterisk (+core dumps) running:
>> asterisk180-1.8.3-85.2
>
> Any chance you have a mix of Asterisk and module versions? Was Zaptel/Dahdi
> compiled with the proper set of headers for your kernel?
>
> Can you start Asterisk from the command line instead of the usual startup
> script? What do the first couple of errors look like? Capturing the output
> via the 'script' command will help.
>
> For example*,
>
>        script foo
>        sudo /usr/sbin/asterisk -C /etc/asterisk/asterisk.conf\
>                -c -d -d -d -f -g -n -p -q -v -v -v
>        exit
>
> Can you turn off auto module loading and start with no modules?
>
> *) I'm a 1.2 Luddite, so the command line arguments may have changed...
>
> --
> Thanks in advance,
> -------------------------------------------------------------------------
> Steve Edwards       sedwards at sedwards.com      Voice: +1-760-468-3867 PST
> Newline                                              Fax: +1-760-731-3000
>

I am mostly a 1.2 guy myself.

Kill safe_asterisk wherever that is being loaded so it stops trying to
start over and over.

I would start with a whole system update and reboot.  Then I would
build everything from source, make sure to whack all of the modules
before doing a menuselect and selecting the modules you need in
Asterisk and then compile.

Generally, when I see this, it is a module problem after an upgrade.
Delete all the modules as I said, only select the modules  you need.
compile Asterisk.  Look at the verbose when starting asterisk with
-vvvvv.  It will generally show you what the offending module is, the
logs just as useful if not more.

Edit your modules.conf  to correct the problem.

When you start Asterisk from the command line with verbose, you should
see where or what module is failing.  Asterisk log files are also very
useful.

My final piece of advice is not to use bleeding edge versions of
Asterisk unless they can make coffee too.

1.2 works great for all of my installations.  T38 support forced me to
use 1.6.x a couple of times.  Since I purchased licensees for FAX for
Asterisk, I expected some support from Digium.  After months of no
answers from Digium or the community, I ditched it and took a big lump
from the company I was working for at the time.

FAX was extremely important to them, each user got a DID for voice and
a DID for FAX.  It worked Ok over TDM PRIs but not SIP.

This was a direct 100meg cross connect from Level 3's cage to our cage
at Equinix in Ashburn VA.

I finally got a refund but nothing could make up for the lost trust in
me from the staff.

1.2 it is.

Thanks,
Steve Totaro