Technical Tip: Getting config-error 'error -130' after upgrade

[ychia]

Description	This article explains the reason for getting 'error -130' after upgrading FortiGate. Sample error messages from config-error-log: >>> "set" "last-failed-login" "1970-01-01" "06:59:59" @ global.system.admin.aaaaa.login-time.aaaaa:value parse error (error -130) >>> "set" "last-login" "1970-01-01" "06:59:59" @ global.system.admin.bbbbb.login-time.bbbbb:value parse error (error -130) >>> "set" "last-failed-login" "1970-01-01" "06:59:59" @ global.system.admin.bbbbb.login-time.bbbbb:value parse error (error -130) >>> "set" "last-login" "1970-01-01" "06:59:59" @ global.system.admin.ccccc.login-time.ccccc:value parse error (error -130) >>> "set" "last-failed-login" "1970-01-01" "06:59:59" @ global.system.admin.ccccc.login-time.ccccc:value parse error (error -130) >>> "set" "last-failed-login" "1970-01-01" "06:59:59" @ global.system.admin.ddddd.login-time.ddddd:value parse error (error -130) >>> "set" "last-failed-login" "1970-01-01" "06:59:59" @ global.system.admin.eeeee.login-time.eeeee:value parse error (error -130)
Scope	FortiGate.
Solution	This config-error -130 means that FortiGate time was not synced when the login attempt happened after the upgrade. Check if the time is synced on FortiGate via the CLI command 'execute time': Sample output showing current date & time: current time is: 14:06:58 last ntp sync:Tue Mar 12 13:57:05 2024 These error messages can be ignored if time is synced.