Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: roseway on April 23, 2016, 07:33:14 AM
-
This version is derived from v5.7.3. Unfortunately the pre-release versions 5.7.5 and 5.7.6 rather messed up the saving and restoring of traffic monitoring data, so if you tested those versions I'm afraid that you probably lost some historical traffic data. I apologise for that, and if you still have some traffic monitoring data which you want to retain, I suggest that you make a note of it before upgrading to this version.
Changes relative to v5.7.3:
- max attainable speeds are now shown on the panel under the graph
- the ES/hour values on the status bar now always show the present day's values
- saving the error averages as text now shows the correct values for each day
- added an option to display traffic by billing month
- fixed incorrect restoring of traffic 'upload plus download' option
Changes in v5.7.3 relative to previous release v5.7.1:
- completely rewritten and simplified average errors section (I believe this fixes the spasmodic "divide by zero" errors)
- the vectoring status is shown on the Stats page
http://www.s446074245.websitehome.co.uk/downloads.html
-
Windows version installed and running OK here....
Stuart
-
Just installed here, all running fine.
-
Likewise on both lines here...
-
Thanks all :)
-
Working fine here on a RPi. :thumbs:
Many thanks
-
Same here on RPi
-
Thanks for the feedback :)
-
Raspberry Pi working fine here also
-
@roseway
Just has a quick look at my stats and found the following glitch; I have not rebooted (PI) but have shutdown and restarted dslstats.
Ian
-
Have you been running DSLstats every day for some time, or were there one or more days recently when you weren't running it?
-
I have been running this version without stop since release date.
I have just reset all values.
Ian
-
I'm looking at this now.
-
Eric last night I re-installed my HG635 router to try to eliminate router issues with my current problems. However I am finding that quite regularly I get Unable to login to router messages which sometimes happen 3 or more times in a row and then it clears and carries on for a while. I am running 5.8 currently. I dont seem to remember this when I was last using DSLStats and the HG635. Any ideas please?
Stuart
-
My hg635 and 5.8 (rasp PI) seems to work without any errors.
Ian
-
Nothing has changed recently in the logging in function of DSLstats. I seem to recall that there have been difficulties with the telnet interface of the HG635 in the past, and I see there's a note against it on my website (http://www.s446074245.websitehome.co.uk/routers.html) referring to this. But the above suggests that this isn't the case.
Another thought is that the option "Modem/router is HG622 type" might just possibly help.
And of course, I have to ask if you're using a WiFi connection between the PC and the modem.
-
Well maybe my HG635 is having problems because of my line problems? Who knows?
Stuart
-
Modem/router is HG622 type
That is ticked on my config
-
Eric I am getting unknown events message now and yes I do have that ticked. Dont worry too much I will put the ZyXEL back later when'the boss' is not on the internet ;)
Stuart
-
@roseway
Just has a quick look at my stats and found the following glitch; I have not rebooted (PI) but have shutdown and restarted dslstats.
Ian
Eric I noticed this as well today on the Windows version, have you had any ideas about it? Mine shows Today and 31-28 May and then the rest are all 19 May with identical data.
Stuart
Edit: Oops does 5.8.1 solve this?
-
No, 5.8.1 doesn't solve it. Apologies to kitzuser87430 for not coming back before, but although I found a possible cause and fixed it, I've just seen the issue today on my own system (I hadn't seen it before).
-
OK Eric, I've updated to 5.8.1 anyway ....
Stuart
-
I believe I have fixed this now. I'll upload a test version in the next day or so.
-
Thanks Eric, I'll keep an eye open for it.
Stuart
-
Good evening all, new user of dslstats & mydslwebstats.co.uk. Using v5.8.0 & having some success uploading data but I must have done something wrong. Data is successfully uploaded but the .exe closes after running for two hours.
Using the 32 bit version loaded on my old dual core laptop running XP service pack 3. Computers on mains power with all the power saving options off except the screen saver which comes in after 15 mins of inactivity.
Don't like Windows so sure I've missed something. Help please?
-
Is the XP set to go into sleep mode or hibernation after 2 hours has expired have a look in the power options
-
The default time per graph page is two hours, so I suppose it's possible that something crashes the program when the graphs start scrolling, but I've never heard of it happening before. You could try changing the time to one hour (Configuration --> Graphs) and see if anything changes.
-
Is the XP set to go into sleep mode or hibernation after 2 hours has expired have a look in the power options
This is what I initially thought. I'll have another look to see if I've missed a sleep mode setting, I've set all the power saving options to never. Thanks
The default time per graph page is two hours, so I suppose it's possible that something crashes the program when the graphs start scrolling, but I've never heard of it happening before. You could try changing the time to one hour (Configuration --> Graphs) and see if anything changes.
Thanks Eric, I'll give that a go & report back.
-
Is the XP set to go into sleep mode or hibernation after 2 hours has expired have a look in the power options
The default time per graph page is two hours, so I suppose it's possible that something crashes the program when the graphs start scrolling, but I've never heard of it happening before. You could try changing the time to one hour (Configuration --> Graphs) and see if anything changes.
Happy to report that the data logging is working OK
As usual the numpty on the computer was the cause of the failure :-[ . As NewtronStar pointed out the dropping of the data upload was due to incorrect power options! As the numpty hadn't "applied" the "never" settings XP was in the wrong power saving mode.
As to the graphs configuration Eric, these work with no issue.
If you look at my data on MyDSLWebStats you'll see a break in the upload at 13:20 on the 16th, there was an error message on screen for DSLstats that said "invalid divisor operation". The app was still open but data recording had stopped. This hasn't happened again and there is now over 24 hours data in WebStats.
Now the problem is understanding what they are telling me. I want to know and get a fix for my abysmal upload rate. Three visits from BT Engineers has got the down rate to 21meg but they won't do anything about the upstream rate, simply saying its 1400m and got aluminium cable in the line. I'll post a separate thread on this.
-
Thanks for sticking your hand up. :)
Regarding the error message, if that was the exact wording, then I've never seen it before and I can't think of an explanation. If it happens again, please try to relate it to something that was happening at the time, if you can.
-
Thanks for sticking your hand up. :)
Regarding the error message, if that was the exact wording, then I've never seen it before and I can't think of an explanation. If it happens again, please try to relate it to something that was happening at the time, if you can.
Eric, sampling stopped at 13:21 today, almost exactly 24 hours after previous restart. The program was not responding message appeared when I maximised, it had been running minimised for previous 24 hours. Before yesterday's restart I configured the graphs to 24 hours. Maybe just a coincidence. I've configured graphs to 2hours & will note what happens.
As to yesterday's error message it closed as the main window opened but I'm pretty sure it said a divisor error. I'll pay more attention if it happens again.
-
Thanks for sticking your hand up. :)
Regarding the error message, if that was the exact wording, then I've never seen it before and I can't think of an explanation. If it happens again, please try to relate it to something that was happening at the time, if you can.
Eric, program froze at 17:05 two hours after restarting with graphs configured to two hours. Error message is <invalid floating point operation
Press Ok to ignore and risk data corruption
Press cancel to kill the program>
I pressed ok, quit the program, restarted program, configured graphs to 24 hours & started sampling.
Will see if program freezes tomorrow tea time unless you want me to do something else that is.
-
I've got a WinXP installation in a virtual machine, so I'll try running that to see if I can reproduce the problem.
-
It's quite easy to overlook the power options as you can have three different profiles and then the change advanced power settings.
-
I've tried running it it for some time in a WinXP installation, but I'm afraid I'm unable to reproduce the problem.
-
Eric very minor issue, I've turned on saving the attenuation text log and each time it write a message to the event log, seems redundant to me. V5.8.1 btw.
Stuart
-
I'll take a look at that, Stuart.
-
Just had a strange problem, but turned out to be a simple solution...
I turned off the MDWS update on my Win7 PC (HG612 modem_stats), and waited 10 minutes. Result: MDWS reported my line to be down, and kept it tagged as "HG612 modem_stats").
Then I added the MDWS configuration to my RPi (which has been running locally for a while now), and turn on the uploading. Result: MDWS continued to report my line to be down. However, MDWS did immediately switch to reporting that I was now using the RPi version for the upload. It was clearly getting the reports, but doing nothing with them!
No change from restarting DSLstats either.
Then I realised DSLstats was logging (locally) with the wrong time. It turns out my RPi was configured to the UTC timezone. As soon as I changed it to "GB-Eire", the uploads went through as normal!
-
Yes, the RPi doesn't set its timezone correctly, so you need to use the command
sudo dpkg-reconfigure tzdata
to get it operating correctly. You'll probably need to repeat this command each time the clocks go back/forward.
I'm not sure why MDWS continued to report your line as down, but I expect Tony has an explanation.
-
I'm not sure why MDWS continued to report your line as down, but I expect Tony has an explanation.
Mike - did you not notice the 40 odd Duplicate Upload e-mails to you :-\
As your clock was now an hour slow you had already uploaded that number of entries... Other than that, MDWS was operating as normal on your line. You had been uploading within 5 secs of the minute change which would explain the previous missing uploads.
-
Mike - did you not notice the 40 odd Duplicate Upload e-mails to you :-\
Nope, but I don't always pay enough attention to email. That machine is undergoing backup prior to a last-minute Win10 upgrade, so I can't check now either.
As your clock was now an hour slow you had already uploaded that number of entries... Other than that, MDWS was operating as normal on your line.
So I guess DSLstats and MDWS both use a "localtime" reporting standard, rather than (say) a reference to UTC. That would explain it...
You had been uploading within 5 secs of the minute change which would explain the previous missing uploads.
My Win7 PC had both DSLstats and HG612 modem_stats running, with them configured to not interfere with each other. I think that meant modem_stats ran at 5-seconds past the minute (and had the MDWS upload duty), while DSLstats ran at around 40 seconds past the minute.
I did find another anomoly, but I'll add that to the other thread....
-
Just started using DSLStats (under Wine on an iMac) and being plagued by problems with teh telnet connection.
12 Jan 2017 08:03:45 Unable to login to modem/router
12 Jan 2017 08:04:58 No response to login user name.
12 Jan 2017 08:04:58 Unable to login to modem/router
12 Jan 2017 08:05:48 Unable to login to modem/router
12 Jan 2017 08:06:38 Unable to login to modem/router
12 Jan 2017 08:07:40 Unable to login to modem/router
12 Jan 2017 08:08:41 Unable to login to modem/router
12 Jan 2017 08:09:46 Unable to login to modem/router
12 Jan 2017 08:10:51 Recording paused
12 Jan 2017 08:10:54 Recording resumed
12 Jan 2017 08:12:07 Auto snapshots taken
12 Jan 2017 08:13:10 Unable to login to modem/router
The router I am using is a ZyXel VMG8924.
I can see a few references to these error messages, but not found anything tht states whether there is a fix / work around for it.
Any thoughts?
-
Do you get that error every time, or occasionally?
If it's every time, the login credentials are probably wrong.
If it's intermittent, is that using the Zyxel in bridge mode or full modem/router?
I never get that error in bridge mode, but frequently got it when downloading at full rate while using the Zyxel as a modem/router.
DslStats only waits a short period before giving up, and the Zyxel just seems to lag a bit when being pushed hard.
The wine on mac may also be adding to this.
-
Do you get that error every time, or occasionally?
If it's every time, the login credentials are probably wrong.
If it's intermittent, is that using the Zyxel in bridge mode or full modem/router?
I never get that error in bridge mode, but frequently got it when downloading at full rate while using the Zyxel as a modem/router.
DslStats only waits a short period before giving up, and the Zyxel just seems to lag a bit when being pushed hard.
The wine on mac may also be adding to this.
It's pretty much every time, although it usually works for a while if I restart DSLStats. (Just checked again to confirm - >10 mins run time so far)
The Telnet port setting, username and password are all correct.
The ZyXel is being used as a Modem/Router, although not under that load most of the time (although i do have a slight obsession with speed tests which I need help for!!).
I guess that wine might be adding to the issue as it will presumably add to the processing time. Not much choice there as I'll probably get shot if I install it on my work laptop.
-
One issue with the Zyxel modem/routers is that with all recent firmware versions (anything later than 6b1) they only accept a single telnet access at any one time, and this can lead to issues with logging in. I don't know if this is relevant to your issue though. One thing you can do is to upgrade DSLstats to the latest pre-release version 5.8.6. This includes an increase in the telnet timeout value, which may help in your situation.
-
One issue with the Zyxel modem/routers is that with all recent firmware versions (anything later than 6b1) they only accept a single telnet access at any one time, and this can lead to issues with logging in. I don't know if this is relevant to your issue though. One thing you can do is to upgrade DSLstats to the latest pre-release version 5.8.6. This includes an increase in the telnet timeout value, which may help in your situation.
I'm using the latest published firmware (1.00(AAKL.15)C0)
Giving v5.8.6 a bash now. Will report back later.
-
Only just had chance to look at teh log file.
Didn't last long.
12 Jan 2017 11:38:34 Recording started
12 Jan 2017 11:38:44 IP address is now 78.149.212.252
12 Jan 2017 11:39:41 Unable to login to modem/router
12 Jan 2017 11:40:38 Unable to login to modem/router
12 Jan 2017 11:41:38 Unable to collect stats 3 or more times in succession
To the extent that it looks as though it failed 1 minute after recording started.
I'm struggling opening a telnet session off the MAC, but will try of the Win8.1 laptop later.
-
Whilst it may not help I had a 8924 before the 8324 I am on now. Originally I tried to use hg612 stats. Regardless of what we tried (worked with BE) the stats would fail after about an hours worth of data. It would get access again about 17 minutes after the first failed attempt. I also had issues when I tried dsl stats. I know there are others with no issue uploading with the 8924 but I couldn't get the one I had to play ball regardless
Have you tried hg612 stats for testing/comparison.
-
I'm struggling opening a telnet session off the MAC, but will try of the Win8.1 laptop later.
Well If you can't manually telnet in then DslStats has no chance. It's obviously not a DslStats issue then but a Mac/wine issue.
You should probably open a separate thread if you want further help diagnosing the problem as Roseway is likely subscribed to this thread and possibly getting emailed each time you post here.