Error code 111 indicates that the web interface has failed to communicate with the underlying control daemon (cc-control). Usually this means that the connection can't be establish due to a network issue, or that cc-control wasn't running at the time, or it's otherwise unresponsive.

Before going into debugging the control daemon, please verify the following first:

- That your host configuration address in your admin area under Management > Hosts, is set to and not your public IP.
- That cc-control is running and active (/etc/init.d/centovacast check)
- That restarting Centova Cast doesn't solve the issue (/etc/init.d/centovacast restart)

If cc-control is not running, or it crashes after a time.

Normally, a cron task set by Centova Cast to run every minute will check on cc-control, and it'll restart the service if it finds is not running. So, if cc-control remains down for more than a minute it means that either the aforementioned cron task is not running correctly, or that cc-control is crashing during restart or shortly after.

To verify that the cron task responsible for checking on cc-control is running properly, use the following commands via SSH console:

For Centos:

tail -f /var/log/cron | grep centovacast

For Debian:

tail -f /var/log/syslog | grep centovacast

You should see the following line (among others) appear once a minute or so:

(root) CMD (/etc/init.d/centovacast check >/dev/null 2>&1)

If you don't see this task running every minute, it would mean that there's something wrong with your cron daemon, or that the Centova Cast crontasks file has been damaged somehow [ If everything else seems Ok but the issue persists].


Was this answer helpful? 1 Users Found This Useful (2 Votes)