vicidial.org

Hi Guys,

Rookie question here, had asterisk not boot automatically this morning (system has been running fine for 6+ months). Not much information in journalctl, is there a better place to look for more indepth information? Service started fine when I manually ran service asterisk start and service vicidial start.

Jan 15 03:43:14 HOSTNAME systemd[1]: vicidial.service: Start operation timed out. Terminating.
Jan 15 03:43:14 HOSTNAME vicidial[1607]: Starting Asterisk...
Jan 15 03:43:14 HOSTNAME systemd[1]: Failed to start LSB: ViciDial Telephony Server.
Jan 15 03:43:14 HOSTNAME systemd[1]: vicidial.service: Unit entered failed state.
Jan 15 03:43:14 HOSTNAME systemd[1]: vicidial.service: Failed with result 'timeout'.

Vicibox 9.0.3
Asterisk 13.34.0-vici
VERSION: 2.14-760a
BUILD: 200701-1525

1) Do not start asterisk as a service. That will run asterisk outside Vicidial's control in the "asterisk" screen.

Test with:

Code: Select all

screen -r asterisk

If that fails, then asterisk is not in the expected Vicidial Screen and under Vicidial's control (and it does need to be). Stop the service and follow the instructions below for auto-start in case of failure.

2) Set the server to auto-start asterisk if it fails in Admin->Servers. This may be delayed if asterisk fails on boot, but it may start it a few minutes later and you may never notice.

3) Asterisk has its own logs. There may be information in the asterisk logs folder or even in the astguiclient log folder, although I don't think so.

4) If you've been running Vicidial for a long time and have made millions of calls, it may be a good idea to go through your asterisk modules and "noload" those you do not need. Especially the sqlite and cdrdb modules.

Happy Hunting!