Right - the save settings button only appears if you have database integration. Without the database, everything goes into a localStorage variable and should be getting updated automatically when ever you make any changes... it could be that I've broken that in the transition but I hadn't noticed anything on my test config.
OK, thanks. I'll probably try database integration later though will keep things as they are for now in case this actually turns out to be something beyond an issue here and some troubleshooting needs to be done.
ddaniel51 wrote:
FYI my R7000 is running below .3 on an idle network with Yamon running.
Thanks, though that router is radically higher-end than mine, so I can't really compare with it. I can just compare with the script stopped vs started, and it does add about two points even when updating is on 60. Note that both stopped/started figures are not at idle, but then the router is never at idle.
var _unlimited_usage=1
var _unlimited_start="23:45"
var _unlimited_end="5:45"
to config.js it's good like that ?
First - the default value for _updatefreq is 15 which means that YAMon updates the internal totals every `_15` seconds... seconds. This means you can set _unlimited_start and _unlimited_end to the actual beginning and end of your unlimited usage interval (there is no need to give 15min buffer)
Second, it has been a long time since I looked closely at that code but I'm pretty sure that both _unlimited_start & _unlimited_end must be on the same side of midnight... so you cannot use the values specified above but you could certainly use:
var _unlimited_usage=1
var _unlimited_start="0:00"
var _unlimited_end="5:45"
Does anyone's unlimited interval start before midnight? If yes, I can look at fixing that limitation. If no, I won't bother?
Also does anyone have more than one unlimited usage interval in the day? I've only heard of them being in the wee hours of the morning.
I updated another router today with 17b and see the same inability to save Settings, so it does appear to be a regression (again, with the save-to-server feature unused).
I think "_ispBillingDay" is inadvertently set to 5 in the default config file (description says it defaults to 1). I only noticed it because of the yellow exclamation point.
I did a little more testing of the server load on same-model routers (set with _updatefreq=60). My router when supporting a household averages about 1 without the script and 3 with (sometimes a little lower but often higher). When at "idle" (meaning just one device doing basically nothing), it's more like 0.1 without and 0.3 with. So it's 3x either way.
Posted: Tue Nov 25, 2014 1:36 Post subject: java script error
Hi Al,
Than you for the bandwidth monitor software. I use it often.
I am getting a java script error in both 2.16 and 2.17b in the browser:
yamon.js:714 Uncaught ReferenceError: users_created is not defined
http://192.168.1.1/user/yamon2.html Failed to load resource: net::ERR_CACHE_MISS
Can you suggest a solution to resolve the error?
Thanks,
Eric
Posted: Tue Nov 25, 2014 3:19 Post subject: Re: java script error
ericd wrote:
Hi Al,
Than you for the bandwidth monitor software. I use it often.
I am getting a java script error in both 2.16 and 2.17b in the browser:
yamon.js:714 Uncaught ReferenceError: users_created is not defined
http://192.168.1.1/user/yamon2.html Failed to load resource: net::ERR_CACHE_MISS
Can you suggest a solution to resolve the error?
Thanks,
Eric
The first line of your users.js file should be something like:
Code:
var users_created="2014-04-16 23:35:37"
If the script is saying that the variable does not exist, it could mean that you users.js has become corrupted. Can you send your file to me in a PM?
Look in /opt/YAMon2/daily-bu2/... you should be able to find a recent version of the file which should get you up and running again (copy the backup to /opt/YAMon2/data and to /tmp/www/data)
Hi Al,
Adding the first line to the users.js file (as you suggested) fixed the problem. Perhaps I had inadvertently deleted it when I edited the file.
Thanks!
Eric
Hi Al,
Adding the first line to the users.js file (as you suggested) fixed the problem. Perhaps I had inadvertently deleted it when I edited the file.
Thanks!
Eric
and I do not see the "reboots":"1" anywhere else in that file...
I'm not particularly concerned because the data seems to be there alright, but somehow the behavior does not make too much sense.
The thing that does intrigue a bit is, that also before the 26th data was added to the file, the Daily Usage did not show any data - so somehow the 'reboot' must have been hidden somewhere else as well...
Just thought I'd let you know in case you are not aware of that situation.
I'm running v2.0.17b and it cannot display the data for Nov 26. It comes up with the error
Code:
Error #4 reading the hourly data file: `data/2014-11-26-hourly_data.js` SyntaxError: missing ) after argument list
and just doesn't show anything in the Daily Usage - and wasn't showing anything before midnight either.
Ok... there is definitely a bug somewhere in the script. You are the second or third person who has reported the missing `}` issue. If you open the hourly file, somewhere in that file, you will find a line that is missing its closing brace bracket. I believe it may be related to the router rebooting but I cannot confirm this.
I'll look at adding a sanity check somewhere to fix this problem automatically...
PeterS-ZH wrote:
Now that 2014-11-01-mac_data.js has been updated, I find the following line above the block with the 26th data:
When the router is rebooted, the value of `uptime` resets to zero. So, as I generate the daily totals from the hourly file, I can the number of times that `uptime` is less than the previous interval to estimate the number of reboots (estimate because this method cannot detect two reboots within the same hour).
Now that I have this info, in the monthly breakdown report, I can flag the days on which there were reboots... hover to get the number - e.g.,
