Alfresco was working but stopped forced shutdown

[houldsworth1]

I am running Alfresco under Ubuntu Server 10.10 running inside VMWare player.  I had everything up and running and everything was fine.  I then shut down VMWare player by just clicking on the [X] - which normally doesn't cause me any problems.  The system shut down very quickly, which would imply that it didn't do it gracefully.  After that I couldn't get Alfresco to run again.

Tomcat is running because I can hit the ip:8080 and get the nice banner.  But nothing else. 

When I tried alfresco.sh start it gives me an error that Tomcat is already running, and when I try alfresco.sh stop it tells me that it can't stop Tomcat because it isn't running  :?

I'm going to uninstall and start again but am worried the same thing will happen again after I have spent time adding content (which, fortunately, I had not done yet) and then I am going to be in a bind.

If anyone has a magic bullet command that forces everything to be reset that would be awesome

Thanks!

[itsgone6]

Hi all,

I get the same problem, only my is due to power failures. I have a UPS, but it doesn't last most of the blackouts. And the Ubuntu server and my UPS don't play nice so I cant even shut down gracefully.

My Alfresco server is full of data.

I am working on Ubuntu 10.10 and am still on Alfresco community 3.4b.

I renamed the catalina.pid service to another name, which has worked before, but this time the server still returns the 404 error when browsing to server:8080/alfresco.

Any recommendations would be greatly appreciated.

Regards

M

[dc41]

I'm having the same problem with a new 3.4d install. I ran into the pdfbox error that killed the process. I replace pdfbox with a newer version, deleted the catalina.pid file and attempted to restart. mysql starts and tomcat says it's restarting, but something interrupts it or shuts it down.

service alfresco status says tomcat is not running but mysql is. A new catalina.pid file is created, but when I try "service alfresco stop" I get the "found but no matching process was found" error. Which log file do I look in to find what's interrupting the tomcat startup?