Not able to connect with postgressql database

I have installed postgres qsl on server A. sonarqube is setup on server B.
When i am passing databse details to sonarqube properties file after that sonarqube is not accessible on browser.

What do the logs say?

Hi Colin,

Below are the sonarqube logs.

2024.05.01 17:40:38 INFO app[o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2024.05.01 17:40:38 INFO app[o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:41989]
2024.05.01 17:40:38 INFO app[o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [/opt/sonarqube/elasticsearch]: /opt/sonarqube/elasticsearch/bin/elasticsearch
2024.05.01 17:40:38 INFO app[o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2024.05.01 17:40:42 WARN app[o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 78
2024.05.01 17:40:42 INFO app[o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2024.05.01 17:40:42 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped
2024.05.01 17:40:43 INFO app[o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2024.05.01 17:40:43 INFO app[o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:38509]
2024.05.01 17:40:43 INFO app[o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [/opt/sonarqube/elasticsearch]: /opt/sonarqube/elasticsearch/bin/elasticsearch
2024.05.01 17:40:43 INFO app[o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2024.05.01 17:40:46 WARN app[o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 78
2024.05.01 17:40:46 INFO app[o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2024.05.01 17:40:46 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped

Is there any configuration need to be update in database configuration.

There are 4 log files. Did you check them all?

In nohup.log i found this

ERROR: [1] bootstrap checks failed. You must address the points described in the following [1] lines before starting Elasticsearch.
bootstrap check failure [1] of [1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
ERROR: Elasticsearch did not exit normally - check the logs at /opt/sonarqube/logs/sonarqube.log
2024.05.02 11:24:23 WARN app[o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 78
2024.05.02 11:24:23 INFO app[o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2024.05.02 11:24:23 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped

Looks like you need to check the platform notes for linux