How to increase the Script Execution Timeout value for plugins
If a plugin's script execution time exceeds the Script Execution Timeout value configured in Site24x7, it could result in errors during plugin installation or disrupt the polling for existing plugin monitors. In such cases, you need to extend the Script Execution Timeout for the respective plugin monitor in Site24x7 to register it successfully and continue viewing your monitoring data.
During installation
To extend the Script Execution Timeout during installation or when the plugin registration has failed, follow the steps below:
- Run the plugin script in the terminal and note down the time it takes for the script to run.
- For Linux servers:
- Navigate to the conf folder in the Site24x7 Linux server monitoring agent directory (/opt/site24x7/monagent/conf/) and open the monagent.cfg file.
- Increase the value of the plugin_timeout parameter to a value greater than the plugin execution time you noted down earlier.
For example, if your plugin script took 67 seconds to execute, increase the plugin_timeout value to 120. - Restart the Site24x7 Linux server monitoring agent.
service site24x7monagent restart - Place the plugin folder you're trying to install in the Site24x7 plugins directory (/opt/site24x7/monagent/plugins/).
- For Windows servers:
- Navigate to the Pluginbin folder in the Site24x7 Windows server monitoring agent directory (C:\Program Files (x86)\Site24x7\WinAgent\monitoring\bin\Pluginbin\) and open the info.config file.
- Increase the value of the scripttimeout parameter to a value greater than the plugin execution time you noted down earlier.
For example, if your plugin script took 130 seconds to execute, increase the scripttimeout value to 150. - Restart the Site24x7 Windows server monitoring agent.
Services.msc -> Site24x7 Windows Agent -> Restart - Place the plugin folder you're trying to install in the Site24x7 plugins directory (C:\Program Files (x86)\Site24x7\WinAgent\monitoring\plugins\).
Within five minutes (i.e., after the next polling event), the plugin will be successfully registered.
After installation
If polling has stopped for existing plugin monitors because the plugin script execution timed out, follow the steps below to increase the Script Execution Timeout value in the Site24x7 web client:
- Navigate to the corresponding plugin monitor, click the hamburger menu
, and select Edit.
- Increase the Script Execution Timeout value to 120 secs (or as applicable) and click Save.
- Restart the server monitoring agent.
If the issue persists, reach out to support@site24x7.com with the plugin details.
Related Articles
How do I add the Dell iDRAC plugin for Windows?
Prerequisites Install the latest version of the Net-SNMP package. Follow these steps to install and configure it. Install Python 3.6. Plugin Installation Create a folder named idrac. Download the files from our GitHub repository and place them in the ...How to troubleshoot my Windows PowerShell Plugin?
By default, the Site24x7 monitoring Windows agent will run as a SYSTEM user. In case, if you would like to verify if the plugin script is giving the output properly as SYSTEM user, follow these steps: Download PsExec from this link and extract the ...Disable alerts for a plugin if the parent server is down
If a plugin monitor's parent server goes down, you can choose to exclude additional alerts from the plugin monitor. This way, you won’t receive alerts when the plugin monitor goes down as a result of the parent server being unavailable. To suppress ...Troubleshoot Error 404, Error 111, and "no host given" error when installing the Apache plugin
When installing the Apache monitoring plugin, you may encounter the following errors: Error_code : URL Error no host given: The "no host given" error message typically indicates an issue with a URL or request that lacks a hostname. If you encounter ...Troubleshoot "[Errno 111] Connection refused" error when installing Tomcat plugins
When installing Tomcat plugins, you may encounter the following error: We failed to reach a server. Reason: [Errno 111] Connection refused: This error indicates that your client is unable to establish a connection to the Tomcat Manager URL, but the ...