.lock file created when installing

[Magnolia Forums (on behalf of Robert Bowen)]

I am trying to install the Magnolia Author (and later Public) WAR files on my Tomcat in Debian Linux. This is a fresh install, there is no pre-existing magnoliaAuthor directory.

First I get a warning:

WARN RepositoryLock Existing lock file ../webapps/magnoliaAuthor/repositories/magnolia/.lock detected. Repository was not shut down properly.

Which makes no sense because this is the first time I am installing. Then comes the error:

ERROR ProviderImpl Unable to initialize repository: The repository home ../webapps/magnoliaAuthor/repositories/magnolia appears to be in use since the file named .lock is already locked by the current process.
javax.jcr.RepositoryException: The repository home ../webapps/magnoliaAuthor/repositories/magnolia appears to be in use since the file named .lock is already locked by the current process.

This error appears 20 times. My Magnolia instance doesn't come up.

What am I doing wrong? I've tried erasing the magnoliaAuthor various times. If it were a database problem (I am using Oracle) I would see the errors ... I've seen them before.

Any clues?

Thanks!

[Magnolia Forums (on behalf of Gr?gory Joseph)]

It sounds like your webapp might be started twice.
Did you check there wasn't another tomcat/magnolia process running ?
How did you deploy it ?

[Magnolia Forums (on behalf of Natalia Gorbunova)]

i know it might be a silly answer but it took me for several hours to understand what i'm doing wrong after moving from windows to linux.
the thing is only root had permissions to modify my magnolia repository directory, that's why the server(glassfish in my case) couldn't lock the repository. it simply couldn't write .lock file there.
chmod solved everything )