Hey Everyone,

Just like the title suggests; when I try to open Device Details with the Dude 2.2, it often crashes, thus requiring me to close the program, and re-open.

This seems to happen somewhat frequently, which is annoying for what is ostensibly a very good piece of network management software.

Any ideas? Running on one of our servers, a Compaq ProLiant ML570.

Adam

How are you running your client? I had this problem when i was running the client off a network drive i moved the program local and it stopped.

I have the program running on the local "C" drive of the Proliant Server. (Actually four drives working in RAID 5)

I use it by remote-desktoping over there and looking at it when I want to see what's going on.

Darn thing wants to freeze when I look at the device details of something in the network.

Adam

I am experiencing the same issue. I have The Dude setup as a service on the server. I remote into the server to manage the software (installed in the default location on C:). Some devices will work just fine, and some (when viewing the settings) will freeze and crash. I have noticed this is v2.2 and v3.0 beta 6 (separate installs on separate servers).

Thank you in advance for any suggestions.

Same EXACT thing here.

Since it is raining this morning, and there are no installs to do, I will be experimenting with putting it on another server and seeing what that does.

This can be a major headache when we are trying to rely on it.

Otherwise, it's great!!

Adam

Ive got some potentialy helpfull info on debuging this. I in the services window removed the services from a device doing this. This allowed me to it opened fine except it shows 4.29G unknown services and 1 unstable service. The services tag shows empty and the device status shows unknown. I figure to someone who coded the thing this might be helpful.

I don't know if that would do us any good; we use the Dude as an early warning system to notify us when a station goes off line.

This is why we need to keep the Ping service running on all of the devices; it is really important to make certain that someone is watching the store when we are out in the field.

Adam

the crash is 'only' on the client end and monitoring is continued im simply saying removing all services gets you back into the device if you have settings or data you want to write down and you would need to remove the device completely and re add it to avoid the particular glitch i am encountering with mine. I am aware of what we all use the dude for, and from all the information i have seen here and in my experience actual monitoring wouldnt be impaired.

How often does your server reboot? And is the dude server shut down before it does? Just another stray thought.

My server reboots perhaps twice per year. The Dude runs on a machine that does DNS lookups, as well as Mail Server work. That's all. The server is a ProLiant ML570.

I too have discovered that if I am to remove a device, and then add it back in I may be able to work around the crashing glitch.

Kind of a shame, really. I like the way that the Dude can share information with everything, all over the map. The SNMP functions as well as the RouterOS stuff is quite handy.

Upgrading to the recent edition didn't seem to be able to fix the bug, I tried that already.

Adam

Hey All,
I'm having the same problem.
I didn't see a fix for it so I thought I'd bump this forum.
Thank you MT staff for the fix in advance!
Rod Neal

The other issue that I seem to be having is the fact that the graphs aren't behaving well.

I tried to follow the "recipe" for making The Dude graph client signal strengths here, but The Dude seems to lack the stability to be able to graph the functions.

It rejects the "data sources" as created by the recipe.

I really like The Dude for it's ability to watch things and monitor things, I wish that it would just be more stable and behave as expected.

Adam

The only way I have tested/read how to fix this, is to completely delete the device. Using the "Discover" option, let the Dude discover the device and services by IP. I have not noticed any issues with "nodes" that I have done this with. I know it is not really a "fix", but maybe a workaround to avoid a little headache.

I too have discovered that if you delete the device and then add it back in when you want to look at something, the Dude doesn't crash. (Or it crashes less frequently)

I would like to try and avoid discovering the device capabilities, because we use it merely to watch for stations dropping out or becoming unstable. I don't think that nine people at our office want to be notified when SSH or Telnet is out of touch via the device........

Maybe I can discover it's capabilities, and then disable the ones that we're not using to try and encourage some stability. Something else to try.

Adam

I would like to try and avoid discovering the device capabilities, because we use it merely to watch for stations dropping out or becoming unstable. I don't think that nine people at our office want to be notified when SSH or Telnet is out of touch via the device........

You could set custom notifications for those services so they are just logged and not emailed.

Hmmm.... Could.

I'll give it a shot.

Thank you!!

Adam

[quote="Adam McLaughlin"]I too have discovered that if you delete the device and then add it back in when you want to look at something, the Dude doesn't crash. (Or it crashes less frequently)

I would like to try and avoid discovering the device capabilities, because we use it merely to watch for stations dropping out or becoming unstable. I don't think that nine people at our office want to be notified when SSH or Telnet is out of touch via the device........

Maybe I can discover it's capabilities, and then disable the ones that we're not using to try and encourage some stability. Something else to try.

Adam[/quote]

During the device "discovery" process (where you enter the IP of the node you are trying to discover), click on the services tab in that same window, and only allow the Dude to discover the services you would like to monitor (or remove the services that you do not want to monitor - device settings - after the node has been discovered). This will avoid any unnecessary notifications.

Thanks router pimp. I will give it a shot tonight when I get back from working in the field.

Adam

Hi.
I have the same problem.
1. Add device - not problem
2. Add service 1 Name:Disk 1 usage < 90% - no problem
3. Add service 2 Name:Disk 2 usage < 90% - appear the problem

4. Delete service 2 problem don't resolving
5. Delete service 1 problem is resolving

6. Trying to add service 1 Name:Disk 1 usage < 90% - problem appear again

7. Delete device and add it again not problem
8. Trying step 2 problem appear again


When you plan to research this bug ?

Thanks.

What I eventually did was to "add a device" and then let the Dude auto discover the device details. Seems as though if the Dude was allowed to discover the details, then everything would be OK. If you specified what you wanted to watch, then there were problems.

Don't ask me why this is, but it seemed to work, and since we run the Dude continuously, it was important for us.

Adam

Hm, this work !

Thanks

But this is a bug.

This is going to be another thread bump but I am experiencing this issue too.

Am running the dude 3.0rc3.

Unfortunately using the "discover" workaround is not a possibility for me. It seems to be a common problem aswell.

Using Vista 32 bit.

Are there any new updates on this bug?

I wrote about this in other tread. http://forum.mikrotik.com/viewtopic.php ... 59#p147878
I have pointed out the exact problem there.

In 3.2 this bug is fixed!

I have the same isue as people before.
On dude 6.38 running on RB3011 when I add device and next edit settings of device, client hang out/crash, after 15 seconds I get information like below:
This is strange because I use only one service to pooling After restart dude server the isue doesn't appear any more. In my opinion this is a bug connected with creating devices.
Do you have simmillar problems?
On production dude 4.0 on Windows Server I don't have this problem.

I found information about this isue also here: http://forum.mikrotik.com/viewtopic.php ... 59#p147878