Monitoring_Thread2.exe

I am continuously getting this error on the workstation running ServersCheck Software.



Monitoring_thread2.exe szAppVer 7.16.0.0 szModName perl58.dll szModVer 5.8.9.825

C:DOCUME~1MR1847~1.BLULOCALS~1TempWERd479.dir00monitoring_thread2.exe.mdmp

C:DOCUME~1MR1847~1.BLULOCALS~1TempWERd479.dir00appcompat.txt

Is this running on a dedicated system? Is there any AV software installed?



Make sure that it runs on a dedicated system as it might be caused by a conflict from another installed software. Same issue with antivirus. ServersCheck performs disk writes often (disk stored data) and AV software scans it continously slowing down system.



ServersCheck unlike many of its competitors, has a built-in fail-over system so that when a subcomponent (such as above one) fails, then it is automatically restarted.

Dedicated Appliance, No Antivirus on this workstation.

As said previously, the message can be ignored as the component is automatically restarted and as such monitoring is not affected. You should see the monitoring_thread2.exe in your task manager

I am having the same issue, dedicated machine w/o AV, but the monitoring _thread2.exe does not restart all the time. Only restarting the monitoring service will restart monitoring_thread2.exe. ver. 7.15.10

Gmillerarmt: what is in your watcher.log (/logging subdirectory)?



Normally the monitoring_watcher.exe continously verifies each monitoring component and if failure is detected then it is restarted.



What would help is doing following:

- 1/ stop the monitoring service

- 2/ double click on monitoring_manager & s-graphs & s-alerts

- 3/ run from command prompt in the serverscheck directory

monitoring_watcher > debuglog.txt



If the monitoring_thread2.exe crashes then send us the debug output

This is the only entry in the watcher log. # Tue Jul 14 12:06:02 2009 Sending alive message to



The process won't crash while i am watching it but I will let it run a few days to see if it does crash.



Serverscheck monitoring_thread2.exe crashed a couple of days ago and I haven't had monitoring.

We have uploaded a new build of the monitoring_watcher component.



Download it and replace current with the downloaded one after having taken a backup.



This build will provide additional debug info while running as a service - no need to run in debug mode.



When you see the error message on the screen as thread initiator, then reply with content of the watcher.log file.



For all: make sure that NO antivirus system is running on the host running the ServersCheck Monitoring Software.



http://files.serverscheck.net/debug/moinitoring_watcher.zip