pgsql resource fails to start with error 'My data may be inconsistent. You have to remove <path>/PGSQL.lock file to force start' in a RHEL High Availability cluster with Pacemaker

Solution Verified - Updated -

Issue

  • Postgres down on Slave in our cluster
  • Our pgsql resource is failing to start after a node rebooted
  • pgsql resource failing with "My data may be inconsistent. you have to remove
    /PGSQL.lock file to force start."

  • pcs status shows an error from my pgsql resource referencing a lock file

     Failed Actions:
 * postgresql_start_0 on node2.example.com 'unknown error' (1): call=16, status=complete, exitreason='My data may be inconsistent. You have to remove /var/opt/rh/rh-postgresql94/lib/pgsql/tmp/PGSQL.lock file to force start.', last-rc-change='Tue Feb 14 23:21:14 2017', queued=0ms, exec=194ms

Environment

  • Red Hat Enterprise Linux (RHEL) 6, 7, 8, 9 with the High Availability Add-On
  • pacemaker
  • One or more pgsql resources managed by the cluster which is configured as master/slave or promotable

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