Additional rough jira notes on the upgrade

Jira Notes.md

@@ -361,6 +361,7 @@ sudo /etc/init.d/jira stop
 cd /opt
 sudo rsync -rav atlassian atlassian.bak.202105
 sudo rsync -rav jira-data jira-data.202106
+sudo mv /opt/atlassian/jira /opt/atlassian/jira-8.12.1
 vim /etc/rc.d/init.d/jira
 # Update path to /opt/atlassian/jira/bin
 sudo /etc/init.d/jira start
@@ -378,9 +379,36 @@ Also, if okta doesn't work, you can try placing okta back:
 sudo cp /opt/atlassian/jira/atlassian-jira/WEB-INF/lib/okta-jira-3.1.3.jar /opt/atlassian/jira-8.13.6/atlassian-jira/WEB-INF/lib/okta-jira-3.1.3.jar
 ```
 
-## If all is well
+## Problems during 4/27/2021 upgrade:
 
+### Jira wouldn't start because JAVA_HOME was not yet. 
+1. edit bin/setenv.sh, search for JAVA_HOME and replace with:
 ```
-sudo mv /opt/atlassian/jira /opt/atlassian/jira-8.12.1
+JAVA_HOME="/opt/atlassian/jre/"; export JAVA_HOME
 ```
+2. Copy the old JRE (and I bet this needs to be updated)
+
+### Jira started, but database won't connect. This was because of SSL.
+1. temporarily removed the verify-ssl command from /opt/jira-data/jira/dbconfig.xml
+2. It started.
+3. Stopped it after it initialized
+
+1. copied /home/jira/.posgres to /opt/jira-data/jira/.postgres (this contains the root cert)
+no change
+Tried /opt/jira-data/.postgres, too.
+
+Left it with `sslmode=require`.
+
+### Noisy catalina error: `The encoding [binary] is not recognised by the JRE`, with full stack trace:
+
+see https://jira.atlassian.com/browse/JRASERVER-71265
+added 3 lines to /opt/atlassian/jira-8.13.6/conf/logging.properties:
+```
+# per https://jira.atlassian.com/browse/JRASERVER-71265
+# Surpress 'The encoding [binary] is not recognised by the JRE'
+org.apache.catalina.connector.Response.level = ERROR
+```
+ 
+## If all is well
 
+do a little dance