Quick Reference
Agent Kick All Error
What Causes This Error
The ‘Kick All Agents’ function in VICIdial admin triggered an error. This function forces all agents offline and is used during emergency shutdowns or system maintenance. Errors occur when the underlying database update fails, active call channels conflict with the kick process, or permissions prevent the operation.
How to Fix It
-
1 Check VICIdial admin log for specific error message
-
2 Verify admin user has sufficient permissions for mass kick operations
-
3 Check MySQL connectivity: mysql -u cron -ptest -e ‘SELECT 1’
-
4 Manually reset agent sessions in database: UPDATE vicidial_live_agents SET status=‘PAUSED’ WHERE campaign_id=‘CAMPAIGN’
-
Check for active calls that may be blocking: asterisk -rx ‘core show channels’
-
6 If sessions are stuck, restart VICIdial web processes: sudo systemctl restart apache2
How to Prevent It
Use the graceful agent logout option when possible rather than forced kick. Test kick functionality during low-traffic periods. Document the kick procedure for managers who need to use it in emergencies.
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 "Agent Kick All Error" error? +
The 'Kick All Agents' function in VICIdial admin triggered an error. This function forces all agents offline and is used during emergency shutdowns or system maintenance. Errors occur when the underlying database update fails, active call channels conflict with the kick process, or permissions prevent the operation.
How do I fix the VICIdial "Agent Kick All Error" error? +
Check VICIdial admin log for specific error message Then: Verify admin user has sufficient permissions for mass kick operations Then: Check MySQL connectivity: mysql -u cron -ptest -e 'SELECT 1' Then: Manually reset agent sessions in database: UPDATE vicidial_live_agents SET status='PAUSED' WHERE campaign_id='CAMPAIGN' Then: Check for active calls that may be blocking: asterisk -rx 'core show channels' Then: If sessions are stuck, restart VICIdial web processes: sudo systemctl restart apache2
How can I prevent the "Agent Kick All Error" error in VICIdial? +
Use the graceful agent logout option when possible rather than forced kick. Test kick functionality during low-traffic periods. Document the kick procedure for managers who need to use it in emergencies.
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 →