Password authentication failed post upgrading sonar to 9.9 along with postgresql to 15.2

  • which versions are you using – sonarqube 9.9.0
  • how is SonarQube deployed: Docker
  • what are you trying to achieve - upgrading sonarqube from 8.9.0 to 9.9.0
  • we have upgraded sonarqube to 9.9.0 and postgres version to 15.2
root@66e4b8507d84:/# psql -U sonar -W
Password:
psql (15.2 (Debian 15.2-1.pgdg110+1))
Type "help" for help.

sonar=# \dn
List of schemas
  Name  | Owner
--------+-------
 public | sonar
(1 row)

post upgrading sonarqube and postgres to latest version , sonarqube container is not coming up , its failing with password authentication error

NOTE : i am able to login to db with username and password

root@66e4b8507d84:/# psql -U sonar -W
Password:
psql (15.2 (Debian 15.2-1.pgdg110+1))
Type "help" for help.

sonar=# \dn
List of schemas
  Name  | Owner
--------+-------
 public | sonar
(1 row)

still its failing with password authentication issue, below is the error logs while starting sonarqube container

WARNING: System::setSecurityManager will be removed in a future release
2023.03.17 14:08:00 INFO  web[][o.s.p.ProcessEntryPoint] Starting Web Server
2023.03.17 14:08:02 INFO  web[][o.s.s.p.LogServerVersion] SonarQube Server / 9.9.0.65466 / ce743843018827cb30c05735e7971523de34bb48
2023.03.17 14:08:02 INFO  web[][o.sonar.db.Database] Create JDBC data source for jdbc:postgresql://postgresql:5432/sonar
2023.03.17 14:08:02 INFO  web[][c.z.h.HikariDataSource] HikariPool-1 - Starting...
2023.03.17 14:08:03 ERROR web[][c.z.h.p.HikariPool] HikariPool-1 - Exception during pool initialization.
org.postgresql.util.PSQLException: FATAL: password authentication failed for user "sonar"
        at org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:659)
        at org.postgresql.core.v3.ConnectionFactoryImpl.tryConnect(ConnectionFactoryImpl.java:180)
        at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(Connectio

Hi,

Can you double-check your envvars? Support for SONARQUBE_JDBC_* was dropped in 9.9, in favor of SONAR_JDBC_*.

At a guess, your usage was inconsistent previously, with some SONAR_ and some SONARQUBE_…? Because with no recognized properties it wouldn’t have tried to connect at all & would have just fallen back to using H2.

 
Ann