Troubleshooting Tip : How to fix the Connection Refused after upgrade FortiAnalyzer

[Nur]

Description	This article describes that after FortiAnalyzer had been upgraded to v7.2.X and v7.4.X, the status FortiAnalyzer from FortiGate showed 'connection refused'.
Scope	FortiAnalyzer and FortiGate.
Solution	Run 'execute log fortianalyzer test-connectivity' from FortiGate to check the error message. execute log fortianalyzer test-connectivity Failed to get FAZ'z status. No responce from server. (-20) Sniffer the packet from FortiAnalyzer and the FortiAnalyzer resets the connection. Telnet from FortiGate will show Failed: Ertiga-kvm09 # exe telnet 10.47.X.X 514 Trying 10.47.X.X... Refused to connected to 10.47.X.X Check from FortiAnalyzer if it is possible to recognize the FortiGate IP using the 'diag fmnetwork arp list' and 'diag fmnetwork netstat list'. After confirming there is no issue on the network layer, check the dashboard from FortiAnalyzer -> Alert Message Console, if any notification shows failed after the upgrade. Most probably the Alert will show 'Postgres upgrade fail. Please rebuild-db '. If the error is visible, it means the FortiAnalyzer failed to rebuild the Database automatically after the upgrade. It is a common process to upgrade FortiAnalyzer from the old version v6.2.X or v6.4.X the Progress will rebuild the database. However, if it fails to rebuild, rebuild the Database manually. The command is 'execute sql-local rebuild-db'. After running the command, check the FortiAnalyzer status from FortiGate. It will show 'Connected'.