Bug #26034
Updated by Vincent MEMBRÉ 20 days ago
Install of rudder-server has an error on postgresql which doesn't start
<pre>
Running scriptlet: java-17-openjdk-headless-1:17.0.13.0.11-4.0.1.el9.x86_64 57/58
Running scriptlet: rudder-server-8.2.3-1.EL.9.x86_64 58/58
Installing : rudder-server-8.2.3-1.EL.9.x86_64 58/58
Running scriptlet: rudder-server-8.2.3-1.EL.9.x86_64 58/58
Job for postgresql.service failed because the control process exited with error code.
See "systemctl status postgresql.service" and "journalctl -xeu postgresql.service" for details.
**************************************************************************************
ERROR: rudder-server postinstall script failed !
Trying to recover the problem, you should check that your instance is properly working
You should also try to manually execute: /opt/rudder/bin/rudder-upgrade
Such errors should not happen, please open an issue for this problem on
https://issues.rudder.io/projects/rudder/issues/new
**************************************************************************************
chmod: cannot access '/var/rudder/configuration-repository/.git': No such file or directory
</pre>
journalctl says
<pre>
Dec 06 12:54:56 server systemd[1]: Starting PostgreSQL database server...
░░ Subject: A start job for unit postgresql.service has begun execution
░░ Defined-By: systemd
░░ Support: https://support.oracle.com
░░
░░ A start job for unit postgresql.service has begun execution.
░░
░░ The job identifier is 2026.
Dec 06 12:54:56 server postmaster[6228]: 2024-12-06 12:54:56.327 UTC [6228] LOG: redirecting log output to logging collector process
Dec 06 12:54:56 server postmaster[6228]: 2024-12-06 12:54:56.327 UTC [6228] HINT: Future log output will appear in directory "log".
Dec 06 12:54:56 server systemd[1]: postgresql.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://support.oracle.com
░░
░░ An ExecStart= process belonging to unit postgresql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Dec 06 12:54:56 server systemd[1]: postgresql.service: Failed with result 'exit-code'.
</pre>
the postgresql log file is more useful
<pre>
2024-12-06 12:54:56.328 UTC [6228] LOG: starting PostgreSQL 13.16 on x86_64-redhat-linux-gnu, compiled by gcc (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3.0.1), 64-bit
2024-12-06 12:54:56.328 UTC [6228] LOG: listening on IPv4 address "127.0.0.1", port 5432
2024-12-06 12:54:56.328 UTC [6228] LOG: could not bind IPv6 address "::1": Cannot assign requested address
2024-12-06 12:54:56.328 UTC [6228] HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
2024-12-06 12:54:56.329 UTC [6228] FATAL: could not create lock file "/var/run/postgresql/.s.PGSQL.5432.lock": No such file or directory
2024-12-06 12:54:56.331 UTC [6228] LOG: database system is shut down
</pre>
So it cannot use ::1, and cannot start
running at a later stage
<pre>
systemctl systemct start postgresql
</pre>
does work though
WORKAROUND:
- restart postgres
- do @/opt/rudder/share/package-scripts/rudder-server-postinst true httpd true@