Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Database: JIRA couldn't connect to your database

서정은 March 16, 2022

I faced a problem to run Jira.

Server version, 7.9.0, via docker.

I didn't changed anything but it doesn't work suddenly now.

 

When I start it and try to access it's web pages, it shows me an error page as below.

 

jira_error2.png

 

I checked dbconfig.xml but couldn't found any special things.

Only one thing that I doubt is I'm not sure if that user name is correct or not. Of course I didn't changed, but I found that the e-mail address of this user id is incorrect. Is there any idea that I can check if this user id is alive or not?

And jdbc:postgresql://postgresql:5432/jira, I tried to check if the port 5432 is opened or not, but it seems ok.

LISTEN 0 128 [::]:5432 [::]:* users:(("docker-proxy",pid=29867,fd=4))

Or if there is any other idea or if you need further information, please let me know.
Thank you in advance!! :)

 

Best Regards,

JESuh

---


<?xml version="1.0" encoding="UTF-8"?>

<jira-database-config>
<name>defaultDS</name>
<delegator-name>default</delegator-name>
<database-type>postgres72</database-type>
<schema-name>public</schema-name>
<jdbc-datasource>
<url>jdbc:postgresql://postgresql:5432/jira</url>
<driver-class>org.postgresql.Driver</driver-class>
<username>some_username</username>
<password>my_password</password>
<pool-min-size>20</pool-min-size>
<pool-max-size>20</pool-max-size>
<pool-max-wait>30000</pool-max-wait>
<validation-query>select 1</validation-query>
<min-evictable-idle-time-millis>60000</min-evictable-idle-time-millis>
<time-between-eviction-runs-millis>300000</time-between-eviction-runs-millis>
<pool-max-idle>20</pool-max-idle>
<pool-remove-abandoned>true</pool-remove-abandoned>
<pool-remove-abandoned-timeout>300</pool-remove-abandoned-timeout>
<pool-test-on-borrow>false</pool-test-on-borrow>
<pool-test-while-idle>true</pool-test-while-idle>
</jdbc-datasource>
</jira-database-config>

1 answer

0 votes
Piyush A (STR)
Community Champion
March 16, 2022

Hi, 
per the question: It was working earlier but now isn't working  - correct?

Try to connect the database from the server. I see you've already tried for LISTEN, but port could be an case here.

 

Also, password reset and make changes to the database once. Meanwhile - install a Postgres admin UI for the database and check the connectivity.

Suggest an answer

Log in or Sign up to answer