You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We are running confluence server in the Ubuntu 22.04. Until now all perfect. But past few days regularly the confluence not working . once we restart after 20 - 30 minutes again the problem occurs.
Then we followed the new security advisory email from atlassian and upgraded our version to 17.18.1
Same server we are running the Bitbucket and Jira. Those are working fine without any issues.
The CPU usage of the service is 85% to 95%. some times uses all cpu. If we stop the confluence the cpu usage is drops to 5 % to 10% . even running the other services Bitbucket and Jira.
The CPU usage is very abnormal for past few days and keep the confluence down after 15 minutes we start.
Please let us know, what are steps we need to follow to fix the issue. Its production server and affecting our development activities. We are waiting for your valuable reply.
Confluence Service crashing frequently
Start by monitoring and reading logs. What are the patterns of usage, and when within them is it failing (note that "it looks random" is a perfectly good answer to that, what we're looking for is patterns. If there isn't one that correlates with user usage patterns, that's fine, you've probably ruled out a load of stuff as causing the crash)
Your logs are probably the first place to look. The most interesting ones are going to be the handful of lines before the crash, but the whole thing is worth a look if you've got high CPU usage all the time. The logs are trying to tell you what the service is actually doing, as well as catching data about failures.
The ones to read first are the application log (<confluence home>/log/atlassian-confluence.log and all the other logs in that directory), then the application server log (<confluence install>/logs/catalina.out )
thanks for your guidance , I checked the confluence logs under
found its a java heap size issue
After I followed the below steps and now the confluence running without any issues.
#Stop Confluence service
took reference from the below discussion
Excellent! I'm glad it was an easy one to find and fix!
One thing that I do find lacking in Atlassian's docs about installing server is that they don't say (loudly enough) "the default setup is only for a trial, demo or quick test system. You should review them with a view to making them suitable for your intended use of the system"
I lost count of the installs I've done years ago, but I know I've changed the memory settings on every one I've done since <mumble> before even thinking of starting the new install up!