After leapp upgrade to RHEL 8.6 and reboot, the satellite-installer execution fails to start postgresql service in Red Hat Satellite 6.11

Solution Verified - Updated -


  • After upgrading the OS from RHEL 7.9 to RHEL 8.6 using leapp and reboot of the server, the leapp_resume activity fails at the backend to complete the satellite-installer execution.

    Jul 14 14:05:28 satellite611 leapp3[7612]: ==> Processing phase `FirstBoot`
    Jul 14 14:05:28 satellite611 leapp3[7612]: ====> * satellite_upgrader
    Jul 14 14:05:28 satellite611 leapp3[7612]:        Execute installer in the freshly booted system, to finalize Satellite configuration
    Jul 14 14:07:44 satellite611 leapp3[8122]: 2022-07-14 14:07:44.163 ERROR    PID: 8122 leapp.workflow.FirstBoot.satellite_upgrader: Could not run the installer, please inspect the logs in /var/log/foreman-installer!
  • None of the services related to satellite were found to be properly running and the postgresql service is in a failed state.

    * postgresql.service - PostgreSQL database server
      Loaded: loaded (/usr/lib/systemd/system/postgresql.service; disabled; vendor preset: disabled)
     Drop-In: /etc/systemd/system/postgresql.service.d
      Active: failed (Result: exit-code) since Thu 2022-07-14 14:06:57 CDT; 14min ago
    Jul 14 14:06:57 systemd[1]: Starting PostgreSQL database server...
    Jul 14 14:06:57 systemd[1]: postgresql.service: Control process exited, code=exited status=1
    Jul 14 14:06:57 systemd[1]: postgresql.service: Failed with result 'exit-code'.
    Jul 14 14:06:57 systemd[1]: Failed to start PostgreSQL database server.   


  • 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