JIRA Startup Failed

Ricardo Batista February 4, 2012

Hello I'm getting an error on installation on VirtualBox with Windows 7 (atlassian-jira-4.4.4) with no antivirus and firewall disable.

JIRA Startup Failed

You cannot access JIRA at present. Look at the table below to identify the reasons

Description

The following plugins are required by JIRA, but have not been started:

  • Gadget Directory Plugin (com.atlassian.gadgets.directory)
  • Embedded Gadgets Plugin (com.atlassian.gadgets.embedded)
  • Gadget Dashboard Plugin (com.atlassian.gadgets.dashboard)
  • Atlassian JIRA - Plugins - Gadgets Plugin (com.atlassian.jira.gadgets)

File: access_log

127.0.0.1 1327x1x1 - [04/Feb/2012:22:07:57 +0000] "GET / HTTP/1.1" 302 - 42308 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1328x2x1 - [04/Feb/2012:22:08:21 +0000] "GET /JiraLockedError HTTP/1.1" 200 3833 12402 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1328x3x1 - [04/Feb/2012:22:08:22 +0000] "GET /favicon.ico HTTP/1.1" 302 - 0 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1328x4x1 - [04/Feb/2012:22:08:22 +0000] "GET /JiraLockedError HTTP/1.1" 200 3833 18 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1331x5x1 - [04/Feb/2012:22:11:23 +0000] "GET /JiraLockedError HTTP/1.1" 200 3833 80 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1335x6x1 - [04/Feb/2012:22:15:17 +0000] "GET / HTTP/1.1" 302 - 0 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1335x7x1 - [04/Feb/2012:22:15:17 +0000] "GET /JiraLockedError HTTP/1.1" 200 3833 0 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1335x8x1 - [04/Feb/2012:22:15:17 +0000] "GET /favicon.ico HTTP/1.1" 302 - 0 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1335x9x1 - [04/Feb/2012:22:15:17 +0000] "GET /JiraLockedError HTTP/1.1" 200 3833 0 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1341x10x1 - [04/Feb/2012:22:21:05 +0000] "GET / HTTP/1.1" 302 - 10 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1341x11x1 - [04/Feb/2012:22:21:06 +0000] "GET /JiraLockedError HTTP/1.1" 200 3833 20 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1344x12x1 - [04/Feb/2012:22:24:07 +0000] "GET /JiraLockedError HTTP/1.1" 200 3833 20 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1347x13x1 - [04/Feb/2012:22:27:08 +0000] "GET /JiraLockedError HTTP/1.1" 200 3833 10 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1350x14x1 - [04/Feb/2012:22:30:08 +0000] "GET /JiraLockedError HTTP/1.1" 200 3833 11 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1353x15x1 - [04/Feb/2012:22:33:10 +0000] "GET /JiraLockedError HTTP/1.1" 200 3833 11 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1356x16x1 - [04/Feb/2012:22:36:18 +0000] "GET /JiraLockedError HTTP/1.1" 200 3833 10 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"

File: catalina.2012-02-04

4/Fev/2012 21:58:29 org.apache.catalina.core.AprLifecycleListener init
INFO: Loaded APR based Apache Tomcat Native library 1.1.20.
4/Fev/2012 21:58:29 org.apache.catalina.core.AprLifecycleListener init
INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
4/Fev/2012 21:58:29 org.apache.catalina.startup.SetAllPropertiesRule begin
WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting property 'minSpareThreads' to '25' did not find a matching property.
4/Fev/2012 21:58:29 org.apache.catalina.startup.SetAllPropertiesRule begin
WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting property 'maxSpareThreads' to '75' did not find a matching property.
4/Fev/2012 21:58:33 org.apache.coyote.http11.Http11AprProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
4/Fev/2012 21:58:33 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 8696 ms
4/Fev/2012 21:58:34 org.apache.catalina.realm.JAASRealm setContainer
INFO: Set JAAS app name Catalina
4/Fev/2012 21:58:34 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
4/Fev/2012 21:58:34 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.32
4/Fev/2012 22:07:10 org.apache.coyote.http11.Http11AprProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
4/Fev/2012 22:07:14 org.apache.catalina.startup.Catalina start
INFO: Server startup in 519005 ms

Thank you!!!

2 answers

1 accepted

4 votes
Answer accepted
Ricardo Batista February 4, 2012

Del all files in:

\Program Files\Atlassian\Application Data\JIRA\plugins\.bundled-plugins

\Program Files\Atlassian\Application Data\JIRA\plugins\.osgi-plugins

0 votes
Julia Buyers November 24, 2024

It seems like you're facing a Jira startup issue where the system cannot start properly due to missing or inactive required plugins (like the Gadget Directory Plugin, Embedded Gadgets Plugin, etc.) while trying to run the Haunted Dorm APK on VirtualBox with Windows 7 (atlassian-jira-4.4.4), with no antivirus and firewall disabled. The error also mentions Jira being "locked," which suggests there may be an issue with the service or Jira's internal processes.

Here’s a step-by-step guide to help resolve the issue:

1. Check Jira Lock State:

  • The logs mention that Jira is "locked." This often happens when Jira wasn't shut down properly or is still in a locked state from a previous start attempt.
  • Clear the lock file:
    • Navigate to the Jira home directory (<Jira Home>/caches/) and look for any .lock files and delete them. This will unlock Jira and allow it to start fresh.

2. Ensure Plugin Compatibility:

  • You mentioned plugins like Gadget Directory Plugin and others. These plugins are often crucial for Jira to load correctly.
  • Verify plugin status:
    • Check if any required plugins are disabled or corrupted in the Jira installation. If possible, start Jira in safe mode and attempt to activate the plugins from the Manage Apps section once Jira is accessible.
  • If plugins were recently added (like Agile and Service Desk), ensure that they are compatible with the version of Jira you're running. You can do this by visiting the Atlassian plugin repository.

3. Permissions Issue:

  • The logs and errors indicate some file access issues (like access_log). Make sure Jira has appropriate permissions to read and write to all necessary files and directories.
  • Verify permissions:
    • Right-click on your Jira directories (e.g., logs, data, installation), go to PropertiesSecurity, and make sure the service account has Full Control over these folders.

4. Check Tomcat Logs:

  • Jira runs on an Apache Tomcat server, and your logs show that the Tomcat server started, but Jira couldn't fully initialize. Check the Tomcat logs for more details:
    • Navigate to the logs directory under Jira’s installation path (likely C:\Program Files\Atlassian\JIRA\logs).
    • Look for catalina.out or atlassian-jira.log files for more detailed error information.

5. Service Restart and Cleanup:

  • Restart the Jira Service: If the above steps don’t resolve the issue, restart the Jira service manually from the Windows Services (services.msc).
  • Clear the Cache and Temporary Files: Delete any contents in the temp and work directories in the Jira home folder. Jira will regenerate these files on restart.

6. Perform a Clean Restart of Jira:

  • Ensure no Jira processes are running (check in Task Manager).
  • If Jira still won't start, attempt a reinstall of Jira after backing up your jira_home and jira_install directories. This may be a last resort if there's corruption in the installation.

7. Investigate Further Errors:

  • Look for any dependency issues with the plugins mentioned in your logs (like Gadget Plugins) which may not be compatible with the Jira version you're using.
  • Revert to a previous backup if the issue started after recent changes or plugin installations.

These steps should guide you toward resolving the issue.

Suggest an answer

Log in or Sign up to answer