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
Issue
- Postgres down on Slave in our cluster
- Our
pgsqlresource is failing to start after a node rebooted pgsqlresource failing with "My data my be inconsistent. you have to remove
/PGSQL.lock file to force start." pcs statusshows an error from mypgsqlresource 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 or 7 with the High Availability Add-On
pacemaker- One or more
pgsqlresources managed by the cluster
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
