Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: roseway on May 20, 2015, 10:15:00 AM
-
The main feature of this version is that it includes full G.INP data in the MDWS uploads, but it also has several other small improvements and bugfixes. Changes since v5.4:-
- G.INP data is included in the MDWS uploads
- the attenuation log now records both line and signal attenuation correctly
- the G.INP graphs now respect the hours per page and line thickness settings
- the G.INP graphs now scroll correctly
- corrected some inconsistencies in the use of the MDWS "Check now" button
- removed unnecessary items in pbParams section of "Items to monitor"
- added an option "Plot baseline values" to QLN and HLog graphs (this plots in
dotted lines the sections which are normally left blank)
- added a graph of LEFTRS to the G.INP section
- when the MDWS option is enabled, the sample period is fixed at 60 seconds
- if a sample is missed as a result of a conflict with HG612_Modem_Stats, the system tray icon flashes
- plus changes already made in pre-release versions:-
v5.4.5 (pre-release version)
- added some G.INP graphs and summary data
- negative dBm power levels are now reported correctly to MDWS
v5.4.3 (pre-release version)
- fixed MDWS upload of upstream RSCorr (FEC) values
- G.INP status is reported to MDWS
v5.4.2 (pre-release version)
- when the modem reports negative SNR per tone values, these are converted to zeroes
on the combined bitloading / SNR per tone graph
v5.4.1 released 19 Feb 2015
- fixed login issue with Huawei HG635
http://www.s446074245.websitehome.co.uk/downloads.html (http://www.s446074245.websitehome.co.uk/downloads.html)
(You may need to press F5 to refresh the page when you first use this link.)
-
Windows version running here OK Eric.
Stuart
-
Thanks Stuart.
-
As is the Raspberry Pi version. :)
-
Thanks :)
-
Raspberry Pi version also working here in sunny Zummerset
toulouse
-
Thanks!
-
Thanks!
b*cat wonders: Are you local? :D
-
Since upgrading I'm once again getting this 'Error code 2 while uploading MyDSLWebStats data'.
Until I have time to try figure out what's happening I've disabled uploading.
-
Since upgrading I'm once again getting this 'Error code 2 while uploading MyDSLWebStats data'.
Until I have time to try figure out what's happening I've disabled uploading.
Do you have more than one copy of curl.exe on your system, i.e. one copy included in the DSLstats package and another one installed separately?
-
No only the one installation.
I'll delete the install and download it again, but that's twice in 1 week 2 different versions both stopped working for no reason.
-
There's obviously something strange going on in your case. What version of Windows are you running?
-
Windows 8.1
Kaspersky AV (set to ignore the dslstats folder)
Nothing else other than run of the mill apps like Office 2013, Adobe Illustrator, Filezilla, Lastpass, Adobe Acrobat and VNC.
-
I tested it on a more or less vanilla Windows 8.1 here and there was no problem, so it seems to be something related to your setup. At some stage I've seen a Windows "Unknown publisher" message relating to curl.exe, and I had to untick the option "Always ask before opening this file", but I don't think it's related to that, because it does run curl.exe. And it doesn't seem to be related to AV software.
I think the most useful thing I can do is to test some different versions of curl.exe and try to offer you some options to test (if you're willing). When I first set this up I'd never used curl before, and very possibly ended up with a version which wasn't the best.
-
It's certainly odd.
I've downloaded it again this morning overwritten all the files, restarted dslstats and it's working fine.
The only thing that is common between each re-installation is the laptop being shut down overnight, no new software or changes.
Don't mess about on my behalf, it's only a minute task getting it working again.
I'm tempted to just place a file copy script that re-installs it on start up.
Thanks.
-
I appreciate your tolerance, but I will investigate some more, to see if there's something I can do to fix it.
-
I don't think its 'curl.exe' causing it.
I shut dslstats down earlier, and on starting it again the error cropped up and copying 'curl.exe' on it's own didn't resolve the problem.
Going to try a few tests.
Update: Seems to be a Windows permission problem I think. If I place DSLSTATS folder on the desktop it works. If I place that folder in the root directory of C: drive then it breaks after a reboot. Bizarre.
-
Bizarre indeed. But thanks for doing that testing, hopefully it will point to a more general solution.
-
Thank you Eric, just done mine and all seems ok :)
-
Thank you :)
-
On Netgear DGND3700 I see small problem.
24 May 2015 13:54:18 IP address is now 178.37.134.48
24 May 2015 13:58:50 Timeout while retrieving stats
24 May 2015 13:58:50 No stats received
24 May 2015 15:02:20 Timeout while retrieving stats
24 May 2015 15:02:20 No stats received
24 May 2015 16:02:50 Timeout while retrieving stats
24 May 2015 16:02:50 No stats received
24 May 2015 16:57:20 Timeout while retrieving stats
24 May 2015 16:57:20 No stats received
24 May 2015 20:31:20 Timeout while retrieving stats
24 May 2015 20:31:20 No stats received
24 May 2015 20:36:50 Timeout while retrieving stats
24 May 2015 20:36:50 No stats received
24 May 2015 21:05:50 Timeout while retrieving stats
24 May 2015 21:05:50 No stats received
24 May 2015 21:14:20 Timeout while collecting signal attn data
24 May 2015 21:14:20 Telnet timeout
24 May 2015 21:16:20 Timeout while retrieving stats
24 May 2015 21:16:20 No stats received
24 May 2015 21:16:50 Timeout while collecting signal attn data
24 May 2015 21:16:50 Telnet timeout
24 May 2015 21:17:20 Timeout while collecting signal attn data
24 May 2015 21:17:20 Unable to collect stats 3 or more times in succession
24 May 2015 21:17:20 Telnet timeout
Sometimes DSLStats reports:
Modem/router firmware: Not reported
-
I don't know whether I can help much with this. The Netgear modem/routers of recent years are quite problematic, and it seems to be related to some sort of instability of the telnet interface.
-
I think it would be helpful if I can disable Modem/router firmware stats, DSLAM/MSAN and Uptime stats (too much telnet commands).
Best regards
konrado5
-
On Netgear DGND3700 I see small problem.
24 May 2015 13:54:18 IP address is now 178.37.134.48
24 May 2015 13:58:50 Timeout while retrieving stats
24 May 2015 13:58:50 No stats received
24 May 2015 15:02:20 Timeout while retrieving stats
24 May 2015 15:02:20 No stats received
24 May 2015 16:02:50 Timeout while retrieving stats
24 May 2015 16:02:50 No stats received
24 May 2015 16:57:20 Timeout while retrieving stats
24 May 2015 16:57:20 No stats received
24 May 2015 20:31:20 Timeout while retrieving stats
24 May 2015 20:31:20 No stats received
24 May 2015 20:36:50 Timeout while retrieving stats
24 May 2015 20:36:50 No stats received
24 May 2015 21:05:50 Timeout while retrieving stats
24 May 2015 21:05:50 No stats received
24 May 2015 21:14:20 Timeout while collecting signal attn data
24 May 2015 21:14:20 Telnet timeout
24 May 2015 21:16:20 Timeout while retrieving stats
24 May 2015 21:16:20 No stats received
24 May 2015 21:16:50 Timeout while collecting signal attn data
24 May 2015 21:16:50 Telnet timeout
24 May 2015 21:17:20 Timeout while collecting signal attn data
24 May 2015 21:17:20 Unable to collect stats 3 or more times in succession
24 May 2015 21:17:20 Telnet timeout
Sometimes DSLStats reports:
Modem/router firmware: Not reported
I’ve seen these type of errors too in the last few days, but it was down to increased latency between my Raspberry Pi and the router. I had to rebuild the Pi due to a failed SD card and initially the wireless adapter was mis-configured resulting in much larger ping times to the router. Once I sorted this the stats gathering returned to normal.
-
I think it would be helpful if I can disable Modem/router firmware stats, DSLAM/MSAN and Uptime stats (too much telnet commands).
Yes, that's a fair suggestion. I'll make those commands optional in the next release.
-
Eric I have a request for the future regarding Alerts. Is it possible to add an alert for being unable to login to the router - and could we also have options for each alert being selective as to whether an alert is emailed or shown in the Event log. My reasoning is that I'd like to email the login failure and maybe the MDWS failure but would not want an email for each of the threshold alerts.
Stuart
-
I can certainly do that, Stuart, but probably not immediately. There are a few small issues which I must attend to first.
-
5.5 running here now on the server okay :)
-
I can certainly do that, Stuart, but probably not immediately. There are a few small issues which I must attend to first.
Thanks Eric, its a nice to have so no worries.
Stuart
-
Eric, are there plans to have an installer for Windows machines?
-
Eric, are there plans to have an installer for Windows machines?
It's one of the things I'd like to do, but I haven't found the time. It's on the todo list but keeps getting superseded by more immediate needs.
-
Hello roseway
It seems dslstats ignores the "per sample" switch on the FEC tab, it always calculates errors per minute. On the CRC tab it works as it sould.
Thank you.
-
Thank you morphium, you're quite right. It will be corrected in the next (pre)release.
-
Eric I do now have to wonder if DSLStats could be causing a problem with my VMG8924 - see my update in this thread (http://forum.kitz.co.uk/index.php/topic,15038.msg290554.html#new), right now this is an open question and I am willing to be shot down in flames but could DSLStats not be logging out correctly always? This is using the Windows version on W7.
Stuart
-
Stuart, I'm certainly not going to shoot you down in flames, but I don't know how to test the theory. The way the code is constructed, sampling should always end with a logout. I suppose that the logout itself could fail, but this would have to happen a number of times, because the modem will accept a number of simultaneous admin logins.
-
Stuart, I'm certainly not going to shoot you down in flames, but I don't know how to test the theory. The way the code is constructed, sampling should always end with a logout. I suppose that the logout itself could fail, but this would have to happen a number of times, because the modem will accept a number of simultaneous admin logins.
Yes I am not sure either ;) I guess what I was wondering was how much checking is done in DSLStats around the logout specifically to make sure as far as possible that it works and exits cleanly. If there is any way a logout could fail and not be detected then eventually the max number of logins could be reached, although how or why that might impact on access to the gui I have no idea. Also I dont know how many simultaneous logins are allowed or why access via SSH using putty cleared the issue other than a clean logout by SSH.
Stuart
-
DSLstats doesn't actually log out as such, it breaks the telnet connection directly. I can put in some extra checking to ensure that it disconnects cleanly, and maybe tries again a few times if necessary. I'll be uploading another pre-release version shortly, so I'll add these extra checks before I do so.
-
Eric on my VMG8924 if I telnet into it manually I always issue a logout command which then replies with
Bye bye. Have a nice day!!!
Connection closed by foreign host.
also just now when I tried to telnet in I guess DSLStats was sampling because I got
telnet 192.168.0.1
Trying 192.168.0.1...
Connected to 192.168.0.1.
Escape character is '^]'.
A telnet session already exist, cannot creat new telnet sessionConnection closed by foreign host.
which implies only 1 telnet session is allowed at a time.
Stuart
-
That does rather imply that the VMG8924 is limited to a single telnet session, and it would seem that an SSH session can be used to clear it. That may be the root of the problem - I'm speculating here, but it could be the case that the telnet session occasionally fails to disconnect cleanly, which wouldn't be a problem with modems which accept more than one telnet login, but leads to a lockup if the modem only accepts a single login.
I've made some changes to add extra checking for disconnects. The program now tries up to 5 times, with a 50 ms pause between tries, and if it fails to disconnect after this, a note is added to the event log.
-
Thanks Eric, that at least will tell if the router is failing to disconnect normally. It was just by chance last night I discovered this as my wife was on her tablet which meant I could not reboot the router to clear it so I thought I'd play a bit and found the SSH thing.
Stuart
-
Really thick question - I have an 8800NL running in VDSL mode and I can't get the program to start recording on Win7 64 bit so what am I doing wrong
Even sillier question - why when I select close the program it doesn't as the task manager shows it as still running
-
For the first question, it looks as though you have the wrong CLI command prefix. It should be 'adsl' or 'xdslctl'. Selecting 'Billion 8800NL' from the drop-down list should set it to 'adsl' automatically.
For the second question, I suspect that you have it configured so that pressing the Exit button minimises the program instead of closing it. Have a look at Configuration --> Misc, in the 'Program close / minimise' section.
-
I tried that first and the minimise option isn't checked
-
Pressing the Exit button or the Window Close button at the top should result in a popup which asks "Do you want to close the program?" Do you see that popup?
-
yes I do
-
@oldjim: Sorry to keep asking questions :)
When you see the popup and answer 'Yes', does the DSLstats window disappear? After doing this, does DSLstats still show in Task Manager a few minutes later? Can you restart DSLstats immediately after closing it down, and if not, can you restart it a few minutes later?
The thought behind these questions is that maybe Task Manager takes some time to register that a program has closed.
-
Sorry - I am talking garbage :-[ the bit that doesn't shut down was the dslstats folder
Which leaves the question as to why it doesn't start recording
I tried with Kaspersky disabled and that didn't help
Is there a command to start it recording which I am missing
-
All you have to do is press the green button, then the label at the top changes to "Recording started at...", and near the top right you should see the word "Sampling" in red for a couple of seconds.
-
I will now go away and hide under a rock :-[ :-[
-
No need to do that ;D
-
I will now go away and hide under a rock :-[ :-[
You would be welcome to make use of my brown-paper bag . . . :paperbag: Just make sure that I am not in residence beforehand! ;)
-
All working and averaging under 2 error secs per hour which I suppose isn't too bad when G.INP isn't enabled but whether it is low enough to drop the interleave level I have no idea
However this part of the log confuses me - how can the login name / password be incorrect
24 Jul 2015 13:18:09 Recording started
24 Jul 2015 13:18:16 IP address is now <snip>
24 Jul 2015 17:58:11 Incorrect login name or password
24 Jul 2015 21:36:15 Timeout while retrieving stats
24 Jul 2015 21:36:15 No stats received
-
It looks as though there were just a couple of times when communication between DSLstats and the 8800NL stuttered. Is your PC directly connected by ethernet, or is it WiFi?
-
ethernet
-
Knowing myself I hesitate, but this morning DSL stats was showing below the graphs the SNRMs but not the Sync speeds. I had to close down and reboot.
-
Much as I want to help, diagnosing these occasional intermittent events is next to impossible. If there's some sort of pattern, or the events happen frequently, there's more possibility. If it's something I can reproduce, then it's much easier.
-
One question
I have set it up to show CRC errors per minute on the graph which really don't look bad but looking at the Router Statistics the only errors which are shown are
OH frame errors
RS uncorrectable errors
HEC errors
Are the CRC errors being reported one of these or something different given that the router isn't reporting them
-
CRC equals OH frame errors (shown as OHFErr in Telnet Data --> Connection Stats)
RS uncorrectable errors (shown as RSUncorr) has its own definition
HEC errors aren't graphed in DSLstats, but are shown in the Error Averages.
-
Much as I want to help, diagnosing these occasional intermittent events is next to impossible. If there's some sort of pattern, or the events happen frequently, there's more possibility. If it's something I can reproduce, then it's much easier.
Understood! I should have had added domething like "in passing"to show it was a mere added comment. :-[
-
Don't worry, I wasn't getting at you. Just explaining why I couldn't do much. :)
-
very minor quibble
see the attached graph of CRC errors
I put the computer to sleep last night and this was the result
-
If the computer is sleeping, DSLstats won't be collecting any data. But as it hasn't been paused, it treats the first sample after waking up as the next sample, with a straight line between them. If you're going to put the computer to sleep, it would be best to pause DSLstats first.
-
Eric I have noticed that after a quite a long time the Events log stops auto-scrolling to display the last entry and always displays the first line of the log when an entry is added. This happens after a number of days. Initially when first started it will auto-scroll as it adds log entries but eventually always displays the first line after adding to the log. This is obviously trivial but if you have a chance to resolve it I would appreciate it as it is a tad tricky to scroll down when viewing my desktop remotely from an adroid tablet or smartphone, which I do periodically to check on things.
Stuart
-
Stuart, I can see how this happens if you have a lot of entries in the event log. The length of the log is currently limited to 500 lines, and when it gets to that length the first entries are progressively deleted. Actually this seems rather pointless, and I'll remove it in the next release (soon).
-
Eric perhaps one solution would be to perhaps rather than enlarge the log give the options to set the auto-save value for the log to a number of lines (up to the maximum) and then to start afresh when it is auto-saved.
Stuart
-
OK, I'll give that some thought, Stuart.
-
This is now implemented in V5.6, which I'm preparing for release. When the event log gets to 500 lines, it's saved to the Snapshots folder with a time-date stamped filename, and the event log is cleared to start afresh.
-
This is now implemented in V5.6, which I'm preparing for release. When the event log gets to 500 lines, it's saved to the Snapshots folder with a time-date stamped filename, and the event log is cleared to start afresh.
Thanks Eric, I thinnk that will be great.
Stuart
-
Eric,
Is there any possibility you might be able to allow more samples per minute to be taken?
I remember in the RouterStats days I had samples every 10 seconds.
-
Not if you're uploading to MDWS, because MDWS only accepts 1 upload per minute. The same applies if you're also using HG612_Modem_Stats with the 'Co-operation' option set.
If neither of these situations apply, then the sample time can be reduced right down to 1 second, although 5 seconds is probably the practical limit, and 10 seconds the sensible limit.
-
I keep getting an access violation on Windows XP :(
-
Without more information there's little I can say. One thing to think about is the location of the DSLstats files - they should be in one of the folders owned by the normal user.
-
This is odd and I cannot see how it happened. I have found, after unsuccessfully attempting update to 5.6, that 5.5 has somehow, without my action got into Roaming rather than Local.
I am confused how that situation could have arisen. May I assume that I may safely move to its proper place in AppData\Local?
-
@renluop: I presume you're referring to the configuration files, not the main DSLstats files? There's no way the latter could move by themselves.
For the configuration files, in the Misc configuration section there's an option "Location of config files". It's possible that the new release didn't detect your location correctly, in which case moving them manually (while DSLstats isn't running) might be successful, but depending on how this happened, you might find that you have to set it up again.
-
Thank you for that. :) I did lose the snapshots, but they were in the picture files library and reinstated in the folder within my version DSLStats.
Hopefully, once I have new specs for my new eyes I won't miss config options!