Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: roseway on March 20, 2014, 10:22:24 AM
-
A collection of small tweaks and fixes.
Changes since v4.44:
- added modem/router firmware version to the Stats summary
- added timestamp to the Stats summary
- added option for a combined web page to the webserver
- added options to save all snapshot items to the webserver (as images and text files)
- fixed incorrect behaviour of ES/hour chart with a user specified max Y value
- disabled manual editing of the snapshot directory (which created multiple directories)
- corrected a small cosmetic defect in the display of CRC and FEC graphs when in logarithmic mode
- the CRC and FEC graphs now don't plot successive zero values in logarithmic mode
- corrected mishandling of negative values in pbParams output
- added command prefix options "xdslctl0" and "xdslctl1" (for C2000A and C2000T modems)
Additionally for v4.50.1: fixed "List index (1) out of bounds" error with some systems (hopefully)
http://dslstats.plainroad.me.uk (http://dslstats.plainroad.me.uk)
-
Up & running and seems fine for me.
Stuart
-
Thanks Stuart.
-
Eric I spoke too soon, I got a list index(1) out of bounds error just now.... and it has started to happen more than once so will got back a release for now.
Stuart
-
Stuart, can you copy your dslstats.ini file to me please, and confirm that this is with the Windows version of DSLstats?
-
Yup this is W2K running the windows version. Attached is the .ini file.
Stuart
-
Thanks, I just want to see if I can reproduce the issue.
-
The 64-bit version (for Linux kernel based systems) is currently running in The Cattery.
At the moment there is nothing to report. :)
-
Thank you :)
-
I've just started the Linux 64-bit version here for now to see if it behaves OK.
Stuart
-
The 64-bit linux version has run for a while with no problems. I've now re-installed the 32-bit Windows version on W2K and will see what happens again....
Stuart
-
Thanks for going to all this trouble, Stuart.
-
I have to report a total lock-up of DSLstats. :(
Recovery was only possible by termination of the process. At present, I have no idea what was the cause/trigger. :-\
-
Eric I spoke too soon, I got a list index(1) out of bounds error just now.... and it has started to happen more than once so will got back a release for now.
Stuart
Stuart, further to this, I've had a similar report from another user, but he said that it was a VB error. The only VB element in DSLstats is the utility IsRunningVB.exe which supports the HG612 Modem Stats co-operation. This shouldn't be running unless you tick the box to enable that co-operation. If the error returns, could you check to see if that process is running.
-
I have to report a total lock-up of DSLstats. :(
Recovery was only possible by termination of the process. At present, I have no idea what was the cause/trigger. :-\
I've never had this happen, so it's a struggle to diagnose. What I'll do is look at all the changes between v4.44 and v4.50 to see if anything leaps out, but if it's only a rare event it may be nothing to do with the latest changes. One possible cause is something going wrong during the sampling process when a separate program thread is reading data from the modem - if an untrapped error occurs at this stage it can give strange results. The other possibility is that a program loop fails to terminate while parsing the data from the modem - this would certainly cause a lockup.
-
Eric I have had DSLStats crash again twice this morning. It happened when I was not watching it and I have a program which watches my running tasks and restarts them automatically if they fail so I have no idea why it is happening. I can confirm that the option you refer to is not ticked and at present that routine is not running. For now I will go back to the previous version.
Stuart
-
The 64bit version for Linux has been running here for almost 24hrs now, with no issues to report. Unlike b*cat who suffered a lock-up, it has remained perfectly stable so far.
PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
20 0 509m 39m 13m S 4.0 1.0 197:34.47 dslstats
-
Thanks BE. I normally run the 64bit Linux version myself, because that's the machine I do the development on. I can't explain b*cat's lockup at present, and it's a bit of a needle in haystack issue.
The issue with the Windows version happens repeatedly, so I hope to nail it down soon. I have this version running in Win2K, and so far (~3 hours) nothing untoward has happened.
-
The issue with the Windows version happens repeatedly, so I hope to nail it down soon. I have this version running in Win2K, and so far (~3 hours) nothing untoward has happened.
My W2K version last ran for about 10 hours before failing at around 07:30 this morning.
Stuart
-
I'll leave it running for 24 hours (at least) and see what happens.
-
I was prompted yesterday to update, and downloaded the zip for 32 bit Windows.
Copied the original folder, then unzipped into it.
After 10 minutes or so of running, it gave the error "list index(1) out of bounds".
I restarted it and left it, later on when I came to check it, I found it had stopped running altogether with no errors on screen.
I then reverted to the earlier version I'd backed up, which as I type is still running happily.
So something doesn't seem quite right.
Is there anything I can do to help diagnose the problem?
I'm using it with my HG612, if that's any help, and it's running on 32 bit Windows XP which is semi-headless (usually accessed by remote desktop)
Ian
-
Thanks Ian. At the moment I'm trying to reproduce this problem, and also looking hard at the differences between v4.44 and v4.50. I'm otherwise occupied this afternoon, but I'll come back to it later.
-
With regards to the total lock-up that I have reported, please do not spend any time in attempting to find the proverbial needle. Until such time as it happens again -- and I can reproduce it -- it should just be noted as an event that had occurred. :)
-
Thanks :)
-
I've been unable to reproduce the "List index out of bounds" error, but I think it's an error in parsing some of the data received from certain modem/router models. I can only see one section of code where this can happen, when it didn't happen in the previous version, and I've corrected that section of code. Could you please test these corrected versions and let me know if they fix the problem. Thank you.
Linux 32bit: http://www.s446074245.websitehome.co.uk/files/dslstats32L-4.50.1.tar.gz (http://www.s446074245.websitehome.co.uk/files/dslstats32L-4.50.1.tar.gz)
Linux 64bit: http://www.s446074245.websitehome.co.uk/files/dslstats64L-4.50.1.tar.gz (http://www.s446074245.websitehome.co.uk/files/dslstats64L-4.50.1.tar.gz)
Windows: http://www.s446074245.websitehome.co.uk/files/dslstats32W-4.50.1.zip (http://www.s446074245.websitehome.co.uk/files/dslstats32W-4.50.1.zip)
(A reminder, by the way: You can't run two instances of DSLstats simultaneously, so please make sure that earlier versions are shut down).
-
OK,
I made a copy of the working DSLstats folder, then unzipped your new Windows version into the existing DSL stats folder, overwriting the contents. Didn't change anything else.
Started the new version at 10:31, it's currently plotting.
Ian
-
DSLstats V4.50 working well on Vista & Window 8.1 and look forward to the Amiga OS release :P
-
Yep, still working fine here.
It had definitely failed once, if not twice, after this length of time running previously.
Ian
-
Thanks Ian, but I won't count my chickens just yet.
-
DSLstats V4.50 working well on Vista & Window 8.1 and look forward to the Amiga OS release :P
That will have to come after the Babbage Difference Engine version. I'm working on that now. ::)
-
I think a version for the Mark II Colossus rebuild (at the National Museum of Computing, Bletchley Park) should be your immediate priority . . . :angel:
-
Well I just installed the 50.1 version on my W2K system and will wait and see. For now I've turned off monitoring it for failure so hopefully if it does barf I will see what the error was. Mine is an HG622 in case that matters.
Stuart
-
Still running for me :fingers:
-
Mine is still going as well....
Stuart
-
Thank you both.
-
Mine is till going stong this morning so I would suggest whatever you changed fixed it.
Stuart
-
Thanks Stuart. The code in question is the section which extracts the modem/router firmware version from the output of the command <command prefix> info --version. It appears that, occasionally, this command fails to produce a proper output, and it was the code which parses this output which tried to read data that wasn't there. That error is now trapped.
-
I have the Windows version of DSLstats and like others I today I have had several instances of the "List index (1) Out of Bounds" error. Also just had the Windows pop-up message tell me "dslstats has stopped working".
As you are invesgtigating this already I will be interested to see what the issue may be.
Regards,
OldTimer
-
Yes, it's been under investigation for a few days. I have a slightly modified version 4.50.1 as described here: http://forum.kitz.co.uk/index.php?topic=13708.msg258516#msg258516 which hopefully corrects the issue.
-
Many thanks for the quick reply. I have installed the updated version.
When the program is sampling, would you expect to see a message that reads "no data returned in latest sample"? That only appeared briefly, but seems to be working normally again.
Regards,
OldTimer
-
For me v4.50 on windows was running for many hours without any errors so far.
What do you think about adding a counter which shows the amount of resyncs, maybe on the stats tab?
-
When the program is sampling, would you expect to see a message that reads "no data returned in latest sample"? That only appeared briefly, but seems to be working normally again.
If it only appears once (or very sporadically) it has no significance. It just means what it says, namely that for some unknown reason the modem/router didn't return the expected data in that sample. You'll commonly see it in the first sample after an unexpected re-sync, for example, or it may be that the CPU in the modem/router is fully loaded with other processing tasks at the time.
-
Hi Eric was wondering why the User Account Control does not popup when running DSLstats not that I am complaining as UAC is a pain in the backside and whish all apps were UAC quiet like yours and the same for HG612_Modem_stats.
-
I'm afraid I hadn't even heard of User Account Control until you mentioned it. DSLstats and HG612_Modem_Stats don't touch the Registry, so perhaps it's something to do with that.
-
From Msoft info
User Account Control (UAC) is a feature in Windows that can help you stay in control of your computer by informing you when a program makes a change that requires administrator-level permission. UAC works by adjusting the permission level of your user account. If you’re doing tasks that can be done as a standard user, such as reading e‑mail, listening to music, or creating documents, you have the permissions of a standard user—even if you’re logged on as an administrator....used with program installation, changing windows firewall settings and such like.
-
For me v4.50 on windows was running for many hours without any errors so far.
What do you think about adding a counter which shows the amount of resyncs, maybe on the stats tab?
Yes, I can do that.
-
I've now made v4.50.1 the "official" upgrade.
-
Good evening Eric my ES/hour seems to be showing as zero yet the graphs shows I had errors in one hour, it was working yesterday and have had an HG612 modem retrain 4 to-day at 5pm because SNRM went below 4.5dB, I have restarted your app since the re-sync but still showing as zero :-\
EDIT: no worrys it's started to display those ES/hours again at 19:54 :)
-
All still working fine here, so your mod fixed the problem it would seem :thumbs:
I wonder if there's any use, other than for me, of a feature, thus :
Currently, DSLStats can be configured to email you when the SNM drops below a specified level. This is great, and notifies me when the unknown neighbour-induced rein has started.
For me, at least, it would then be useful to know when the SNM has returned to it's previous level, or returned to a preset level.
Maybe it could email when SNM drops below level x, then look for when it returns above user specified level y?
Ian
-
Maybe it could email when SNM drops below level x, then look for when it returns above user specified level y?
Yes, that can be done.
-
Maybe it could email when SNM drops below level x, then look for when it returns above user specified level y?
Yes, that can be done.
That would be great, but only if it's useful to others!
Ian
ps can you make it play MP3 files for given events? And have loadable skins? And.... ;D
-
ps can you make it play MP3 files for given events? And have loadable skins? And.... ;D
:whip:
-
Currently, DSLStats can be configured to email you when the SNM drops below a specified level. This is great, and notifies me when the unknown neighbour-induced rein has starte
Thats all fine & dandy but a email to say your SNRM is dropping below 5.0dB is not going to fix the reason why it's getting that low & when at home I can see this without an email so I don't see the point of this it's just App candy ???
-
Thats all fine & dandy but a email to say your SNRM is dropping below 5.0dB is not going to fix the reason why it's getting that low & when at home I can see this without an email so I don't see the point of this it's just App candy ???
It's not going to fix anything, but I think it helps in gathering data if you have an email log that shows at 9pm on Sunday the SNM dropped to 2db then at 10:20pm Sunday it returned to 6db. Currently it's only showing you when it drops, not when it recovers. For me, at least, this would be useful. It avoids having to wade through days worth of logged data.
However, I will continue to complain until the program contains an html5 compatible browser. Oh, and can it be a Microsoft RDP client too? Thanks ;D
Ian
-
Thats all fine & dandy but a email to say your SNRM is dropping below 5.0dB is not going to fix the reason why it's getting that low & when at home I can see this without an email so I don't see the point of this it's just App candy ???
It's not going to fix anything, but I think it helps in gathering data if you have an email log that shows at 9pm on Sunday the SNM dropped to 2db then at 10:20pm Sunday it returned to 6db. Currently it's only showing you when it drops, not when it recovers. For me, at least, this would be useful. It avoids having to wade through days worth of logged data.
However, I will continue to complain until the program contains an html5 compatible browser. Oh, and can it be a Microsoft RDP client too? Thanks ;D
Ian
Ok I forgot most ADSL users don't have an HG612 to run HG612_Modem_stats :blush:
-
Currently, DSLStats can be configured to email you when the SNM drops below a specified level. This is great, and notifies me when the unknown neighbour-induced rein has starte
Thats all fine & dandy but a email to say your SNRM is dropping below 5.0dB is not going to fix the reason why it's getting that low & when at home I can see this without an email so I don't see the point of this it's just App candy ???
It was added at a user's request, and I find it very useful myself, particularly for low SNRM events which occur in the middle of the night. It can also be useful for remote monitoring. Sure, it's not going to fix anything, but information is always a good thing.
-
sorry Eric just got my first ever error using DSLstats will check the event viewer for any info, but this is what came up on the screen with a ding sound.
-
sorry Eric just got my first ever error using DSLstats will check the event viewer for any info, but this is what came up on the screen with a ding sound.
Are you running 4.50 or 4.50.1? The former has a bug like that and the latter fixes it.
Stuart
-
Are you running 4.50 or 4.50.1? The former has a bug like that and the latter fixes it.
Stuart
Using v4.50 at the moment have V4.50.1 downloaded but not yet installed.
Thanks Broadstairs
-
Just noticed that on my errors tab the averages screen now shows zeros for all values when showing 24 hour averages, now having played with values they now show up averages for 24 hours starting today an 11:48. Not a big problem but strange none the less.
Stuart
-
When a new 24-hour period starts, it takes some time before the averages start to register, particularly if your error rates are rather low. I don't know if that's the explanation in your case.
I'm aware that this function isn't perfect, and I need to give it some more attention, but for the moment it doesn't have a high priority.
-
When a new 24-hour period starts, it takes some time before the averages start to register, particularly if your error rates are rather low. I don't know if that's the explanation in your case.
I'm aware that this function isn't perfect, and I need to give it some more attention, but for the moment it doesn't have a high priority.
That might well explain it Eric, no worries just thought I'd mention it seems fine now but it was just I'd never seen it before ;)
Stuart
-
Works 'straight out of the box' with a Zyxel WMG8324. Nice one eric :clap2:
Only thing Ive noticed is the colouring of the vdsl tones for the first 4 bands are either blue or purple
eg
PS just thought... you may want these?
Discovery Phase (Initial) Band Plan
US: (6,31) (882,1193) (1984,2770)
DS: (33,857) (1218,1959) (2795,4083)
-
I'll check that out. It looks like an uncomplicated band plan with no overlapping bands, but clearly something isn't right.
Could you show me the medley phase as well please?
-
Here you go :)
Medley Phase (Final) Band Plan
US: (6,31) (882,1193) (1984,2770)
DS: (41,857) (1218,1959) (2795,4083)
-
Thanks, I'll have a look at it.
(Not a lot different, is it? :) )
-
I had dslstats working fine earlier - until I changed the routers default password.
I cant seem to change it in dslstats gui though and it keeps saying incorrect login name or password when it attempts to telnet. The password in dslstats seems to keep going back to the default, & Ive also had a floating point error.
I could be wrong, but it doesnt look like changing the password in the gui saves it to the ini file.
---
added
I had the bright idea of attempting to change the.ini but that doesnt work as it looks like its encrypted.
I also cant change the password back to the default in the Zyxel, as it wont accept it "The password must contain 6 to 256 characters"
-
You probably can't change the password while DSLstats is recording (I'll have to check that) but you should be able to change it if you stop recording first. Failing that, you really should be able to change it if you stop recording, then close down DSLstats and restart it. Make sure that you don't have it configured to start recording automatically on startup.
I'll put this on the list for investigation, but in the meantime, I'm sure it will work if you start it up without starting recording.
-
You probably can't change the password while DSLstats is recording (I'll have to check that) but you should be able to change it if you stop recording first.
Make sure that you don't have it configured to start recording automatically on startup.
That did the trick thank you :)
-
I do need to smarten that up a bit. :)
-
Eric could you possibly add some more options for alerts? Currently I dont use the SNRM alert but presume it writes to the event log (with a time stamp) if no email is selected.
I am seeing some spikes in CRCs and FECs which I would like to be able to track more easily in the log so perhaps an option for CRCs or FECs over a certain value. It would help me see the timing of these events and whether or not they happen at the exact same recording sample and make it easier hopefully to track down the cause.
Stuart
-
Stuart, currently the alerts don't do anything unless you tick the option "Send email notification of events". Your suggestion of an alternative option to send them to the event log is a good one. And adding more triggers is easy enough to do. I'll include this in the next release.
-
Stuart, currently the alerts don't do anything unless you tick the option "Send email notification of events". Your suggestion of an alternative option to send them to the event log is a good one. And adding more triggers is easy enough to do. I'll include this in the next release.
Thanks Eric, look forward to it.
Stuart
-
Only thing Ive noticed is the colouring of the vdsl tones for the first 4 bands are either blue or purple
I think I've fixed this. The band detection logic was confused by an unusual value in the SNR margin section of your pbParams output - the U0 value is shown as 'NR' (what does that mean?). The result was that it believed that band U0 wasn't being used. I've corrected this, and you can download the corrected version at http://www.s446074245.websitehome.co.uk/files/dslstats32W-4.50.2.zip . This is the full archive, but you only need to replace the executable dslstats.exe.
By the way, this version also fixes the other issue you reported. It's now not possible to edit the login details while recording is in process; you have to stop or pause recording first.
Please test this version and (hopefully) confirm that the band colours are now correct.
-
I have this running nicely with a Zoom X4 5751. The only issue I have is a lack of bit loading information. The modem returns
adsl info --Bits
adsl: ADSL driver and PHY status
Status: Showtime Retrain Reason: 4
Channel: INTR, Upstream rate = 448 Kbps, Downstream rate = 4928 Kbps
Tone number Bit Allocation
>
I guess this is probably a firmware problem on the modem.
-
I have this running nicely with a Zoom X4 5751. The only issue I have is a lack of bit loading information. The modem returns
adsl info --Bits
adsl: ADSL driver and PHY status
Status: Showtime Retrain Reason: 4
Channel: INTR, Upstream rate = 448 Kbps, Downstream rate = 4928 Kbps
Tone number Bit Allocation
>
Sadly I can't do anything about that, because the --Bits command is what DSLstats uses as its source of bitloading information. It seems odd that the data is missing though.
-
I think I've fixed this. The band detection logic was confused by an unusual value in the SNR margin section of your pbParams output - the U0 value is shown as 'NR' (what does that mean?). The result was that it believed that band U0 wasn't being used. I've corrected this, and you can download the corrected version at http://www.s446074245.websitehome.co.uk/files/dslstats32W-4.50.2.zip . This is the full archive, but you only need to replace the executable dslstats.exe.
By the way, this version also fixes the other issue you reported. It's now not possible to edit the login details while recording is in process; you have to stop or pause recording first.
Please test this version and (hopefully) confirm that the band colours are now correct.
Thanks vm eric, I somehow missed your post the other day.
I can confirm that the band colouring is now correct.
Ive also tested the config changes only work when paused and that seems good too.
FYI Im using the settings from the VMG1312 in the drop-down box, but you may also like to add the VMG8324-B10A to your page here (http://www.s446074245.websitehome.co.uk/routers.html) confirming that it works with dslstats.
Thank you for all the work put into dslstats :)
-
Thanks for confirming that. :)
I'll add the model to the compatibility list.
-
I seem to have hit a slight hiccup that may be worth mentioning. I had to change the router password last night, & Ive been unable to get dslstats to work since.
The error I get is "Second stage login failure".
Ive tried renaming the .ini to force a new one, but I still get the same error when I try to change the password from the default which is set in dslstats.
---
Ive just tried downloading a fresh copy of 4.50.1 (pre-fix) which works fine - but obviously has the graph colour error....
so next I dropped in your fix just like I did the other day.. and it works, but obviously I've lost all my preferences.
-
That's an odd one. That error message should never be seen unless you have the login option "Requires command to enter shell" ticked. Presumably you haven't? If you still have the renamed dslstats.ini which didn't work, could you check if the value "Usesecondstage" in the Login section is set.
In the meantime I'll try to reproduce the error.
-
Is this what you need?
Encrypted=1
Router=Zyxel VMG1312-B
IPaddress=192.168.1.1
Telnetname=admin
Telnetpassword={removed}==
Usesecondstage=1
Shelltext=
TelnetPort=23
Annex M=0
Thomson=0
Synchronise=0
-
oh... just looked at the current working one
Encrypted=1
Router=Zyxel VMG1312-B
IPaddress=192.168.1.1
Telnetname=admin
Telnetpassword={removed]==
Usesecondstage=0
Shelltext=
TelnetPort=23
Annex M=0
Thomson=0
Synchronise=0
So somehow I must have accidentally ticked 'requires command to enter shell' whilst changing the password?
I dont recall doing so, but if Im reading the config correctly, then I must have .
-
That's it. The option "Usesecondstage" is set. I wonder how that happened? If you change that value to zero, DSLstats should work with that version of dslstats.ini (assuming that the password is now correct).
I do still need to look at this more closely, to see if the unintended setting of that option was the result of a bug, and also to see if I can improve on how the program handles this situation.
-
Oh well glad mystery is sorted. sorry to have bothered you.. :-[
i did try fix it myself before mentioning it.. Guess I never spotted I may have got a bit trigger happy when changing the password.
Wasnt having a good night last night, so I must have done something stupid.
Bit sick of PCs & routers atm - should be elsewhere, but waiting a call back from Zyxel. :(
-
Even if it was an accidental mistake, I can still learn something from it and try to give better feedback to the user.