[rhn-users] Critical system on RHN due to completed errataremaining at status "None" rather than "Completed"?

[Homard-Roy Wes]

Hi Daryl and thanks for your reply!

-----Original Message-----
From: rhn-users-bounces at redhat.com [mailto:rhn-users-bounces at redhat.com]
On Behalf Of Daryl Herzmann
Sent: 25 February 2008 14:46
To: Discussions about Red Hat Network (rhn.redhat.com)
Subject: Re: [rhn-users] Critical system on RHN due to completed
errataremaining at status "None" rather than "Completed"?

Hi Wes,

On Mon, 25 Feb 2008, Homard-Roy Wes wrote:

>> I am trying to set up a new RHEL 5 system but according to RHN, my 
>> system is a critical system and is out of date.

>Did you install RHEL 5 and then register it to RHN just now?  Or has it

>been registered for a while?  Do you have auto-apply-errata checked on
the 
>RHN website or yum-updatesd configured locally?

I have just installed and registered RHEL 5 within the last week or two.
I don't have auto-apply-errata checked on the RHN website as I had read
that this wasn't a good idea...

After reading your reply I have found yum-updatesd.conf which I haven't
previously touched. It is currently:

[main]
# how often to check for new updates (in seconds)
run_interval = 3600
# how often to allow checking on request (in seconds)
updaterefresh = 600

# how to send notifications (valid: dbus, email, syslog)
emit_via = dbus

# automatically install updates
do_update = no
# automatically download updates
do_download = no
# automatically download deps of updates
do_download_deps = no

Should I change some of those "no"'s to "yes"'s and if so do I need to
restart anything after editing it?


>> If I click on "Critical Updates Available (update now)", I am taken
to 
>> the list of relevant errata most of which have a status of "None" 
>> although sometimes a handful have a status of "Pending" or "Failed"
if I 
>> have recently scheduled an update. However the errata with the "None"

>> status are all ones which I have previously scheduled and which 
>> completed successfully according to the details tab of their
individual 
>> errata update pages. Should these not be at a status of "Completed"
now 
>> and therefore not still appearing in the list of errata which I still

>> need to apply?

>Unfortunately, you can't rely on RHN to automatically schedule errata
for 
>application.  You need to either setup yum-updatesd to automatically
apply 
>new errata 

So do_update = yes?

Is my problem that although I schedule the errata to be applied at the
RHN end (and they appear to be scheduled and completed), they then get
sent to my machine but are not then actually being installed at my end
so when a check is next made with RHN it doesn't think I've got them
yet?

>or run 'yum -y update' from cron.  If you are looking to get 
>your machine currently updated, you can run

>yum -y update

>from the command line.  That should get your system in an updated
state.

Thanks very much - I'll try that asap!

>HTH,
>   daryl

_______________________________________________
rhn-users mailing list
rhn-users at redhat.com
https://www.redhat.com/mailman/listinfo/rhn-users