Checking FortiManager log output

While upgrading a FortiManager unit, use the console to check the log output in real-time. Check for any errors or warnings.

Following is a sample console output with warnings or errors you might encounter during an upgrade:

Please stand by while rebooting the system.

Restarting system.

Serial number:FMG-VM0A11000137

Upgrading sample reports...Done.

Upgrading geography IP data...Done.

rebuilding log database (log storage upgrade)...

Prepare log data for SQL database rebuild...Done.

Global DB running version is 222, built-in DB schema version is 432

......

upgrading device ssl-vpn flags...done

upgrading scripts ...

Invalid schedule. The device 10160520 does not belong to script 136's adom

Invalid schedule. The device 33933609 does not belong to script 46's adom

Invalid schedule. The device 10515974 does not belong to script 46's adom

......

Invalid schedule. The device 1709397 does not belong to script 46's adom

Invalid schedule. The device 1709397 does not belong to script 46's adom

Invalid schedule. The device 1407292 does not belong to script 46's adom

upgrading scripts ... done

upgrading script log ...

Failed to upgrade some script logs. Please use "diagnose debug backup-oldformat-script-logs" to upload the failed logs into a ftp server

upgrading script log ... done

Upgrading adom vpn certificate ca ...

......

Finish check-upgrade-objects [32923/49325]

Upgrade all DB version ...

Global DB running version is upgraded to 432

Database upgrade finished, using 846m11s