FortiSOAR Knowledge Base
FortiSOAR: Security Orchestration and Response software provides innovative case management, automation, and orchestration. It pulls together all of an organization's tools, helps unify operations, and reduce alert fatigue, context switching, and the mean time to respond to incidents.
sramanujam
Staff
Staff
Article Id 400587
Description

This article provides step-by-step instructions to resolve the error 'ERROR manager: start(): 492', which occurs due to permission issues accessing files in the PostgreSQL data directory on the primary node.

 

------------------------------------------------

Enter username for SSH connection to 'fsrmaster.labclstr.fortinet.com' (or press enter if the username is 'csadmin'):

Enter SSH password for user 'csadmin' on 'fsrmaster.labclstr.fortinet.com':

Validating SSH credentials

Fetching HA configuration details of fsrmaster.labclstr.fortinet.com

[2025-07-10 10:18:12] ERROR manager: start(): 492: ------------------------------------------------

Error:

There was an issue accessing all files in the PostgreSQL data directory of primary node. Please ensure that all files in the postgresql directory have the correct permissions assigned to the postgres user to avoid operation failure.

------------------------------------------------

Scope FortiSOAR 7.5.x, 7.6.x.
Solution Step 1: Log in to the primary node and execute the following command to list files in the PostgreSQL data directory that are not owned by the postgres user. By default, FortiSOAR may have a file named resv_space owned by root.

 

sudo ls -ltrhR /var/lib/pgsql | grep -v " postgres " | grep "-"

-rw-r--r--. 1 root     root     1.0G Mar 28 18:02 resv_space

 

Move any other files not owned by postgres to a different directory outside of the /var/lib/pgsql path.

 

Step 2: Restart the services on the primary node.

 

sudo csadm services --restart

 

Step 3: Finally, run the join cluster command on the secondary node according to the deployment type.

 

csadm ha join-cluster --status active --role secondary --primary-node fsrmaster.labclstr.fortinet.com

 

Note: It is always highly recommended to take a snapshot of the instance before making any changes to the system. Restarting the FSR-services are service-impacting, so please plan accordingly.

Contributors