This article describes why the standby FortiWeb node logs show power module power-up logs in the event logs, even though the FortiWeb node did not go down as indicated by the System Uptime section in the output of the get system status command.
Event log:
Command output:
get sys status International Version: FortiWeb-XXXXX 7.4.3,build0638(GA),240405 Serial-Number: FV-YYYYYYYYYYYYY Bios version: 00010001 System Part-Number: ZZZZZZ-ZZ Log hard disk: Available Hostname: FWEB-2 Operation Mode: Reverse Proxy FIPS-CC mode: disabled System Uptime: [25 day(s) 2 hour(s) 55 min(s)] <----- System uptime indicates it was always up. Current HA mode: active-passive, backup HA member: Serial-Number Priority HA-Role FV-XXXXXXXXXXXXX 9 secondary FV-YYYYYYYYYYYYY 4 primary Database Status: Available
Scope
FortiWeb.
Solution
- The primary FortiWeb will synchronize its configuration with the secondary FortiWeb.
- The secondary FortiWeb will reload the configuration.
- The resource check module will begin to check different items, including the status of the power module.
- If they are found to be up, a log will be generated stating ‘Power module <power module number> power up’, which simply indicates that it is up after being checked by the resource check module.