Satellite Postgresql upgrade hits maximum number of semaphore sets

Solution Verified - Updated -


  • During Satellite 5.5 to Satellite 5.6 upgrade the Postgresql daemon fails to start (pgstartup.log):
* Setting up Selinux..
** Database: Setting up database connection for PostgreSQL backend.
** Database: Installing the database:
** Database: This is a long process that is logged in:
** Database:   /var/log/rhn/install_db.log
*** Progress: #
Could not install database.
  • Futher inspection of /var/lib/pgsql/pgstartup.log shows the following semaphore issue:
2013-10-08 19:10:49.689 EDT FATAL:  could not create semaphores: No space left on device
2013-10-08 19:10:49.689 EDT DETAIL:  Failed system call was semget(5432006, 17, 03600).
2013-10-08 19:10:49.689 EDT HINT:  This error does *not* mean that you have run out of disk space.
        It occurs when either the system limit for the maximum number of semaphore sets (SEMMNI), or the system wide maximum number of semaphores (SEMMNS), would be exceeded.  You need to raise the respective kernel parameter.  Alternatively, reduce PostgreSQL's consumption of semaphores by reducing its max_connections parameter (currently 603).


  • Red Hat Satellite 5.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