Red Hat Bugzilla – Bug 240348
Deadlocks on errata import.
Last modified: 2014-03-31 19:48:09 EDT
In stage, three users tried to import errata at close to the same time. One of
them failed due to an oracle deadlock. The logs don't say much more than that,
so it's possible the cause was all three being done at a similar time. Still, we
should look into this, as this was supposedly fixed by the kickstart index.
I'm one of them :-) I tried to push procmail errata - 2007:9165-2.
Today I pushed 2 erratas simultaniously, 2007:9208 & 2007:9165 both from
errata.devel, without any issues.
Scratch the second paragraph, my fingers are writing something totally different
from what my brain wants.
Today pushing two erratas at once from errata.devel RHBA-2007:9208 - rusers bug
fix update and RHBA-2007:9154 - mgetty bug fix update (1 second after the first)
I got the deadlock error after waiting for a few minutes. Seems easily reproduceble.
Done Pushing Files
Updating issue and update dates to 2007-05-17.
Pushing to RHN (this could take a while)....
ORA-00060: deadlock detected while waiting for resource
Error Class Code: 23
Error Class Info: Could not update database entry.
pushing to RHN (qa):
Server was http://scripts.vip.stage.redhat.com/BUGZILLA/
Error Push to Red Hat Network failed 1.
Please contact email@example.com if you believe this to be in error.
Grant, please track this with the other db stuff