https://www.puppet.com/community logo
Join Slack
Powered by
# puppet
  • r
    puppetdb logs are usually pretty chatty too.
  • l
    I had to roll back a puppetdb update
  • l
    but it will really depend on the error
  • l
    Copy code
    ERROR [p.p.c.services] Will retry database connection after temporary failure: java.sql.SQLTransientConnectionException: PDBMigrationsPool: default - Connection is not available
  • l
    so many lines lol
  • l
    that's the error I was getting
  • l
    try disabling ssl on the connection string in /etc/puppetlabs/puppetdb/config.d/database.ini (iirc) and ensuring there's a proper host (not hostssl) line on the postgres pg_hba and see if it starts
  • l
    if it fails for you, we should probably file a bug report
  • b
    @Les Shiner did you check the postgres logs?
  • l
    @bastelfreak for me, it was something about the migrationspool and ssl, backing off ssl made it work immediately
  • b
    yeah. If the puppetdb module is used, it usually sets up ssl/plaintext comnections correctly
  • l
    both of us are using the puppetdb module
  • l
    I am betting Les is using puppet 6
  • b
    The jetty.ini file was pretty important, too. Here's my jetty.ini sanitized of junk: [jetty] host = 0.0.0.0 port = 8080 ssl-host = 0.0.0.0 ssl-port = 8081 ssl-key = /etc/puppetlabs/puppetdb/ssl/private.pem ssl-cert = /etc/puppetlabs/puppetdb/ssl/public.pem ssl-ca-cert = /etc/puppetlabs/puppetdb/ssl/ca.pem access-log-config = /etc/puppetlabs/puppetdb/request-logging.xml client-auth = want ssl-cert-chain = /etc/puppetlabs/puppetdb/ssl/cert.pem ssl-protocols = TLSv1.2
  • l
    yea, in this case it's the database connection that's the problem
  • b
    But I am pretty sure I am using SSL.
  • l
    puppetdb doesn't even get started for that file to matter
  • c
    in AWS the PostgreSQL instance does not use SSL by default. You have to manually turn it on with a parameter group
  • l
    @Lumiere you're talking about this setting in database.ini?
    Copy code
    subname = //Master.ksmxe13yf34ergehjclg4kj1vh.bx.internal.cloudapp.net:5432/puppetdb?ssl=true&sslfactory=org.postgresql.ssl.LibPQFactory&sslmode=verify-full&sslrootcert=/etc/puppetlabs/puppetdb/ssl/ca.pem&sslkey=/etc/puppetlabs/puppetdb/ssl/private.pk8&sslcert=/etc/puppetlabs/puppetdb/ssl/public.pem
  • c
    @Lumiere I sent you a PM
  • l
    yes
  • l
    just change true to false?
  • l
    or remove everything after puppetdb?
  • l
    I would remove everything after puppetdb
  • l
    comment the line and then copy it honestly
  • l
    will do
  • l
    Copy code
    2023-01-25 21:05:40.169 UTC [36668] puppetdb@puppetdb LOG:  no match in usermap "puppetdb-puppetdb-map" for user "puppetdb" authenticated as "<http://master.ksmxe13yf34ergehjclg4kj1vh.bx.internal.cloudapp.net|master.ksmxe13yf34ergehjclg4kj1vh.bx.internal.cloudapp.net>"
2023-01-25 21:05:40.169 UTC [36668] puppetdb@puppetdb FATAL:  certificate authentication failed for user "puppetdb"
    This is the postgresql log that i'm reading, which is full of this error
  • l
    @Lumiere i tried your suggestion and that didn't resolve the issue
  • l
    what's crazy is that i've stood this up before, with the exact same code. No issue. This time though... it doesn't like me
  • c
    Likely missing an entry in 
    pg_ident.conf
    that associates the 
    <http://master.ksmxe13yf34ergehjclg4kj1vh.bx.internal.cloudapp.net|master.ksmxe13yf34ergehjclg4kj1vh.bx.internal.cloudapp.net>
    certificate CN with the 
    puppetdb
    database user.
1...285286287...428Latest