Cyrus file locking issues

[John C. Amodeo]

Rob & Scott,

We've run into this problem on Linux and it was determined glibc was most
likely the problem.  John Wade wrote a file locking patch for 2.0.16 that has
worked for us flawlessly for about a year now.  Its really saved us from a
situation where we had to restart the Cyrus server every night.  I promised
him lunch & and beer if he's ever in the area...

Check here: http://servercc.oakton.edu/~jwade/cyrus/readme.html

-John

Rob Siemborski wrote:

> On Thu, 20 Feb 2003, Scott Adkins wrote:
>
> > whole university, so the less we do to it, the better.  We will upgrade
> > to the latest greatest version when summer gets here, which seems to
> > get here pretty quick anyways...
>
> By this I hope you mean 2.1.12, since 2.0 is really done except
> for security updates.  For what its worth, a number of locking issues have
> been solved in the 2.1 tree.
>
> > So, has anyone else seen this problem?  If this was a recognized problem
> > and has since been fixed, which version of the Cyrus server was this
> > finally fixed in?
>
> I've never seen it before in that version, 2.0.16 was pretty stable.  It
> seems strange to me that the processes that are getting stuck will move.
> Are they trying to acquire a lock on some other file?  If so, what is it?
>
> Generally in a deadlock situation, killing the stuck process should
> resolve the problem, so this seems like more of a kernel issue to me but I
> wouldn't want to place the blame there prematurely.
>
> -Rob
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456
> Research Systems Programmer * /usr/contributed Gatekeeper