Centova Technologies Forum
Centova Cast v3 => Bugs and issues => Topic started by: jdownj on October 15, 2012, 05:00:49 am
-
The bandwidth monitors do not appear to be working, is there a simple dependency I might be missing? Noticed both on Debian Squeeze and Ubuntu Lucid(10.04). If it's more involved than that, where should I start, what logs will help debug this?
-
Please clarify what, exactly, is not working, and how it is failing to work.
-
Yes I have this problem also, no bandwidth stats and all my clients stats (page=statistics) are all at zero
I have run
UPDATE settings SET lastlogprocess=NOW();
but it does not seem to be working this time -- it did work a couple months ago on a different server
-
Yes I have this problem also, no bandwidth stats and all my clients stats (page=statistics) are all at zero
When you say the client stats are "all at zero", do you have any user agents, countries, or tracks reported on their respective tabs? Or is there just *nothing*?
If it's the latter (nothing at all showing up) then there's almost certainly something wrong with your cron job. In that case, please try running:
/usr/local/centovacast/bin/ccmanage processlogs all --debug
And see if it terminates with an error of some sort. The statistics definitely work fine on a few of our production machines I've checked with the latest build, so hopefully the above will yield something useful to help track down the problem.
-
nothing -- no stats, bandwidth usage, nothing but disk space -- I ran the script but no change
-- I do have one Icecast account and the stats work on it but the other SHOUTcast2 accounts they do not, the Icecast account is the newest so I am sure I have given enough time.
I have also pm'ed you my server details if you want to take a look
-
I ran the script but no change
The reason you didn't see any errors when you ran it is because none of your streams had any activity... access.log was 0 bytes for all of your streams. :)
After tuning in to one of your streams (thereby generating some log data) and running the command I provided, it generated a bunch of errors which explained what was going wrong and led me to a fix. Thanks for the server access!
-
Mine is fine now :)
-
And I had a hung cron job. Non-issue here then, just didn't understand the architecture about the cron job updating the stats.