Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: roseway on March 27, 2013, 08:02:40 AM
-
Changes since v2.6:
- improved the handling of update notifications, with user options
- update notifications now display the changelog
- fixed issue whereby system close button would instantly close program when system tray options were enabled
- fixed issue whereby "per minute" graph values were always shown as whole numbers
- improved the handling of error conditions
- added option to save login diagnostic information to the event log (enabled by default)
- changed the order of event log entries to show sequence of events more clearly (oldest first)
- using special login, extra commands can be sent to the router after logging in for the first sample in a session
- added option of command line parameters "minimise" (or "minimize") and "startrecording"
- added plots of maximum attainable rates to the connection speed graph
http://rsux.plainroad.me.uk
-
Eric its running OK here. One small point is that your new X with down arrow has moved to the left so that when Sampling is displayed it overlays the X. Linux 32bit.
Stuart
-
Thanks Stuart. I can see what's happened there - the Exit button should be glued to the right-hand end of the toolbar, so when you resize the window the button stays in the same relative position. But it's lost its glue and now stays in the same horizontal position as you resize the window. I'll upload fixed versions later this morning.
-
Fixed version 2.71 now uploaded.
-
Eric that's sorted the X thing. Also I like the new download options to use a custom directory which worked fine.
Stuart
-
Thanks Stuart
-
If the attainable is the same as the sync it will only show the attainable rate (layer's overlap).
Nice update though :)
-
If the attainable is the same as the sync it will only show the attainable rate (layer's overlap).
Yes, and if the attainable rate is very close to the actual rate the graph looks a bit messy, which is why I added the options to show/hide the attainable rate plots. I may add the possibility to display the attainable rates on a separate graph if people think it's worth it.
-
Eric I still have the floating point error if running minimised and could not see the event log to see if there was anything in it.
Stuart
-
Possible to add a higher clipping value of 200 on the CRC errors? :D
Edit: Changing the value no longer works doesn't apply the change to the graph.
-
Eric I still have the floating point error if running minimised and could not see the event log to see if there was anything in it.
I wish I could reproduce this, but I can't. Could you copy your rsux.ini file to me please, so I can check if there's anything different about your configuration which might help to locate the problem.
-
Possible to add a higher clipping value of 200 on the CRC errors? :D
Edit: Changing the value no longer works doesn't apply the change to the graph.
Yes, I can increase the maximum value.
When you say it doesn't work, are you saying that changing the value doesn't rescale the graph, even when there are values plotted which are higher than the current maximum Y axis value? What I mean by this is that increasing the clipping value won't rescale the graph if all the values currently plotted are within the present Y axis range.
-
Yeah, you were right normally it's above it you see. :D
Could be nice to increase the value as mine often goes above the 200 limit.
-
Eric I still have the floating point error if running minimised and could not see the event log to see if there was anything in it.
I wish I could reproduce this, but I can't. Could you copy your rsux.ini file to me please, so I can check if there's anything different about your configuration which might help to locate the problem.
Yer tis .....
Dont mind running a debug version if it helps....
Stuart
-
Eric,
With one annoying (for me) exception this version runs OK so far. All previous versions survived windows standby OK, but this one halts after a standby and has to be manually restarted, this of course looses the traces up that that point. I hope it is not too hard to see what has changed.
I get the message "Unable to login to router" in red at the top. That message occurred previously but it remained sampling and recovered. This time it stops recording and as noted a manual restart is needed.
les
-
Yer tis .....
Dont mind running a debug version if it helps....
Stuart
Thanks Stuart. I see that you have some automatic snapshots set up. I wonder if that's the origin of the issue. I've left rs-ux running with your config (adjusted for my system of course) to see what happens.
I might take you up on the debug offer if nothing comes out of this test.
-
Eric,
With one annoying (for me) exception this version runs OK so far. All previous versions survived windows standby OK, but this one halts after a standby and has to be manually restarted, this of course looses the traces up that that point. I hope it is not too hard to see what has changed.
I get the message "Unable to login to router" in red at the top. That message occurred previously but it remained sampling and recovered. This time it stops recording and as noted a manual restart is needed.
les
I'm sorry about this. I'll give it some serious attention.
-
Has crashed (not responding)twice for me so far today, previous version didn't crash once.
-
Has crashed (not responding)twice for me so far today, previous version didn't crash once.
Were any messages displayed, or anything else which would help to trace the cause?
-
It just says it has stopped working, sorry.
-
OK, thanks, I'll try to find what changes from the previous version might account for the problem.
-
Hai, It crashed again when it does crash it seems to be when it's coming out of the tray.
This may be useful
Problem signature:
Problem Event Name: APPCRASH
Application Name: rsw.exe
Application Version: 2.7.1.0
Application Timestamp: 00000000
Fault Module Name: StackHash_c21f
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c000041d
Exception Offset: 743f4b02
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 2057
Additional Information 1: c21f
Additional Information 2: c21fc548df3ccc8cf9b54fd219af2a9c
Additional Information 3: 818b
Additional Information 4: 818b9d7327b167c9569eb88e612edab8
-
Yes, that may help, thanks.
-
One other v2.70-71 issue. A SNRM tweak with special login enabled fails "second stage login". It still works with normal login.
I am dropping back to 2.6 for the moment so as run through standby and as I doubt that I will add more, to your list for 2.7!!!.
I guess you will need to finalize with just bug fixes soon and not add new features and new bugs.
-
I guess you will need to finalize with just bug fixes soon and not add new features and new bugs.
Yes, that's my conclusion too, and it's where I'm devoting all my attention now.
-
Dont mind running a debug version if it helps....
Stuart
Stuart, I'd like to take you up on this offer. I've built a debug version of the 32-bit Linux v2.71. You can download it from:
http://s446074245.websitehome.co.uk/files/rs-ux32-2.71-debug.tar.gz
Many thanks.
-
Eric its running here now OK and minimised.
Just one point I did manage to get two copies running at one point (only one recording) and it gave
(rsux:16275): Gdk-CRITICAL **: IA__gdk_window_get_root_coords: assertion `GDK_IS_WINDOW (window)' failed
which might or might not be an issue, they were both minimised. However with only one copy running it seems fine so far, now to wait for the error.
Stuart
-
Eric we have lift off... here is the debug info from a failure while running minimised....
[New Thread 0xb785db40 (LWP 18188)]
[Thread 0xb785db40 (LWP 18188) exited]
(rsux:16299): Gdk-CRITICAL **: IA__gdk_drawable_get_size: assertion `GDK_IS_DRAWABLE (drawable)' failed
RaiseSrcDrawableNil 089C2DB0=GtkEventBox [VPrDb] LCLObject=088431B4=CRCTab:TTabSheet<Is MainWidget><Is CoreWidget>
ERROR in LCL: TGtk2WidgetSet.StretchCopyArea SrcDC=08B7B12C Drawable=nil
Creating gdb catchable error:
$0812863D
$080EC30C
$080EA9EB
$081B3C07
$081B37FA
$081C8E5E
$08169846
$0815B057
$083729DA
Program received signal SIGFPE, Arithmetic exception.
0x080eaa15 in RAISEGDBEXCEPTION (MSG=0x8b8082c 'TGtk2WidgetSet.StretchCopyArea SrcDC=08B7B12C Drawable=nil')
at lclproc.pas:865
865 lclproc.pas: No such file or directory.
Missing separate debuginfos, use: debuginfo-install GConf2-3.2.5-3.fc17.i686 atk-2.4.0-1.fc17.i686 cairo-1.10.2-7.fc17.i686 dbus-glib-0.98-2.fc17.i686 dbus-libs-1.4.10-7.fc17.i686 expat-2.1.0-1.fc17.i686 fontconfig-2.8.0-8.fc17.i686 freetype-freeworld-2.4.8-4.fc17.i686 gamin-0.1.10-12.fc17.i686 gdk-pixbuf2-2.26.1-1.fc17.i686 glib2-2.32.4-2.fc17.i686 glibc-2.15-58.fc17.i686 gtk2-2.24.13-1.fc17.i686 gvfs-1.12.3-1.fc17.i686 libX11-1.5.0-2.fc17.i686 libXau-1.0.6-3.fc17.i686 libXcomposite-0.4.3-3.fc17.i686 libXcursor-1.1.13-1.fc17.i686 libXdamage-1.1.3-3.fc17.i686 libXext-1.3.1-1.fc17.i686 libXfixes-5.0-2.fc17.i686 libXi-1.6.1-1.fc17.i686 libXinerama-1.1.2-1.fc17.i686 libXrandr-1.3.1-3.fc17.i686 libXrender-0.9.7-1.fc17.i686 libbluray-0.2.3-1.fc17.i686 libffi-3.0.10-2.fc17.i686 libgcc-4.7.2-2.fc17.i686 libpng-1.5.10-1.fc17.i686 libselinux-2.1.10-3.fc17.i686 libstdc++-4.7.2-2.fc17.i686 libxcb-1.9-1.fc17.i686 libxml2-2.7.8-9.fc17.i686 oxygen-gtk2-1.3.2.1-1.fc17.i686 pango-1.30.0-1.fc17.i686 pixman-0.28.0-1.fc17.i686 zlib-1.2.5-7.fc17.i686
(gdb)
Let me know if you need more...
Stuart
-
Thanks for that, Stuart. Now I must work out what it means.
-
Is it possible you could add averages of the total amount of errors per sec, min and hour please?
Displayed in text format
Thanks :)
-
Yes, I'll put that on the todo list, after I've fixed a couple of irritating bugs. :)
-
Eric we have lift off... here is the debug info from a failure while running minimised....
........
Let me know if you need more...
Stuart
Using your rsux.ini on my 'other' machine I've managed to reproduce the bug. It seems to be system dependent, as I can't reproduce it on my main machine. With the help of your debug information I've found where the error occurs and fixed it properly (I hope). It was in the code that handled automatic snapshots. I've got the fixed version running on my other machine, with your rsux.ini and minimised, and after several hours the error hasn't occurred, whereas previously it would happen on the first autosave, one hour after starting. I'm going to do some more testing, but it's looking hopeful.
-
Eric that's good news. If you would like me to test it as well I am quite happy to do so since the problem always happened to me.
Stuart
-
Thanks Stuart, I'll upload a test version for you later today.
-
Stuart, I've uploaded a test version for you to try. It's a debug version, but don't run it with gdb initially at least, because gdb will probably throw up false positives (exceptions which are handled and don't affect program operation).
http://s446074245.websitehome.co.uk/files/rs-ux32-2.72-debug.tar.gz
-
Eric I'll run it in the morning now as the pc will be shut down soon.
Stuart
-
It's running minimised now so we will see if anything happens.
A couple of observations.
My DSL uptime has stopped incrementing after 49 days 17 hours 2 minutes and 46 seconds but the system uptime is still going at 59 days plus. I suspect this is a function of the data from my HG622 but wondered if anyone else is seeing this?
My other observation is that I notice it is problematic restoring the program from the systray. Right click and restore gets it back and immediately disappears back to the systray, but a single left click on the systray icon restores it OK.
Stuart
-
My DSL uptime has stopped incrementing after 49 days 17 hours 2 minutes and 46 seconds but the system uptime is still going at 59 days plus. I suspect this is a function of the data from my HG622 but wondered if anyone else is seeing this?
You can see the source of this data right at the end of the "Connection stats" section of the Telnet data - the line starting "Since link time". I just copy the time shown there directly.
My other observation is that I notice it is problematic restoring the program from the systray. Right click and restore gets it back and immediately disappears back to the systray, but a single left click on the systray icon restores it OK.
That's odd, I haven't seen this behaviour. Did it work properly previously?
-
My other observation is that I notice it is problematic restoring the program from the systray. Right click and restore gets it back and immediately disappears back to the systray, but a single left click on the systray icon restores it OK.
That's odd, I haven't seen this behaviour. Did it work properly previously?
Well I think its always done this but because of the crash I did not minimise much.
Stuart
-
My DSL uptime has stopped incrementing after 49 days 17 hours 2 minutes and 46 seconds
Just out of curiosity I got my calculator out, and it works out that this time is equal to 4294966000 milliseconds, a number which is very close to 2^32 (4294967296). So it's pretty clear that the router firmware stores this value in a 4-byte integer and it can't go any higher.
-
My DSL uptime has stopped incrementing after 49 days 17 hours 2 minutes and 46 seconds
Just out of curiosity I got my calculator out, and it works out that this time is equal to 4294966000 milliseconds, a number which is very close to 2^32 (4294967296). So it's pretty clear that the router firmware stores this value in a 4-byte integer and it can't go any higher.
Maybe I should re-sync ;)
Stuart
-
Eric this morning when I started rsux I got this error on start up:-
"<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">" is an invalid float.
Second time of starting it did not happen.
Stuart
-
My DSL uptime has stopped incrementing after 49 days 17 hours 2 minutes and 46 seconds
Just out of curiosity I got my calculator out, and it works out that this time is equal to 4294966000 milliseconds, a number which is very close to 2^32 (4294967296). So it's pretty clear that the router firmware stores this value in a 4-byte integer and it can't go any higher.
Eric I just got my calculator out and used the AS value on my HG622, this comes out about right for the time since DSL re-sync, so for the HG622 at least the AS value seems fine to DSL uptime. I suspect that the AS value may stop around 97 days assuming a 4 byte signed counter.
Stuart
-
Eric this morning when I started rsux I got this error on start up:-
"<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">" is an invalid float.
Second time of starting it did not happen.
Stuart
I've no idea where that came from. Rs-ux/w accesses the rsux website in a couple of places, but the headers on the rsux web pages are W3C referenced, not IETF. Unless it happens again, I really can't see where to look for this one.
-
My DSL uptime has stopped incrementing after 49 days 17 hours 2 minutes and 46 seconds
Just out of curiosity I got my calculator out, and it works out that this time is equal to 4294966000 milliseconds, a number which is very close to 2^32 (4294967296). So it's pretty clear that the router firmware stores this value in a 4-byte integer and it can't go any higher.
Eric I just got my calculator out and used the AS value on my HG622, this comes out about right for the time since DSL re-sync, so for the HG622 at least the AS value seems fine to DSL uptime. I suspect that the AS value may stop around 97 days assuming a 4 byte signed counter.
Stuart
Yes, I agree with that, but unfortunately the AS value isn't consistent between different types of router. As I've been typing it's occurred to me that one way to handle this would be to retain the present system until the time gets up to 49 days 17 hours 2 minutes and 46 seconds (or thereabouts), and then switch over to displaying the AS value.
-
Eric if the user selects HG622 in the router type you could switch this automatically, obviously if they set up manually and you dont know router model then you could leave as is.
Stuart
-
I can certainly give that some consideration, although it won't apply only to the HG622 - I'm currently using the HG612, and that uses the AS value in the same way. To do it properly I would need to have a little database of compliant devices. I'm guessing here, but it may perhaps apply to all devices using the BCM 6368.
-
Eric this test version has been running now for a while and done several snapshots with no issues at all. I suspect the problem I had yesterday with the funny error was due to some glitch on the net considering the header was not from you page. Does look like you've fixed the error I was getting.
Stuart
-
Thanks Stuart. I can't think of any other explanation for the odd error. I'm currently testing solutions to the other reported issues, then I'll be uploading a new bugfix version.
-
Eric anytime you would like some additional testing let me know as I'm always happy to oblige if I'm around.
Stuart
-
Thanks again Stuart.