[Spacewalk-list] RESOLVED:RE: Clients not seeing updates after spacewalk-repo-sync

[VERGEER, BOB H.]

Thanks Michael.  Taskomatic was running but hung. I restarted it a few times before I realized that PostgresDB was out of space. Resolving that, restarting taskomatic and cleaning up the cache on the clients resolved the issue.

Thanks again,
--
Bob


-----Original Message-----
From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Michael Mraka
Sent: Tuesday, December 04, 2012 3:45 AM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Clients not seeing updates after spacewalk-repo-sync

VERGEER, BOB H. wrote:
% Environment:
% 
% -          Spacewalk server and client 1.7.
% 
% -          Host and server OS CentOS 6.3
% 
% Issue:   I ran an repo-sync on the spacewalk server to update the
% CentOS6 primary and update channels. They now show 6686 & 949 packages
% respectively.  However, registered clients are not seeing the updates.
% I have cleaned repo and metadata and removed /var/cache/yum/* on the
% clients. When I issue a yum list updates, the caches are rebuilt but
% only with the original number of available packages (6346 & 715).
% The UI shows updates available for the client but the client itself
% does not see any. Scheduling the updates through the UI fails with
% "nothing to update".  I feel that I am missing some step  on the
% server side but I can't determine what it is.  Any thoughts?

This is most likely caused by  taskomatic not running.

You may check 'Last Repo Build' and 'Repo Cache Status' values on the
channel detail page.

And also timestamps (and content) of files in
/var/cache/rhn/repodata/<channel_label>.


Regards,

--
Michael Mráka
Satellite Engineering, Red Hat

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

Confidentiality notice: 
This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer.