cancel
Showing results for 
Search instead for 
Did you mean: 

EFM 3.2 service start error

SOLVED
Level 3 Adventurer

EFM 3.2 service start error

Hello,

 

We have successfully setup EDB Streaming replication (version 9.6) on 1 Master and 2 Slaves. Now we are trying to set up Failover Manager 3.2, but fails with below error while starting the EFM.

pic1.pngError screehshot

When we go through the logs at /var/log/efm-3.2/startup-efm.log,it says below:

pic2.png

 

We have also verified /etc/sudoers for below entry:

pic3.png

 

Everything looks good, but still we are facing the issue. Please help us in this regard.

1 ACCEPTED SOLUTION

Accepted Solutions
EDB Team Member

Re: EFM 3.2 service start error

Hi Mahisha, 

 

From the below error we have noticed that "/etc/edb/efm-3.2/efm.properties fie doesn't have the proper permission it says "Permission denied" error, Could you please check that "/etc/edb/efm-3.2/efm.properties" file should have "0644" permission. If it as less than 0644 permission for "/etc/edb/efm-3.2/efm.properties" file then we get below error "Permission denied".

 

We have tested it internally by changing the "/etc/edb/efm-3.2/efm.properties file permission from 0644 to 0600 then we have received the exact error "Permission denied" which you are getting.

 

Please find the attched screenshot for your reference

EFM.png

7 REPLIES 7
EDB Team Member

Re: EFM 3.2 service start error

Hi Mahisha, 

 

From the below error we have noticed that "/etc/edb/efm-3.2/efm.properties fie doesn't have the proper permission it says "Permission denied" error, Could you please check that "/etc/edb/efm-3.2/efm.properties" file should have "0644" permission. If it as less than 0644 permission for "/etc/edb/efm-3.2/efm.properties" file then we get below error "Permission denied".

 

We have tested it internally by changing the "/etc/edb/efm-3.2/efm.properties file permission from 0644 to 0600 then we have received the exact error "Permission denied" which you are getting.

 

Please find the attched screenshot for your reference

EFM.png

Level 3 Adventurer

Re: EFM 3.2 service start error

Hello Kapil,

Thanks for your response and solution, we are able to start the efm cluseter on witness and Master servers, but facing issue while starting the EFM on standby servers. Please find below error for your refrence. Help much appreciated.

 

[root@awsgpbdfcodpr03 efm-3.2]# more startup-efm.log

8/28/18 2:22:42 AM Starting agent.

8/28/18 2:22:42 AM Trigger file validation failed. Could not start agent as standby. See logs for more details.

[root@awsgpbdfcodpr03 efm-3.2]# more efm.log

8/28/18 2:20:58 AM com.enterprisedb.efm.Environment doInit INFO: Properties loaded from /etc/edb/efm-3.2/efm.properties

 

8/28/18 2:20:58 AM com.enterprisedb.efm.Environment doInit INFO: Starting Failover Manager, version 3.2.0 using /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.181-3.b13.el7_5.x86_64/jre

 

8/28/18 2:22:42 AM com.enterprisedb.efm.Environment doInit INFO: Properties loaded from /etc/edb/efm-3.2/efm.properties

 

8/28/18 2:22:42 AM com.enterprisedb.efm.Environment doInit INFO: Starting Failover Manager, version 3.2.0 using /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.181-3.b13.el7_5.x86_64/jre

 

8/28/18 2:22:42 AM com.enterprisedb.efm.utils.LockFile lock INFO: created lock file: /var/lock/efm-3.2/efm.lock

 

8/28/18 2:22:42 AM com.enterprisedb.efm.utils.LockFile lock INFO: Starting lock monitor for: /var/lock/efm-3.2/efm.lock

 

8/28/18 2:22:42 AM com.enterprisedb.efm.DBMonitor isSuperUser INFO: Performing is_superuser query for database user enterprisedb on jdbc:postgresql://192.168.216.118:5010/edb?ApplicationName='efm-3.2'

 

8/28/18 2:22:42 AM com.enterprisedb.efm.DBMonitor isInRecovery INFO: Performing pg_is_in_recovery query on jdbc:postgresql://192.168.216.118:5010/edb?ApplicationName='efm-3.2'

 

8/28/18 2:22:42 AM com.enterprisedb.efm.DBMonitor isInRecovery INFO: Query result: true

 

8/28/18 2:22:42 AM com.enterprisedb.efm.exec.ExecUtil performExec INFO: [sudo /usr/edb/efm-3.2/bin/efm_root_functions dbservicestatus efm]

 

