Hello,
We are using HostMonitor 6.54 and Log Analyzer 5.35 and we're logging to a SQL database.
Hostmonitor is working fine until we open Log Analyzer to generate some reports. At that moment all RCC's and web interfaces lose their connection. The SQL database is on another server than Hostmonitor, and I start the Log Analyzer on my workstation and connect to the SQL database, so I don't exactly see why we lose all those connections.........
I have to say that we have a big database, but we are supposed to generate reports up to 3 months back. Generating reports takes a lot of time, but I don't mind as long as I don't lose the connection on the RCC and Web Interfaces. At this moment I can't generate reports because it pauses the monitoring and that's unacceptable.
Can someone tell me how to solve this?
Thanks!
Connection problem (RCC+Web) when starting Log Analyzer SQL
Do you see any errors in system log? System log file is specified on System Log page in the Options dialog.
If there is some ODBC/SQL related problem and ODBC driver does not respond for a long period of time, this may slow down HostMonitor (and monitoring) and RCC may drop connection by timeout.
What exactly ODBC driver do you use? Is there any updates/paches available for this driver?
Regards
Alex
If there is some ODBC/SQL related problem and ODBC driver does not respond for a long period of time, this may slow down HostMonitor (and monitoring) and RCC may drop connection by timeout.
What exactly ODBC driver do you use? Is there any updates/paches available for this driver?
Regards
Alex
Last edited by KS-Soft on Mon Nov 05, 2007 7:39 am, edited 1 time in total.
When you setup ODBC log, you may use "Add custom filter" option to select data for 3 last months. This may spead up process a lot (if your database contains records for several years...)I have to say that we have a big database, but we are supposed to generate reports up to 3 months back
http://www.ks-soft.net/hostmon.eng/la/i ... dbcManager
Regards
Alex
I enabled the system log and I'll let you know tomorrow if there are some ODBC/SQL related problem in the system log file (I can't shut down monitoring now so I scheduled a report for tonight).KS-Soft wrote:Do you see any errors in system log? System log file is specified on System Log page in the Options dialog.
If there is some ODBC/SQL related problem and ODBC driver does not respond for a long period of time, this may slow down HostMonitor (and monitoring) and RCC may drop connection by timeout.
What exactly ODBC driver do you use? Is there any updates/paches available for this driver?
Regards
Alex
The version of the ODBC driver for SQL server on the Hostmonitor server (Windows 2003 Server) is 2000.86.1830.00 and om my workstation (WIndows XP SP2) it is 2000.85.1117.00.
Even if I add a custom filter for only the last day, the connected RCC's and Web Interfaces lose their connection.......!!!!
In the system log there are only 3 events:
11/06/2007 07:00:05 Primary log error. ODBC error code: 4294967295 ([Microsoft][ODBC SQL Server Driver][SQL Server]SHUTDOWN is in progress. Log off) Logging initiated by "WNT714 CPU usage" test.
11/06/2007 07:00:05 Primary log error. ODBC error code: 4294967295 ([Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite (send()) [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network documentation) Logging initiated by "WNT711 Memory - Available MBytes" test.
11/06/2007 07:00:05 Primary log error. ODBC error code: 4294967295 ([Microsoft][ODBC SQL Server Driver]Communication link failur) Logging initiated by "WNT13 Memory - Available MBytes" test.
These are because the SQL server restarted.
Any suggestions?
Again, the monitoring stops and we lose all RCC and Web interface connections at the moment we connect the SQL database through Log Analyzer...!!!!
11/06/2007 07:00:05 Primary log error. ODBC error code: 4294967295 ([Microsoft][ODBC SQL Server Driver][SQL Server]SHUTDOWN is in progress. Log off) Logging initiated by "WNT714 CPU usage" test.
11/06/2007 07:00:05 Primary log error. ODBC error code: 4294967295 ([Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite (send()) [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network documentation) Logging initiated by "WNT711 Memory - Available MBytes" test.
11/06/2007 07:00:05 Primary log error. ODBC error code: 4294967295 ([Microsoft][ODBC SQL Server Driver]Communication link failur) Logging initiated by "WNT13 Memory - Available MBytes" test.
These are because the SQL server restarted.
Any suggestions?
Again, the monitoring stops and we lose all RCC and Web interface connections at the moment we connect the SQL database through Log Analyzer...!!!!
So, what exactly is the question?
a) Why your SQL server restarted? If this is result of some error, you should ask developer of the server (Microsoft).
b) may be your server is restarted by schedule and question is why RCC loses connection to HostMonitor? As I said ODBC driver may slow down HostMonitor. Actually it may lead to any error, even crash HostMonitor because ODBC driver works in address space of the process.
Quote from the manual
1) ODBC Log timeout specified on Primary Log page (and/or Backup Log page if your are using backup log) in the Options dialog
2) Timeout that you specify when RCC connects to HostMonitor
3) General RCI timeout specified on RCI page in the Options dialog
If timeout #2 or #3 is shorter than timeout #1, then RCC may lose connection in case of some error related to your SQL server or ODBC driver. Actually it may lose connection if timeout #2 and #3 is slightly longer than timeout #1. Because several ODBC error may occur one after another.
So, if RCC connection is so critical for you, increase timeout. However I do not think this is a big problem. When RCC loses connection you may easily reconnect it.
While Web Service does not keep connection to HostMonitor, it connects and send request when you refresh web page.
Next, if you worry about "monitoring stops", I should ask why do you think monitoring stops? Do you see "Start" button on HostMonitor's toolbar? Probably monitoring was paused for a while, not sopped?
When ODBC driver cannot connect to SQL server within specified timeout, it should report error and return operation to HostMonitor. If several ( actually 8 ) ODBC errors occured one by one, HostMonitor disables ODBC logging for a while so monitoring will continue.
Your system log shows just 3 errors. Normally if ODBC timeout is 10 sec, monitoring should be paused for 30 sec maximum. Unfortunately many ODBC drivers do not process "timeout" option correctly and may hold HostMonitor for a longer time. Sometimes 3 consecutive errors may pause monitoring for 10 minutes. Sure, RCC will drop connection in such case.
Regards
Alex
a) Why your SQL server restarted? If this is result of some error, you should ask developer of the server (Microsoft).
b) may be your server is restarted by schedule and question is why RCC loses connection to HostMonitor? As I said ODBC driver may slow down HostMonitor. Actually it may lead to any error, even crash HostMonitor because ODBC driver works in address space of the process.
Quote from the manual
If ODBC driver works correctly, you should check 3 optionsNote #2: you must be sure that ODBC driver (provided by 3rd party) works reliable and will not cause HostMonitor to crash. E.g. Microsoft dBase Driver v 4.00 causes resource leakage; Oracle driver v8 may crash application.
1) ODBC Log timeout specified on Primary Log page (and/or Backup Log page if your are using backup log) in the Options dialog
2) Timeout that you specify when RCC connects to HostMonitor
3) General RCI timeout specified on RCI page in the Options dialog
If timeout #2 or #3 is shorter than timeout #1, then RCC may lose connection in case of some error related to your SQL server or ODBC driver. Actually it may lose connection if timeout #2 and #3 is slightly longer than timeout #1. Because several ODBC error may occur one after another.
So, if RCC connection is so critical for you, increase timeout. However I do not think this is a big problem. When RCC loses connection you may easily reconnect it.
While Web Service does not keep connection to HostMonitor, it connects and send request when you refresh web page.
Next, if you worry about "monitoring stops", I should ask why do you think monitoring stops? Do you see "Start" button on HostMonitor's toolbar? Probably monitoring was paused for a while, not sopped?
When ODBC driver cannot connect to SQL server within specified timeout, it should report error and return operation to HostMonitor. If several ( actually 8 ) ODBC errors occured one by one, HostMonitor disables ODBC logging for a while so monitoring will continue.
Your system log shows just 3 errors. Normally if ODBC timeout is 10 sec, monitoring should be paused for 30 sec maximum. Unfortunately many ODBC drivers do not process "timeout" option correctly and may hold HostMonitor for a longer time. Sometimes 3 consecutive errors may pause monitoring for 10 minutes. Sure, RCC will drop connection in such case.
Regards
Alex