[asterisk-users] Strange and complete failure of Asterisk 1.8

[Duncan Turnbull]

DNS failure could do this

Asterisk used to get stuck in a symmetric DNS request wait state which meant everything ground to a halt as it waited for a reply while DNS timed out.

The recommended option was either ip only or a DNS proxy that failed fast this letting asterisk continue 

Cheers Duncan 



> On 27/05/2015, at 11:55 pm, Stefan Viljoen <viljoens at verishare.co.za> wrote:
> 
> Hi all
> 
> We've had a very strange failure on an Asterisk 1.8 install that has been
> running for about a year at a customer site.
> 
> The physical hardware is fine, all other services off the Centos 6.5 server
> are running. Only Asterisk is not working...
> 
> The first symptom was that no calls can be made over the SIP phones used
> with it, and no calls could be received over the SIP trunk connected to it.
> 
> I checked and noted that 
> 
> sip show peers
> 
> in the CLI would either do nothing (e. g. just show asterisk*cli> again,
> with no response) or it would return only this:
> 
> asterisk*CLI> sip show peers
> Name/username              Host                                    Dyn
> Forcerport ACL Port     Status
> asterisk*CLI>
> 
> A module show like sip also does literally nothing, just
> 
> asterisk*cli> module show like sip
> asterisk*CLI>
> 
> Soon after this, I lost the capacity to get any response if I do an asterisk
> -r on the commandline - it would just hang indefintely.
> 
> Did a reboot, and then, I couldnt start asterisk at all - entering
> 
> # asterisk
> 
> would also just hang.
> 
> So, I recompiled asterisk from source and reinstalled the executable and all
> the module files. Still the same.
> 
> I happened to have an older asterisk executable from a few months before
> laying around and sha256summed it - and there was a difference in the
> checksum vs. the non-working asterisk binary - BUT it turned out that the
> newly recompiled asterisk binary has the SAME SHA256 checksum as the
> non-working asterisk binary.
> 
> System seems fine otherwise, nothing relevant in /var/log/messages or dmesg
> indicating a hardware failure. /var/log/asterisk/messages also contains no
> strange warnings or errors.
> 
> Anybody got any idea why I cannot resuscitate my Asterisk install, even
> after recompiling it from scratch from source? Why would asterisk die like
> this in the first place?
> 
> Thanks
> 
> 
> -- 
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>               http://www.asterisk.org/hello
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users