8/28/18 2:22:42 AM com.enterprisedb.efm.exec.ExecUtil performExec INFO: ProcessResult{exitValue=0, errorOut='', stdOut='â edb-as-9.6.service - EDB Postgres Advanced Server 9.6

   Loaded: loaded (/usr/lib/systemd/system/edb-as-9.6.service; enabled; vendor preset: disabled)

   Active: active (running) since Sat 2018-08-25 07:17:52 EDT; 2 days ago

 Main PID: 14138 (edb-postgres)

   CGroup: /system.slice/edb-as-9.6.service

           ââ14138 /finbdodbprod/edb/bin/edb-postgres -D /finbdodbprod/edb/data

           ââ14139 postgres: logger process

           ââ14140 postgres: startup process   recovering 00000001000000000000002

           ââ14141 postgres: wal receiver process   streaming 0/23047968

           ââ14142 postgres: checkpointer process

           ââ14143 postgres: writer process

           ââ14144 postgres: stats collector process

 

Aug 25 07:17:51 awsgpbdfcodpr03.ad.evoncloud.com systemd[1]: Starting EDB Postgres Advanced Server 9.6...

Aug 25 07:17:51 awsgpbdfcodpr03.ad.evoncloud.com bash[14116]: WARNING --> PERL_INSTALL_PATH is not set in /finbdodbprod/edb/etc/sysconfig/plLanguages.config file

Aug 25 07:17:51 awsgpbdfcodpr03.ad.evoncloud.com bash[14116]: WARNING --> PYTHON_INSTALL_PATH is not set in /finbdodbprod/edb/etc/sysconfig/plLanguages.config file

Aug 25 07:17:51 awsgpbdfcodpr03.ad.evoncloud.com bash[14116]: WARNING --> TCL_INSTALL_PATH is not set in /finbdodbprod/edb/etc/sysconfig/plLanguages.config file

Aug 25 07:17:52 awsgpbdfcodpr03.ad.evoncloud.com systemd[1]: Started EDB Postgres Advanced Server 9.6.'}

 

8/28/18 2:22:42 AM com.enterprisedb.efm.utils.RecoveryConfUtils validateTriggerFileLocation INFO: Validating trigger file location from recovery.conf file.

 

8/28/18 2:22:42 AM com.enterprisedb.efm.exec.ExecUtil performExec INFO: [sudo -u enterprisedb /usr/edb/efm-3.2/bin/efm_db_functions validatetriggerlocation efm]

 

8/28/18 2:22:42 AM com.enterprisedb.efm.exec.ExecUtil performExec WARNING: ProcessResult{exitValue=1, errorOut='', stdOut='ERROR: Could not read the trigger file location from recovery.conf file  at /finbdodbprod/edb/data.'}

 

8/28/18 2:22:42 AM com.enterprisedb.efm.utils.RecoveryConfUtils validateTriggerFileLocation SEVERE: Failed to validate trigger file location.

 

8/28/18 2:22:42 AM com.enterprisedb.efm.nodes.EfmNode commonShutdown INFO: Starting shutdown.

 

8/28/18 2:22:42 AM com.enterprisedb.efm.nodes.EfmNode setNodeState INFO: New internal state: SHUTDOWN

 

8/28/18 2:22:42 AM com.enterprisedb.efm.nodes.EfmAgent shutdown INFO: Exiting.

 

 

 

 

Level 3 Adventurer

Re: EFM 3.2 service start error

Hi Kapil,

We tried to add below entry in recovery.conf  on slave node to resolve the issue which I've specified above in this thread.

 

trigger_file='<file_location>'

 

Now It's leading to new error as below:

Pic3.PNG

 

I've created a separate topic on this error. Sorry for the any confusion caused.

 

 

 

 

 

EDB Team Member

Re: EFM 3.2 service start error

Hi Mahisha,

 

Thank you for the update.

 

As you mentioned in the separate topic that now your able to add the standby nodes on EFM cluster. Please let us know if you need any other information/assistance.

Highlighted
Adventurer

Re: EFM 3.2 service start error

HI manisha,

 i have a differnent error to startup efm-2.1,

[root@HKDTUATDB01 ~]# systemctl efm-2.1 start
Unknown operation 'efm-2.1'.
[root@HKDTUATDB01 ~]# systemctl start efm-2.1
Job for efm-2.1.service failed because the control process exited with error code. See "systemctl status efm-2.1.service" and "journalctl -xe" for details.
[root@HKDTUATDB01 ~]#
[root@HKDTUATDB01 ~]#
[root@HKDTUATDB01 ~]# systemctl status efm-2.1 -l
● efm-2.1.service - EnterpriseDB Failover Manager 2.1
Loaded: loaded (/usr/lib/systemd/system/efm-2.1.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2018-12-15 13:39:45 +08; 7s ago
Process: 22885 ExecStart=/bin/bash -c /usr/efm-2.1/bin/runefm.sh start ${CLUSTER} (code=exited, status=1/FAILURE)

Dec 15 13:39:45 HKDTUATDB01 systemd[1]: Starting EnterpriseDB Failover Manager 2.1...
Dec 15 13:39:45 HKDTUATDB01 systemd[1]: efm-2.1.service: control process exited, code=exited status=1
Dec 15 13:39:45 HKDTUATDB01 systemd[1]: Failed to start EnterpriseDB Failover Manager 2.1.
Dec 15 13:39:45 HKDTUATDB01 systemd[1]: Unit efm-2.1.service entered failed state.
Dec 15 13:39:45 HKDTUATDB01 systemd[1]: efm-2.1.service failed.

Dineshkumar Ashokan
EDB Team Member

Re: EFM 3.2 service start error

If EFM doesn't start, check the startup log.

 

Cheers,

Bobby

 

EDB Team Member

Re: EFM 3.2 service start error

Also, since you're talking about 2.1 and this 3.2 topic is marked "solved," it would be nice if you started a new topic. Also, make sure you're on the latest 2.1 (which is 2.1.2), otherwise the answer to whatever your problem is might be "that was fixed in 2.1.2."

 

Bobby