debug
Use this command to turn debug log output on or off.
By default, the most verbose logging that is available from the web UI for any log type is the Information severity level. Due to their usually unnecessary nature, logs at the severity level of Debug are disabled and hidden. They can only be enabled and viewed from the CLI. Typically this is done only if your configuration seems to be correct, you cannot diagnose the problem without more information, and possibly suspect that you may have found either a hardware failure or software bug.
To generate debug logs, you must:
1. Set the verbosity level for the specific module whose debugging information you want to view, via a debug log command such as:
2. If necessary configure any filters specific to the module whose debugging information you are viewing, such as:
3. If necessary start debugging specific to the module, such as:
4. Enable debug logs overall. To do this, enter:
5. View the debug logs. For convenience, debugging logs are immediately output to your local console display or terminal emulator, but debug log files can also be uploaded to a server. For more complex issues or bugs, this may be required in order to send debug information to
Fortinet Technical Support. To do this, use the command:
6. The CLI will display debug logs as they occur until you either:
• Disable it by either typing:
or setting all modules’ debug log verbosity back to 0. To reset all verbosity levels simultaneously, you can use the command:
• Close your terminal emulator, thereby ending your administrative session.
• Send a termination signal to the console by pressing Ctrl+C.
• Reboot the appliance. To do this, you can use the command:
To use this command, your administrator account’s access control profile requires only r permission in any profile area.
Syntax
Variable | Description | Default |
debug {enable | disable} | Select whether to enable or disable recording of logs at the debug severity level. | disable |
Related topics