Maybe we can collect all the bugs we find in one thread and get a sticky on it?
If there is a location that is supposed to be used for bugs please inform me. Most of everything I have found is really no big deal but it would be nice to see them fixed.
If you use F11 and The dude is on your 2nd display it disapears, hitting f11 again restors it to normal.
When you creat a 2nd copy of a probe it doesn’t creat a new XML id tag? That is just just a guess. My two functions had the same graph even though they were looking at different OIDs. Deleting the 2nd copy of the function and creating from scratch fixed it. I have also seen links that seem like they have the same issue so I figure it has to do with the XML identifier somehow.
Running snmp walk on a few different devices will crash the client.
When you creat a 2nd copy of a probe it doesn’t creat a new XML id tag? That is just just a guess. My two functions had the same graph even though they were looking at different OIDs. Deleting the 2nd copy of the function and creating from scratch fixed it. I have also seen links that seem like they have the same issue so I figure it has to do with the XML identifier somehow.
Could you be more specific about the problem ?
Are you talking about Probes or Charts ?
Running snmp walk on a few different devices will crash the client.
It sounds as problems of these devices, perhaps they are crashing from SNMP requests. You have to contact manufacturer and inform them that SNMP is crashing their routers.
Hi sergejs, I just wanted to say first that The Dude is great and I really am enjoying it. The little quirks aside the program totally rocks.
Sorry I was a little unclear on the details for the probe issue but I will try to explain. I was planning on creating three probes to gather ups battery capacity, battery temperature and ups load. You can find the details of the probes in the probe thread. I created the first probe from scratch, highlighted it in the probe list clicked the copy and paste buttons then renamed the new probe. I changed the probe Available, Error and Value strings to different OIDs and once I had finished the changes to the new probe I highlighted it in the list of probes clicked on the copy and paste buttons again and proceeded to modify the 2nd copy of the probe. Once I had all the edits done I added the probes as services to my UPSs. While examining the 2nd copy of the probe it had the same counters as the 1st copy of the probe. I double checked that the 2nd copy of the probe was in fact using a different OIDs and it was so I just deleted the 2nd copy of the probe and recreated it from scratch. That fixed it.
As for the SNMP part. All my routers and switches are Cisco. The issue is when I run Snmpwalk on any device the first time after starting The Dude it works fine, close it and run Snmpwalk again it may or may not work, the window appears but it doesn’t draw all the parts of the window. It seems completely random as to when but if i run Snmpwalk more than a few times The Dude client stops responding. I know snmpwalk can run for a long time but the window when it works correctly updates as it finds the available OIDs. When it fails the only thing I can do is end task on The Dude and start it again… The router or switch I am walking doesn’t crash and as soon as The Dude is up and running I can immediately run Snmpwalk again on the same device and sucessfully Snmpwalk from a fresh restart of The Dude.
Like I said eariler The Dude is amazing and the quirks are easy to work around with RC2 out today I am looking forward to seeing how good the new version is. Thank you for the great program.
