[Spacewalk-list] Issues upgrading to next point release

[Ree, Jan-Albert van]

>

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 11:19 AM

> > 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.
>
> Good investigation. Not sure what version you Spacewalk server is but
> we bumped up the taskomatic memory for 1.7.

I am running 1.7 now, upgraded from an initial 1.6 install. The java memory was set at 256/512 which I bumped up to 512/1024

> If the taskomatic was failing and not regenerating the repo data,
> I don't really see how the re-registered machine could have gotten the
> content though. ;-)

Solved that too... with a new sl-release I got a new yum repository file, so I wasn't getting the packages from my Spacewalk server but from an external SL repository, sorry for the confusion. And the re-registering was needed since the /etc/redhat-release contained a different version compared to the old systemid file which was generated upon initial registration.
--
Jan-Albert van Ree