Thanks Ryan. As it happens, I rationalised everything so that the
container is now running under account tomcat6 instead of root, since
that wasn't in any case good from a security point of view. The entire
Tomcat tree belongs to tomcat6.
That hasn't made any difference.
I suspect that Magnolia is trying to create the lock file more than
once, since I delete the lock file and then restart Tomcat. Plain
Jackrabbit doesn't seem to have any problems.
Ryan Gardner wrote:
could be a permissions issue. When I've had that happen before it has
been because I ran it as root once and then tried to run it again as a
non privileged user so it couldn't delete the lock file.
Delete the deployed webapp and try to get it to deploy again.
Ryan
On Mar 10, 2008, at 6:25 PM, Charles Johnson wrote:
I'm using Debian Etch, Tomcat 6 and magnolia-bundled-webapp-3.5.4
I can't start the app since there seems to be an issue with a lock
file in the repository directory. I googled on the error string, and
although it seems to be a known issue, I couldn't see a clear
solution. How can I correct this?
Please see the server log file at
http://www.cehjohnson.btinternet.co.uk/misc/catalina.out
Charles
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------