My Dude server is running on a Windows XP Machine.
The Dude service keeps crashing. It has been running on this machine for almost a year and had no issues till recently. I am sure we are taxing the system with the server and are looking at putting on a new server but need to keep this one running till we get a new one in place.
The server is.
Windows XP SP 3
Duel Pentium 4 3GHz
2 GB of Ram
There is over 200 items being monitored right now. Just recently it started to have issues as we have added devices. We have removed all other running processes we could in the Dude except the Anti Virus.
I have attatched a copy of the error but it does not say much.
Are you running v4 beta? If your dude.db file is 2GB or more search this forum to compact the database and do that. The reason you would have a db file larger than 2GB is the default chart times if they are not default.
If you don’t have a 2GB database file start monitoring memory in the dude server. If you have a memory leak is it most likely due to probes running against windows boxes. Pick a group of windows probes, disable them… divide and conquer from there.
If the computer is very slow change the polling rate to 1 minute or more.
We are moving this to a new server and see if this helps as it it is still crashing with polling every 5 minutes. Will see if server is just not fast enough to keep up.
Update your windows SP3 with the help of windows update and after update restart the computer.
Repair your dude server and try to run & have you really sure that your computer has no virus…
Having this same issue on Windows XP and Windows Server 2012 R2.
This only started occurring about two weeks ago and but has been running solid for over two years before that. Our database file is only about 350MB.
I exported from win xp into the fresh install on win serv 2k12 hoping it would clear up the leak.
I sorted through the recent action log changes within the last month and nothing sticks out that would be different then any other device being monitored.
Has anyone ran into this and found a specific solution?
The problem seems to stem from SNMP. Once I disabled global SNMP, the problem stopped. I then proceeded to enable only the devices that need it and with v2. So far its been running fine.
