We are running EDB AS 9.6 on RHEL 7.2.
As part of OS security patch update, we have brought down the EDB databases to partch the OS.
Once the OS patching is done we are trying to bring up the EDB databases but facing below error:
Any suggestions/Solutions are much appreciated.
Can you check whether the lock folder "/var/lock/edb/as9.6/edb-as-9.6" is present on the server with the appropriate permission for touching the lock file ?
If not create the directory path and then try starting the postgres service.
Hope this helps.
Thank you so much for sharing your thoughts, we have verified and found that "/var/lock/edb/as9.6/edb-as-9.6" is not present, once we create the path with proper privilges the DB comes up.
Now the problem is, this issue is reoccuring whenever we reboot our Linux machine edb/as9.6/edb-as-9.6 disappears from /var/lock once we reboot the machine, we had to recrate the location to bring up the DB, and we are facing this issue on our AWS environment only. Also tied to reproduce the issue on our Azure environment but it works fine even after reboot.
I suspect that this issue is occuring due to the below scenario.
1) Highlighted entery i.e, "d /var/lock/edb/as9.6 0755 enterprisedb enterprisedb -" is missing in the "edb-as-9.6.conf"
2) File "edb-as-9.6.conf" is missing from the server.
[root@localhost as9.6]# cat /usr/lib/tmpfiles.d/edb-as-9.6.conf
d /var/run/edb/as9.6 0755 enterprisedb enterprisedb -
d /var/lock/edb/as9.6 0755 enterprisedb enterprisedb -
d /var/log/edb/as9.6 0755 enterprisedb enterprisedb -
The above two scenarios should be valid in your case then only it will be creating a directory "/var/lock/edb/as9.6/" after rebooting the srever.
Hope this helps you.