Script Timeout

Top  Previous  Next

 

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.

 

Script Timeout

 

Section: HKEY_LOCAL_MACHINE\SOFTWARE\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)

 

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).

 

 

Running Kiwi Syslog Server on a native 64-bit machine?

 

 On 64-bit Windows installations, Kiwi Syslog Server runs in WOW (Windows on Windows) 32-bit

 emulated mode.  In WOW mode, the SolarWinds registry hive resides in:

 HKEY_LOCAL_MACHINE\Software\WOW6432Node, not in HKEY_LOCAL_MACHINE\Software

 as it does on a native 32-bit Windows environment.

 

 If you are running Kiwi Syslog Server on a native 64-bit windows machine, please re-map all

 registry settings from HKEY_LOCAL_MACHINE\Software\SolarWinds\... to:

HKEY_LOCAL_MACHINE\Software\WOW6432Node\SolarWinds\...