NetProbe - The Processes plugin is reporting "ERROR: Failed to execute * processes - plugin PROCESSES timed out" error. What does this mean ?
Related to Copied
Processes plugin timed out, Failed to execute, plugin PROCESSES timed out, Processes plugin not working, ERROR: Failed to execute.
Problem Copied
- The Processes plugin is showing Failed to execute .. plugin PROCESSES timed out in the NetProbe Log file and displaying TIMED OUT in the sampling status.
Possible Causes Copied
Root Cause 1 -
RegEx mode set to default
Root Cause 2 -
Use of regular expression wildcards
Root Cause 3 -
NetProbe running out of file descriptors
Root Cause 4 -
Advanced Tab options selected including wide process support, cache wide process names, adjust for logical CPU’s.
Root Cause 5 -
Monitored processes have high number of threads (10,000 or more), which can increase the handling time needed for Processes plugin.
Possible Solutions Copied
Solution Root Cause 1 - Please check the regexMode setting under the Advanced tab. The default value of this setting is Extended which uses the POSIX extended regular expression syntax installed on the Netprobe host. Depending on the Netprobe version, the Netprobe package includes PCRE or newer PCRE2 library. It is generally recommended to select PCRE as a more optimised option.
Solution Root Cause 2 - The use of regular expression wildcards or lookahead patterns may be inefficient or return too much information. Look to use a regex test website to test and streamline the options.
Solution Root Cause 3 - Check the limits by running ulimit -a. Increase file descriptors limit if a limit is imposed.
Solution Root Cause 4 - Uncheck the “Cache Wide Process Names” and related option at the Advanced tab.
Solution Root Cause 5 - Uncheck the “Show Process Details” option at the Advanced tab.