Menu ▾ ▴

vixta 2010 beta on virtualmachine an proxy

Help
Anonymous
2009-12-02
2012-08-27

  • Anonymous

    Anonymous - 2009-12-02

    well

    I've installed the vixta 2010 on a sun virtualized machine over ubuntu 9

    the thing is I cannot run yum update

    I set the proxy (no need for user/pass) in yum.conf

    I comment all mirrors adn uncomment all base from all yum.repos.d

    but I cannot update nor install anything

    any ideas ?

     

  • sal

    sal - 2009-12-02

    you must comment the second line in /etc/yum.conf

     

  • Anonymous

    Anonymous - 2009-12-03

    you mean, comment the mirros ?

    yes I did at first time, but, as soon I restart my vm I will check it out

     

  • Anonymous

    Anonymous - 2009-12-03

    I commented out

    first the exclude... same problem

    then the cache... same problem

     

  • snitram

    snitram - 2009-12-03

    could you try to use devel.repos and see if problem persist?

     

  • Anonymous

    Anonymous - 2009-12-03

    this is my yum.conf

    ============


    exclude=kernel, kmod, fedora, anaconda, plymouth, oxygen-icon-theme

    cachedir=/var/cache/yum

    keepcache=1

    debuglevel=2

    logfile=/var/log/yum.log

    exactarch=1

    obsoletes=1

    gpgcheck=1

    plugins=1

    metadata_expire=1800

    installonly_limit=2


    proxy=http://myproxyip:port/<br>


    -# PUT YOUR REPOS HERE OR IN separate files named file.repo

    -# in /etc/yum.repos.d



    (i just include the - before the # to correct display the line)

     

  • Anonymous

    Anonymous - 2009-12-03

    ok, I'll try it

     

  • sal

    sal - 2009-12-03

    please send us the print screen/log of the error

    (gande abraço e obrigado sinitram)

     

  • Betto McRose

    Betto McRose - 2009-12-04

    bash-4.0# yum update

    Loaded plugins: refresh-packagekit

    Error: Cannot retrieve repository metadata (repomd.xml) for repository:
    fedora. Please verify its path and try again

    bash-4.0#

    this took about 15 to 20 mins

     

  • Betto McRose

    Betto McRose - 2009-12-04

    by the way, I comment the cachedir line to get this result

    only commenting that line a can/cannot connect

     

  • snitram

    snitram - 2009-12-04

    2009-12-04 13:33:42 WET

    hi, when you commented the lines didn t you forget to edit etc/hosts and put

    80.239.156.215 mirrors.fedoraproject.org

    213.129.242.84
    mirrors.rpmfusion.org

    so u should have edited theese 2 files:

    /etc/yum.repos.d/fedora.repo and

    /etc/yum.repos.d
    /fedora-updates.repo.

    un-commented all the lines that start with the
    term baseurl and place a comment before all lines that start with mirrorlist.

    Then edit your /etc/hosts file and append the following to it’s contents:

    80.239.156.215 mirrors.fedoraproject.org

    213.129.242.84 mirrors.rpmfusion.orgNow try updating your

    this info was on fedora project
     

  • snitram

    snitram - 2009-12-04

    do all that and it shoukld work just fine, its a known bug regarding fedora
    project repositories

    also check if ip's are correct 80.239.156.215 & 213.129.242.84

    and if still doesnt work esxport http_proxy= IP:port variable

     

  • Betto McRose

    Betto McRose - 2009-12-04

    none of the given IPs pings

     

  • Betto McRose

    Betto McRose - 2009-12-04

    this is my /etc/hosts file

    127.0.0.1 localhost.localdomain localhost

    ::1 localhost6.localdomain6 localhost6

    80.239.156.215 mirrors.fedoraproject.org

    213.129.242.84 mirrors.rpmfusion.org

    70.91.168.58 download.fedora.org

    152.46.7.222 download.fedoraproject.org


     

  • Betto McRose

    Betto McRose - 2009-12-04

    well, I was checking the centos5 config (also on a vm) an it's the same
    configuration, nothing more than the specified proxy line in the yum.conf and
    it works pretty well

     

  • snitram

    snitram - 2009-12-04

    yes, i didnt have the time to check it at that time but that's why i told you
    to check, and so you tested it and none of the ip's ping. May i conclude that
    you replaced with the ones that do ping?

    66.35.62.166 for mirrors.fedoraproject.org and

    134.108.44.54 for rpm fuion

     

  • snitram

    snitram - 2009-12-04

    this ip you have is also not correct.

    although it may point to some kind of mirror it certainly doesnt point to
    download.fedoraproject.org

    152.46.7.222 download.fedoraproject.org

    correct to: 209.132.176.120

     

Log in to post a comment.