Old linux VM with Jira, need to migrate

Question

Customer has an old Linux VM that ran their Jira servicedesk for a time. They want this migrated to a new server as the Linux VM has been having some issues and was shut down months ago.

Going through the migration instructions nets me nothing as I believe whoever installed Jira on this got cutesy with it and didn't install default as they should have. Any idea how to see if Jira is even running, where the database/files would be, and whatever else I should look for? There are some Jira folders on a second drive but nothing matches what the instructions are asking for.

Checked netstat and no 'Jira' ports are listening; at least anything labeled Jira. I'm coming from a place where no one knows how any of this works so it's a black box right now as the company fired all their IT and devops guys.

Jim Knepley - ReleaseTEAM · Answer

It's possible that the /opt/atlassian directory and contents were deleted after the process was started. Though not good, that's not as critical as it might seem.

If you still have /var/atlassian, you could be lucky.

I'm pretty sure the directories under /mnt are the shared home directories. You'll want to keep those.

If all you're missing is /opt/atlassian, you can reinstall Jira via the installer and you've got a good chance that it will work. I would try to install the same version, if you can figure out what that was.

Port-wise, LSOF is the gold standard to discover that, but you might try the default 8080.

daniel · Answer

So Jira looks to be running but not sure where. The process data looks like this:

jira 4180 3877 8 15:47 ? 00:05:54 /opt/java/openjdk/bin/java -Djava.util.logging.config.file=/opt/atlassian/jira/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xms384m -Xmx2048m -XX:InitialCodeCacheSize=32m -XX:ReservedCodeCacheSize=512m -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 -Djira.downgrade.allowed=true -XX:-OmitStackTraceInFastThrow -Djava.locale.providers=COMPAT -Djira.home=/var/atlassian/application-data/jira -Datlassian.plugins.startup.options=-fg -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 -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 -XX:+ExplicitGCInvokesConcurrent -Dignore.endorsed.dirs= -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

I see /opt/atlassian in the printout but that doesn't exist if I type cd /opt/atlassian. Nothing exists on the main drive under that structure.

There are two Jira folders on a second drive in something called /mnt. There's jira and jira-servicemanagement. There is a dbconfig.xml under both.

The customer states that they have jira software and jira servicedesk. I don't know the difference between the two. Maybe that's what this jira and jira-servicemanagement folders are?

Jim Knepley - ReleaseTEAM · Answer

If you can identify the process id using the "ps" command like @Sagar Mahajan said, you can learn tons with the "lsof" command, notably file locations and open network ports.

The database configuration will be in a file called dbconfig.xml, by default in the /var/atlassian/application-data/jira directory. That will contain the database host, database name, and credentials.

Network port configuration is in server.xml (strictly speaking, that's a Tomcat file).

Customizations to the JRE like settings for heap memory are in setenv.sh.