Up2date problem

[Scott Carper]

After I successfully run up2date, the next time I check for updates, it says
there are  updates available (and these are not the same as the previous
update); but when I launch up2date, it says "Your system is fully updated.
No new packages are needed."  I have to reboot the system before the
available updates will be downloaded and installed by up2date.

Any ideas?  Any help would be appreciated.

Thanks.
Scott

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.8.6 - Release Date: 3/30/2005

[Kam Leo]

On Mar 31, 2005 7:00 PM, Scott Carper <scarper68(a)comcast.net&gt; wrote:
>  After I successfully run up2date, the next time I check for updates,
> it says
>  there are  updates available (and these are not the same as the previous
>  update); but when I launch up2date, it says "Your system is fully updated.
>  No new packages are needed."  I have to reboot the system before the
>  available updates will be downloaded and installed by up2date.
>  
>  Any ideas?  Any help would be appreciated.
>  
>  Thanks.
>  Scott
>   
You encountered what I consider one of the biggest annoyances with
up2date.  You get notification about available updates, run up2date,
and the repository and/or mirror from mirrorlist has not gotten
resynced..

So here are some possible actions that you can take:

1. Do not react immediately upon receiving an update notification.
Wait several hours before trying so that the mirrors can sync up.
2. Disable the update agent.  Perform updates manually or update via a cron job.
3. File either an RFE or a bug report in Bugzzilla,
https://bugzilla.redhat.com/bugzilla/ .

[Erich Carlson]

I've run into those same various conditions on running up2date at times.
By the next day it is usually fine.

What I haven't been able to get around, very often, or perhaps just get
lucky at times. Is that after a package is downloaded, before it will
install, I get a web server 404 error thrown at me telling me the file,
isn't available, which of course it is, because I just downloaded it. So
I run the up2date again, select the package, it says the package has
already been downloaded and installs it. It is a pain in the ass, but at
least it works.

Erich

[William Hooper]

Kam Leo said:

>  You encountered what I consider one of the biggest annoyances with
>  up2date.  You get notification about available updates, run up2date, and
>  the repository and/or mirror from mirrorlist has not gotten resynced..
>
>  So here are some possible actions that you can take:
>
>
>  1. Do not react immediately upon receiving an update notification.
>  Wait several hours before trying so that the mirrors can sync up.
>  2. Disable the update agent.  Perform updates manually or update via a
>  cron job.
>  3. File either an RFE or a bug report in Bugzzilla,
>  https://bugzilla.redhat.com/bugzilla/ . 
4. Configure up2date to use a fast mirror for you rather than relying on
the default mirror list.  If up2date and rhn-applet are looking at the
same mirror you won't have any problem.

-- 
William Hooper

[jim lawrence]

On Apr 1, 2005 10:20 AM, William Hooper <whooperhsd3(a)earthlink.net&gt; wrote:
>  
>  Kam Leo said:
>  
>  > You encountered what I consider one of the biggest annoyances with
>  > up2date.  You get notification about available updates, run up2date, and
>  > the repository and/or mirror from mirrorlist has not gotten resynced..
>  >
>  > So here are some possible actions that you can take:
>  >
>  >
>  > 1. Do not react immediately upon receiving an update notification.
>  > Wait several hours before trying so that the mirrors can sync up.
>  > 2. Disable the update agent.  Perform updates manually or update via a
>  > cron job.
>  > 3. File either an RFE or a bug report in Bugzzilla,
>  > https://bugzilla.redhat.com/bugzilla/ .
>  
>  4. Configure up2date to use a fast mirror for you rather than relying on
>  the default mirror list.  If up2date and rhn-applet are looking at the
>  same mirror you won't have any problem.
>  
>  --
>  William Hooper
>  
>  --
>  fedora-list mailing list
>  fedora-list(a)redhat.com
>  To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
>   
Or change the RHn up2daet applet to reflect yum 
First grab gyum 
http://fedoranews.org/tchung/gyum/2.0/fc3/2.0-5/
then grab the applet 
http://fedoranews.org/tchung/gyum/2.0/gyum-applet/
right click the RHN applet and exit it 
then go to system tools and choose gyum-update alert icon 


