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!
- Create your own custom emoji 🔥 - "Shake for Feedback" on mobile 📱 - An endless supply of GIFs via GIPHY 🤩 Is there anything quite as nice as a pleasant surprise? Comment below with what...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events