Hi
I'm currently running Dude 4.0beta3. I have noticed this issue several times since I started using Dude, so it has happened with several Dude releases and with two or three different PCs, allways with Windows XP.

Symptoms are that Dude stops making graphs.
Services.msc -> Net Stop "The Dude Server"; Net Start "The Dude Server"
Ok, the graphs are here once again.
Sometimes I perform a trace before stoping and starting the Dude Service, sometimes after. I usually find a high snmp traffic with one of the devices being polled by The Dude. Today I have found it with a big router/switch which had the Polling disabled. In the trace I saw it was a snmpwalk of all its interfaces.
Today I have opened the Process Explorer and I have found that the process started with the command
"C:\Program Files\Dude\dude.exe" --server --service
was using 650Mbytes.

The workarounds I use may be
Deleting the device and defining it from scratch without AutoDiscovery.
Disable the polling in most devices with uninteresting information. This hasn't worked today.
Define the most devices I can with the "no snmp" community, and change this community to 1 tries, 3000ms timeout, version none.

I don't need to poll this router/switch, what I need is to graph the traffic in one of its interfaces.

Regards

I believe you are going to have to spend some time examining your probes to determine which ones have a memory issues. There was a post quite a while ago that claimed monitoring servers exposed memory leaks. I have not seen it in my setup but I monitor very few servers. Most likely you will find a specific probe that is written incorrectly but this is just a guess.

The dude will collect interfaces on the snmp tab for "monitored interfaces" even if polling is disabled. I have not seen it collect other stuff while polling is disabled so the things you are seeing might be caused by the memory leak and not the standard operation of the Dude or it was reading the monitored interfaces and not all of them.

I only manually add devices so I don't know if auto discover is causing you more issues, certainly setting no snmp should stop all polling but then you can't monitor interface traffic... My dude server is running ~160MB.

Here is a long term graph of my server showing memory usage is not growing. I would add your server to your collection and then divide and conquer. If you can graph memory utilization climbing it should be easy to determine when it stops. Good luck,
Lebowski