firstly thanks for making gargoyle, however after installing yesterday I have 1 major issue.
Running Linksys WRT54GL, with 1.2.4 firmware.
Yesterday it was recording web usage fine (my primary reason for using gargoyle), however now when I look at daily usage yesterdays usage is back to 0, and it is recording todays usage (see screenshot below). Is this a known issue? I could shift to the latest experimental version if that will fix the issue.
the rest of the days have been showing usage fine, however when I try view the months usage, It is not calculating correctly, as per screenshot below. What would be awesome would be being able to input a specific date range
hopefully I can get a response to this, even if its trying the latest version, or again is this a known issue or something new?
One other person reported something similar about a month ago, but I could never replicate the problem (so I couldn't track down/fix it). I'll revisit the problem and see if I can figure out what is going on. this definitely looks like a bug.
I have noticed the first time point getting zeroed out like you describe once or twice, but I haven't encountered a situation where the numbers don't add up. I've been meaning to check on the zeros, but I haven't figured out exactly what causes it (again I can't reliably replicate it -- I've just noticed it when checking on something else, and if I re-intall/reflash in testing that issue, the zeros are gone and I can't replicate them again).
I'm also experiencing the same bug on my WRT54GL running Gargoyle 1.3.3.
I installed Gargoyle on Aug 4, until yesterday it was properly recording all data. Today I checked the usage and the month value has gone down, upon checking the daily usage Aug 4 values have reset to 0.
I had this same issue with the stable version of Gargoyle (1.2.4). No idea how to replicate it.
Don't worry, I haven't forgotten about this bug -- it's just proven a real pain to debug.
DoesitMatter: No, I'm 99% sure this is not a memory issue. There's a bug in there, somewhere. The problem is finding it.
What's happening is the last time point is getting zeroed under some very specific set of circumstances, that I have yet to identify. I think that a reboot is necessary to trigger it, but it doesn't always happen after a reboot.
The reason the numbers aren't adding up is that when you compare shorter time scales and the longer time scales after the last time point got zeroed, different amounts of time are lost and they don't add up. As far as I can tell it's just the last time point that changes -- everything else remains accurate.
What I really need in order to fix this, is a procedure for reproducing it 100% of the time from a clean install. I've seen it pop up myself once or twice, but I haven't been able to figure out what it was that caused it to happen, or to get it to happen again reliably.
I'll have another crack at fixing the problem this weekend, but it's a nasty little bug.
Today I started having miscalculation of the bandwith usage on the bandwidth_distribution.sh page. The quota still seem to track the usage properly and still no memory errors.
