Hi , I hope anybody came across this issue everyday our server get this error and i have remove the pid then its start working again. but it is annoying to restart server everyday. Please would anybody tell the cause of it. we are normally use goodsync to scynrozie the documents with Alfresco
Generally this means that there has been an incorrect shutdown and/or restart of a component (usually tomcat). I have only experienced this on very odd occasions when Tomcat has aborted.
What should happen is that the tomcat startup script creates a file with it PID in it and when you shut tomcat down it kills the process with that PID and deletes the file. It looks like what has happened here is that tomcat is being killed off but it is not being killed off using the scripts (alfresco.sh which in turn runs the tomcat ctl.sh scripts) so when you try and restart it it cannot find the PID in the file to kill.
Make sure that you always use alfresco.sh start / stop / restart and you should not experience this problem.
Is Alfresco up and available each morning (i.e. can you log in via a browser)?
Hi Bob, first of all thank you for the reply, actually normally suddenly alfresco goes down and we have remove the PID and then normal we restart alfresco with .alfresco.sh stop , so seems issue is somewhere , log is also full of messages
Hi , thank you for the reply but would you tell how i can find seems log is full and it is difficult to find what the shutdown , what could be the possible indicator in log
Your problem will be outside of alfresco. But the alfresco log may help give a clue like the last time that alfresco was last up and running.
The time may give you a clue if for example it shuts down at around 1 am in the morning before a backup runs. Or the machine that is running alfresco may be powered off each night. (I once worked with a system that was unplugged by the cleaners every night to run their vacuum cleaners. And I heard just last week of an irate customer complaining about nightly uploads not being completed when their corporate energy saving policy was to turn off all desktop PCs before going home)
It could also be that annoying linux feature that randomly shuts down the biggest, unused process if the machine is under stress.
