[Spacewalk-list] Client execution returned "Error whileexecuting packages action: empty transaction [[6]]" (code -1)

[Gruel Alexander]

Thanks, that brought me an idea - I used the Spacewalk 1.6 client file repository with a 1.7 server - funny thing though is,
even before I installed the updates, just for the fun of it, I rescheduled the package installation that failed about 10 times
yesterday.. and it went through without an issue. Very weird case of "fixed itself overnight.." but I will investigate further if
I can find the root cause of it 

-----Ursprüngliche Nachricht-----
Von: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] Im Auftrag von Milan Zazrivec
Gesendet: Donnerstag, 8. März 2012 16:41
An: spacewalk-list at redhat.com
Betreff: Re: [Spacewalk-list] Client execution returned "Error whileexecuting packages action: empty transaction [[6]]" (code -1)

> Hello all,
> 
> I'm new to this list (and to Spacewalk in general) and hope you might 
> be able to help me:
> 
> I recently installed Spacewalk 1.7 using the OracleXE Backend on 
> RHEL6.2, and created a local repository / channel and assigned it to a 
> test client (which registers successful, also rhel 6.2)
> 
> Spacewalk sees the necessary updates for the client, but if I schedule 
> them (or only one package for testing), as soon as I run rhn_check 
> (-v/vv/vvv) on the client, it fails with the error: Client execution 
> returned "Error while executing packages action: empty transaction 
> [[6]]" (code -1)
> 
> this is also the only line in the output of rhn_check -vvv that looks 
> bad to my unknowing eyes:
> 
> I know there has been a bug in yum-rhn-plugin which has been talked 
> about in September, but that affected 5.7 and the versions don't seem 
> to be similar at all, so I presume this is another problem with the 
> configuration on my end - I would be happy about a nudge in the right 
> direction where to troubleshoot this problem.

Is your client stock RHEL-6.2 or has it been upgraded with latest Spacewalk client packages?

I cannot really tell what the cause of your problem is, but it certainly would be worth to find out -- in the past I always used python debugger to see why would yum libraries think that there's nothing to do in the scheduled transaction.

-MZ

> Regards,
> Alexander Gruel
> 
> > Mit freundlichen Grüßen/ Kind regards Alexander Gruel
> > -------------------------------------------------------
> > IT-Systems Engineer / Abteilung IT-Operations
> > 
> > COR&FJA AG
> > Humboldtstr. 35
> > D-70771 Leinfelden-Echterdingen
> > Phone: +49 711 94958-219  I  Fax: +49 711 94958-8219
> 
> Mobile: +49 151 10863635
> 
> > E-mail: alexander.gruel at cor.fja.com I www.cor.fja.com
> > 
> > Sitz der Gesellschaft: Leinfelden-Echterdingen
> > Registergericht: Amtsgericht Stuttgart, HRB 222956
> > Geschäftsführer: Thorsten Budde, Klaus Hackbarth, Milenko Radic, 
> > Volker Weimer, Ulrich Wörner, Rolf Zielke
> > 
> > Diese E-Mail enthält vertrauliche und/ oder rechtlich geschützte 
> > Informationen. Wenn Sie nicht der richtige Adressat sind oder diese 
> > E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den 
> > Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren 
> > sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
> > 
> > This e-mail may contain confidential and/ or privileged information. 
> > If you are not the intended recipient (or have received this e-mail 
> > in
> > error) please notify the sender immediately and destroy this e-mail. 
> > Any unauthorised copying, disclosure or distribution of the material 
> > in this e-mail is strictly forbidden.

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list