Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,551,670
Community Members
 
Community Events
184
Community Groups

After a system reboot the first run of startup of Jira Server Fails - cant connect to db

Having a weird error that has started happening with the last 3 (or 4) updates, where the first time I run the startup it fails (immediately) with an error that says it cannot connect to the database (which is running).  I simply have to re-run the startup command and it then works.  Here is my setup:

Fedora 32

Jira Server 8.11.0

Postgresql 12.3

I am fully aware that Jira doesn't support 12.3 we have a requirement that all software has to be to the latest version and on the second start everything works.

Any idea of what I can look at?

1 answer

1 accepted

0 votes
Answer accepted

I found this was related to the fact that I had changed the systemctl file by putting a want into it and then enabling the service.  So when I rebooted it, it was really already starting up, and not relizing this, I would restart it which caused the problem.  I worked around by stoping the service and then starting it again.

The fix (read "not work around") was to disable the service so that it didn't start automatically at reboot.  Which is really what I wanted.  I could have also just let it start at boot and everything would be OK.

This took a long time to figure out as I just did the workaround and got used to it.  I would only restart the Linux system once a month!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events