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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Just worked through a strange upgrade to confluence 6.15.8 using the bin file on Linux.
We have CIS level 2 controls in place on Linux/Postgres and one result is that umask is set to 077.. I expected an upgrade script to set up the environment it needed but alas no...
Everything the upgrade touches get permissions based on that umask..
This results in error messages that imply a corrupt install, like the "/opt/atlassian/confluence/bin/bin/setenv.sh not found" type of message.
Also /etc/init.d/confluence, which is used as the systemd unit file gets 700 perms which means confluence will not start with systemctl but will with the start-confluence.sh...
and more than a few permission denied red herrings..
I see a lot of permission related upgrade mishaps over the years for this product in this forum and online. This took me a minute to figure out.
If you are upgrading you may want to clear your environment, including the umask, in your shell before starting.. the script simply isn't smart enough to do that...
Hope this helps!