EnterpriseDB/repmgr

/run/repmgr directory not created via repmgr_14-5.3.2 package installation

fgrandvarlet opened this issue · 0 comments

[postgres@xxx ~]$ /usr/pgsql-14/bin/repmgr --version
repmgr 5.3.2

When I run the repmgr-14.service service via :
systemctl start repmgr-14.service
the service is failing and when I consult the logs of /var/log/message I have the following messages:

Jun 23 02:58:54 edf14 repmgrd: [2023-06-23 02:58:54] [NOTICE] using provided configuration file "/etc/repmgr/14/repmgr.conf"
Jun 23 02:58:54 edf14 repmgrd: [2023-06-23 02:58:54] [NOTICE] repmgrd (repmgrd 5.3.2) starting up
Jun 23 02:58:54 edf14 repmgrd: [2023-06-23 02:58:54] [INFO] connecting to database "host=192.168.56.214 port=5433 user=repmgr dbname=repmgr connect_timeout=2"
Jun 23 02:58:54 edf14 systemd: Can't open PID file /run/repmgr/repmgrd-14.pid (yet?) after start: No such file or directory
Jun 23 02:58:54 edf14 repmgrd: [2023-06-23 02:58:54] [ERROR] could not open PID file /run/repmgr/repmgrd-14.pid
Jun 23 02:58:54 edf14 systemd: Daemon never wrote its PID file. Failing.
Jun 23 02:58:54 edf14 systemd: Failed to start A replication manager, and failover management tool for PostgreSQL.
Jun 23 02:58:54 edf14 systemd: Unit repmgr-14.service entered failed state.
Jun 23 02:58:54 edf14 systemd: repmgr-14.service failed.

After seeing that the /run/repmgr directory was missing and having created it manually, everything works normally.
Note that this directory is present after a reboot of the server.

I do not notice this phenomenon with the installation of the repmgr_14-5.4.0 package which has the effect of automatically creating the /run/repmgr directory

Is this a known issue in version 5.3.2 that you fixed in the latest version ?