[599] in Moira
what causes this?
daemon@ATHENA.MIT.EDU (Mark Rosenstein)
Tue Apr 27 10:35:56 1993
Date: Tue, 27 Apr 93 10:35:36 -0400
From: Mark Rosenstein <mar@MIT.EDU>
To: hoffmann@MIT.EDU
Cc: bug-moira@MIT.EDU
In-Reply-To: hoffmann@MIT.EDU's message of Fri, 23 Apr 93 10:38:58 -0400 <9304231438.AA07463@Paddington>
Moira generates MR_BUSY "the database is busy; try again later" errors
whenever an attempt to gain a lock on the database fails a 30 second
timeout. This happens when:
1. You are unlucky in your timing against someone registering,
as the main register operation takes almost exactly 30 seconds
2. Sporadicallly while DCM updates are running (i.e. 11:05pm - 4am)
3. Someone is doing database maintenance: there are a number
of maintenance procedures while read-lock the database. We generally
avoid doing these during business hours.
4. Something is broken.
I've seen case 4 several times recently, and haven't been able to
figure out why. The last time, all attempts to modify a user account
were failing. Restarting the moira server fixed it. My feeling is
that since updating the moira server to a maxine running Ingres 6.3,
things have been less stable. We may want to program a weekly restart
of the servers...
-Mark
