Initial installation and configuration worked, but when I shut down both of them and tried to restart I get errors and locks. I've tried to provide as much detail below as I can. This is an evaluation installation. I know that when I get to production the servers that these applications will reside on will be shut down from time to time to initialize security patches.

Oracle VirtualBox VM version 4.1.8 r75467
OS: CentOS 6.0

VirtualBox settings:
Memory allocation: 1024 MB
Storage: 20 Gb
Network: Bridged Adapter

OS User account: jira
Groups: jira and apache
Java Version: 1.6.0_ 17
Opened ports 8080 and 8060 (tcp) on Firewall
JIRA Installation: /opt/atlassian-jira-5.0.1-standalone
Fisheye Installation: /opt/fecru-2.7.11

JAVA is set to my .bash_profile:
export JAVA_HOME=/usr/

JIRA_HOME is found at the top system directory level as /jira with permissions set to rwx for group and owner, which are both set to the root.jira ownership and rx for other.

jira-application.properties: jira.home =/jira

Under the database configuration:
Entity model field type name :hsql
Entitiy model schema name :PUBLIC
Database Version :HSQL Database Engine - 1.8.0
Database Driver :HSQL Database Driver - 1.8.0
Database URL :jdbc:hsqldb:/jira/database/jiradb
Database JDBC config :hsql jdbc:hsqldb:/jira/database/jiradb

When I run the ./startup.sh script, it is as the JIRA user.

Initial installation and configuration seemed to work perfectly. I was able to run everything,
got my licenses, JIRA worked. I chose to create a VM snapshot and then shut everything down
using the supplied shutdown scripts.

When I try to restart everything (jira) ./startup.sh it seems to work, but as I look in the
catalina.out log I find errors

main FATAL [atlassian.jira.startup.JiraStartupLogger]

The following plugins are required by JIRA, but have not been started: Atlassian JIRA - Plugins -
Project Config Plugin (com.atlassian.jira.jira-project-config-plugin), Embedded Gadgets Plugin
(com.atlassian.gadgets.embedded, Gadget Dashboard Plugin (com.atlassian.gadgets.dashboard),
Opensocial Plugin (com.atlassian.gadgets.opensocial), Gadget Directory Plugin (com.atlassian.gadgets.directory),
Atlassian JIRA - Plugins - Gadgets Plugin (com.atlassian.jira.gadgets)

main FATAL [atlassian.jira.upgrade.UpgradeLauncher] Skipping, JIRA is locked.
main INFO [atlassian.jira.scheduler.JiraSchedulerLauncher] JIRA Scheduler not started: JIRA startup checklist failed.

It doesn't make sense that I can install and configure everything on one day, and do a soft
shutdown of the application and have it now tell me that it can't start up plugins that it
apparently used the time before.

I've removed the lock a few times, made sure the last jira process was killed off and tried
to restart it again, ran the ./start-jira.sh script and got the following:

main FATAL [jira.web.dispatcher.JiraWebworkActionDispatcher]

JIRA startup failed, JIRA has been locked.

org.apache.coyote.http11.Http11Protocol start
INFO: starting Coyote HTTP/1.1 on http-8080

I saw that there might have been an issue with the java 1.6.0_17 release so I did an update to
java 1.6.0_22 and removed the lock again, and stopped the jira process that was running. I
ran the ./startup.sh

In the catalina.out file, I see:
main ERROR [atlassian.plugin.manager.PluginEnabler] Unable to start the following plugins
due to timeout while waiting for plugin to enable: com.atlassian.jirafisheyeplugin

Then a few lines down:

main FATAL [jira.web.dispatcher.JiraWebworkActionDispatcher]

JIRA startup failed, JIRA has been locked.

org.apache.coyote.http11.Http11Protocol start
INFO: starting Coyote HTTP/1.1 on http-8080

    CommentAdd your comment...

    1 answer


      As I was about to test another option, I knew I would have to kill off the current running jira process. The ps -ef | grep jira returned with the following process running. I happened to look at the string a little closer and found that the /usr/bin/java was being set to /usr//bin/java/. I went into my .bash_profile and reset the JAVA_HOME to JAVA_HOME=/usr INSTEAD of /usr/. I killed the process, removed the lock file in the /jira home directory and ran the ./startup.sh script. I followed through on the catalina.out file and found that everything ran perfectly.

      jira 9162 1 1 10:31 pts/0 00:06:35 /usr//bin/java -Djava.util.logging.config.file

        CommentAdd your comment...