After upgrade to HostMon 6.42c from 5.92, Shell Script test reports Timed Out status if run time exceeds 5 minutes, even if Timeout is set to 0 on the test.
The test runs a long-running maintenance script which may take 30-60 minutes to run.
Test was modified to use new Irregular Schedule function, Run Once a Day at a specific time.
HM 6.42c Shell Script times out if run>5 min & timeou
-
KS-Soft Europe
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
Hello,
I have faced to the similar problem with Shell Script Timed Out status. It sounds strange, but after I had perfomed "hostmon.exe /uninstallservice" and then "hostmon.exe /installservice", everything started to work again. Probably, it helps you too. P.S. Do not forget to specify appropriate account in Options > Service tab.
Regards,
Yoorix
I have faced to the similar problem with Shell Script Timed Out status. It sounds strange, but after I had perfomed "hostmon.exe /uninstallservice" and then "hostmon.exe /installservice", everything started to work again. Probably, it helps you too. P.S. Do not forget to specify appropriate account in Options > Service tab.
Regards,
Yoorix
1) We changed nothing in the code.
2) I think you could not excute tests that need more than 15 min without using undocumented option - ProbeTimeout
You should put ProbeTimeout=3600 into [Misc] section of hostmon.ini file. 3600 sec = 60 min. I think you have used this option but somebody changed ini file (may be you have used fresh installation?)
3) May be its not good idea to use such "tests"? I think its better to start script on schedule (using built0n Scheduler or standard Windows scheduler) and check result (some log) 3 hours later?
Regards
Alex
2) I think you could not excute tests that need more than 15 min without using undocumented option - ProbeTimeout
You should put ProbeTimeout=3600 into [Misc] section of hostmon.ini file. 3600 sec = 60 min. I think you have used this option but somebody changed ini file (may be you have used fresh installation?)
3) May be its not good idea to use such "tests"? I think its better to start script on schedule (using built0n Scheduler or standard Windows scheduler) and check result (some log) 3 hours later?
Regards
Alex
Shell Script times out after 5 minutes when Timeout=0
Thanks as always for the assistance.
We set ProbeTimeout=3600 and restarted the HM service, but the script still times out at 5 minutes exactly.
You're right about the "tests" comment: it's more of a scheduled batch job, and we're using he HM scheduling capability to run the script accordingly. We want to run it in HM so that we can log the Reply value it returns back to the same ODBC logging database we have now and integrate results with our perfmon and other monitored metrics. It also gives us one interface and scheduling system where everything resides, rather than two or three, and therefore one corresponding interface, code base, set of standards, etc. From an operational perspective, it's a lot easier to manage that way.
The value returned by the script is the run time duration of the script: basically, it's a "speed test" for certain system components. If it runs long, we need to know quickly. Checking the result after some arbitrary delay just isn't business-acceptible.
Also, if any HM Timeout is set to 0, isn't that supposed to mean no timeout? These same tests were working fine without timing out on 5.92, and started to time out immediately after the upgrade to 6.42c. If you haven't changed anything in the code, and we didn't change our "speed test" script, test parameters, or HM operating environment, would you have any other suggestions as to next steps to resolve this issue?
We set ProbeTimeout=3600 and restarted the HM service, but the script still times out at 5 minutes exactly.
You're right about the "tests" comment: it's more of a scheduled batch job, and we're using he HM scheduling capability to run the script accordingly. We want to run it in HM so that we can log the Reply value it returns back to the same ODBC logging database we have now and integrate results with our perfmon and other monitored metrics. It also gives us one interface and scheduling system where everything resides, rather than two or three, and therefore one corresponding interface, code base, set of standards, etc. From an operational perspective, it's a lot easier to manage that way.
The value returned by the script is the run time duration of the script: basically, it's a "speed test" for certain system components. If it runs long, we need to know quickly. Checking the result after some arbitrary delay just isn't business-acceptible.
Also, if any HM Timeout is set to 0, isn't that supposed to mean no timeout? These same tests were working fine without timing out on 5.92, and started to time out immediately after the upgrade to 6.42c. If you haven't changed anything in the code, and we didn't change our "speed test" script, test parameters, or HM operating environment, would you have any other suggestions as to next steps to resolve this issue?
Shell Script times out after 5 minutes when Timeout=0
In response to Max's question:
Could you provide more information, please?
- What Windows do you use? Service Pack?
Win 2003 SP 1
- Is HostMonitor started as a service or as an application?
Service
- What account do you use to start hostMonitor service?
NETWORK SERVICE
Could you provide more information, please?
- What Windows do you use? Service Pack?
Win 2003 SP 1
- Is HostMonitor started as a service or as an application?
Service
- What account do you use to start hostMonitor service?
NETWORK SERVICE