SiS Support Tip: How to troubleshoot an URL monitor failing intermittently
These are the troubleshooting steps that you could follow to find out the root cause of the issue or to give you enough information that you can provide to an HP Support engineer to help you fix the issue:
- Use the SiteScope URL tool to verify the issue. On SiteScope UI go to Tools tab > Web Tools > URL Tool > enter the URL that is failing and configure it the same way it is configured in the monitor and Run the tool to check the results.
Test the URL using a different web browser, if it works, then this could point to a configuration issue in the web browser, like proxy settings.
Check the URL availability using the sslget tool:
- On a command prompt go to SiteScope\tools directory.
- Run the following command: sslget -timeout 59 -x <YOUR_URL> -ignoreUnknownCA -ignoreErrors –noEncodePostData
Where <YOUR_URL> is the URL failing in SiteScope.
- Check the output.
Check the path a packet of information takes from the SiteScope server to the network host of the URL, using command tracert in Windows and traceroute in Linux. This will be useful to find out why the URL is unreachable because you will see where the connection fails.
Run the command when the URL is working and when it is not so you can compare them.
Use multiple load threads, by default some web browsers are set to download multiple items simultaneously but SiteScope is set just to one, so increase this property.
In the groups\master.config file, set the property: urlLoadThreads from 1 to 4.
Enable URL and http client Debugs. Go to \<SiteScopeInstallationFolder>\conf\core\Tools\log4j\PlainJava folder and copy from the log4j.properties.debug file the whole section under:
# URL monitors (Including SilverStream monitor, Apache monitor, IPlanet Server monitor and Oracle 9i Application Server monitor)
# HTTP Client Debug
Then paste it at the bottom of file \<SiteScopeInstallationFolder>\conf\core\Tools\log4j\PlainJava\log4j.properties. Save the changes and restart SiteScope.
Run the monitor and right after that, look at the following log files under \logs folder and provide them to HP Support:
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.