Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: roseway on July 29, 2017, 02:53:57 PM
-
Changes since v6.0.3:
- Fixed floating point error when saving snapshots of average errors in Windows version
- HG612_Modem_Stats co-operation option is now available on Linux and RPi versions
- added option not to include routine events (snapshots) in the event log
- fixed integer conversion error when using cat /proc/net/dev for traffic
Note: The HG612_Modem_Stats co-operation change is to support users who want to run both programs, but on different machines. On Linux and RPi machines, all the option does is force sampling to take place between 35 and 40 seconds after the minute. This assumes that HG612_Stats is set to run just after the minute. The user must manually ensure that only one of the programs is uploading to MDWS.
Full changelog at http://dslstats.me.uk/changelog.html
Downloads: http://dslstats.me.uk/downloads.html
-
- fixed integer conversion error when using cat /proc/net/dev for traffic
It works without errors now. Thank you roseway.
-
My pleasure.
-
Stable on my troublesome Win x64 machine so far.
Is it possible that the errors you have eliminated could be the cause of such oddities as the program sometimes closing by itself when focused (instantly, without the usual "should I close?" confirmation dialogue) and the occasional "access violation" message on start-up?
-
It's just possible, but very difficult to be sure.
-
Roseway
Working fine on my PI with HG612 Modem stats co-op mode set.
Thanks again for all your work on this software
Ian
-
Thank you :)
-
What is the correct way to update dslstats from one version to another?
-
Also working fine on my Raspberry Pi with NO HG612 cooperation.
Thanks for your efforts, Eric
toulouse
-
@roseway
Eric, I upgraded by RPi program revision to the pre-release V.6.0.4 yesterday and have noticed today that I am only achieving 70% uploads now to MDWS (ID tiffy), have always achieved 99 -100% previously.
I am running DSLStats on an old Mk.1 B RPi which was OK with program V.6.0.1 although did top out the CPU for approx. 5 secs. just after uploading, this does not look any different with the new program revision, the CPU usage indicator appears just about the same.
I have obviously checked that all the configuration options are still the same after program change.
I know you have added an additional stat. upload to MDWS since the previous version I was running (V.6.0.1) could this possibly be pushing my old RPi into difficulties now ?
I can revert to the old program revision again if you think this would be a worthwhile exercise ?
-
@tiffy: there have been no changes since v6.0.1 which would account for intermittent uploads. HEC values have always been included in the uploads, but using zeroes as placeholders. The recent change was to replace the zeroes with real values. The amount of extra load on the RPi is negligible. Something else must have changed.
-
What is the correct way to update dslstats from one version to another?
The safest way is to copy all the files to a new folder alongside the one you're upgrading from, and run it from there. If the configuration files are in their default location, that should be all you need to do.
-
@tiffy: there have been no changes since v6.0.1 which would account for intermittent uploads. HEC values have always been included in the uploads, but using zeroes as placeholders. The recent change was to replace the zeroes with real values. The amount of extra load on the RPi is negligible. Something else must have changed.
Eric, Thanks for the reply, may well be coincidental, I've noticed that browser response has been very slow at times this morning, will leave alone for a day or two to see if the 70% uploads figure improves or gets any worse.
I have retained the V.6.0.1 folder on the RPi so I can try reverting back to that very easily if things don't improve, just thought it was strange that this was coincident with the program revision change.
-
roseway
Does the program automatically start sampling at xx sec past the minute, (without hg612 co-op)
Tiffy
Check what time the PI is sampling against a known correct time (https://www.timeanddate.com/worldclock/fullscreen.html?n=298 (https://www.timeanddate.com/worldclock/fullscreen.html?n=298))
Ian
-
@ kitzuser87430 (Ian)
Not completely sure what you mean, my fault I'am sure, ref. sampling time checking.
In my previous post I'am refering to the 60 sec. (default value) program sample when the RPi (DSLStats) collects the modem stats and the CPU momentarily saturates.
It's my understanding, limited as it is, that DSLStats uploads to MDWS @ xx sec's after each hour, is this the time you are refering to with respect to real time checking ?
Is that the only time DSLStats uploads to MDWS ?
I am not running HG612 Stats so do not have the co-operation option selected.
-
By default, DSLstats starts sampling as soon as you press the green button.
If it's configured to upload to MDWS, the period from several seconds before the minute to just after the minute is not allowed, so if you press the green button during this period you will see a "Brief pause" message in red until about 2 seconds after the minute.
If you enable the option "HG612_Modem_Stats co-operation", then sampling starts between 35 and 40 seconds after the minute, and you will see "Synchronising..." in red if you press the green button outside this period.
-
Eric, many thanks for the clarification, much appreciated.
-
Even for me it seems OK! As a BTW I can't recall having seen before in Event Log, "No response to login user name." What is not responding to what, please, and why?
-
Not completely sure what you mean
I see what you mean, it is not obvious what I am on about.
1) Ensure your PI clock is correct (to the second)
2) Ensure you sample as soon as possible in the new minute.
The uploads (every min) to MDSLWS should then be fine.
Ian
-
I have posted this several times already but here it is again.
The time at which you are uploading is always shown on MDWS at the top right of the status bar above the graphs. It's in square brackets underneath the legend of [USec] and reads something like [44s]. In tiffy's case is is 44 sec which is not a problem. It IS a problem if you upload close to 00 sec as it's then possible to upload two logs inside the same minute which will generate a duplicate error. Somewhere between 5 and 45 secs is ideal depending on whether you have HG612 Modem Stats running as well.
If you are running a slow machine earlier is better to avoid timeouts on the hourly uploads at around 57/58 mins to the hour.
-
Tony, many thanks for the further clarification, much appreciated.
Apologies for the repetition requirement, I do trawl the MDWS help files, kitz tutorials and all related forum threads but due to my somewhat limited understanding as a relatively new user of MDWS I have abviously missed some important information, still on a steep learning curve.
It's my understanding that there is no user control of the hourly upload time and the only user control of the 60 sec. uploads is by selection of "HG612 stat's co-operation" option if applicable ?
I note today that my upload % is recovering on MDWS, was down to 75% yesterday which I thought might be coincident to change of DSLStats program from R.6.0.1 to R.6.0.4 the previous day, Eric has assured me this should not be the case.
@kitzuser87430 (Ian)
It's obvious that I'am certainly not fully ofey with the data uploading timing of DSLStats to MDWS, Tony has kindly explained this now.
Yes, my RPi RTC is correct to the best of my knowledge, I am running Raspian Jessie.
I did implement the RTC enhanced update procedure on Windows as outlined on MDWS, obviously only applicable when I was running DSLStats on my desktop PC, I am not aware of any similar procedure for RPi to enhance RTC accuracy ?
-
It's my understanding that there is no user control of the hourly upload time and the only user control of the 60 sec. uploads is by selection of "HG612 stat's co-operation" option if applicable ?
The hourly upload time is fixed.
For DSLStats (without the cooperation option) you can simply start or stop/restart at the time you want to upload between 5 and 35 secs past the hour. Your 44 secs is okay currently, I'd leave it alone. Why it suddenly decided to upload okay I have no idea, nothing changed at this end.
-
Tony, Thanks for the further clarification.
I think the upload % decrease was likely attributable to what appeared to be a general slow down at this end yesterday, don't really know why, my upload % figure is recovering quickly today.
As it appeared to happen just after DSLStats program update I thought there may be a connection.