After installing JIRA and trying to get to the configuration (Linux version) I can see that java process is using 90% CPU and Disk usage is going up too. When I try to access the page, it takes a lot of time, and finally times out. I know it's not a 404 since I get the page title, but I get a blank page.
Is this a normal behaviour, is the first launch usually taking a lot of resource? I'm suspecting the server to be initializing, but timing out for some reason.
I'm using Ubuntu 11.10.
When I start the service I get:
To run JIRA in the foreground, start the server with start-jira.sh -fg
executing using dedicated user: jira
.... .NMMMD. ...
.IMMMMMM. .NMMMN. .MMMMMN,
Version : 5.1.4
Detecting JVM PermGen support...
PermGen switch is supported. Setting to 256m
If you encounter issues starting or stopping JIRA, please see the Troubleshooting guide at http://confluence.atlassian.com/display/JIRA/Installation+Troubleshooting+Guide
Server startup logs are located in /opt/atlassian/jira/logs/catalina.out
Using CATALINA_BASE: /opt/atlassian/jira
Using CATALINA_HOME: /opt/atlassian/jira
Using CATALINA_TMPDIR: /opt/atlassian/jira/temp
Using JRE_HOME: /opt/atlassian/jira/jre/
Using CLASSPATH: /opt/atlassian/jira/bin/bootstrap.jar
Using CATALINA_PID: /opt/atlassian/jira/work/catalina.pid
Existing PID file found during start.
Removing/clearing stale PID file.
Also, if it isn't working, I'd like to know if there's a written procedure for uninstalling JIRA correctly. (I've ran the .bin file and don't know what has been added and where).
I believe that this problem is the amount of physical RAM of your server, since you have only 512MB and it is not enough to proper run JIRA. Additionally, I could see that you have only 128MB allocated to the JVM, on your Java settings.
Thus, please increase your physical RAM to at least 2GB and increase the JVM memory, as per the instructions on the following article:
For more information about the hardware recommendations for JIRA, please refer to the following document:
Do you have multiple JIRA processes running? What output do you get if you type the following:
ps aux|grep jira
If there are multiple JIRA processes running, the behavior you mentioned can sometimes occur. Be sure there are no processes running when you run the start up command.
You can also tail the jira log file on startup if you want to see what's happening.
bin/startup.sh ; tail -f /opt/atlassian/jira/logs/atlassian-jira.log (or whatever the path to your log files is)
Also check the jira log file under /opt/atlassian/jira/logs/atlassian-jira.log for errors; that may help you pinpoint any startup errors. Or you can paste them here and get help.
You should be able to fix the problem without uninstalling.
Here's the pastebin link : http://pastebin.com/DN84ZryS
As you can see there seems to be many plugins that can't be loaded...
You definitely need to reduce the memory setting in JIRA's setenv.sh or wherever this has been set.
It says: Maximum Allowable Memory : 742MB
Meaning you've allocated 742MB to it when you've got 512MB including OS overhead and other things. Try that. However, it isn't recommended to run JIRA on a 512mb VPS.
Could you tell me why there's an IO exception at the startup (after changing the min/max memory)
2012-09-13 08:39:34,280 main ERROR [atlassian.jira.plugin.PluginPath$JiraHomeAdapter] Unable to delete file: /var/atlassian/application-data/jira/plugins/.osgi-plugins/felix/felix-cache/bundle44/bundle.id exists:true canRead:true canWrite:false isDirectory:false 2012-09-13 08:39:34,281 main FATAL [atlassian.jira.upgrade.PluginSystemLauncher] A fatal error occured during initialisation. JIRA has been locked. com.atlassian.plugin.osgi.container.OsgiContainerException: Unable to clean the cache directory: /var/atlassian/application-data/jira/plugins/.osgi-plugins/felix
It looks like you've also got permissions problems with your directories. Please ensure the user running JIRA has enough read/write rights. It currently doesn't have the right to delete a file.
Having said that, might be good to clear the felix cache in this case by deleting everything inside the felix-cache folder.
Every team in the world is unique, and so Atlassian believes that each and every team's best way of working needs to be molded to their unique circumstances – ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot