[asterisk-users] asterisk sudden restart - 1.4.18.1

[Leif Madsen]

das sandesh wrote:
> Hi,
> 
> Asterisk got stopped this morning after 20 minutes and phones went to 
> 'No Service' and then got started automatically after 20 min, as I could 
> see in the full log that asterisk got started at so and so time:
> [Feb 10 08:29:31] VERBOSE[31013] logger.c: Asterisk Event Logger Started 
> /var/log/asterisk/event_log
> [Feb 10 08:29:31] VERBOSE[31013] logger.c: Asterisk Dynamic Loader Starting:
> 
> But I am trying to find why did it stopped (and there was no record of 
> asterisk stopped?) and then get restarted.....In the log I could also see :
> 
> [Feb 10 08:02:05] VERBOSE[7027] logger.c:     -- Incoming call: Got SIP 
> response 500 "CSeq Number Out of order" back from 192.168.10.16
> [Feb 10 08:02:05] VERBOSE[7027] logger.c:     -- Incoming call: Got SIP 
> response 500 "CSeq Number Out of order" back from 192.168.10.16
> [Feb 10 08:02:05] VERBOSE[7027] logger.c:     -- Incoming call: Got SIP 
> response 500 "CSeq Number Out of order" back from 192.168.10.16
> [Feb 10 08:02:08] VERBOSE[7004] logger.c:     -- Remote UNIX connection
> [Feb 10 08:02:08] VERBOSE[28272] logger.c:     -- Remote UNIX connection 
> disconnected
> 
> During this period (from 8:02 till 8:29) all the phones went to 'No 
> Service'....I checked all the logs and could not find any reason why it 
> was down or any log that shows asterisk was down at that point......any 
> ideas are appreciated...

Check /tmp/ as there may be a core.##### file there which you could generate a 
backtrace from to determine the issue (if you're able to understand what is 
outputs :))

At the least, if such a core file exists, then you could line it up with the 
time to see if that was indeed the case. If there is a core file, it means 
something caused Asterisk to crash.

> Asterisk version: 1.4.18.1

This version is quite old, and if the issue was a crash that brought the system 
down momentarily, it is possible this issue may already be resolved.

Leif!