Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: roseway on May 18, 2017, 03:46:52 PM
-
This version replaces v5.9.4, which had some issues with the telnet timeout arrangement on some systems.
Windows users: please remember that DSLstats must be installed in the user's own section of the directory hierarchy, not in the top level of C:\ or in Program Files or Program Files(x86). The self-extracting installer installs the files in an appropriate location by default.
http://dslstats.me.uk/downloads.html
-
Linux 64-bit ordinary version. Downloaded, installed and executing. All seems to be well.
-
Thank you.
-
Linux 64-bit ordinary version. Downloaded, installed and executing. All seems to be well.
Ditto for RPi
-
Thank you.
-
Likewise Win32 :)
-
Now working okay on the rpi with the huawei hg635
Thanks for all the time and effort you put in to this software.
Ian
-
Downloaded 5.9.5 windows installer then used your uninstaller to remove previous version then ran the your exe installer all working well on Windows 10 Creator pro 64bit and and nice to see your blue paw icon back.
EDIT also running on the RPI I don't expect any issues to come to light on this hardware :fingers:
-
All ok at the moment :) Thank you for your hard work.
-
Thank you.
-
Looking at the log since lunch time :o
I have not seen it that bad :(
Have you got a timer on now as each day at about 18.00 hrs it starts going wrong. !
The graphs look ok still.
-----------------------------------------------------------------------------------
19 May 2017 11:43:01 Recording started
19 May 2017 11:43:05 IP address is now xxxxxxxxxx
19 May 2017 12:43:04 Auto snapshots taken
19 May 2017 13:43:19 Auto snapshots taken
19 May 2017 14:43:20 Auto snapshots taken
19 May 2017 15:43:35 Auto snapshots taken
19 May 2017 16:43:50 Auto snapshots taken
19 May 2017 17:44:05 Auto snapshots taken
19 May 2017 18:44:20 Auto snapshots taken
19 May 2017 18:57:47 Timeout while collecting system uptime
19 May 2017 18:57:47 Telnet timeout
19 May 2017 18:57:50 Unable to login to modem/router
19 May 2017 18:58:04 Unable to collect stats 3 or more times in succession
19 May 2017 18:58:04 Unable to login to modem/router
19 May 2017 18:58:19 Unable to login to modem/router
19 May 2017 18:58:35 Unable to login to modem/router
19 May 2017 18:59:03 Timeout while collecting bitloading data
19 May 2017 18:59:03 Telnet timeout
19 May 2017 18:59:06 Unable to login to modem/router
19 May 2017 18:59:19 Unable to login to modem/router
19 May 2017 18:59:34 Unable to login to modem/router
19 May 2017 18:59:49 Unable to login to modem/router
19 May 2017 19:00:04 Unable to login to modem/router
19 May 2017 19:00:32 Timeout while collecting signal attn data
19 May 2017 19:00:32 Telnet timeout
19 May 2017 19:00:36 *** Second stage login failure. Did you enable the option "Requires command to enter shell" by mistake?
19 May 2017 19:00:36 Second stage login failed
19 May 2017 19:00:49 Unable to login to modem/router
19 May 2017 19:01:04 Unable to login to modem/router
19 May 2017 19:01:32 Timeout while collecting signal attn data
19 May 2017 19:01:32 Telnet timeout
19 May 2017 19:01:35 Unable to login to modem/router
19 May 2017 19:01:49 Unable to login to modem/router
19 May 2017 19:02:04 Unable to login to modem/router
-
I regularly see unable to login to router in my log, I put it down to the WD9970 router being hacked and not being powerful enough and me using wifi to access stats. Still on 5.9 btw.
-
@tickmike: I think something else must have changed. With v5.9.5 I reverted to the telnet timeout arrangement which was used prior to v5.9.4, but with slightly increased timeout values. I really don't believe that this could have resulted in more telnet timeouts. And there's nothing in DSLstats which is timed to happen at around 18:00.
@banger: I can't disagree with your conclusion.
-
Not sure what :hmm:
I can go back to 5.7.1, 5.8.2, 5.9, 5.9.3, 5.9.4
Would you like me to try one ?.
-
Not sure what :hmm:
I can go back to 5.7.1, 5.8.2, 5.9, 5.9.3, 5.9.4
Would you like me to try one ?.
It might be an idea to revert back to the current release version, 5.9, move your existing configuration files to a safe location and set-up/re-configure as if it is a new installation of the utility.
-
It might be an idea to revert back to the current release version, 5.9, move your existing configuration files to a safe location and set-up/re-configure as if it is a new installation of the utility.
I have put 5.9 in another directory and re-made the start up link, Listening to Radio One at the moment so I will re-boot before I go to bed ;D
Laptop is on 24/7 so see what the logs are like at lunch time.
-
Just had a look at 5.9 logs.
20 May 2017 02:09:54 The configured modem/router is Huawei HG612
20 May 2017 02:09:57 Recording started
20 May 2017 02:10:01 IP address is now xxxxxxxxxxxxxxx
20 May 2017 03:10:00 Auto snapshots taken
20 May 2017 04:10:14 Auto snapshots taken
20 May 2017 05:10:29 Auto snapshots taken
20 May 2017 06:10:29 Auto snapshots taken
20 May 2017 07:10:44 Auto snapshots taken
20 May 2017 08:10:44 Auto snapshots taken
20 May 2017 09:10:59 Auto snapshots taken
20 May 2017 10:11:14 Auto snapshots taken
----------------------------------------------------------
will look later.
.....................................................................
On my spare laptop with a Spare HG612 hooked up to it with 5.9.5 (not sure if this is a good test )
Just set up.
The log is ok at the moment but the word 'Sampling' is up all the time !.
-
I have put 5.9 in another directory and re-made the start up link, Listening to Radio One at the moment so I will re-boot before I go to bed ;D
Laptop is on 24/7 so see what the logs are like at lunch time.
This test was ok with two errors , Unable to login to modem/router, Unable to collect stats 3 or more times in succession. Both when a DLM re-sync happened. so no problem.
-
On my spare laptop with a Spare HG612 hooked up to it with 5.9.5 (not sure if this is a good test )
Just set up.
The log is ok at the moment but the word 'Sampling' is up all the time !.
With the word 'Sampling' still there
I stopped the test after some time with lots of errors (as well as ' no stats available error' as it was not on the DSL connection.)
I always use a sample time on 15 seconds.!
Hope this helps.
-
Thanks for the information :)
-
Eric I was running 5.9.4 but today changed to 5.9.5. On start up it does not show the correct modem/router model although this did not seem to stop it from working. I stopped, corrected router model and started recording again. I though it should remember the correct modem/router across version changes and program restarts, or perhaps is this simply a display bug?
Stuart
-
It should remember it, Stuart, although it has no effect on the operation of DSLstats. It's just informative (and a convenient way of getting most of the configuration details set up initially). Now you raised it, I see that mine has forgotten the modem type as well. I'll have a look at it.
-
I decided to update to 5.9.5 as I have DSLStats hang up on PC restart after a power cut last night. However I have now gone back to 5.9.4 after getting floating point errors this morning. I'll see what happens now with 5.9.4.
Stuart
Still seeing floating point errors on 5.9.4 as well. Will try clearing settings and try again.
-
Tried again with 5.9.4 but still getting floating point errors. Now to go back to a previous release.
Stuart
Now running 5.9.3 to see if I still get these errors. Note I finally started 5.9.4 with a new .ini file.
-
I went back to 5.9.5 this evening and created a whole new directory and added the contents of the zip file. I then copied the dslstats.ini (new one) across but left all the other files in the old directory (like traffic & stuff). So far no more fp errors. The problem I suspect was a power cut had corrupted a file but no way to find out which one. Hopefully in the morning I'll know if I've been successful.
Stuart
-
I'm fairly sure that there's no difference between recent versions of DSLstats which would account for the FP errors in some cases. So I look forward to your latest results. Another factor which can affect this problem is where the DSLstats files are installed, and DSLstats does misbehave if it's installed in the top level of C:\ or in Program Files or Program Files(x86).
-
Eric DSLStats is installed on the D: drive. This morning all seems good now, so something got corrupted by the power failure but no idea what. I am not monitoring traffic either before or now but was some time ago. So if you ignore the traffic files what else could cause FP errors. I had overwritten all the distribution files so all of them got replaced. It must have been one or more of the files created at run time. Anyway it has been running 5.9.5 since late yesterday evening with no issues so far (fingers crossed).
Stuart
-
I wish I could answer the question, Stuart, but as far as I can determine, all of the floating point operations in my own code are protected by error trapping, so they shouldn't result in any unexpected error messages. So if these FP errors are genuinely produced by DSLstats they must originate somewhere in the library code which I use. As I've said elsewhere, chasing this down when I can't reproduce the errors myself is beyond me at present.
-
Eric if it is any help at all I still have the DSLStats directory which has causes the FP errors if you wanted to have a play with any of the files, or would like me to have a look at the contents of any specific files.
Stuart
-
Stuart, if I could have a copy of the suspect configuration files I'll have a look at them to see if anything leaps out. Just the files, not the folders in the same location. You may want to remove the passwords from dslstats.ini, although they're encrypted and I have no interest in them.
-
Sent you the ini files. Let me know if you want anything else.
Stuart
-
I've received them, thanks. There were only two files though. I would have expected es_data.txt and errors1.dat as well - were those not there?
-
I've received them, thanks. There were only two files though. I would have expected es_data.txt and errors1.dat as well - were those not there?
Sorry Eric, I'll send those now, when you said config files I thought of ini files only.
Stuart
-
Received, thanks. Sorry if I wasn't clear.
-
Eric I was running 5.9.4 but today changed to 5.9.5. On start up it does not show the correct modem/router model although this did not seem to stop it from working. I stopped, corrected router model and started recording again. I though it should remember the correct modem/router across version changes and program restarts, or perhaps is this simply a display bug?
Stuart
I think this one can be put to bed. It's the consequence of a corrupted routers.dat file which appeared in v5.9.2 and was half corrected in v5.9.3. I made an amateurish error in only providing for 51 models in the list (don't ask) and when the number exceeded this it caused problems with the models at the end of the list, i.e. the Zyxel models. This was resolved in v5.9.5, and from then on DSLstats should remember the selection.
-
Thanks Eric, trivial I know but good to get it resolved.
Stuart