Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Kiwi Syslog Server > Kiwi Syslog Server Administrator Guide > Registry settings for Kiwi Syslog Server > ScriptTimeout


Table of contents
No headers

Use this Kiwi Syslog Server registry setting to specify the timeout value for scripts.

Section (32-bit Windows OS) HKEY_LOCAL_MACHINE\SOFTWARE\SolarWinds\Syslogd\Properties
Section (64-bit Windows OS) HKEY_LOCAL_MACHINE\Software\WOW6432Node\SolarWinds\Syslogd\Properties
Value (STRING) ScriptTimeout
Min value 0 (No timeout - not recommended)
Max value 60000
Default value 10000
Type Timeout in milliseconds (10000 = 10 seconds)

Some scripts may take longer to run than others. If your script causes a timeout error, you may want to extend the timeout value for running the script. Because the scripts are processed in real time, a script that takes a long time to run may cause message loss or delay the processing of other messages in the queue. If you have a complex or long running script, it is recommended that you run it as a post process. To do this, use the Windows Scripting Host to run your script against the log file that Kiwi Syslog Server creates. Try to avoid using long running scripts in real time.

By default, the script can run for a maximum of 10 seconds before returning a timeout condition. If your scripts need more time to process the data in real-time, you can extend the timeout up to a maximum of 60 seconds. Setting the timeout value to 0 will cause the script to never timeout (this setting is not recommended as it can cause the program to fail if a script gets into an infinite loop).

Last modified
15:33, 2 Mar 2017