Sonarqube not working with PostgreSQL15

SonarQube
,
1

Hello,

i’ve installed SonarQube 9 with Postgresql-15 on a redhat-release v8.6.
Now i have a few issues.

I’ve uncommented in sonar.properties the following as the documentation said to do:

sonar.jdbc.username=username
sonar.jdbc.password=password

In this scenario i can see the port 9000 in LISTEN stat with netcat but the Web Url do not work.

The other issue is this.
If i want to use Postgresql, and in this case commenting out:

sonar.jdbc.url=jdbc:postgresql://localhost/sonarqube?currentSchema=my_schema

i don’t see port 9000 listening.
What could be the problem?

I hope this makes sense. Let me know if you need more info.
Thank you so much for helping me.

2

What do the logs say?

3

here are attached the log
ce.log (1.2 KB)
es.log (3.8 KB)
sonar.log (1.3 KB)
web.log (12.9 KB)

4

Well here’s a big problem.

2024.04.12 09:44:38 INFO web[][o.s.s.p.LogServerVersion] SonarQube Server / 9.1.0.47736 / 98d09fa4f1400143dbea332952db3aa6984be125

This version is past EOL. You should upgrade to either the latest version or the current LTA (long-term active version) at your earliest convenience. Your upgrade path is:

9.1 → 9.9.4 → 10.4 (last step optional)

You may find these resources helpful:

If you have questions about upgrading, feel free to open a new thread for that here.

If your error persists after upgrade, please come back to us.

5

ok , thank you for the feedback. I’ve updated sonarqube and now it seems everything is up but i read these errors in the postgresql logs:

2024-04-15 16:54:18.977 CEST [106228] STATEMENT: CREATE TABLE schema_migrations (version VARCHAR (255) NOT NULL)
2024-04-15 16:54:29.581 CEST [106517] ERROR: no schema has been selected to create in at character 14
2024-04-15 16:54:29.581 CEST [106517] STATEMENT: CREATE TABLE schema_migrations (version VARCHAR (255) NOT NULL)
2024-04-15 16:54:40.348 CEST [106831] ERROR: no schema has been selected to create in at character 14
2024-04-15 16:54:40.348 CEST [106831] STATEMENT: CREATE TABLE schema_migrations (version VARCHAR (255) NOT NULL)
2024-04-15 16:55:55.920 CEST [60884] LOG: checkpoint starting: time
2024-04-15 17:00:25.008 CEST [60884] LOG: checkpoint complete: wrote 4071 buffers (24.8%); 0 WAL file(s) added, 0 removed, 3 recycled; write=269.079 s, sync=0.003 s, total=269.088 s; sync files=537, longest=0.001 s, average=0.001 s; distance=43521 kB, estimate=43521 kB
[root@RP-GITLAB02 log]# tail -f postgresql-Mon.log
2024-04-15 16:54:08.537 CEST [105938] ERROR: no schema has been selected to create in at character 14
2024-04-15 16:54:08.537 CEST [105938] STATEMENT: CREATE TABLE schema_migrations (version VARCHAR (255) NOT NULL)
2024-04-15 16:54:18.977 CEST [106228] ERROR: no schema has been selected to create in at character 14
2024-04-15 16:54:18.977 CEST [106228] STATEMENT: CREATE TABLE schema_migrations (version VARCHAR (255) NOT NULL)
2024-04-15 16:54:29.581 CEST [106517] ERROR: no schema has been selected to create in at character 14
2024-04-15 16:54:29.581 CEST [106517] STATEMENT: CREATE TABLE schema_migrations (version VARCHAR (255) NOT NULL)
2024-04-15 16:54:40.348 CEST [106831] ERROR: no schema has been selected to create in at character 14
2024-04-15 16:54:40.348 CEST [106831] STATEMENT: CREATE TABLE schema_migrations (version VARCHAR (255) NOT NULL)

6

I’m not a Postgres expert, but this StackOverflow post might help you.