Quick Reference
Asterisk Not Running
What Causes This Error
The Asterisk process has stopped or crashed. This causes complete failure of all call processing — no outbound calls can be placed, no inbound calls can be received, and all active calls are dropped. Common causes include memory exhaustion, segmentation faults, codec issues, and failed Asterisk upgrades.
How to Fix It
-
1 Check Asterisk process: ps aux | grep asterisk
-
2 If not running, check logs for crash reason: tail -200 /var/log/asterisk/messages
-
3 Check system memory: free -h (Asterisk crashes on OOM)
-
4 Restart Asterisk: sudo systemctl restart asterisk
-
5 If restart fails, check for stale lock file: rm -f /var/run/asterisk/asterisk.pid then restart
-
After restart, verify it’s running: asterisk -rx ‘core show version’
-
Check trunk registrations: asterisk -rx ‘sip show registry’
How to Prevent It
Implement Asterisk crash monitoring with automatic restart (systemd watchdog or supervisord). Set up memory alerts at 80% threshold. Schedule regular server reboots during low-traffic windows. Keep Asterisk version pinned to avoid unplanned upgrades.
ViciStack’s free 30-day support plan includes unlimited live VICIdial troubleshooting. If you can’t resolve this error with the steps above, our engineers will connect to your system and fix it directly — no support tickets, no hourly billing.
Frequently Asked Questions
What causes the VICIdial "Asterisk Not Running" error? +
The Asterisk process has stopped or crashed. This causes complete failure of all call processing — no outbound calls can be placed, no inbound calls can be received, and all active calls are dropped. Common causes include memory exhaustion, segmentation faults, codec issues, and failed Asterisk upgrades.
How do I fix the VICIdial "Asterisk Not Running" error? +
Check Asterisk process: ps aux | grep asterisk Then: If not running, check logs for crash reason: tail -200 /var/log/asterisk/messages Then: Check system memory: free -h (Asterisk crashes on OOM) Then: Restart Asterisk: sudo systemctl restart asterisk Then: If restart fails, check for stale lock file: rm -f /var/run/asterisk/asterisk.pid then restart Then: After restart, verify it's running: asterisk -rx 'core show version' Then: Check trunk registrations: asterisk -rx 'sip show registry'
How can I prevent the "Asterisk Not Running" error in VICIdial? +
Implement Asterisk crash monitoring with automatic restart (systemd watchdog or supervisord). Set up memory alerts at 80% threshold. Schedule regular server reboots during low-traffic windows. Keep Asterisk version pinned to avoid unplanned upgrades.
Part of the Complete VICIdial Implementation Guide
Need Help Fixing This Error?
Our VICIdial experts can diagnose and resolve this issue quickly. Get a free performance audit and we'll identify all critical problems.
Get Your Free Audit →