The “metadata ….” Error indicates that your yum cache (provided by the 
Spacewalk server) is out of with what is actually available through the 
Spacewalk package database.  This can be because taskomatic isn’t running or 
there’s a problem somewhere.  Check your logs under /var/log/rhn/ for any 
issues with taskomatic or any other components.

However, I’ve run into this before and I do the following to get around it 
(NOTE: your paths will probably be different than mine):

# Blow away all cached metadata
rm -fr /data/pkg/cache/rhn/repodata/

# restart spacewalk so empty repodata cache directory is recreated.
spacewalk-service stop
spacewalk-service start

# If not already, cache credentials for spacecmd (This assumes you have 
configured ~/.spacecmd/config previously)
spacecmd softwarechannel_list

# Regenerate repo data for all channels
for i in `spacecmd softwarechannel_list`; do spacecmd 
softwarechannel_regenerateyumcache $i; done

# Waited a few minutes for data to regenerate

Once that’s done and the metadata caches are updated (you’ll see updated 
directories under the cache dir and you should see info in the taskomatic 
logs), go to each registered spacewalk client and run

yum clean all

If this doesn’t work, I would have to say that you’ve got something else wrong 
somewhere else.

Good luck.

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Daryl Rose
Sent: Wednesday, December 14, 2016 5:58 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] RHEL 6.x repository not syncing from parentchannel


Hello everyone,



I have not received any replies from my previous posting, so I thought that I 
would post an update hoping someone would see it and reply.



This error seems to go deeper than just syncing from Red Hat.  Server that are 
currently registered to the Spacewalk server are not able to access the RHEL 
repository on SW.  If issuing the "yum update" command, we receive the error:


Error: failed to retrieve repodata/primary.xml.gz from rhel-6-server-rpms
error was [Errno -1] Metadata file does not match checksum


If I issue the "yum repolist" command, I only see "0" for packages.



So, this issue is larger that what I initially thought. Anyone have any 
thoughts or idea's?



Daryl

________________________________
From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
<spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of Daryl Rose <darylr...@outlook.com<mailto:darylr...@outlook.com>>
Sent: Friday, December 9, 2016 2:56 PM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] RHEL 6.x repository not syncing from parentchannel


So,  I resurrected the old server from the grave and copied the contents of 
"/var/cach/rhn/reposync/rhel-6-server-rpms" to 
"/var/cach/rhn/reposync/content_dist_rhel_server_6_$releasever_$basearch_os" 
and ran a sync.  The sync worked.



The sync worked, but it caused a new error.  A team member registered a Red Hat 
server just after I made these changes.  The server registered, but  with the 
following error:



Bad id for repo: logstash 5.x, byte =   8



I'm guessing that something within the data that I copied over does not align 
with the repository on SW?



Another thing that I noticed is that the directory structure in the old 
reposync directory is different than the new server.  For example:



OLD:

/var/cache/rhn/reposync/centos-7-extra

/centos-7-server-rpms

/centos-7-updae

/centos_7_channel

/centos_7_plus


NEW:
/var/cache/rhn/reposync/centos_7_centosplus_x86_64_
/centos_7_extras_x86_64_
/centos_7_os_x86_64_
/centos_7_updates_x86_64_

Is that a SW v2.3 vs. v2.6 change?

Thanks

Daryl

________________________________
From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
<spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of Daryl Rose <darylr...@outlook.com<mailto:darylr...@outlook.com>>
Sent: Thursday, December 8, 2016 10:32 AM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] RHEL 6.x repository not syncing from parentchannel


More questions:



When I run "spacewalk-repo-sync --channel=rhel-6-server-rpms",  I get the error:



ERROR: Cannot retrieve repository metadata (repomd.xml) for repository: 
content_dist_rhel_server_6_$releasever_$basearch_os. Please verify its path and 
try again

What creates the content in 
"/var/cache/rhn/reposync/content_dist_rhel_server_6_$releasever_$basearch_os"?

