cancel
Showing results for 
Search instead for 
Did you mean: 

Alfresco Tomcat Error - catalina.pid....

bensewell
Champ in-the-making
Champ in-the-making
Hi,

Running Alfresco 3.4.d on Centos 5.5.  Everytime i restart the machine tomcat refuses to start. 

When i try manually using the ./alfresco.sh start it give an error of:

PID File:  (/opt/alfresco-3.4.d/tomcat/temp/catalina.pid) found.  Is tomcat still running? Start aborted.
/opt/alfresco-3.4.d/tomcat/scripts/ctl.sh : tomcast could not be started.

But if i delete the said file and then try and try to stop start it still fails.

Then if i do a ./alfresco.sh restart it brings tomcat back up.

Anyone know what i need to do to make it come online on reset?  Some change in config file / parameter setup?

Thanks,
5 REPLIES 5

nikolaricci
Champ in-the-making
Champ in-the-making
I had same problem, after power loss. And after new boot up, tomcat couldn't start, then I've removed  catalina.pid and then started successfully.  Smiley Happy

acommons
Champ on-the-rise
Champ on-the-rise
Same issue here after an orderly system shutdown. I have Alfresco registered as a service so I'm assuming that an orderly stop will be intitiated as part of the shutdown - i.e. service alfresco stop.

I have no problem manualy staring and stopping with alfresco.sh however if I use the service command I get errors displayed on the service alfresco stop. Alfresco seems to stop and the catalina.pid file goes away so a restart is fine but the errors are still a worry.

cheers

bensewell
Champ in-the-making
Champ in-the-making
Yes I can get round this fault, its just something a bit annoying that shouldnt really happen.  I have noticed a tidyup script in the alfresco folders which i might run to see if it gets rid of the problem then link it onto the back of the stop and restart alfresco scripts if it works.

acommons
Champ on-the-rise
Champ on-the-rise
My gut reaction (a.k.a. wild guess) is that this is a race condition on system shutdown.

No evidence to back that up of course  :lol:

pmachado
Champ in-the-making
Champ in-the-making
looks like after a power failure or a hard stop of a virtual machine, the /tomcat/temp/catalina.pid file keeps a pid number that becomes invalid to the next system startup. it should be solved with a init script deleting this file before tomcat starts.
Anybody knows how to fix that?