Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[broadstairs]

I'd go with leaving it at 5 secs and if it only happens on the first sample then it is probably not an issue, however if it happens later on then it may be.

Stuart

[kitz]

I've been having a think about the "timeout" issue, and I see that Stuart also sees the same issue with the first sample of a session.

Just a note Eric, mine isnt at the beginning.   The time on mine was when I was logged into the GUI, which is when it usually occurs for me.
I'd installed 5.5.4,  checked all was working ok which it was. Then I went to the GUI which is why its 12 mins after startup.

[broadstairs]

I've been having a think about the "timeout" issue, and I see that Stuart also sees the same issue with the first sample of a session.

Just a note Eric, mine isnt at the beginning.   The time on mine was when I was logged into the GUI, which is when it usually occurs for me.
I'd installed 5.5.4,  checked all was working ok which it was. Then I went to the GUI which is why its 12 mins after startup.

I suspect I might see it when doing things in the GUI as well. I'd suspect that the processor or memory gets overloaded temporarily when accessing vis telnet and the web interface at the same time but I think you would need to be doing stuff in the web interface to cause it rather than just looking.

Stuart

[npr]

DSLstats v5.5.4 RPi version.
On the errors averages page, when clicking to increase the "days ago" count I get a "invalid floating point operation" error.

Don't remember getting this error with the previous version.
HTH

[roseway]

I know there are one or two anomalies in the average error rates, although I haven't seen this particular issue. I'll have another look at the relevant code, but in the meantime I suggest that you press the "Reset values" button to reset the data.

[npr]

Just tried it again and it's ok now. 

After a bit of testing, I find I only get this fault after restarting DSLstats and it goes away after the second sampling.
The fact I have it set to only sample every 10 minutes makes this more noticeable than on the default 1 minute sample time.
So I guess this is just a cosmetic issue, I don't see the need to spend time on it.

[roseway]

OK, thanks for letting me know.

[tickmike]

Thanks Eric for the new version  .
works well with one issue, on my DG834GT under 'stats' page it does not show DSLAM/MSAN type

Stats recorded 15 Jul 2015 14:56:47

DSLAM/MSAN type:           
Modem/router firmware:     AnnexA version - A2pB023o.d20e
---------------------------------

The logs are now better with No errors about 'can not log in ' .

[roseway]

Thanks for the report. Did it show the DSLAM/MSAN type previously? Some modems don't have the vendor command in their repertoire. The command for the DG834GT would be adslctl info --vendor

[tickmike]

Well it did show it, I will try my HG612  soon after the DLM sorts itself out because I have upset it .

Last week I got my isp Eclipse to try ADSL2 on my line so it may have something to do with that.

Will the 'Stats' tab details be stored in the DSLstats  folder files ?.

[roseway]

Will the 'Stats' tab details be stored in the DSLstats  folder files ?.

No, not unless you've set it up to autosave.

[krypton]

Thanks roseway for the new versions.
You tried to fix the "Per sample" option under the FEC graph in v5.5.1. Unfortunately DSLstats still does not switch to "per sample" if selected.

[roseway]

Unfortunately DSLstats still does not switch to "per sample" if selected.

I see you're right. I'm sorry about that. It will be fixed in the next version.

[tickmike]

From my post above, I tried the HG612   and it showed the DSLAM  data now I have put my DG834GT back it nows shows the data
Stats recorded 22 Jul 2015 10:41:49

DSLAM/MSAN type:           IFTN:0x70c8 / v0x70c8
Modem/router firmware:     AnnexA version - A2pB023o.d20e
DSL mode:                  ADSL2
Status:                    ShowtimeRetrain
Uptime:                    1 hours 34 min 7 sec
Resyncs:                   0 (since 21 Jul 2015 12:50:17)

 

But now it does not show QLN or Hlog

adslctl info --QLN
adslctl: ADSL driver and PHY status
Status: IdleRetrain Reason:     0

Tone number      QLN
   0            0.0000
   1            0.0000
   2            0.0000
   3            0.0000
   4            0.0000
   5            0.0000
   6            0.0000
   7            0.0000
   8            0.0000
   9            0.0000
   10           0.0000

etc.

adslctl info --Hlog
adslctl: ADSL driver and PHY status
Status: IdleRetrain Reason:     0

Tone number      Hlog
   0            0.0000
   1            0.0000
   2            0.0000
   3            0.0000
   4            0.0000
   5            0.0000
   6            0.0000
   7            0.0000
   8            0.0000
   9            0.0000
   10           0.0000

etc.



and it says
 up time of '1 hours 34 min 7 sec' but on the bottom of the GUI graphs,
 'System' up-time as 21hrs 56 min 26 sec
and
AS up-time as 21hrs 26 min 50 sec.

Should the 'up-time'  ones be the same. 

[roseway]

The value of Uptime which is given in the Stats summary is taken from a line near the beginning of the stats which starts "Link Uptime", if this line exists. I believe that the DG834GT may be one of the models where this line does exist. If it doesn't exist, then it's taken from the line "Since Link time =..." line near the end of the stats. If this line doesn't exist either, then it's calculated from the available seconds (AS).

The "System uptime" is the time since the modem was last booted.

The "AS uptime" at the bottom is calculated from the available seconds, and this is shown if the "Since Link time =..." line doesn't exist.

This probably isn't ideal for the DG834GT, but it was part of the compromises I had to make to get realistic uptimes from various modems which report the data in different ways.

Concerning the lack of QLN and HLog graphs, I suppose you do have these enabled in the "Items to Monitor" section?