First, please note that the statistics, bandwidth, and disk space totals are updated only once every 12 hours.  If you have not waited at least 12 hours, please do so before attempting to further diagnose this problem.

You can change the update frequency for the statistics by editing /home/centovacast/system/config.php and changing the LOGROTATE_FREQUENCY setting.

If you have waited at least 12 hours and the statistics are still not updating, this indicates that for some reason, your Centova Cast cron job is not running properly.  Please check the following, in order:

1. Has your Centova Cast cron job been removed or altered?
   
   Login to your server via SSH as root and check /etc/crontab for the Centova Cast cron job.  It should look something like the following (all on one line):
   
   */5 * * * * centovacast /home/centovacast/system/runascc/runascc exec ccmanage cronjob all >/dev/null
   
   The cron job is automatically set up by the installer, so if it does not exist then someone or something has removed it and you'll need to replace it.
   
   
2. Is your cron daemon actually running the cron job?  Even if the Centova Cast cron job is correctly configured in /etc/crontab, other mistakes in your /etc/crontab file may cause the cron daemon to fail to run the cron job.
   
   Check your cron log (usually /var/log/cron on Red Hat-based Linuxes) and search for the word "centovacast".  Find the most recent entry (near the bottom), check the date stamp and make sure it has been running within the past day.
   
   
3. Is your Centova Cast cron job working correctly? Try running the following command:
   
   /home/centovacast/system/runascc/runascc exec ccmanage cronjob all --debug
   
   Note that this may appear wordwrapped above, but should all be entered on one line.
   
   When you run the above command, you should see something like:
   
   INF Checking for crashed servers...
   OK Check complete
   
   If you see errors regarding cronjob.lck, this likely indicates that your setuid binaries in /home/centovacast/system/runascc/ have lost their setuid bits and/or are owned by the wrong account, and you'll need to refer to this article.
   
   If you see any other error messages, then it could be that there is a problem with Centova Cast itself.  If so, please open a ticket with the support department and provide us the error messages, and we'll help you to diagnose the problem.
   
   
4. Is the log processing job terminating with an error?  In some cases, problems with a particular stream can cause the log processing job to exit with an error, which will prevent the remaining accounts from being processed.  Try running the following command:
   
   /home/centovacast/system/runascc/runascc exec ccmanage processlogs all --debug 
   
   If the problem is still not obvious, please open a ticket with the support department and provide us the complete output of the above command, and we'll help you to diagnose the problem.  Please be sure to send the output as a file attachment -- for example, to create a zip file with the output, run:
   
   /home/centovacast/system/runascc/runascc exec ccmanage processlogs all --debug > debug.log 2>&1
   gzip -9 debug.log
   
   And then send us debug.log.gz as a file attachment.
   

Note that if you are not seeing the statistics graphs at all (i.e., if you are seeing no graphs, or red X's where the graphs should be) then this indicates a completely different problem.  In that case, please see the following knowledge base article:
Statistics graphs missing (or showing red X's)