We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduced with 53b2a37 (affecting PuppetDB 8.6.0), stopping the Postgres database will cause PuppetDB to shutdown several seconds later.
2024-07-17 13:40:02,427 WARN [pool-3-thread-2] [p.p.jdbc] Caught exception. Last attempt, throwing exception. 2024-07-17 13:40:02,427 ERROR [pool-3-thread-2] [p.p.c.services] Unable to read schema version: PDBReadPool - Connection is not available, request timed out after 3000ms. 2024-07-17 13:40:02,430 INFO [main] [p.t.internal] Beginning shutdown sequence
Failing to connect to Postgres should not trigger a shutdown.
Start PuppetDB, get past maintenance mode, stop Postgres.
The text was updated successfully, but these errors were encountered:
Migrated issue to PDB-5771
Sorry, something went wrong.
Fixed in #3992
No branches or pull requests
Describe the Bug
Introduced with 53b2a37 (affecting PuppetDB 8.6.0), stopping the Postgres database will cause PuppetDB to shutdown several seconds later.
Expected Behavior
Failing to connect to Postgres should not trigger a shutdown.
Steps to Reproduce
Start PuppetDB, get past maintenance mode, stop Postgres.
The text was updated successfully, but these errors were encountered: