when I issue an '/etc/init.d/asterisk start' or 'service asterisk start' command, nothing happens, except for the single process 'astcanary /var/run/asterisk/alt.asterisk.canary.tweet.tweet.tweet 21756' briefly visible in the 'ps ax' output.
I checked /var/log/messages, syslog, daemon.log, asterisk/messages - there is nothing whatsoever.
I can run asterisk normally, and if I issue part of
I need to be able to collect core dumps, but since Asterisk's CWD is / (so claims procfs), it'll never be able to write them. I've confirmed my suspicions by allowing world write to / and SIGABRT the process, lo and behold, I had a core.
I can obviously use core_pattern to override system-wide, but I rather like the default behavior of dumping core to the cwd.
I am using Asterisk 184.108.40.206 and a MySQL database connected via ODBC to store CDRs. When my MySQL database isn't available when Asterisk starts or has an outage while Asterisk is running, I would expect Asterisk to retry to connect to the database, but this doesn't happen!