Technical Tip: lockdb_update and lockdb_commit errors after logging into firewall via console connection

The errors lockdb_update and lockdb_commit can be observed when logging into the FortiGate via GUI or serial console:

• These errors can result due to space issues on the firewall.
• Do a backup of the config file and do a simple reboot of the firewall in the maintenance period to see if it helps as a workaround.
• It is possible to backup the required logs and then delete those that are not required as describes in the following KB article: Technical Tip: How to delete FortiGate log entries stored in memory or local disk.
• Verify the space with the following debug commands:

fnsysctl du -i /tmp
fnsysctl df -h
fnsysctl df -k
diag sys flash list
fnsysctl cat /proc/slabinfo
fnsysctl du -i /tmp
fnsysctl du -i /dev/shm
fnsysctl du -i /dev/cmdb

Note:

'fnsysctl' requires Super_admin (administrator account with super_admin permission profile) access to execute.

FortiGate will produce an error otherwise. For further information, see this KB article: Technical Tip: fnsysctl command returns Unknown action 0

• If logs are not required, it is possible to delete them or format the log disk.

execute log delete-all

Or:

exec formatlogdisk --> Requires reboot.

After these steps, the errors should disappear.