Announcements
This site is in read only until July 22 as we migrate to a new platform; refer to this community post for more details.
Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

apigee-postgres master-standby setup

Hello Guys, 

I am new with Apigee, I am trying to setup apigee on-prem. Installation of Apigee-Postgresql failed with this error : 

pigee-configutil: apigee-postgresql: # OK
apigee-service: apigee-postgresql: Not running (NO_LOCKFILE)
apigee-service: apigee-postgresql: status=2, continuing
apigee-service: apigee-postgresql: Not running (DEAD)
apigee-service: apigee-postgresql: status=3, continuing
apigee-service: apigee-postgresql: Not running (DEAD)
apigee-service: apigee-postgresql: status=3, continuing
apigee-service: apigee-postgresql: Not running (DEAD)
apigee-service: apigee-postgresql: status=3, continuing
apigee-service: apigee-postgresql: Not running (DEAD)
apigee-service: apigee-postgresql: status=3, continuing
apigee-service: apigee-postgresql: Not running (DEAD)
apigee-service: apigee-postgresql: apigee-postgresql is dead
Error: setup.sh: /opt/apigee/apigee-service/bin/apigee-service exited with unexpected status 3 

I run this command : /opt/apigee/apigee-setup/bin/setup.sh -p ps -f /tmp/configFile

can you please provide any guidelines about this 

and the log file of  /opt/apigee/var/log/apigee-postgresql/apigee-postgresql.log 

postgres: could not access the server configuration file "/opt/apigee/data/apigee-postgresql/pgdata/postgresql.conf": No such file or directory


should I start service : postgresql-14.service before the installation of apigee-postgres ? 


Thanks 

1 4 357
4 REPLIES 4

williamssean
Former Googler

I haven't installed OPDK in quite some time, but you should not have to start the Postgres service before you run the Apigee install script as the install script will take care of this for you.  

A few of things that I would.

1. Make sure the file is actually located in that directory.

If it is not there, then something happened with the initial setup. I would reinstall the Apigee setup script and then execute the pg install again.

2.  If the file is located in that directory, then make sure that the owner has at least read access to that file.  

sudo chmod 644 /opt/apigee/data/apigee-postgresql/pgdata/postgresql.conf

 3.  If Postgres was already installed on that server, then I would uninstall it and let the Apigee install script install it instead.

I hope this helps with your troubleshooting.  

Hi @BassemSelim! Thank you for your question! I hope you found the information provided helpful. A big thank you @williamssean for your valuable assistance!

If the suggested solution worked for you, feel free to mark it as an accepted solution so that others in the community can benefit from the information as well.

Let us know if you need any further assistance.

I came across this thread after running into the same issue as OP while trying to upgrade our on-prem production environment to 4.52.00.

@williamssean would uninstalling and letting the Apigee install script re-install the Postgres component remove analytics and other data?

We were also able to confirm that the conf file had read permissions prior to running the upgrade on the component.

Hello @BassemSelim,

You need to validate the config file, check if the port is open... I remember that when installed apigee OPDK in my first implementations I had it this error.

Follow this process: https://docs.apigee.com/private-cloud/v4.52.00/set-master-standby-replication-postgres

always I followed it and the installation of OPDK was successful.