| Description |
This article describes the reason why CPU goes high when enabling WAD debug may impact in production traffic. |
| Scope |
FortiProxy Azure VM. |
| Solution |
During troubleshooting on FortiProxy, it can be possible to enable WAD to debug to collect information during investigations. Common command as below:
diag wad debug enable category all <-- all: refer to all debug. Note: do not use production hours.
Or selected category (eg. auth, policy, or http).
After enabling the debug using 'diag debug enable', it is possible to observe CPU goes high which is expected due to debugging is always recommended, enabling the filter option whenever running debug commands.
If observing a similar symptom, run the debug command below to check if there is any value appearing for this entry '0 IO-APIC 4-edge ttyS0' on any of the CPU.
diagnose hardware sysinfo interrupts
Do run the command multiple times to ensure the counter does increase, and from the above output, it may trigger CPU3 to be high due to debug parsing out via console (ttys0). Use the below command to disable debug output to the console, which is not usually used as the output is slower than SSH:
diagnose debug console no-user-log-msg enable Related article: |
