All questions related to installations, configurations and maintenance of Advanced Host Monitor (including additional tools such as RMA for Windows, RMA Manager, Web Servie, RCC).
We are running Hostmon as a service on a Win 2003 server. the service is using approx 170MB of RAM. in addition, we connect using the RCC. this keeps getting disconnected and then will not reconnect and the process remains in task manager despite stopping the service in windows service control manager.
we have a seperate installation on another server where the service only uses 16MB of RAM.
What version of HostMonitor do you use on both systems?
What the difference between these systems? Different Windows? Service Pack? Some 3rd party software, like antivirus monitor, personal firewall, content monitoring software, non-standard winsock components?
Do you use ODBC logging or ODBC Query test method? The same version of ODBC driver is installed on both systems?
Both server installations are Win 2003 SP1 running Hostmon v6.24 housed in seperate datacentres.
server with prob does log limited info via MySQL ODBC driver back to a DB on a seperate site.
Another customer has similar problem with MySQL ODBC driver. We are investigating this problem...
What version of ODBC driver do you use? Server version?
Could you disable ODBC logging for testing?
What about 3rd party software on both systems? Antivirus monitor, personal firewall, content monitoring software, non-standard winsock components?
KS-Soft wrote:What version of ODBC driver do you use? Server version?
Could you disable ODBC logging for testing?
What about 3rd party software on both systems? Antivirus monitor, personal firewall, content monitoring software, non-standard winsock components?
MySQL ODBC driver ver 3.51
Altiris deployment server is installed on this server
no other non-standard software
We cannot reproduce any problems using MySQL ODBC driver version 3.51.11, 3.51.12. However another customer experienced significant resource leakage using these drivers. He fixed the problem by updating to ODBC driver version 5.00 (I assume 5.00.11).
If you cannot disable ODBC logging, lets try to update the driver.
Or may be you can switch from Full to Brief logging mode?