-- 

Jim Lawrence
Registered Linux User: #376813
********************************************************
When I'm feeling down, I like to whistle. 
It makes the neighbor's dog run to the end of his chain and gag himself.
************************************

[Paul Howarth]

jim lawrence wrote:
>  On Apr 1, 2005 10:20 AM, William Hooper
> <whooperhsd3(a)earthlink.net&gt; wrote:
>  
> >Kam Leo said:
> >
> >
> >>You encountered what I consider one of the biggest annoyances with
> >>up2date.  You get notification about available updates, run up2date, and
> >>the repository and/or mirror from mirrorlist has not gotten resynced..
> >>
> >>So here are some possible actions that you can take:
> >>
> >>
> >>1. Do not react immediately upon receiving an update notification.
> >>Wait several hours before trying so that the mirrors can sync up.
> >>2. Disable the update agent.  Perform updates manually or update via a
> >>cron job.
> >>3. File either an RFE or a bug report in Bugzzilla,
> >>https://bugzilla.redhat.com/bugzilla/ .
> >
> >4. Configure up2date to use a fast mirror for you rather than relying on
> >the default mirror list.  If up2date and rhn-applet are looking at the
> >same mirror you won't have any problem.
> >
> >--
> >William Hooper
>  
>  Or change the RHn up2daet applet to reflect yum 
>  First grab gyum 
>  http://fedoranews.org/tchung/gyum/2.0/fc3/2.0-5/
>  then grab the applet 
>  http://fedoranews.org/tchung/gyum/2.0/gyum-applet/
>  right click the RHN applet and exit it 
>  then go to system tools and choose gyum-update alert icon  
Unfortunately gyum doesn't work with repos defined in /etc/yum.repos.d 
(they have to be merged in with yum.conf) and so this isn't a very good 
solution for FC3.

Making yum, up2date, and rhn-applet all point to the same repo to avoid 
inconsistencies is a bit more awkward to set up, but it's a "cleaner" 
solution.

Paul.

[William Hooper]

jim lawrence said:
[snip]
>  Or change the RHn up2daet applet to reflect yum
>  First grab gyum
>  http://fedoranews.org/tchung/gyum/2.0/fc3/2.0-5/
>  then grab the applet http://fedoranews.org/tchung/gyum/2.0/gyum-applet/
>  right click the RHN applet and exit it then go to system tools and choose
>  gyum-update alert icon 
Not sure how that would help...

If gyum and gyum-applet use the mirror list, you will have the same
problem.  On any given run gyum-applet and gyum may use a different
mirror.

If gyum and gyum-applet can't use mirror lists, this is just a long way
around setting the updater to point to a single mirror instead of a mirror
list.

-- 
William Hooper

[Kam Leo]

