[Spacewalk-list] Issues upgrading to next point release

Ree, Jan-Albert van J.A.v.Ree at marin.nl
Fri Aug 3 09:06:26 UTC 2012


>

Jan-Albert van Ree
Linux System Administrator
MSuG MARIN Support Group
E mailto:J.A.v.Ree at marin.nl
T +31 317 49 35 48

MARIN
2, Haagsteeg, P.O. Box 28, 6700 AA Wageningen, The Netherlands
T +31 317 49 39 11, F , I www.marin.nl

-----Original Message-----
> From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-
> bounces at redhat.com] On Behalf Of Jan Pazdziora
> Sent: Friday, August 03, 2012 10:30 AM
>
> On Fri, Aug 03, 2012 at 07:59:46AM +0000, Ree, Jan-Albert van wrote:
> > However now that updates tagged with 6.3 are coming out my Spacewalk
> server shows these updates as being available, but I am unable to apply
> them to my clients. If I do a 'yum clean all ; yum upgrade' I get '0
> updates available'
> >
>
> What happens if you schedule the update from Spacewalk's WebUI and
> pick it up with rhn_check -vv -- will it get installed?

It tries but can't fetch the updates and gives a

D: Sending back response ((6,) 'Error while executing package action: empty transaction', {})

> Spacewalk generates the repo data for the channels after any change
> in the channel takes place, via an asynchronous job. The Last Repo
> Build field in the channel page on the WebUI shows the timestamp of
> the last repo generation, so you might want to check if it was updated
> alright. I assume it was, otherwise your newly registered machine
> wouldn't get them either, but we should know for sure.

Those dates are indeed very old... last build date is 10-7-2012 , last modified is 3-8-2012
Looking at the task schedule, it shows "SKIPPED" since 10-7-2012
So that looks like my main problem indeed... looking at the taskomatic daemon log I see Java heap space OutOfMemory errors...
I've increased Xms and Xmx in /usr/share/rhn/config-defaults/rhn_taskomatic_daemon.conf and now it works again.

I have little over 10K packages in the channel that fails, which seems reasonable. Should I split things up further?

> I have no idea what the sl-release package contains or overwrites,
> so I won't speculate on this one. Does the package own the
> /etc/sysconfig/rhn/systemid file? What does rpm -qf
> /etc/sysconfig/rhn/systemid?

Systemid isn't owned by any package according to RPM

> Aren't some proxies between the clients and the Spacewalk server that
> could be source of the problem?

No, the machines are on the same VLAN, with nothing but a switch between them.

Thanks for the help so far.
Regards,
--
Jan-Albert van Ree




More information about the Spacewalk-list mailing list