Confluence PID issue. (Removing/clearing stale PID file)

vignesh4sh · 12-04-2012, 06:14 AM

Hi,
I have installed Jira and Confluence on ubuntu server.
I using 3 tomcat like jira,jira1,jira2.
eg: example.com:8040/jira, example.com:8070/jira1, example.com:8080/jira2

Jira works fine and i can log in and works at a time in 3jira. But I cant able to work in confluence at a same time. when i start the 3 confluence service. It used to run single confluence only.

when i start the other two confluence. I getting this error.

Quote:

Existing PID file found during start.
Removing/clearing stale PID file.

I stuck in this.
please give me any idea

Thanks.

unSpawn · 12-04-2012, 07:09 AM

Why not just do what it says and removing the stale PID file? If you don't know where the PID file is created inspect /etc/init.d/confluence, or any shell scripts in the /bin/ directory of where you installed Confluence, for PID entries or check /var/run for a "confluence.pid"?

vignesh4sh · 12-04-2012, 10:27 PM

Thanks for reply,

I removed the catalina.pid file and restarted confluence, confluence1,confluence2.
Again getting same response.

Quote:

Existing PID file found during start.
Removing/clearing stale PID file.

I couldn't able to run all three confluence.

Thanks,

unSpawn · 12-05-2012, 05:08 AM

To avoid spending unnecessary time on diagnostics please first:
- ensure your Confluence installation was done by the book, meaning like the official Confluence documentation suggests,
- if Confluence ran OK after installation then review any changes you made since for syntax and other errors,
- enable Confluence logging (and if set disable JAVA_OPTS=confluence.ignore.debug.logging in setenv.sh) and check wherever it's configured to log4j to for clues,
- check Apache tomcat logs for clues.

If that doesn't show clues remove the PID file again, then run your Confluence startup script like this:

Code:

/bin/bash -vx /etc/init.d/confluence start 2>&1|tee /tmp/confluence.tee

then inspect "/tmp/confluence.tee" for lines leading up to the "Existing PID file found during start." message for clues. Note if /etc/init.d/confluence actually executes another startup script (for example "/INSTALLPATH/confluence/startup.sh") then have Bash execute that script with the right arguments and output through tee.

If that doesn't work then check http://confluence.atlassian.com/disp...mentation+Home and http://confluence.atlassian.com/disp...edge+Base+Home or else http://support.atlassian.com/

vignesh4sh · 12-05-2012, 07:00 AM

Hi,
Thanks for your suggestion.

I have checked log
while confluence1 works. confluence2 and confluence3 stopped and getting same error like

Quote:

Existing PID file found during start.
Removing/clearing stale PID file.

This is my confluence2 log

Quote:

5 Dec, 2012 6:15:20 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 36457 ms
5 Dec, 2012 6:15:20 PM org.apache.catalina.core.StandardServer await
SEVERE: StandardServer.await: create[8000]:
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(Unknown Source)
at java.net.ServerSocket.bind(Unknown Source)
at java.net.ServerSocket.<init>(Unknown Source)
at org.apache.catalina.core.StandardServer.await(StandardServer.java:406)
at org.apache.catalina.startup.Catalina.await(Catalina.java:676)
at org.apache.catalina.startup.Catalina.start(Catalina.java:628)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
5 Dec, 2012 6:15:20 PM org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8041
5 Dec, 2012 6:15:21 PM org.apache.catalina.core.StandardService stop
INFO: Stopping service Tomcat-Standalone
5 Dec, 2012 6:15:21 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [] registered the JDBC driver [org.hsqldb.jdbc.JDBCDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
5 Dec, 2012 6:15:21 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
5 Dec, 2012 6:15:21 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [] registered the JDBC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
5 Dec, 2012 6:15:21 PM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
SEVERE: The web application [] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@1516490]) and a value of type [org.dom4j.DocumentFactory] (value [org.dom4j.DocumentFactory@a14e84]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.
5 Dec, 2012 6:15:21 PM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
SEVERE: The web application [] created a ThreadLocal with key of type [com.atlassian.core.logging.ThreadLocalErrorCollection$2] (value [com.atlassian.core.logging.ThreadLocalErrorCollection$2@29d50d]) and a value of type [java.lang.Boolean] (value [false]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.
log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository.
5 Dec, 2012 6:15:26 PM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8041

Thanks

unSpawn · 12-05-2012, 07:14 AM

Quote:

Originally Posted by vignesh4sh

Thanks for your suggestion.

Well at least you confirmed / replied to one of the things I suggested...

Quote:

Originally Posted by vignesh4sh

Code:

5 Dec, 2012 6:15:20 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 36457 ms
5 Dec, 2012 6:15:20 PM org.apache.catalina.core.StandardServer await
SEVERE: StandardServer.await: create[8000]:
java.net.BindException: Address already in use

I'm not a Java / Tomcat guru but doesn't that strike you as somewhat odd? I mean, shouldn't you investigate that as it's the first error that hits the log?