long_running_procs
makes sure that certain processes do not run longer than the configured time.
This test runs on all VSX Contexts.
Parameter
|
Description
|
elapsed_time
|
Longest time in seconds a process should run
Default: 60 seconds
Minimum recommended value: 30
|
processes_to_check
|
List of process to check
Each process must be in quotes. Put a space between each test.
Default: "fw ctl zdebug" "fw ctl debug" "fw ctl kdebug" "fw monitor" "sim dbg" "tcpdump"
Example: processes_to_check=("fw ctl zdebug" "fw ctl debug" "fw ctl kdebug" "fw monitor" "sim dbg" "tcpdump")
|
Example:
-----------------------------------------------------------------
| Status | Test performed |
-----------------------------------------------------------------
| [FAILED] | Long running processes |
| [PASSED] | SecureXL status |
| [PASSED] | PPACK debug flags |
| [PASSED] | FW1 debug flags |
| [PASSED] | Local logging |
| [PASSED] | Templates disabled from rule |
| [PASSED] | Correction table entries |
| [PASSED] | Delayed notifications |
| [PASSED] | Routing cache entries |
| [PASSED] | Swap saturation |
| [PASSED] | Neighbour table overflow |
-----------------------------------------------------------------
Found potential CPU hogging processes:
-----------------------------------------------------------------
Blade PID ELAPSED TIME CMD
[1_01] 1484 03:48 00:00:00 tcpdump -nnni eth1-01
Found the following issues:
-----------------------------------------------------------------
[ All] The process 'tcpdump' is running for more than 60 seconds
|
