Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Products Best Practices Hardware Guides Products A-Z
Summary
By Solution
By 4D Pillars
By Cloud
Secure Networking
Unified SASE
Security Operations
Secure SD-WAN
Secure Access Service Edge (SASE)
ZTNA
LAN Edge
Identity and Access Management
Next Generation Firewall
Public Cloud
Private Cloud
FortiCloud
Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
    • More >>
    Unified SASE
  • Single Vendor SASE
  • Cloud Network Security
  • Secure Endpoint Connectivity
  • Web Application / API Protection
    • More >>
    Security Operations
  • Security Operations Automation
  • Identity
  • Early Detection & Prevention
    • More >>
    Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
  • Communication & Surveillance
    • Unified SASE
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Cloud Network Security
  • Cloud-Native Security
  • Web Application / API Protection
    • Security Operations
  • Security Operations Automation
  • Endpoint
  • Data Protection
  • Identity
  • Email
  • Early Detection & Prevention
  • Expert Services
  • Edge Firewall
  • Orchestration & management
  • SD Branch
  • Application Delivery
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Secure Private Access
  • Thin Edge
  • Identity
  • Application Gateway
  • Enterprise Asset Management
  • Endpoint Agent
  • Agentless Security Posture
  • Identity
  • Wireless
  • Switching
  • Identity
  • Privilege Acccess Management
  • Next Generation Firewall
  • Orchestration & management
  • Expert Services
  • All
  • All
  • Account Management
  • SAAS Management
  • SAAS Application Security
  • Managed Services
  • Platform as a service (PAAS)
  • Other SAAS Services
    • 4D Resources
    Solution Hubs
  • 4D Pillars
  • Cloud
  • Popular Solutions

    • CLI Reference

    Home FortiWeb 6.2.2 CLI Reference
    6.2.2
    7.6.1
    7.6.0
    7.4.5
    7.4.4
    7.4.3
    7.4.2
    7.4.1
    7.4.0
    7.2.10
    7.2.9
    7.2.8
    7.2.7
    7.2.6
    7.2.4
    7.2.3
    7.2.2
    7.2.1
    7.2.0
    7.0.9
    7.0.8
    7.0.7
    7.0.6
    7.0.4
    7.0.3
    7.0.2
    7.0.1
    7.0.0
    6.4.3
    6.4.2
    6.4.1
    6.4.0
    6.3.23
    6.3.19
    6.3.18
    6.3.17
    6.3.16
    6.3.15
    6.3.14
    6.3.13
    6.3.11
    6.3.10
    6.3.9
    6.3.7
    6.3.6
    6.3.5
    6.3.4
    6.3.3
    6.3.2
    6.3.1
    6.3.0
    6.2.6
    6.2.5
    6.2.4
    6.2.3
    6.2.2
    6.2.1
    6.2.0
    6.1.2
    6.1.1
    5.7.0
    5.6.1
    5.6.0

    debug

    debug

    Use this command to turn debug log output on or off.

    Debug logging can be very resource intensive. To minimize the performance impact on your FortiWeb appliance, use packet capture only during periods of minimal traffic, with a local console CLI connection rather than a Telnet or SSH CLI connection, and be sure to stop the command when you are finished.

    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:

    Set the verbosity level for the specific module whose debugging information you want to view, via a debug log command such as:

    debug application hasync {0 | 1 | 2 | 3 | 4 | 5 | 6 | 7}

    If necessary configure any filters specific to the module whose debugging information you are viewing, such as:

    debug flow filter server-ip "10.0.0.10"

    If necessary start debugging specific to the module, such as:

    debug flow trace start

    Enable debug logs overall. To do this, enter:

    debug enable

    View the debug logs. For convenience, debugging logs are immediately outputted to your local console display or terminal emulator, but debug log files can also be uploaded to a server.

    To do this, use the command:

    debug upload

    For more complex issues or bugs, this may be required in order to send debug information to Fortinet Customer Service & Support (https://support.fortinet.com).

    Debug logs will be generated only if the application is running. To verify this, use system top . Otherwise, use debug crashlog instead.

    The CLI will display debug logs as they occur until you either:

    • Disable it by either typing:

      diagnose debug disable

      or setting all modules’ debug log verbosity back to 0. To reset all verbosity levels simultaneously, you can use the command:

      diagnose debug reset

    • 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:

      execute reboot

      To use this command, your administrator account’s access control profile requires only r permission in any profile area.

    Syntax

    diagnose debug {enable | disable}

    Variable Description Default

    debug {enable | disable}

    		 Select whether to enable or disable recording of logs at the debug severity level. disable

    Related topics

    Previous
    Next

    debug

    debug

    Use this command to turn debug log output on or off.

    Debug logging can be very resource intensive. To minimize the performance impact on your FortiWeb appliance, use packet capture only during periods of minimal traffic, with a local console CLI connection rather than a Telnet or SSH CLI connection, and be sure to stop the command when you are finished.

    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:

    Set the verbosity level for the specific module whose debugging information you want to view, via a debug log command such as:

    debug application hasync {0 | 1 | 2 | 3 | 4 | 5 | 6 | 7}

    If necessary configure any filters specific to the module whose debugging information you are viewing, such as:

    debug flow filter server-ip "10.0.0.10"

    If necessary start debugging specific to the module, such as:

    debug flow trace start

    Enable debug logs overall. To do this, enter:

    debug enable

    View the debug logs. For convenience, debugging logs are immediately outputted to your local console display or terminal emulator, but debug log files can also be uploaded to a server.

    To do this, use the command:

    debug upload

    For more complex issues or bugs, this may be required in order to send debug information to Fortinet Customer Service & Support (https://support.fortinet.com).

    Debug logs will be generated only if the application is running. To verify this, use system top . Otherwise, use debug crashlog instead.

    The CLI will display debug logs as they occur until you either:

    • Disable it by either typing:

      diagnose debug disable

      or setting all modules’ debug log verbosity back to 0. To reset all verbosity levels simultaneously, you can use the command:

      diagnose debug reset

    • 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:

      execute reboot

      To use this command, your administrator account’s access control profile requires only r permission in any profile area.

    Syntax

    diagnose debug {enable | disable}

    Variable Description Default

    debug {enable | disable}

    		 Select whether to enable or disable recording of logs at the debug severity level. disable

    Related topics

    Previous
    Next