After leapp upgrade to RHEL 8.6, postgresql fails with 'could not bind IPv4 address' or 'Is another postmaster already running on port 5432' error.

Solution Verified - Updated -

Issue

  • After fixing the postgres /var/lib/pgsql/data permission/ownerhsip issue, service fails with following error.
May 12 07:40:45 x543573 postmaster[613675]: 2023-05-12 07:40:45 PDT LOG:  could not bind IPv4 address "127.0.0.1": Address already in use
May 12 07:40:45 x543573 postmaster[613675]: 2023-05-12 07:40:45 PDT HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
2023-05-12 07:40:45 [ERROR ] [configure] May 12 07:40:45 x543573 postmaster[613675]: 2023-05-12 07:40:45 PDT FATAL:  could not create any TCP/IP sockets
2023-05-12 07:40:45 [ERROR ] [configure] May 12 07:40:45 x543573 postmaster[613675]: 2023-05-12 07:40:45 PDT LOG:  database system is shut down
2023-05-12 07:40:45 [ERROR ] [configure] May 12 07:40:45 x543573 systemd[1]: postgresql.service: Main process exited, code=exited, status=1/FAILURE
2023-05-12 07:40:45 [ERROR ] [configure] May 12 07:40:45 x543573 systemd[1]: postgresql.service: Failed with result 'exit-code'.
2023-05-12 07:40:45 [ERROR ] [configure] May 12 07:40:45 x543573 systemd[1]: Failed to start PostgreSQL database server.

Environment

  • Red Hat Satellite 6.11
  • Red Hat Enterprise Linux 8.6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content