Dan Williams wrote on 10/31/2006 01:00:45 PM:
On Fri, 2006-10-27 at 02:01 -0400, Joe Todaro wrote:
>
> Hi,
>
> Has anyone ever seen a yum/depsolve-related error like this before in
> their *plague-0.5.0* build environment, and then tried *killing* the
> job that had caused it? This was problem three of three which I had
> mentioned in my previous posts. And it too had surfaced last week
> while we started stress-testing our buildsystem. Actually, the error
> you see below in itself was *not* the problem (we knew how to fix
> that) -- rather, it was the fact that we were *unable* to kill the job
> (plague-client kill 204) that was responsible for causing the error.
Fix has been committed to HEAD, attaching the patch for your
convenience.
OK, I've installed the patch, restarted the server, and submitted the
build request.
Here's the error that occurred this time:
364 (fuse-sshfs): Starting tag 'fuse-sshfs-1_6-4_ocrhel4' on target
'oc-rhel4-pre'
364 (fuse-sshfs): Requesting depsolve...
364 (fuse-sshfs): Starting depsolve for arches: ['x86_64', 'i386'].
Exception in thread PackageJob: 364/fuse-sshfs:
Traceback (most recent call last):
File "/usr/lib64/python2.3/threading.py", line 436, in __bootstrap
self.run()
File "/usr/share/plague/server/PackageJob.py", line 93, in run
self._pkg_job.process()
File "/usr/share/plague/server/PackageJob.py", line 741, in process
if func():
File "/usr/share/plague/server/PackageJob.py", line 609, in
_stage_depsolve
if self._arch_deps_solved(arch) == False:
File "/usr/share/plague/server/PackageJob.py", line 513, in
_arch_deps_solved
base.log = logger.Logger(threshold=threshold, file_object=sys.stdout)
NameError: global name 'logger' is not defined
Thanks again!
Joe
Thanks!
Dan
> ====== THE ERROR ======
> 204 (fuse-sshfs): Starting tag 'fuse-sshfs-1_6-4_ocrhel4' on target
> 'oc-rhel4-pre'
> 204 (fuse-sshfs): Requesting depsolve...
> 204 (fuse-sshfs): Starting depsolve for arches: ['x86_64', 'i386',
> 'i686'].
> Exception in thread PackageJob: 204/fuse-sshfs:
> Traceback (most recent call last):
> File "/usr/lib64/python2.3/threading.py", line 436, in __bootstrap
> self.run()
> File "/usr/share/plague/server/PackageJob.py", line 86, in run
> self._pkg_job.process()
> File "/usr/share/plague/server/PackageJob.py", line 753, in process
> if func():
> File "/usr/share/plague/server/PackageJob.py", line 618, in
> _stage_depsolve
> if self._arch_deps_solved(arch) == False:
> File "/usr/share/plague/server/PackageJob.py", line 562, in
> _arch_deps_solved
> except yum.Errors.PackageSackError, exc:
> AttributeError: 'module' object has no attribute 'PackageSackError'
>
> ====== OUR FIX ======
> We updated line 680 in the *die* method of the
> */usr/share/plague/server/PackageJob.py * module. Here's the patch:
>
>
> Again, can someone please review the fix.. We just want to make sure
> that it won't come back to *haunt* us later on / or possibly even be
> *masking* another problem. Thank you.
>
> -Joe
> --
> Fedora-buildsys-list mailing list
> Fedora-buildsys-list(a)redhat.com
>
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
[attachment "old-yum-fixes.patch" deleted by Joe
Todaro/Poughkeepsie/IBM] --
Fedora-buildsys-list mailing list
Fedora-buildsys-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list