Centova Technologies Forum

Centova Cast v3 => Bugs and issues => Topic started by: My Auto DJ on August 24, 2012, 06:32:00 am

Title: stats, disk space, bandwidth usage not showing
Post by: My Auto DJ on August 24, 2012, 06:32:00 am
All of my stats including disk space & bandwidth usage are stuck @ zero -- both in my Centova admin and on the users panel (STEVE YOu HAVE MY ADMIN LOGIN DETAILS IN YOUR PM IF YOU WANT TO TAKE  A LOOK) :)

Title: Re: stats, disk space, bandwidth usage not showing
Post by: Centova - Steve B. on August 24, 2012, 11:52:53 am
Ahh, thanks -- that's a bug with how the database is initialized for new installations.  You can correct that by running this SQL query:

UPDATE settings SET lastlogprocess=NOW();

Fixed for the next build.
Title: Re: stats, disk space, bandwidth usage not showing
Post by: Vortex on August 27, 2012, 08:56:24 am
same problem here...  i'll wait for the update thxxx  8)
Title: Re: stats, disk space, bandwidth usage not showing
Post by: My Auto DJ on August 27, 2012, 09:06:17 am
I ran the command Steve provided and it does work for me now but it took about a full day before the data  started to display
Title: Re: stats, disk space, bandwidth usage not showing
Post by: crossfirehosting on September 11, 2012, 09:32:44 pm
ok i just downloaded and had a few streams up for a day or so and im getting the same error here.

everything stuck at zero.

how to fix this.
Title: Re: stats, disk space, bandwidth usage not showing
Post by: llamas on October 30, 2012, 06:16:56 pm
Ahh, thanks -- that's a bug with how the database is initialized for new installations.  You can correct that by running this SQL query:

UPDATE settings SET lastlogprocess=NOW();

Fixed for the next build.

This bug is still in version 3.0.0b2 :(
Many stations are with statistics at zero and I have a hard time discovering this issue.

Sorry for my bad english.
Title: Re: stats, disk space, bandwidth usage not showing
Post by: Centova - Steve B. on October 31, 2012, 03:43:58 pm
This bug is still in version 3.0.0b2 :(
No, it's not.  Other users have reported another statistics issue in the latest build which we're looking into (and is probably what you're experiencing) but the issue reported in this thread is definitely resolved.