Forum Discussion
Apache Log4j Detection Optimizations Summary: While the...
I am really confused by this sentence - Note that the plugin timeout can be adjusted under Advanced Settings to a different timeout other than the default of one hour to assist in performance. When I check "Advanced Settings > plugin timeout" it is set to 320 seconds or a little over five minutes. Where is the one-hour setting? @Scott Przywara @Donald Bakowski
The default one hour timeout comes from the plugin itself.
The custom setting, timeout.<plugin ID>, can be set for specific plugins such as 156001 (e.g. timeout.156001).
From the Advanced Settings page:
Enter the plugin ID in place of <plugin ID>. The maximum time, in seconds, that plugin <pluginID> is permitted to run before Nessus stops it. If set for a plugin, this value supersedes plugins_timeout.
I added this custom setting. Is this correct? Also, Would it be better to edit the plugin timeout for more than one hour or less than one hour for better performance? @Donald Bakowski @Scott Przywara @Greg Betz
How can this be configured if you leverage Nessus Agent linked directly to Tenable.io?
Did this work for you Richard?
Does this actually increase the timeout for plugins 156000/156001? Asking because it looks like it's timing out on our AIX boxes? Is it in seconds?
@John Ruiz , it does increase the timeout for plugins 156000/156001. The value is in seconds.
