Hi,
We are trying to start the jira-tomcat, but after started it throws the jira application startup failed due to some errors.
Hence not able to see the jira front page, receiving 404 page. Advice to solve the issue
Regards
Sa
Hi
Ivar Sønstabø [Bouvet ASA] and Nic, thanks for sharing your views, solved the issu based on the below URL. Moreover the error due to tar, actualy we want to use gtar , hence all the class files got extracted proroperly ....
http://confluence.atlassian.com/display/JIRA/Solaris+ClassNotFoundException
You should accept your own answer as the solution :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi!
What does the log say? e.g. jira-home\logs\
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Pls find the sample logs
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) log4j:ERROR Could not instantiate appender named "filelog". Sep 28, 2011 11:27:35 AM org.apache.catalina.core.StandardContext start SEVERE: Error listenerStart Sep 28, 2011 11:27:36 AM org.apache.catalina.core.StandardContext start SEVERE: Context [/atlassian-jira] startup failed due to previous errors Sep 28, 2011 11:27:36 AM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory monitor Sep 28, 2011 11:27:36 AM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory test Sep 28, 2011 11:27:36 AM org.apache.catalina.core.StandardContext start SEVERE: Error listenerStart Sep 28, 2011 11:27:36 AM org.apache.catalina.core.StandardContext start SEVERE: Context [/test] startup failed due to previous errors Sep 28, 2011 11:27:36 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on http-8080
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you add a bit more? There is not much to go on here.
Can you also add some info on the version you are installing? And if it is standalone, for demo, etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can delete the file and try and start Jira again. That will create a new file with less lines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
And the full log?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
The whole catalina.out file is around 5200 lines, does there is any option to attach file in this forum
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Mail it to jira.log@gmail.com
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, Java logs are long and painfully detailed, which makes it hard to find the actual error. The important bit here is
ERROR Could not instantiate appender named "filelog".
and generally, you need to look for more lines like that. In fact, it's best to simply skim a log file for the more English lines in it, as they're where to start.
But, I've seen the error above before - can you check that your installation has full read/write permissions on the log directory, and then check that there is only one log4j.jar in the installation's classpath. If in doubt, just go to the root of the Jira installation and search for "log4j" - more than one file of the same name can cause this and removing extra copies can fix it. If not, then you want to search the whole environment it's running in, which is a little more complex.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I believe you should do what @Nic says. Everything in the log points to an issue with log4j (which is weird since you've used the standalone installer (it should be included))
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.