I agree that it's a perfectly valid setup, in fact I have my Spacewalk instance registered to itself. I don't think that you error is related to being self-registered.

Look in /var/cache/rhn/repodata/ on the Spacewalk server, is there a directory / metadata files for that channel? If not, is the taskomatic service running? Are there errors in /var/log/rhn/rhn_taskomatic_daemon.log related to not being able to generate the metadata?

-Stephen

On 12/12/2014 04:47 AM, Matt Bayliss wrote:
Waldrino:

Thanks for your reply - I did investigate whether this was recommended
prior to doing it, according to a post from someone with apparently good
credentials (Red Hat Satellite engineer) its OK to do this.

https://www.redhat.com/archives/spacewalk-list/2011-October/msg00010.html

However this was a while ago and things may have changed.  If this is
not what most people are donig then I'll reconsider.


Matthew:

I hadn't, I have now but sadly it didn';t help - same error in log.  To
reply to your question, I have registered the spacewalk "master" server
directly to itself.

Regards,

Matt

    On Thu, Dec 11, 2014 at 2:53 PM, Matt Bayliss <[email protected]
    <mailto:[email protected]>> wrote:

        I am testing a Spacewalk 2.2 server with a connected proxy and
        three hosts connected via the proxy.  I can successfully update
        packages both on the proxy and hosts connected though it.

        I have added my Spacewalk 2.2 server to itselff, using its DNS
        FQDN rather than localhost, however when I try to update
        packages for it I get the following error in /var/log/up2date:

        Cannot retrieve repository metadata (repomd.xml) for repository:
        centos6-base-x86_64

        I have checked the httpd logs and can't spot a relevant error,
        what could be the problem?

        Regards,

        Matt

        Full /var/log/up2date log:

        <class 'yum.Errors.RepoError'>: Cannot retrieve repository
        metadata (repomd.xml) for repository: centos6-base-x86_64.
        Please verify its path and try again



        _______________________________________________
        Spacewalk-list mailing list
        [email protected] <mailto:[email protected]>
        https://www.redhat.com/mailman/listinfo/spacewalk-list



    _______________________________________________
    Spacewalk-list mailing list
    [email protected] <mailto:[email protected]>
    https://www.redhat.com/mailman/listinfo/spacewalk-list




_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list


_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list

Reply via email to