All of the other channels that I created all have "cachecookie, packages, 
primary.xml.gz, primary.xml.gz.sqlite, repomd.xml and updateinfo.xml.gz".

There must be a process that creates this content, but what, I'm not sure.  How 
can I manually create this content?

Thanks

Daryl

________________________________
From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
<spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of Daryl Rose <darylr...@outlook.com<mailto:darylr...@outlook.com>>
Sent: Thursday, December 8, 2016 9:26 AM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] RHEL 6.x repository not syncing from parentchannel


Quick update.



Poking around on Red Hat I found a doc that suggested that I look at the  name 
in /etc/sysconfig/network and ensure that the hostname is FQDN and then run 
"spacewalk-hostname-rename".   Host name was not FQDN, so I renamed it, but 
because I use a signed cert, will running spacewalk-hostname-rename cause a 
problem with that cert?



Thanks



Daryl

________________________________
From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
<spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of Daryl Rose <darylr...@outlook.com<mailto:darylr...@outlook.com>>
Sent: Thursday, December 8, 2016 8:55 AM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] RHEL 6.x repository not syncing from parentchannel


Robert,



Yes, the server is registered and has an active subscription with Red Hat.  As 
a matter of fact, I just now re-registered to make sure that all is good.   I 
can see from the command line subscription manager that the server is 
subscribed, and I confirmed that it is entitled.



I use a "signed" cert so I'm wondering if the signed cert has something to do 
with this?  However, I found a troubleshooting document on Red Hat that 
verifies that I am entitled and using the certificate provided by Red Hat to 
communicate back to them.

Thank you

Daryl
________________________________
From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
<spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of Robert Paschedag 
<robert.pasche...@web.de<mailto:robert.pasche...@web.de>>
Sent: Wednesday, December 7, 2016 11:48 PM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] RHEL 6.x repository not syncing from parentchannel

I think you should check your entitlements. But I also don't know, how you 
could "manually" connect to the repo (with username/password or token inline in 
URL).

Is your server listed as entitled within your RedHat account?
________________________________
Von: Daryl Rose<mailto:darylr...@outlook.com>
Gesendet: ‎06.‎12.‎2016 17:26
An: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Betreff: Re: [Spacewalk-list] RHEL 6.x repository not syncing from parentchannel

I decided to try the sync from the command line.  This time I received an error:



ERROR: Cannot retrieve repository metadata (repomd.xml) for repository: 
content_dist_rhel_server_6_6Server_x86_64_os_. Please verify its path and try 
again

The path came out of the redhat.repo file that came from Red Hat when I 
registered the server.  Its the same path that was used on the previous server.

Any suggestions?

Thank you.

Daryl

________________________________
From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
<spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of Daryl Rose <darylr...@outlook.com<mailto:darylr...@outlook.com>>
Sent: Monday, December 5, 2016 3:00 PM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: [Spacewalk-list] RHEL 6.x repository not syncing from parent channel


I just realized that the last Red Hat errata for RHEL 6.x is from August.  I 
looked at the sync logs and it doesn't appear that anything is syncing at all 
from the RHEL channel.



I just recently migrated to a physical server.  I successfully registered the 
server and attached an entitlement to the server.  If I run "yum update" on the 
server, it lists latest updates from the RHEL channel.



This is what I see in the reposync log:


2016/12/05 14:49:42 -05:00 Command: ['/usr/bin/spacewalk-repo-sync', 
'--channel', 'rhel-6-server-rpms', '--type', 'yum']
2016/12/05 14:49:42 -05:00 Sync of channel started.
2016/12/05 14:49:42 -05:00 Repo URL: https:<rhel 6 rpm channel>
2016/12/05 14:49:42 -05:00 Sync of channel completed in 0:00:00.


If I haven't received any syncs since August, then this broke long before I 
migrated to the physical server.



Any thoughts?



Daryl


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

Reply via email to