Posted: Wed Nov 07, 2018 14:05 Post subject: Changing monthly data cap
Upgraded my ISP package and that increases the monthly data cap. The yamon readme.txt file states that "config.file" may be changed on the fly so I modified _monthlyDataCap to the new value. This did not update the graph on the main yamon summary report page. Additionally changing monthlyDataCap (no underscore this time) in /opt/YAMon3/data/2018/10/2018-10-mac_data.js with yamon stopped then restarting yamon worked.
Just hoping this information could save others some digging. Your installation and month folder paths will need to be adjusted. Note that I did not have any success with the "Bandwidth Allowance Cap" in the settings tab of the web interface.
I keep finding no stats for devices in the Live tab. It will work for some time, but not sure how long. Seems that it works for a few hours. This time it worked yesterday, but today it doesn't. this isn't the first time I've seen it. I ran setup.sh last time and it fixed it; now back to this.
ColoradoUser wrote:
YAMon stops running and/or recording data: My problems appear to be identical to that being discussed by aloss and al_c. I have tried the aloss cron job suggestion, with the same result he gets: the cron job keeps YAMon running, but after a few hours all device data drops away. Side note: I see devices continue to appear in the “Live” report, but all have gone to an “unknown” source name in the “live” data – although all devices are still present and properly named in the “devices” tab. So I suspect Al is right about the iptables modifications going south.
I have this issue almost everyday, I love the software but it really is becoming a chore now, I the data on the devices tab is all correct however on the live tab everything shows "unkown"
To fix it I have to export the users.js file again, stop yamon, replace it, then start it back up and it works again.
Posted: Tue Nov 13, 2018 11:01 Post subject: Large values appearing
Every 5 days or so I get an inexplicably and impossibly large values. I read somewhere on here this could be due to restarting etc, where stopping doesn't actually stop everything. It is a bit of a pain to have to look for these values and zero them.
So does anyone have a script that could just zero any inexplicably large values?
Also if it really is due to not stopping processes correctly does anyone have a script to just kill the floating processes before executing the YAMon start script?
YAMon stops running and/or recording data: My problems appear to be identical to that being discussed by aloss and al_c. I have tried the aloss cron job suggestion, with the same result he gets: the cron job keeps YAMon running, but after a few hours all device data drops away. Side note: I see devices continue to appear in the “Live” report, but all have gone to an “unknown” source name in the “live” data – although all devices are still present and properly named in the “devices” tab. So I suspect Al is right about the iptables modifications going south.
I have this issue almost everyday, I love the software but it really is becoming a chore now, I the data on the devices tab is all correct however on the live tab everything shows "unkown"
I've recently noticed this issue as well i.e.YAMon stops recording hourly data, and I've only started doing some digging. It's definitely iptables related as I see this in the log.
Code:
00:01:14 2 checkChainEntries: YAMON34v4 returned only 0 entries?!? Resetting iptables rules
The messages suggests that Al tries to handle it but what is the root trigger is not clear to me yet. It usually takes a few days of running to kick in for me. Because I don't like at live tabs that much, not sure if it's related. I'll keep digging but a YAMon restart fixes.
For my set up here are the potential/unusual things that may help trigger.
1. Running a bridge network and as a result multiple bridge mac entries
2. Doing mobile phone tethering so it's possible that the mobile tethering resets that may be a trigger.
Posted: Thu Nov 15, 2018 13:36 Post subject: Re: Changing monthly data cap
yoyoma2 wrote:
Upgraded my ISP package and that increases the monthly data cap. The yamon readme.txt file states that "config.file" may be changed on the fly so I modified _monthlyDataCap to the new value. This did not update the graph on the main yamon summary report page. Additionally changing monthlyDataCap (no underscore this time) in /opt/YAMon3/data/2018/10/2018-10-mac_data.js with yamon stopped then restarting yamon worked.
Just hoping this information could save others some digging. Your installation and month folder paths will need to be adjusted. Note that I did not have any success with the "Bandwidth Allowance Cap" in the settings tab of the web interface.
I used to keep the bandwidth cap *only* in the config.file.
Now, it is added to the monthly usage file HOWEVER it is added only when the monthly file is created. I currently do not update the value in the active monthly usage file if the value changes mid-month.
So the short answer is next month things should be correct.
You can always modify the active monthly file yourself.
I will look into updating the value (presumably on restart and/or if I detect a change in your config.file).
I keep finding no stats for devices in the Live tab. It will work for some time, but not sure how long. Seems that it works for a few hours. This time it worked yesterday, but today it doesn't. this isn't the first time I've seen it. I ran setup.sh last time and it fixed it; now back to this.
ColoradoUser wrote:
YAMon stops running and/or recording data: My problems appear to be identical to that being discussed by aloss and al_c. I have tried the aloss cron job suggestion, with the same result he gets: the cron job keeps YAMon running, but after a few hours all device data drops away. Side note: I see devices continue to appear in the “Live” report, but all have gone to an “unknown” source name in the “live” data – although all devices are still present and properly named in the “devices” tab. So I suspect Al is right about the iptables modifications going south.
I have this issue almost everyday, I love the software but it really is becoming a chore now, I the data on the devices tab is all correct however on the live tab everything shows "unkown"
To fix it I have to export the users.js file again, stop yamon, replace it, then start it back up and it works again.
What is happening to your users.js on the router? Is it getting corrupted in someway?
Otherwise I'm baffled as to why re-exporting is necessary?!?
I keep finding no stats for devices in the Live tab. It will work for some time, but not sure how long. Seems that it works for a few hours. This time it worked yesterday, but today it doesn't. this isn't the first time I've seen it. I ran setup.sh last time and it fixed it; now back to this.
ColoradoUser wrote:
YAMon stops running and/or recording data: My problems appear to be identical to that being discussed by aloss and al_c. I have tried the aloss cron job suggestion, with the same result he gets: the cron job keeps YAMon running, but after a few hours all device data drops away. Side note: I see devices continue to appear in the “Live” report, but all have gone to an “unknown” source name in the “live” data – although all devices are still present and properly named in the “devices” tab. So I suspect Al is right about the iptables modifications going south.
I have this issue almost everyday, I love the software but it really is becoming a chore now, I the data on the devices tab is all correct however on the live tab everything shows "unkown"
To fix it I have to export the users.js file again, stop yamon, replace it, then start it back up and it works again.
What is happening to your users.js on the router? Is it getting corrupted in someway?
Otherwise I'm baffled as to why re-exporting is necessary?!?
That's just how I was handling it, however I can confirm restarting yamon also fixes the issue for a time.
Does anyone know why this is happening and/or how to permanently fix it? I'm getting crazy large numbers about once or twice a month that are throwing my whole report off, and I can't keep going and back digging through the usage files to fix it.
What happens if you start or restart from webgui-Administration>Commands?
Thank you for replying. I am unsure of what you are referring to as I used PuttY and WinSCP for all of my configuration.
I believe I've got it running now without the PuTTy window open. However, I find that the auto-logout of 30' prevents YaMon from updating. Is there a way to have YaMon get updates without logging into the router, or do I need to disable the auto-logout?
Thank you for replying. I am unsure of what you are referring to as I used PuttY and WinSCP for all of my configuration.
However, I find that the auto-logout of 30' prevents YaMon from updating. Is there a way to have YaMon get updates without logging into the router, or do I need to disable the auto-logout?
I keep finding no stats for devices in the Live tab. It will work for some time, but not sure how long. Seems that it works for a few hours. This time it worked yesterday, but today it doesn't. this isn't the first time I've seen it. I ran setup.sh last time and it fixed it; now back to this.
ColoradoUser wrote:
YAMon stops running and/or recording data: My problems appear to be identical to that being discussed by aloss and al_c. I have tried the aloss cron job suggestion, with the same result he gets: the cron job keeps YAMon running, but after a few hours all device data drops away. Side note: I see devices continue to appear in the “Live” report, but all have gone to an “unknown” source name in the “live” data – although all devices are still present and properly named in the “devices” tab. So I suspect Al is right about the iptables modifications going south.
I have this issue almost everyday, I love the software but it really is becoming a chore now, I the data on the devices tab is all correct however on the live tab everything shows "unkown"
To fix it I have to export the users.js file again, stop yamon, replace it, then start it back up and it works again.
What is happening to your users.js on the router? Is it getting corrupted in someway?
Otherwise I'm baffled as to why re-exporting is necessary?!?
That's just how I was handling it, however I can confirm restarting yamon also fixes the issue for a time.
At the top of the live usage tab you should see an entry: `Last update: 2018/11/17 13:14:03` where the date is a link that'll open the most recent live usage data file (by default: http://192.168.1.1/yamon/js/live_data3.js)
When things stop updating, what do you see when you click that link?
Does anyone know why this is happening and/or how to permanently fix it? I'm getting crazy large numbers about once or twice a month that are throwing my whole report off, and I can't keep going and back digging through the usage files to fix it.
Yikes... generally speaking, I've only ever seen crazy numbers in two circumstances:
1. integer overflow (but those have largely stopped after I wrote my own addition routines)
2. when you somehow get two instances of YAMon running simultaneously... in theory this should not be possible as the script starts, it checks to see if another instance is running but I've seen it happen especially if I'm starting and stopping the script in rapid succession (which leads me to believe there is a race condition somewhere in the code).
Do you have log file from when the numbers went wonky? If yes, can you send them to me? If no, can you set loglevel=0 and wait for it to happen again and then send the logs?
In terms of fixing the issue, unfortunately, it is largely handraulic - i.e., you'll have to manually edit the hourly files. Once those have been fixed, you can run h2m.sh to fix the monthly file.
What happens if you start or restart from webgui-Administration>Commands?
Thank you for replying. I am unsure of what you are referring to as I used PuttY and WinSCP for all of my configuration.
I believe I've got it running now without the PuTTy window open. However, I find that the auto-logout of 30' prevents YaMon from updating. Is there a way to have YaMon get updates without logging into the router, or do I need to disable the auto-logout?
Thank you again.
I'm not familiar with the auto-logout feature... where do you find it?
Did you create the startup/shutdown scripts when you ran setup.sh? (If yes, there'll be entries in the DD-WRT Gui-->Administration-->Commands tab.
Otherwise, I usually manually restart things from a PuTTY window... `/opt/YAMon3/restart.sh 0`
(restart.sh will shutdown any currently running instances and then launch a fresh one. The training `0` parameter tells the script to shutdown and restart right away (with a zero second delay)