Mock/yum race
Ralf Corsepius
rc040203 at freenet.de
Wed Jan 10 12:12:30 UTC 2007
Hi,
I am facing a bizarre and pretty severe problem with mock:
On a remote (FC5) machine, mock-yum started to consume 100% of cpu-time,
seemingly during a chroot'ed run of yum[1].
Peculiarly disturbing about this: This is job is running as "root", with
me not having root privileges on the affected machine.
# ps aux | grep mock
root 28303 98.0 1.0 20280 10756 ? R 02:32
208:15 /usr/bin/python /usr/libexec/mock-yum
--installroot /var/lib/mock/fedora-5-i386-local/root resolvedep m4 emacs
gawk perl
I am inclined to blame this to be a side-effect of one of these infamous
yum/rpm/kernel deadlocks/races and/or yum/rpm arkward handling of
interrupts [1][2].
Ralf
[1] yum's behavior on "^C" and rpm being problematic wrt. rpmdb locking.
[2] This had been a lengthy remote over-night build job, with me
initially having been ssh'ed to the remote machine and the connection
having gone down some time during the run.
More information about the fedora-devel-list
mailing list