Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: toulouse on July 10, 2017, 04:26:24 PM
-
Hello,
I've recently noticed that in addition to my MDWS status showing as 98% complete, that I appear not to be uploading data consistently every hour. It seems that I am failing to upload at minute 57 or 58 of each hour, which means that small gaps appear in my MDWS graphs. My setup is a Billion 8800NL with Raspberry Pi (latest version with current software) running DslStats (v6.0.1). MDWS user name is the same as here, i.e. toulouse. I believe that this may have started following the recent MDWS 'outage', but I could be way off target there.
Is anyone able to offer any suggestions as to what may be causing this, and how I might avoid the situation and return to full stats and graphs.
Thanks for any constructive comments
toulouse
-
I have seen this as well on my pi3 using both 8800nl /hg612 and a vmg 8324. If I get a gap I compare the gap on other stable uploaders to see if it mdws or not . Sometimes my 8800nl seemed to get the probable telnet occaisional lock out. I have just reverted back to 8324 with windows dsl stats instead of my pi3 as a test.Seems to be back at 100% again for now.
I think comparing your gaps is a good place to start just to check.
-
Looking at logs etc I'd guess that your setup (RPi) can't cope with the four files that are uploaded at that time each hour (Bits/Tone, HLog, QLN and SNR/Tone). You are timing out at your end.
Exactly why I have no idea - except that you are uploading at 42 secs past the hour. If you can get that earlier (turn off Hg612 Modem Stats co-op?) or restart DSLStats just after the hour it will give you more time to upload.
There are other people with gaps in the uploads but they are for different reasons.
-
Thanks for your comments Tony and skyeci. As a starting point, I have tried restarting DslStats just after 5pm this afternoon, and will check back in around an hour to see if a gap occurs around 6pm.
I've checked the DslStats Event Log, but cannot find anything that suggests uploads are failing. Should I be checking something in MDWS instead ?
toulouse
-
You are still uploading at 43 secs or so. Are you sure you haven't got HG612 Modem Stats co-operation checked in DSLStats? Turn it of if so. It's in Configuration > Misc and needs unchecking. (Always asssuming that the RPi version has the option which I don't know).
If you look at the top right hand corner of a pane where the status bar is, where it says Uptime, on the second row that shows the Uptime figure, after that there is a figure in square brackets [43s] which show the time you are uploading at....
-
.Are you running your 8800nl as a modem & router or modem only out of interest?
-
@skyeci - I'm using the 8800NL as both modem and router, as I have been for many, many months
-
I would be inclined to try a windows build to see if it improves the upload status. Even if for just a couple of days. Perhaps if it resolves it you could try rebuilding the pi?
Are you running hg612 stats as well or not?
-
I think he's missed my post.... He doesn't need to be running it, you can set the option anyway.
-
I just wondered if he has hg612 running on a windows device as it doesnt work on a pi...
-
@skyeci and @tbailey2
Sorry guys, I had to step away from the computer for a while.
I do have a Windows 8.1 laptop which I will try tomorrow.
I definitely DO NOT have Hg612 Modem Stats running or enabled in DslStats on the Raspberry Pi. I was never able to get it running properly even when I was using a HG612 many, many months ago. Probably operator error !! However, as far as I am aware, since moving DslStats on to the Raspberry Pi, I thought everything was working OK, until I noticed the current problem(ette).
toulouse
-
Sorry to jump in , I have the same problem with the gaps ,using a billion 8800nl as a modem/ router with Dsl stats on my win 8.1 pc no Hg612 modem stats ticked
Same username for stats as forum name
-
Yours isn't the same problem though and is much worse. Have seen this several times before and seems to be the Billion 8800 itself. It's been noted before but I'm unaware of any solution or why it only affects some examples.
@toulouse
Your last few hourly uploads have been okay although I see you haven't changed the upload time yet.
-
In modem only mode I could obtain 100% on the pi3 but not as consistent as my current windows build when being used with my 8800nl.
It could be because perhaps the 8800nl in modem/router mode might be too busy. I would try the windows build before changing anything else and see if it improves or not
-
Yours isn't the same problem though and is much worse. Have seen this several times before and seems to be the Billion 8800 itself. It's been noted before but I'm unaware of any solution or why it only affects some examples.
Thanks, some time if I reboot the router it corrects it's self till I have to turn of the pc then it returns
Thanks again
-
Probably telnet session locking out..
-
Just a quick follow-up to my questions from yesterday.....
.....it looks to me as if things are now back to normal, i.e. no more gaps in the MDWS graphs and the status is now showing as 100%.
@tbailey2 - could you confirm that my uploads are now working as they should be please. Also, I would be interested to know how I might influence the time at which uploads are initiated, if it is possible to do so.
Thanks
toulouse
-
Aside from the HG612_Modem_Stats co-operation (which is for Windows only) the way to influence the upload time is to start recording soon after the start of a minute. I think Tony's suggestion was a good one, because the Raspberry Pi is a low powered device, and the extra processing required once an hour for the QLN, HLog, Bitloading and SNR per tone graphs could possibly be a factor in the missing uploads. If you start recording near to the start of the minute you have the maximum time for processing the data.
Of course this all depends on the accuracy of the clock in the device running DSLstats, and you should make sure that the RPi clock is properly synchronised with NTP.
-
Looks fine at the moment although why it suddenly did so I have no idea.
You still have NOT definitely confirmed that you have physically checked (Configuration > Misc) that the HG612 Modem Stats Cooperation option is NOT enabled.
Assuming you can see the DSLStats window, every time it takes a sample, it says Sampling at top right for a short period (here it's for a fraction of a second). If you load it and start it up say at about 50 secs to the hour, it will pause for a while and not sample before about 5 secs past which is what you want. The only reason I know of why it would sample at 43 secs is if the co-operation entry is set (irrespective of whether the HG612 program is actually running) which delays it past 35 secs (from memory)? Other than that maybe your pi is knackered and/or running extremely slowly or ......
Maybe Eric can comment please?
EDIT
Eric didn't see your post sorry. Checking the RPi clock would be a very good idea ;)
-
You still have NOT definitely confirmed that you have physically checked (Configuration > Misc) that the HG612 Modem Stats Cooperation option is NOT enabled.
It can't be enabled on the Raspberry Pi, it's for Windows only.
-
So it isn't present on the RPi menu, that's what I've been trying to find out.
-
@Eric and tbailey2,
Thanks both for your additional comments.
I can confirm that the HG612 Modem Stats Cooperation is DEFINITELY NOT SET and neither is HG612 Modem Stats running on any machine here. I have a mix of the following :
Mac-Mini running OSX (latest version)
Windows XP and 8.1
Raspberry Pi 3 x4 plus various other Model B - not all running at once. DslStats is running on one of the Pi 3s.
I have taken on board the suggestions about ensuring that the clock time on the Pi is correct, and will look into checking and updating this via ntp perhaps every 3 or 4 hours or more frequently if thought wise. Having said all this, it does strike me that the situation appears to have cured itself since late yesterday afternoon, and whether that is as a result of the various things I tried yesterday or that magic that technology provides, I am not really sure.
Anyway, for now, I'll keep an eye on things and let you know if the problem reappears.
Thanks,
toulouse
-
On the Linux and Raspberry Pi versions of DSLstats the option can be seen, but it's greyed out and can't be enabled.
-
it's greyed out and can't be enabled
It would be beneficial to me (and maybe others) if this was possible to be set. I have hg612stats running on a windows machine and DSLStats on a raspberry PI.
I have to take care that the PI starts at hh:mm:10 and the windows machine task is set for hh:mm:45.
Ian
-
Yes, I can do that. It never occurred to me that some users would want to run the two programs on separate machines.
When that option is enabled, DSLstats samples at 35-40 seconds after the minute, as HG612_Stats is assumed to start on the minute.
-
HG612_Stats is assumed to start on the minute.
Good idea :)
That's another thing - if HG612 Stats starts exactly on the minute +/- it doesn't upload to MDWS properly as small differences in the time can cause duplicate uploads- I remember that Ronski added an option to delay the start if needed quite recently.