Hide Forgot
Description of problem: When the database starts UNsuccessfully using db-control because of wrong HBA specified, db-control status says the database is not running even though the service is running (and the database just failed to connect). This means the database can not be stopped using db-control because "db-control stop" says it is already shut down. Version-Release number of selected component (if applicable): Tried on 570 and 580 How reproducible: Deterministic Steps to Reproduce: 1. CONFFILE=/opt/rh/postgresql92/root/var/lib/pgsql/data/pg_hba.conf # or another correct location of pg_hba.conf based on version 2. vim $CONFFILE # change rhnschema to rhnschemax 3. db-control stop 4. db-control start 5. db-control status The database is offline. 6. SERVICENAME=postgresql92-postgresql # or another correct service name based on version 7. service $SERVICENAME status # the service is actually running postmaster (pid <ID>) is running... 8. db-control stop # let's show why this can be a problem Database already shut down. 9. vim $CONFFILE # let's fix the config file to its original state 10. db-control start # this fails because the database service never got stopped 11. db-control status # the database can not be started correctly using db-control because with the service still running, the fixed config will never get relaoded The database is offline. Actual results: db-control status shows the database is offline which leads to inability to stop the database using db-control Expected results: db-control stop # should stop the database db-control status # I am not sure about this, but maybe it should provide output based on which I am able to determine whether the postgre service is running or not Additional info: service $SERVICENAME restart # properly restarts the service
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog. This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.