From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020916
Description of problem:
Using up2date my system is consistent: when a new errata is
announced, up2date finds it and applies it. But in the
errata view of the Red Hat Network website for this machine
I am prompted to apply errata updates which I know have already
been applied via update (verified using rpm -q).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Log into red hat network as maspotts
2. Click on Errata or Packages
3. Observe errata RPMS and compare with system via 'rpm -q'
Actual Results: eg. I have: python-1.5.2-43.71 installed, but I see (under
python-1.5.2-43.71.i386.rpm is a critical up2date that has not yet
been applied. If I look in the 'List/Remove Packages' screen then
it tells me that I have python-1.5.2-42.71 installed.
Expected Results: The database should accurately reflect my system, since up2date
is working properly and I have run it, and rhn_check today, and
regularly in the recent past.
Try running 'up2date -p' from the command line and see if that helps.
up2date can function even if RHN does not have your package profile. The
website, on the other hand, requires a system's package profile to be useful.
Ran 'update -p', but got usual message about 'demo service disabled'.
Problem persists, although last check-in date now matches the 'update -p'
time, but I don't know whether the disabled demo service prevented the
synchronisation from taking place.
If the message was along the lines of:
Demo service currently disabled due to high load. If you would like
to see Red Hat's policies on Demo service, or find out how you can
purchase a subscription service and receive priority download access,
please go to http://rhn.redhat.com/preview/index.pxt
then try again when we're not throttling our servers. Currently, the machines
look pretty open, so I'd try again soon.
Servers still throttled this morning; I'll keep trying, on and off...
Any luck yet?
Still getting demo service disable (roughly 10 attempts since yesterday).
I'm still trying sporadically...
Still no luck getting past the "demo service disabled" stage; actually
I'm finding rhn almost unusable these days using 'demo' service. Fair
enough I guess, although it might be less depressing to simple cancel
all non-paid service so I wouldn't be tempted to keep trying!
Got in, finally! After running 'update -p' the database is in sync
again. Thanks for the advice. Maybe update should sync the database
whenever it checks in to retrieve errata, to avoid this situation?
Works, closing. The problem has been fixed in an upcoming errata, as well as the