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,556,460
Community Members
 
Community Events
184
Community Groups

Jira does not start properly after upgrading the server's memory

I noticed the server was running at >90% memory so I decided to add a gig of memory. After rebooting Jira no longer works. Error 521: Web server is down.  


When starting or stopping Jira with:

/opt/atlassian/jira/bin/start-jira.sh
/opt/atlassian/jira/bin/stop-jira.sh


Everything looks normal.  Jira appears to be running but there is no web access.  There are no errors, there is no information about what is going on.  Nothing was changed whatsoever except upgrading the server from 2GB memory to 3GB, otherwise the configuration is identical.

How do I fix this?

This is Jira 8.2.3
Running on: CentOS 7.5 x64

 

 

1 comment

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 26, 2019

A 521 error is not "server down", it's "I can't get a tcp/ip connection to the service", which is usually a network error rather than server.

Check the routing and firewalls between you and the server.

I guess cloudflare needs to update their error messages if that's true, but in this case the server was down. For whatever unkonwn reason it turned out that nginx stopped automatically starting on startup after the memory upgrade. I cannot figure out why, but manually starting nginx got Jira back up.


Thanks.

Comment

Log in or Sign up to comment