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
Yesterday, I backed up our Jira Server (v8.12.1) and tried to upgrade Ubuntu from 16.04 to 18.04.
During upgrade I got perl and apache version incompatibility errors and because of these issues, upgrade was cancelled.
After that attempt, restarted the server and checked jira modules and pages, and everything was working fine - was planning to revert back to the backup if that wasn't the case.
Today is monday, and people started using Jira, and I realized a message at the administrative pages in Jira.
Then I realized the mail queue and mails were stuck at the error queue.
No matter what I tried with the outgoing email test page, I couldn't manage to make notification emails work. So, it's too late for restoring from the backup since people started using Jira today...
I suspect that these issues arised because of the perl version installation during the Ubuntu Upgrade. I was asked to upgrade from a 5.22 version of perl to 5.26, and I said YES. After that, Apache version mismatch came up and didn't succeed (that was the error failing the upgrade).
Now I think that reverting back to the default Perl version that comes with Ubuntu 16.04 may fix that issue.
Do you have any comments about the idea of Perl downgrade? Would it work?
I am down for a new server installation and upgrading to the latest version of Jira on a new box, but need to fix that too, until I manage that.
Thank you for your comments!