[Spacewalk-list] pushing to client, not

[m.roth2006 at rcn.com]

Hey, travellig,

>Date: Fri, 27 Mar 2009 17:55:18 +0000
>From: travellig travellig <travellig at gmail.com>  
<snip>
>Question #2:
>
>If you are debugging osad, you will want to tail to /var/log/osad instead
>
>or
>
>osad -NNNNN
>
>Schedule job in UI and watch the log.
>
>Hope it helps.
>
Wish it did. For some reason, osad wasn't running. I started it as a service, and scheduled a push of just one package. Went right away... and failed, with exactly the same error I had before in /var/log/up2date, that yum couldn't find repomd.xml

So, is there anyone out there who can tell me if I need to generate, in spacewalk 0.4, the repomd.xml's for each channel?

      mark
>On 3/27/09, m.roth2006 at rcn.com <m.roth2006 at rcn.com> wrote:
>> Question #1: if I have osad running on the client, will it try to update by
>> itself, or only if I push from the server? (I want only the latter.)
>>
>> Question #2: the last time I tried to schedule something, it failed. In the
>> up2date log on the client, I get the wretched error handling of a stack, but
>> it finally says that it could not find the repomd.xml on the server. Does
>> this need to exist in the repository on the client? If so, do I need to
>> generate it, or is that something that should have been created when I did
>> the rhnpush?
>>
>>        mark
>>
>> _______________________________________________
>> Spacewalk-list mailing list
>> Spacewalk-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>
>
>
>-- 
>travellig.
>
>_______________________________________________
>Spacewalk-list mailing list
>Spacewalk-list at redhat.com
>https://www.redhat.com/mailman/listinfo/spacewalk-list