Asterisk suddenly stopped

[ctc_olsen]

I've been digging for the cause of this but it simply stopped after months of usage. I got the error when I do asterisk -vvvvvr.

Unable to connect to remote asterisk (does /var/run/asterisk.ctl exist?)

asterisk.ctl is there when I checked this. I did a reboot and the problem went away. Does anyone know what could have caused this issue?

[ctc_olsen]

Anyone please?

[geoff3dmg]

I've had this happen on my systems where:

a) Asterisk crashes
b) Asterisk never starts due to slow networking at boot.

Either way, on newer SVN releases you can go into Admin -> Servers and set 'Auto-Restart Asterisk' to 'Y' to get round the issue.

[ctc_olsen]

Thank you for the response. Do you know by any chance on which logfile I could look at to check what happened during this time(when it stopped)? /var/log/messages doesn't seem to give me anything and /var/log/asterisk/messages on stores messages for the past 24H.

[geoff3dmg]

1) You can check in the log rotated syslog/asterisk logs. They should be in the same place as the current logs but with a date in the file name.
2) You can check if a service failed to start by asking systemd, for example for the Vicidial start up (which includes asterisk) run this: ' systemctl status vicidial.service'

[ctc_olsen]

Thanks for the input Geoff.

[williamconley]

Excellent geoff3dmg.

On an added note, it is possible to rotate the asterisk logs in the CLI as soon as you start it up (or at any time really) by issuing "logger rotate" in the asterisk cli or (asterisk -rx 'logger rotate") from the linux cli. This could give you the ability to peruse the prior logs at your leisure by starting a new log set.

But upgrading Vicidial to get the auto-restart function is a very good idea if this happens more than once.