(Upd:) Re: PATCH: depsolve-kill fix for plague-0.5.0
by Joe Todaro
Joe Todaro/Poughkeepsie/IBM wrote on 11/01/2006 01:33:47 PM:
> 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
I got it working tho in the meantime by removing the code 'logger.' from
the beginning of the command on the next line:
base.log = logger.Logger(threshold=threshold, file_object=sys.stdout)
Here's the new error message, by the way, successfully reporting a
package dependency we need t fix:
366 (fuse-sshfs): Requesting depsolve...
366 (fuse-sshfs): Starting depsolve for arches: ['x86_64', 'i386'].
Exception in thread PackageJob: 366/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 743, in process
if func():
File "/usr/share/plague/server/PackageJob.py", line 610, in
_stage_depsolve
if self._arch_deps_solved(arch) == False:
File "/usr/share/plague/server/PackageJob.py", line 548, in
_arch_deps_solved
pkg = base.returnPackageByDep(dep)
File "__init__.py", line 1342, in returnPackageByDep
YumBaseError: No Package found for fuse-devel
Thanks so much!!
Joe
>
> 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
17 years, 6 months
PATCH: depsolve-kill fix for plague-0.5.0
by Joe Todaro
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.
====== 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
17 years, 6 months
plague-server issues (4.4.1)
by Evan Klitzke
Hello everyone,
I have been trying to get plague working. I have installed the plague
programs that come with Fedora Core 6 (4.4.1). When running
plague-server, I get the following error:
[evan@thinkpad ~]$ plague-server
Using database engine sqlite.
Builders:
------------------------------------------------------------------------------------------
http://127.0.0.1:8888 i386 i486 i586 i686 athlon
noarch alive
Traceback (most recent call last):
File "/usr/bin/plague-server", line 198, in ?
main()
File "/usr/bin/plague-server", line 152, in main
bm_server.register_instance(ui)
AttributeError: 'NoneType' object has no attribute 'register_instance'
As a consequence, plague-client cannot connect to the server --
connection attempts always return '(111, 'Connection refused')'. Does
anyone know if this is a known issue that has been fixed in a newer
release? Alternatively, is there a way to get lots of
debugging/logging output? I poked around the code a bit, but I'm not
really sure how I would go about debugging it.
I have also tried the CVS snapshot, but I had problems importing the
yum logger module, presumably because this is a yum feature that isn't
in FC6. I wouldn't mind using the CVS checkout if it fixes the
aforementioned problem, but I'd rather not have to upgrade a bunch of
other programs to bleeding edge versions to get plague working.
-- Evan Klitzke
17 years, 6 months