KS-Soft

Thank you, that worked perfectly!

I am trying to setup a LDAP monitor, but I am getting the response "historical protocal version requested, use LDAPv3 instead"

Is there anyway to tell HostMonitor to use LDAPv3 when sending requests?

Thanks

I can't say that it is fixed, only that it isn't crashing. I'll keep it running for a couple more weeks to be sure. Right now though we are planning to just stay on 6.80 with POP monitors disabled since this seems stable, and the stability of the system is worth more than monitoring a few POP server...

Just wanted to give an update. Our main HM still hasn't bugged out since disabling POP3 tests. Additionally, since using the newest exe the POP3 test list is still running fine too.

All of our pop3 tests are hitting linux machines running Zimbra mail servers. We don't monitor anything else using pop3 tests. I'll put up your custom exe today and let you know if the pop3 testlist still encounters the bug.

Our main hostmonitor with pop3 tests disabled is still running fine. The pop3 testlist experiences the bug all the time, I don't even really restart it anymore. There is no antivirus running on either our main HM or test HM system. Our pop3 tests are monitoring 3 servers checking multiple test accou...

Monday morning update: Our main HostMonitor is still running normally. The POP3 testlist HostMonitor encountered the bug again.

So our main Hostmonitor had the bug again. Only this time when trying to bring up a dialog hostmonitor actually pops up a message saying "Cannot create dialog. Looks like the system is out of resources." One of the test lists finally had a problem also! It is the POP3 test list, and when t...

Update: No problems yet since my last post, on either the normal HM or the tests. All tests continue to run.

Just want to keep you guys up to date. I have done two things since yesterday: 1) Rebooted our primary HostMonitor server. It is now only running the normal hostmonitor again (using the recompiled exe). This should be a cleaner test, as I don't think I rebooted the machine itself when I switch exes ...

Bad news The HostMonitor using the new exe began having problems at around 8:27PM on Friday (PDT). None of the custom HostMonitor lists have experienced a problem. I am sending you the perf log of the process, but I checked it out myself and nothing weird happened appears to have happened around the...

Just wanted to give an updated. I have been running the 4 new test lists (using the standard 6.8 build) and our normal HostMonitor (using the exe with the old memory manager) since Friday afternoon. No problems as of yet. I'll keep you posted.

Our main HostMonitor service encounter the problem again (with the MySQL tests disabled). I noticed around 6pm, but I don't know exactly how long it was in a bad state but it couldn't have been more than a few hours. I have now switched to using the new exe you provided. None of the other hostmonito...

I have enabled a counter log for each hostmonitor process (yesterday when I started the 4 test lists), the counter log is recording every stat under the "Process" performance object. Highest handle usage in order: HostMonitor.exe, svchost.exe, services.exe, csrss.exe, lsass.exe, dllhost.ex...

I'll try to get you a performance measurement after 3 hours of time next time we restart the HM service. Unfortunately I don't have have many choices in reducing handle count, as I said the machine is a dedicated HostMonitor machine and has little else running. I'll check for a few extraneous servic...