How do I run jira on Ubuntu after changing domain names?

Question

I am running jira on an azure ubuntu instance.

I recently changed the DNS on our jira instance.  Before changing the DNS it was complaining that two instances of jira were running.

Setup: The jira.home directory is locked

The jira.home directory /var/atlassian/application-data/jira is locked by another running instance of JIRA. Your jira.home directory can only be used by one running JIRA instance.
Review our documentation for more information on setting your JIRA home.

After changing it, it says : 104.46.xx.yy refused to connect.  This is when I enter http://104.46.xx.yy:8080/.

I tried a reboot and an upgrade, interesting to note during the upgrade:

insserv: warning: script 'K01jira1' missing LSB tags and overrides
insserv: warning: script 'K01jira2' missing LSB tags and overrides
insserv: warning: script 'jira1' missing LSB tags and overrides
insserv: warning: script 'jira2' missing LSB tags and overrides
insserv: warning: script 'K01jira1' missing LSB tags and overrides
insserv: warning: script 'K01jira2' missing LSB tags and overrides
insserv: warning: script 'jira1' missing LSB tags and overrides
insserv: warning: script 'jira2' missing LSB tags and overrides

It appears jira is running:

jira@jira:~$ ps aux | grep jira
jira2 1448 0.7 33.8 3025812 1190480 ? Sl 12:32 4:18 /opt/atlassian/jira/jre//bin/java -Djava.util.logging.config.file=/opt/atlassian/jira/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xms384m -Xmx768m -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory -XX:-OmitStackTraceInFastThrow -Datlassian.plugins.startup.options= -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Xloggc:/opt/atlassian/jira/logs/atlassian-jira-gc-%t.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=20M -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+PrintGCCause -classpath /opt/atlassian/jira/bin/bootstrap.jar:/opt/atlassian/jira/bin/tomcat-juli.jar -Dcatalina.base=/opt/atlassian/jira -Dcatalina.home=/opt/atlassian/jira -Djava.io.tmpdir=/opt/atlassian/jira/temp org.apache.catalina.startup.Bootstrap start
root 6033 0.0 0.1 92832 4396 ? Ss 21:41 0:00 sshd: jira [priv]
jira 6038 0.0 0.1 36800 3752 ? Ss 21:41 0:00 /lib/systemd/systemd --user
jira 6045 0.0 0.0 61276 2000 ? S 21:41 0:00 (sd-pam)
jira 6100 0.0 0.0 92832 2384 ? S 21:41 0:00 sshd: jira@pts/0
jira 6102 0.0 0.1 12932 4276 pts/0 Ss 21:41 0:00 -bash
jira 10345 0.0 0.0 27636 1432 pts/0 R+ 21:59 0:00 ps aux
jira 10346 0.0 0.0 12944 1012 pts/0 S+ 21:59 0:00 grep --color=auto jira

I installed ubuntu desktop and tried 127.0.0.1:8080 in firefox.  It didn't work :-(

Was I meant to reconfigure it after changing the DNS?  Is there a way to manually start jira or test it locally on ubuntu that I will know whether or not it is working?

seanjmc · Answer

Thanks Andrew,

That sounds sensible.  I managed to fix the issue around 3am in the morning and have mostly forgotten what I did!  I think I deleted the lock file and sudo stopped and started the service as it was complaining it belonged to jira2.  I think there was something else too but to be honest, I can't recall as I spent a LOT of time getting vncserver working which was pointless in the end.

Andy Heinzer · Answer

Hi Sean,

Out of the box when you start Jira, the webserver Jira uses (Tomcat), will bind its use on all network interfaces of that server.   However it is possible that your configuration has specific bound to a particular network interface.  If this happens, then requests to localhost or 127.0.0.1 won't work unless that's the interface Jira is set to use.

I'd recommend checking out our KB on this in How to run JIRA on a specific IP.  It explains how you can check/configure Jira's server.xml file in order to operate a connector.   If no 'address' parameter is defined on the connector, then Jira will bind itself to all the available interfaces of that server.   It might help to remove any address parameter from your connector, save that file, and restart jira for this setting change to take effect.

When you start Jira, you can also check out the catalina.out file.  This is a log file created by Tomcat in the server installation directory/logs/   If the JIRAHOME logs aren't being updated, it can help to check this for log entries as well.