[asterisk-users] Permanent restart after upgrade

[Steve Totaro]

On Fri, Jun 10, 2011 at 1:48 AM, Hans Witvliet <hwit at a-domani.nl> wrote:
> On Thu, 2011-06-09 at 16:32 -0700, Steve Edwards 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...
>>
> No dahdi/zaptel involved.
> I'll be off to work in a while, report back later.
>
>
> hw
>

It amazes me when people run into a problem but refuse to post logs or
verbose when you start Asterisk.  Nothing meaninful.

I would wager a gentleman's bet that I can have your system working
just fine in a half hour or less (unless your bandwidth sucks).

If I do it, then you have to post to the list and you owe me a favor,
plus, in the future you have to help someone else.

If I don't, I have to post my failure to the list and I owe you a favor.

I have spare cycles, just let me know.

Thanks,
Steve Totaro