On Apr 1, 2005 7:20 AM, William Hooper <whooperhsd3(a)earthlink.net&gt; wrote:
>  
>  Kam Leo said:
>  
>  > You encountered what I consider one of the biggest annoyances with
>  > up2date.  You get notification about available updates, run up2date, and
>  > the repository and/or mirror from mirrorlist has not gotten resynced..
>  >
>  > So here are some possible actions that you can take:
>  >
>  >
>  > 1. Do not react immediately upon receiving an update notification.
>  > Wait several hours before trying so that the mirrors can sync up.
>  > 2. Disable the update agent.  Perform updates manually or update via a
>  > cron job.
>  > 3. File either an RFE or a bug report in Bugzzilla,
>  > https://bugzilla.redhat.com/bugzilla/ .
>  
>  4. Configure up2date to use a fast mirror for you rather than relying on
>  the default mirror list.  If up2date and rhn-applet are looking at the
>  same mirror you won't have any problem.
>   
Tried both the mirrorlist and fast local mirrors (e.g.
ftp://mirrors.kernel.org, ftp://mirror.stanford.edu, and
ftp://limestone.uoregon.edu among others) and continue to encounter
this problem.

What mirror are you using to get such good results?

>  --
>  William Hooper
>

[William Hooper]

Kam Leo said:
>  On Apr 1, 2005 7:20 AM, William Hooper
> <whooperhsd3(a)earthlink.net&gt; wrote:
>
> >
> > Kam Leo said:
> >
> >
> >> You encountered what I consider one of the biggest annoyances with
> >> up2date.  You get notification about available updates, run up2date,
> >> and the repository and/or mirror from mirrorlist has not gotten
> >> resynced..
> >>
> >> So here are some possible actions that you can take:
> >>
> >>
> >>
> >> 1. Do not react immediately upon receiving an update notification.
> >> Wait several hours before trying so that the mirrors can sync up.
> >> 2. Disable the update agent.  Perform updates manually or update via a
> >>  cron job. 3. File either an RFE or a bug report in Bugzzilla,
> >> https://bugzilla.redhat.com/bugzilla/ .
> >>
> >
> > 4. Configure up2date to use a fast mirror for you rather than relying
> > on the default mirror list.  If up2date and rhn-applet are looking at
> > the same mirror you won't have any problem.
> >
>
>  Tried both the mirrorlist and fast local mirrors 
Mirror_s_.  As long as you have multiple mirrors configured there is a
chance that one will update before another.  Pointing to a single mirror
will eliminate that.

[snip]
>  What mirror are you using to get such good results? 
A local lan-only one, but _what_ mirror doesn't matter, the _number_ of
mirrors being more than one is what matters.

-- 
William Hooper

[Alexander Dalloz]

Am Fr, den 01.04.2005 schrieb Kam Leo um 18:36:

>  > 4. Configure up2date to use a fast mirror for you rather than
> relying on
>  > the default mirror list.  If up2date and rhn-applet are looking at the
>  > same mirror you won't have any problem.
>  > 
>  
>  Tried both the mirrorlist and fast local mirrors (e.g.
>  ftp://mirrors.kernel.org, ftp://mirror.stanford.edu, and
>  ftp://limestone.uoregon.edu among others) and continue to encounter
>  this problem.
>  
>  What mirror are you using to get such good results? 
I can't recommend you a good US American mirror, but using out German
mirror at TU Chemnitz I face no real problem with up2date. Since the
first day with FC1 I am using no other tool than up2date here on my
desktop PC. It may be not the fastest horse, but up2date works for me
without the often reported major issues. And I am just patient when
updates are announced to let the mirror sync with the master 'borg
cube'.
William already gave a good hint while I am typing.

Alexander


-- 
Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773
legal statement: http://www.uni-x.org/legal.html
Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.10-1.771_FC2smp 
Serendipity 18:49:19 up 2 days, 16:15, load average: 0.37, 0.53, 0.57

[Jared Buck]

This happens with me sometimes - not all update servers (the program 
contacts several) have every update.  Best thing to do is re-run up2date 
a couple times in succession; sometimes the program needs a little 
prodding of this kind to get it to update properly.

Your solution of rebooting the machine also works, of course.

Jared B.

Scott Carper wrote on 3/31/2005, 7:00 PM:

>  After I successfully run up2date, the next time I check for updates,
>  it says
>  there are  updates available (and these are not the same as the previous
>  update); but when I launch up2date, it says "Your system is fully
>  updated.
>  No new packages are needed."  I have to reboot the system before the
>  available updates will be downloaded and installed by up2date.
>
>  Any ideas?  Any help would be appreciated.
>
>  Thanks.
>  Scott
>
>  --
>  No virus found in this outgoing message.
>  Checked by AVG Anti-Virus.
>  Version: 7.0.308 / Virus Database: 266.8.6 - Release Date: 3/30/2005
>
>
>  --
>  fedora-list mailing list
>  fedora-list(a)redhat.com
>  To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
>