[Spacewalk-list] Updating a system

[Waldirio Manhães Pinheiro]

Humm

The sync of your channel had concluded ??

If not, this is the prob.

You can see in your server in /var/log/rhn/* files.

B'regards
Em 06/11/2014 19:55, "Daryl Rose" <rosede12 at gmail.com> escreveu:

> Waldirio,
>
> Yes, the client is registered with SW.  Here is the output from yum
> repolist:
>
> [root at daryl-centos65-demo01 ~]# yum repolist
> Loaded plugins: fastestmirror, rhnplugin, security
> This system is receiving updates from RHN Classic or Red Hat Satellite.
> Loading mirror speeds from cached hostfile
> epel/metalink
>                                                             |  15 kB
> 00:00
>  * base: mirror.es.its.nyu.edu
>  * epel: mirror.steadfast.net
>  * extras: mirror.oss.ou.edu
>  * updates: centos.host-engine.com
> repo id                                                        repo name
>
> status
> base                                                           CentOS-6 -
> Base
>   6518
> centos-65-base-x86_64                                          CentOS 6.5
> Base - x86_64
>     0
> epel                                                           Extra
> Packages for Enterprise Linux 6 - x86_64
>           0
> extras                                                         CentOS-6 -
> Extras
>      0
> spacewalk-client                                               Spacewalk
> Client Tools
>       0
> updates                                                        CentOS-6 -
> Updates
>     0
> repolist: 6518
>
>
> I had looked in /var/log/messages for errors, but nothing.  I did not see
> the /var/log/up2date, but now that you point me in that direction, I found
> something.
>
> <class 'yum.Errors.RepoError'>: Cannot retrieve repository metadata
> (repomd.xml) for repository: centos-65-base-x86_64. Please verify its path
> and try again
>
>
> Okay, this gives me something to go on.  What path is it looking for?  The
> machine is registered.  I can see it in SW and as demonstrated in yum
> repolist, the machine is registered with the correct channel.
>
> Thanks
>
> Daryl
>
>
>
>
> On Thu, Nov 6, 2014 at 3:21 PM, Waldirio Manhães Pinheiro <
> waldirio at gmail.com> wrote:
> >
> > Daryl
> >
> > Answers bellow
> >
> > ______________
> > Atenciosamente
> > Waldirio
> > msn: waldirio at gmail.com
> > Skype: waldirio
> > Site: www.waldirio.com.br
> > Blog: blog.waldirio.com.br
> > LinkedIn: http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646
> > PGP: www.waldirio.com.br/public.html
> >
> > On Thu, Nov 6, 2014 at 6:55 PM, Daryl Rose <rosede12 at gmail.com> wrote:
> >>
> >> Okay, now that I have a system setup and registered, I'm trying to do
> an update.
> >>
> >> I picked one package and selected it to update.  The package is queued,
> but the update has not run.
> >>
> >> In a past life, I've used Satellite Server to update Red Hat servers.
> I used the rhn_check command to force the update.  However, when I tried
> rhn_check on my test server I received Python errors:
> >>
> >> This error came from the System History Event record:
> >>
> >>> Client execution returned "Fatal error in Python code occurred [[6]]"
> (code -1)
> >>
> >>
> >> Three questions.
> >>
> >> 1. Any idea what this error is, and how do I correct it?
> >
> >
> > Are your machine really registered in SW !?, when you execute yum
> repolist, what appear as result !?
> >
> >>
> >> 2. Where are the log files located so I can review any errors?
> >
> >
> > In the /var/log/up2date or /var/log/messages, although I recommend
> execute the command rhn_check -vv
> >
> >>
> >> 3. How log does a package normally get queued before it's pushed out to
> the client?
> >
> >
> > You can use spacecmd or spacewalk-errata, I really need check in the
> command (don't remember right now)
> >
> >>
> >>
> >> In reference to the last question. I set the schedule to run at the
> nearest 1/2 hour, but the package was never pushed out to the client.
> >
> >
> > Take a look in this post - http://blog.waldirio.com.br/?p=738
> >>
> >>
> >> Thanks.
> >>
> >> Daryl
> >>
> >
> > Take Care
> >>
> >>
> >>
> >> _______________________________________________
> >> Spacewalk-list mailing list
> >> Spacewalk-list at redhat.com
> >> https://www.redhat.com/mailman/listinfo/spacewalk-list
> >
> >
> >
> > _______________________________________________
> > Spacewalk-list mailing list
> > Spacewalk-list at redhat.com
> > https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20141106/83cc29f9/attachment.htm>