Page 1 of 2 12 LastLast
Results 1 to 10 of 18

Thread: Upgrade Error

  1. #1
    Junior Member
    Join Date
    Sep 2011
    Posts
    11

    Upgrade Error

    Hi,

    I have v2 running on Fedora release 16 (Verne) but when I try and do an upgrade I get part way through the process (after the dependency checks etc) and I get the following error :-

    Package(s) data still to download: 5.6 M
    http://yum.vortexbox.org/releases/16...fc16.i686.rpm: [Errno 14] HTTP Error 200 - OK : http://yum.vortexbox.org/releases/16....fc16.i686.rpm
    Trying other mirror.


    Error Downloading Packages:
    vortexbox-2.0-38.fc16.i686: failure: vortexbox-2.0-38.fc16.i686.rpm from vortexbox: [Errno 256] No more mirrors to try.


    Can anyone point me in the right direction to solving this please ?

    Ian

  2. #2
    Administrator Ron Olsen's Avatar
    Join Date
    Dec 2009
    Location
    Boulder CO USA
    Posts
    4,963
    Try again later. Repository access errors are often transitory.

  3. #3
    Junior Member
    Join Date
    Sep 2011
    Posts
    11
    Quote Originally Posted by Ron Olsen View Post
    Try again later. Repository access errors are often transitory.
    Thanks - I have been trying for a couple of days now, will try again tonight and let you know if it has been resolved

    Ian

  4. #4
    Administrator Ron Olsen's Avatar
    Join Date
    Dec 2009
    Location
    Boulder CO USA
    Posts
    4,963
    You could also try updating from the command line:

    1. Login to your VortexBox; see http://info.vortexbox.org/tiki-index.php?page=Login

    2. Enter
    Code:
    yum clean all; yum update
    3. Report any error messages.

    If the problem persists, reboot your VB and try again.

  5. #5
    Administrator andrew's Avatar
    Join Date
    Nov 2008
    Location
    New Hampshire
    Posts
    3,619
    Our repo is always up so it must be a network problem of some kind. Try using a static IP and let VortexBox select the DNS server.

  6. #6
    Junior Member
    Join Date
    Sep 2011
    Posts
    11
    Quote Originally Posted by andrew View Post
    Our repo is always up so it must be a network problem of some kind. Try using a static IP and let VortexBox select the DNS server.
    Hi,

    I have run an update from the command line (with a static IP and letting VB select DNS) and get the same error :-

    Finishing rebuild of rpms, from deltarpms
    <locally rebuilding deltarpms> | 33 MB 00:49
    Presto reduced the update size by 77% (from 33 M to 7.8 M).
    Package(s) data still to download: 5.6 M
    (1/3): mpd-1.16.8-2.fc16.i686.rpm | 302 kB 00:08
    (2/3): vb-GUI-2.0-9.fc16.noarch.rpm | 979 kB 00:18
    http://yum.vortexbox.org/releases/16...fc16.i686.rpm: [Errno 14] HTTP Error 200 - OK : http://yum.vortexbox.org/releases/16/i386/RPMS
    /vortexbox-2.0-38.fc16.i686.rpm
    Trying other mirror.


    Error Downloading Packages:
    vortexbox-2.0-38.fc16.i686: failure: vortexbox-2.0-38.fc16.i686.rpm from vortexbox: [Errno 256] No more mirrors to try.

  7. #7
    Administrator andrew's Avatar
    Join Date
    Nov 2008
    Location
    New Hampshire
    Posts
    3,619
    try

    ping google.com

    or

    ping yum.vortexbox.org

    and post your results

  8. #8
    Administrator Ron Olsen's Avatar
    Join Date
    Dec 2009
    Location
    Boulder CO USA
    Posts
    4,963
    Try this:
    Code:
    wget http://yum.vortexbox.org/releases/16/i386/RPMS/vortexbox-2.0-38.fc16.i686.rpm
    yum localinstall vortexbox-2.0-38.fc16.i686.rpm
    If this works, then try
    Code:
    yum clean all; yum update
    Report any error messages.

  9. #9
    Quote Originally Posted by andrew View Post
    try

    ping google.com

    or

    ping yum.vortexbox.org

    and post your results
    Hello, I have the same error message too when I try and upgrade.

    Ping results are (I think, I've never done this before)...

    From Google.com

    "PING google.com (74.125.228.78) 56(84) bytes of data.
    64 bytes from iad23s07-in-f14.1e100.net (74.125.228.78): icmp_seq=1 ttl=58 time=2.72 ms
    64 bytes from iad23s07-in-f14.1e100.net (74.125.228.78): icmp_seq=2 ttl=58 time=2.77 ms
    64 bytes from iad23s07-in-f14.1e100.net (74.125.228.78): icmp_seq=3 ttl=58 time=2.79 ms
    64 bytes from iad23s07-in-f14.1e100.net (74.125.228.78): icmp_seq=4 ttl=58 time=2.76 ms
    64 bytes from iad23s07-in-f14.1e100.net (74.125.228.78): icmp_seq=5 ttl=58 time=2.76 ms
    64 bytes from iad23s07-in-f14.1e100.net (74.125.228.78): icmp_seq=6 ttl=58 time=2.73 ms
    64 bytes from iad23s07-in-f14.1e100.net (74.125.228.78): icmp_seq=7 ttl=58 time=2.77 ms
    64 bytes from iad23s07-in-f14.1e100.net (74.125.228.78): icmp_seq=8 ttl=58 time=2.77 ms
    64 bytes from iad23s07-in-f14.1e100.net (74.125.228.78): icmp_seq=9 ttl=58 time=2.83 ms
    64 bytes from iad23s07-in-f14.1e100.net (74.125.228.78): icmp_seq=10 ttl=58 time=2.75 ms"


    ...and from yum.vortexbox.org...

    "PING yum.vortexbox.org (174.127.107.174) 56(84) bytes of data.
    64 bytes from slmp-550-34.slc.westdc.net (174.127.107.174): icmp_seq=1 ttl=49 time=78.4 ms
    64 bytes from slmp-550-34.slc.westdc.net (174.127.107.174): icmp_seq=2 ttl=49 time=78.7 ms
    64 bytes from slmp-550-34.slc.westdc.net (174.127.107.174): icmp_seq=3 ttl=49 time=78.7 ms
    64 bytes from slmp-550-34.slc.westdc.net (174.127.107.174): icmp_seq=4 ttl=49 time=78.4 ms
    64 bytes from slmp-550-34.slc.westdc.net (174.127.107.174): icmp_seq=5 ttl=49 time=78.4 ms
    64 bytes from slmp-550-34.slc.westdc.net (174.127.107.174): icmp_seq=6 ttl=49 time=78.4 ms
    64 bytes from slmp-550-34.slc.westdc.net (174.127.107.174): icmp_seq=7 ttl=49 time=78.3 ms
    64 bytes from slmp-550-34.slc.westdc.net (174.127.107.174): icmp_seq=8 ttl=49 time=78.4 ms
    64 bytes from slmp-550-34.slc.westdc.net (174.127.107.174): icmp_seq=9 ttl=49 time=79.2 ms
    64 bytes from slmp-550-34.slc.westdc.net (174.127.107.174): icmp_seq=10 ttl=49 time=78.4 ms"


    Does that help?

    I've tried updating from the GUI a few times and rebooted both VB and my router, still no joy I'm afraid, still the same error messages as the chap in the original post.

    Best,

    Dave.

  10. #10
    Administrator Ron Olsen's Avatar
    Join Date
    Dec 2009
    Location
    Boulder CO USA
    Posts
    4,963
    Read post #8 and try the commands given there.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •