Uploaded image for project: 'PuppetDB'
  1. PuppetDB
  2. PDB-4555

PuppetDB connection failure causing shutdown

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: PDB 5.2.10, PDB 6.3.5, PDB 6.7.1
    • Fix Version/s: PDB 6.7.2, PDB 6.3.6, PDB 5.2.11
    • Component/s: None
    • Labels:
      None
    • Template:
    • Acceptance Criteria:
      Hide

      PuppetDB does not crash on startup when Postgres is not available and will retry the connection until a successful connection is made

      Show
      PuppetDB does not crash on startup when Postgres is not available and will retry the connection until a successful connection is made
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      PDB-4509 introduced a regression where PuppetDB would attempt to make an initial database connection, if this failed, it would shutdown. Now PuppetDB will retry the database connection as before.
      Show
      PDB-4509 introduced a regression where PuppetDB would attempt to make an initial database connection, if this failed, it would shutdown. Now PuppetDB will retry the database connection as before.
    • QA Risk Assessment:
      Needs Assessment

      Description

      PuppetDB requires Postgres to be started before PuppetDB, otherwise its first connection to the database will fail, causing PuppetDB to throw and error and shutdown with the following message

      ERROR [p.t.internal] Error during service start!!! java.sql.SQLTransientConnectionException: PDBMigrationsPool - Connection is not available, request timed out after 3011ms.
      

      Previously, if postgresql was not running, PuppetDB would retry the connection with the message

      ERROR [p.p.c.services] Will retry database connection after temporary failure: java.sql.SQLTransientConnectionException: PDBMigrationsPool - Connection is not available, request timed out after 3008ms.
      

      This was introduced by this query to Postgres that happens outside the "try again" loop for database connection failures.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              austin.blatt Austin Blatt
              Reporter:
              austin.blatt Austin Blatt
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support