i guess it is because of error in path
/opt/atlassian/jira/jre//bin/java
I don't know where to set it
I tried looking into setenv.sh - could not find.
Hi pareshkumar,
If your MySQL is indeed on localhost, I recommend you to set it like localhost.
If you want to connect with another server, and it's name is not being recognized, you can try to put the IP address or set the IP and the Hostaname on /etc/hosts file. This will make the server recognize the Server Name by its IP.
Hi Pareshkumar,
We'll need more details on this case, like:
* How're you starting JIRA
* What message you're seeing on screen
* What message you're seeing on <install folder>/logs/catalina.out
Best regards,
Felipe Alencastro
start-jira.sh
To run JIRA in the foreground, start the server with start-jira.sh -fg
executing using dedicated user: jira1
.....
.... .NMMMD. ...
.8MMM. $MMN,..~MMMO.
.?MMM. .MMM?.
OMMMMZ. .,NMMMN~
.IMMMMMM. .NMMMN. .MMMMMN,
,MMMMMM$..3MD..ZMMMMMM.
=NMMMMMM,. .,MMMMMMD.
.MMMMMMMM8MMMMMMM,
.ONMMMMMMMMMMZ.
,NMMMMMMM8.
.:,.$MMMMMMM
.IMMMM..NMMMMMD.
.8MMMMM: :NMMMMN.
.MMMMMM. .MMMMM~.
.MMMMMN .MMMMM?.
Atlassian JIRA
Version : 6.2
Detecting JVM PermGen support...
PermGen switch is supported. Setting to 384m
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:/opt/atlassian/jira/bin/tomcat-juli.jar
Using CATALINA_PID: /opt/atlassian/jira/work/catalina.pid
Existing PID file found during start.
Tomcat appears to still be running with PID 28344. Start aborted.
does it stuck somewhere?
(catlina.log) attached
Lets start by making sure there is no JIRA instance running. In order to do it so, please run the following command from your Terminal:
ps aux | grep jira // as the output, you will find something similar to: rafael 9176 24.6 2.2 3799364 182160 s001 U 5:14PM 0:06.10 /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/bin/java -Djava.util.logging.config.file=/<jira-home>/jira-6.2.4/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -XX:MaxPermSize=384m -Xms384m -Xmx768m -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 -XX:+PrintGCDateStamps -XX:-OmitStackTraceInFastThrow -Djira.home=/var/www/ATLASSIAN/data/jira-6.2.4 -Djava.endorsed.dirs=/<jira-home>/jira-6.2.4/endorsed -classpath /<jira-home>/jira-6.2.4/bin/bootstrap.jar:/<jira-home>/jira-6.2.4/bin/tomcat-juli.jar -Dcatalina.base=/<jira-home>/jira-6.2.4 -Dcatalina.home=/<jira-home>/jira-6.2.4 -Djava.io.tmpdir=/<jira-home>/jira-6.2.4/temp org.apache.catalina.startup.Bootstrap start rafael 9233 0.0 0.0 2432784 600 s001 S+ 5:14PM 0:00.00 grep jira // Please, kill the process as per following: kill -9 9176 // where 9176 is the processID to my JIRA instance, in the example above mentioned
According to the above mentioned, your JAVA_HOME is pointing to JAVA JRE instead of JAVA JDK. Please, review where your Java JDK6 or JDK7 is installed and setup your JAVA_HOME as per Installing Java documentation.
After you have done that, go to <jira-home> directory and run the following from your terminal:
./bin/start-jira.sh
In case you continue on experiencing difficulties on starting up your JIRA instance, I would kindly advise you to open a Support ticket under (https://support.atlassian.com)
Kind regards,Rafael
after looking into catlina.out
i founc
SEVERE: Unable to create directory for deployment: /opt/atlassian/jira/conf/Catalina/localhost
is this the issue? if yes how to resovle it
Please, make sure the user running JIRA has enough privileges to read/write/execute files/directories under the location /opt/atlassian/jira
By going to your Terminal, type in:
ls -alh /otp/atlassian
The above will display something like:
drwxr-xr-x@ 15 rafael staff 510B May 7 11:23 . drwxrwxrwx 31 rafael wheel 1.0K Jun 12 16:23 .. drwxr-xr-x@ 28 rafael staff 952B May 1 21:48 jira (...)
Please, run the following command from your Terminal:
sudo chmod -R 755 /opt/atlassian/jira
Now, your JIRA will have permissions to read/write/execute files/directories under the location /opt/atlassian/jira
still same error
I have tried stop-jira.sh
it throws:
PID file found but no matching process was found. Stop aborted.
----------------------------------------
is it ps aux | grep java or ps aux | grep jira
--------------------------------------------------
I have tried ps aux | grep jira
it shows output
root 40395 0.0 0.0 103248 824 pts/1 S+ 22:21 0:00 grep jira
------------------------
then i executed kill -9 40395
error
-bash: kill: (40395) - No such process
Please guide
i'm getting below error even after deleting lock file
Unable to create and acquire lock file for jira.home directory '/var/atlassian/application-data/jira'.
******************************************************************************************************
2014-06-12 22:41:25,456 localhost-startStop-1 WARN [atlassian.jira.startup.ChecklistLauncher] Setting an unset default variable "plugin.webresource.batching.off" to: false
2014-06-12 22:41:25,457 localhost-startStop-1 INFO [atlassian.jira.startup.JiraStartupLogger] Running JIRA startup checks.
2014-06-12 22:41:25,457 localhost-startStop-1 FATAL [atlassian.jira.startup.JiraStartupLogger] Startup check failed. JIRA will be locked.
2014-06-12 22:41:25,547 localhost-startStop-1 INFO [jira.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/application-data/jira/dbconfig.xml
2014-06-12 22:41:25,789 localhost-startStop-1 ERROR [jira.web.dispatcher.JiraWebworkActionDispatcher]
******************************************
JIRA startup failed, JIRA has been locked.
Hello Pareshkumar,
In order to execute start-jira.sh you MUST run the following:
./start-jira.sh
Please, read carefully our comments.
On previous messages, I have inform to run the following command:
Please, notice that processID 9176 is the one for JIRA. ProcessID 9233 has been generated through your command (ps aux | grep jira).
If you haven't install JIRA as a Linux service, please, shutdown your server and restart it. This should kill all process associated to JIRA.
Once you do that, please try to start JIRA (./start-jira.sh)
Please, make sure the user running JIRA has adminstrative right.
Apparently you're facing a permission related problem. I'm assuming you used the JIRA installed and have your data folder on the default path.
chown -R jira:jira /opt/atlassian/ chown -R jira:jira /var/atlassian/
Now, while logged in with JIRA user, try running start-jira.sh again.
-bash: start-jira.sh: command not found
when i try to execute start-jira.sh using jira user it throws
Is this a memory issue?
setenv.txt
catlinaout1.txt (catlinaout1.txt) (setenv.txt)
You have to start it with the full path, it's probably /opt/atlassian/jira/bin
So try that logged in with JIRA user:
/opt/atlassian/jira/bin/start-jira.sh OR /opt/atlassian/jira/bin/startup.sh
Pareshkumar,
Could you try the command ./start-jira.sh when in the /opt/atlassian/jira/bin directory?
(do not remove the leading ./! , really type in ./start-jira.sh )
Peter
touch: cannot touch `/opt/atlassian/jira/logs/catalina.out': Permission denied
/opt/atlassian/jira/bin/catalina.sh: line 387: /opt/atlassian/jira/logs/catalina.out: Permission denied
Now I'm able to access Jira however when i try to setup mysql connection by putting server name as localhost it works however when i put actual server name it says user does not have access to @serveretc
Access denied for user 'jirauser'@'domain.com' (using password: YES)
You need to grant privileges on the MySQL server to the user and to the JIRA server.
It looks like you're new here. Sign in or register to get started.