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

[Deleted user]

The following plugins fail to load:

Gadget Directory Plugin (com.atlassian.gadgets.directory)

Atlassian Navigation Links Plugin (com.atlassian.plugins.atlassian-nav-links-plugin)

Atlassian JIRA - Plugins - Gadgets Plugin (com.atlassian.jira.gadgets)

It is a newly installed instance of JIRA. I configured the database connection to mysql and set up a user. Then I started the server with the start-jira.sh. I am using a ubuntu vserver.

Logfile: Log

What I have tried so far:

• Removed the .lock file
• Used Java 6 instead of 7
• Restarted
• Added the JVM parameter -Datlassian.plugins.enable.wait=500
• Increased memory to 1024m for min AND max
• Increased Permsize to 512m
• Cleared the work folder in installation dir
• Removed the '.osgi-plugins' and the '.bundled-plugins' folders
• Reinstalled

Observations:

• plugins seem to load till the last 5-10 ones
  • then timeout messages appear, but i dont know why
• every plugin gets managed to load while the 2000 Timer is running
  • the last ones still get an TIMER error in the log files

[Jen Connor]

Setting the -Datlassian.plugins.enable.wait=300 argument as explained in the link Fabio gave resolved this issue for me. It takes about 10 minutes for Jira to start up now, but at least it is able to start all of the plugins.

[Fabio Racobaldo _Herzum_]

Perfect! I'm happy for that

[Deleted user]

As described in the question this doesn't help me. I set the wait timer to 5000 but this still doesn't help.

[Michael Brinson]

I'm in exactly the same boat Stephan.

I've got pretty nearly identical specs as you also:

Ubuntu 12.04.4 LTS

And I've tried all of the same resolutions as well with no change in results.

I end up with the same 3 plugins failing to load as well.

Did you ever get this resolved?

[Andrea Bodei]

What is the procedure to set -Datlassian.plugins.enable.wait=300 ?

[Dave Woods]

Setting the timeout worked for me.  In my Win 7 box, just added it to setenv.bat.  Also I had to open permissions to the  C:\Program Files (x86)\Atlassian folder to allow the lock file to be created

[Fabio Racobaldo _Herzum_]

Hello Stephan,

please take a look here https://confluence.atlassian.com/display/JIRAKB/JIRA+System+Plugin+Timeout+While+Waiting+for+Plugins+to+Enable

It's seems a timeout issue.

Let me know,

Fabio

[Deleted user]

java -Djava.io.tmpdir=./ -jar support-tools.jar

Benchmark: RandomAccessFile

TOTALS

--------------------

statavgmedianminmax

--------------------

open76.60942.00327.04217.291.035

r/w31.05627.32717.613249.342

close8.4377.6754.81895.907

delete94.41039.48928.38316.871.992

--------------------

All times are in nanoseconds.

This results seem to be good or excellent. It's not the disk drive speed.

lscpu

Architecture: i686

CPU op-mode(s): 32-bit, 64-bit

Byte Order: Little Endian

CPU(s): 4

Vendor ID: AuthenticAMD

CPU family: 16

Model: 2

Stepping: 3

CPU MHz: 750.000

BogoMIPS: 3817.64

Virtualization: AMD-V

Should'nt be the CPU either.

lshw -short -C memory

H/W path Device Class Description

========================================

/0/0 memory 2GiB System memory

/0/1/0 memory 128KiB L1 cache

/0/1/1 memory 512KiB L2 cache

Memory should be fine too.

Am I missing something?

[whereisaaron]

Installing 6.2.4 on a stock CentOS 6 on an AWS c3.large instance I had the same problem. The first time I started it about 30 plugins timed out, the second restart only these three. I changed the plugin timer to 600 and that allow Jira to start.

[Michael Brinson]

Aaron - When you say you changed the plugin timer, are you just talking about the -Datlassian.plugins.enable.wait=300 argument, or do you mean you somehow went into the settings for each plugin and added the :=600 option to the plugin?

[whereisaaron]

Michael - I changed just that one global setting to a larger value rather than any per-plugin settings.

[Andrea Bodei]

Page not found

[Andrea Bodei]

I have the same problem with a x86-64bit dual-core 16GB RAM under Linux Ubuntu 15.04 (kernel 4.0.9). I hope to don't have to reinstall JIRA again.

[Andrea Bodei]

I have the same problem

[Daniel Wester]

What are the specs of the machine you're running on? I've seen this issue on a small amazon vm and bumping up the CPU helped there.

[Deleted user]

It is a linux vserver with Ubuntu 12.04.4 LTS.

Maxx-RAM is 2GB.

Guaranteed RAM is 1GB.

Maybe i should take more guaranteed RAM.

What is the smallest amount Jira and JVM need?

[Deleted user]

lscpu

Architecture: i686

CPU op-mode(s): 32-bit, 64-bit

Byte Order: Little Endian

CPU(s): 4

Vendor ID: AuthenticAMD

CPU family: 16

Model: 2

Stepping: 3

CPU MHz: 750.000

BogoMIPS: 3817.64

Virtualization: AMD-V

[Fabio Racobaldo _Herzum_]

Hello Stephan,

take a look here in order to fix your problem https://confluence.atlassian.com/display/JIRAKB/JIRA+does+not+Start+Due+to+Disabled+Bundled+Plugin

If not, please provide me more information about the log.

Hope this helps,

Fabio

[Deleted user]

SELECT * FROM pluginstate where pluginenabled = 'false';

gets me an empty dataset, so the plugins are enabled.

[Fabio Racobaldo _Herzum_]

any error on the log file?

[Deleted user]

I uploaded a log file: http://justpaste.it/atlassian-jira-log