Please keep testing instances (custom lists) running for a while, may be some instance will fail later.
We are preparing another testing HML file... if that instance will work fine as well, probably problem within some action
Regards
Alex
HostMonitor can't open dialogs, error in the event log
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 last time.
2) I have moved all the test HostMonitors to another machine so they don't interfer with the normal HostMonitor. I am running all 8 of the test lists I have received on that machine.
I did both of the above yesterday morning, so it has been about a day so far. I'll let you know what comes of it, and feel free to send any more tests you want me to run my way as I am more than happy continuing to try and find out what is going on.
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 last time.
2) I have moved all the test HostMonitors to another machine so they don't interfer with the normal HostMonitor. I am running all 8 of the test lists I have received on that machine.
I did both of the above yesterday morning, so it has been about a day so far. I'll let you know what comes of it, and feel free to send any more tests you want me to run my way as I am more than happy continuing to try and find out what is going on.
Last edited by astewart on Tue Aug 14, 2007 11:45 am, edited 1 time in total.
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 trying to access a dialog it gives pops up an error with:
"Access violation at address 006270BA in module 'hostmon.exe'. Read address 00000057" followed by a second error "Access violation at address 0042D47C in module 'hostmon.exe'. Read address 3B8BF090" These errors are nearly identical to the errors we have been getting with the standard hostmonitor, I am going to disable all of my POP3 tests in the main hostmonitor and see if that stops it from crashing.
One of the test lists finally had a problem also! It is the POP3 test list, and when trying to access a dialog it gives pops up an error with:
"Access violation at address 006270BA in module 'hostmon.exe'. Read address 00000057" followed by a second error "Access violation at address 0042D47C in module 'hostmon.exe'. Read address 3B8BF090" These errors are nearly identical to the errors we have been getting with the standard hostmonitor, I am going to disable all of my POP3 tests in the main hostmonitor and see if that stops it from crashing.
Does HostMonitor with disabled POP3 tests still work fine? We have created a lot of POP3 tests to check our servers but cannot reproduce any problem, everything works just fine.
I would say this is antivirus related problem but... you don't have any antivirus. Right?
Probably there is error in our code that appears under some rare circumstances We don't see it so far
Is it possible to use your servers for testing (if you could create some test accounts for us)? How many different POP3 servers you are monitoring?
Regards
Alex
I would say this is antivirus related problem but... you don't have any antivirus. Right?
Probably there is error in our code that appears under some rare circumstances
We don't see it so far Is it possible to use your servers for testing (if you could create some test accounts for us)? How many different POP3 servers you are monitoring?
Regards
Alex
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 accounts per server (3 each). Some of the tests use the default timeout value of 60 (9 tests), and some use a timeout value of 1 (4 tests). So we have a total of 13 pop3 tests.
The pop3 test list you provided multiples the same tests mentioned above for a total of 104 tests in the pop3 testlist.
Unfortunately I don't have any servers I could let you personally play around on. I would be more than happy to run the pop3 testlist with a debug exe or more specific testlists or something though.
I thought about maybe trying to construct a POP3 converstation using the TCP test to see if it has the same problem, but I haven't had time to try and figure that out yet.
There is no antivirus running on either our main HM or test HM system.
Our pop3 tests are monitoring 3 servers checking multiple test accounts per server (3 each). Some of the tests use the default timeout value of 60 (9 tests), and some use a timeout value of 1 (4 tests). So we have a total of 13 pop3 tests.
The pop3 test list you provided multiples the same tests mentioned above for a total of 104 tests in the pop3 testlist.
Unfortunately I don't have any servers I could let you personally play around on. I would be more than happy to run the pop3 testlist with a debug exe or more specific testlists or something though.
I thought about maybe trying to construct a POP3 converstation using the TCP test to see if it has the same problem, but I haven't had time to try and figure that out yet.
We modified POP3 related code a little. I don't think that "mistake" could lead to crash... however lets try this update www.ks-soft.net/download/hm684c.zip
If it would not help, we will need to create some special utility for testing....
BTW: Do you use different mail servers in your environment? or may be all servers use the same version of mail software?
Regards
Alex
If it would not help, we will need to create some special utility for testing....
BTW: Do you use different mail servers in your environment? or may be all servers use the same version of mail software?
Regards
Alex
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 servers. If there are other features we want in the future we may upgrade then.
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 servers. If there are other features we want in the future we may upgrade then.