Description
This article describes how to troubleshoot the issue that can make the FortiNAC UI inaccessible and get a 'System process down error'.
Scope
FortiNAC, FortiNAC-F.
Solution
In cases where a customer reports that they are unable to access the FortiNAC GUI and getting a 'system process down error'. This generally happens due to a failover for some reason and leads to system processes going down.
To resolve the issue, it is required to manually resume control on the primary if matches this scenario.
Steps to be taken:
- Check with the user that it is an HA pair.
- Once confirmed, check if the secondary is Running-In control through the secondary GUI -> Dashboard -> Main or through CLI by running the command:
cat .networkConfig (in the bin directory)
- Check the status, if it shows 2 means, secondary is in Control.
- Once confirmed, it is then possible to identify the reason for this failover through the logs.
- It can be necessary to check the disc space on the secondary if it was unable to replicate prior and lost communication with the Primary, and that is why it took control.
- Clean out old backup files from /bsc/campusMgr/master_loader/mysql/backup/ and check the disc space status again and it should look good after the clean-up.
- Now perform a manual failover from CLI to the primary server. Refer to the attached document for this process:
Technical Tip: Manually resume control to primary server via CLI
- Once this is done, validate to confirm the admin GUI is accessible on the primary and secondary is ready to take control in case it needs to.
