Message "Found a stale lockfile. Trying to remove it" filling up the disk

[Alessandro Vernet]

I am hitting a case where when starting Tomcat, eXist outputs non-stop the following line to the standard output:

Found a stale lockfile. Trying to remove it:  ...\apache-tomcat-6.0.16\webapps\exist\WEB-INF\data\dbx_dir.lck
File lock last access timestamp: Jul 9, 2008 ...\apache-tomcat-6.0.16\webapps\exist\WEB-INF\data\dbx_dir.lck

Maybe this happens because the server was not shut down properly, or because the database is corrupted, but the problem I have here is that when the standard output goes to a log file, that log file grows. And grows, and grows :). In one case it grew to a several GB until the disk ran out of space.

I am using some fairly recent code in the 1.2.2 stable branch.

Is there something I can do to prevent this?

Alex

[Wolfgang Meier-2]

> I am hitting a case where when starting Tomcat, eXist outputs non-stop the
> following line to the standard output:
>
> Found a stale lockfile. Trying to remove it:
> ...\apache-tomcat-6.0.16\webapps\exist\WEB-INF\data\dbx_dir.lck
> File lock last access timestamp: Jul 9, 2008
> ...\apache-tomcat-6.0.16\webapps\exist\WEB-INF\data\dbx_dir.lck

Normally, eXist should show this message once, then remove the stale
lockfile and continue. If it fails to remove the lock, the db should
stop. I'm surprised to hear that the database works despite of this message?

Wolfgang

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

[Alessandro Vernet]

Hi Wolfgang,

Wolfgang Meier-2 wrote:

Normally, eXist should show this message once, then remove the stale
lockfile and continue. If it fails to remove the lock, the db should
stop. I'm surprised to hear that the database works despite of this message?

The database doesn't work after this message. And actually, there is no "after", as it keeps logging the same message in what appears to be an infinite loop. We got this on a test machine last week with code from the 1.2.2 stable branch from 2 weeks ago. Do you have an idea of why this could happen?

Alex

[Wolfgang Meier-2]

Hi Alessandro,

> The database doesn't work after this message. And actually, there is no
> "after", as it keeps logging the same message in what appears to be an
> infinite loop.

Ok, it looks like the db could indeed enter into an infinite loop if the
stale lock file could not be properly deleted. eXist would re-try forever.

I fixed this in trunk and the eXist-stable-1.2 branch:

http://exist.svn.sourceforge.net/exist/?rev=7989&view=rev

Wolfgang

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

[Alessandro Vernet]

Wolfgang,

Wolfgang Meier-2 wrote:

I fixed this in trunk and the eXist-stable-1.2 branch:

http://exist.svn.sourceforge.net/exist/?rev=7989&view=rev

Excellent! Thank you for this.

Alex