Troubleshooting

If the FortiSRA system runs abnormally, pinpointing the failed component can be challenging. This chapter presents the usage of built-in debug tools to speed up finding errors.

You must have system administrator and CLI permissions to use the debug features including debug trace files. See Role.

To use FortiSRA debug feature, debug category and level must be set.

In the CLI console, enter the following commands to set debug category and level:

diagnose wad debug enable category <category>

diagnose wad debug enable level <level>

For example:

diagnose wad debug enable category session #The category is session

diagnose wad debug enable level info #The level is set to info

For debug level settings, all the higher level traces are included, e.g., when the debug level is set to info, error and warn levels are displayed too, but verbose is hidden.

Once the category and level variables are set up in the CLI, traces are displayed in the CLI.

Troubleshooting network gateways

In the CLI console, enter the following commands:

 diagnose wad debug enable category gateway #dumps gateway config cache and the ongoing gateway session
diagnose test application wad 426
diagnose test application wad 429

See troubleshooting Issue: WebRDP session recording fails and closes active session.