Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Help!! Centos repo error

[root@vps yum.repos.d]# yum --enablerepo=epel install yasm
Loaded plugins: fastestmirror, refresh-packagekit
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os error was
14: PYCURL ERROR 6 - "Couldn't resolve host 'mirrorlist.centos.org'"
Error: Cannot find a valid baseurl for repo: base

this is what I got when trying to install yasm from rpmforge repo.. I got same error when trying to update using

yum update

Centos 6.4 64bit

Comments

  • What's in /etc/resolv.conf ? Maybe there is a broken resolver and you need to use another one.

  • JohnRoeJohnRoe Member
    edited November 2013

    @rds100 said:
    What's in /etc/resolv.conf

    this is the content

    `# Generated by NetworkManager
    search server.com

    No nameservers found; try putting DNS servers into your

    ifcfg files in /etc/sysconfig/network-scripts like so:

    #

    DNS1=xxx.xxx.xxx.xxx

    DNS2=xxx.xxx.xxx.xxx

    DOMAIN=lab.foo.com bar.foo.com

    `

    how it should be?

  • See, here's your problem.
    Put there something like:

    nameserver 8.8.8.8

    And then try again.

  • JohnRoeJohnRoe Member
    edited November 2013

    @rds100 said:
    See, here's your problem.
    Put there something like:

    nameserver 8.8.8.8

    And then try again.

    works!! simple as abc..
    thank you..
    my node offline minutes ago.. after reported, my provider solved it.. and then, this problem appear..
    I know what to do if it happen again :)
    thank you bro

  • This is on a VPS? Stop the NetworkManager (chmod 000 it). It will be screwing your network config when it runs.

  • JohnRoeJohnRoe Member
    edited November 2013

    @rds100 said:
    This is on a VPS? Stop the NetworkManager (chmod 000 it). It will be screwing your network config when it runs.

    yah..vps.. where is the file ?? I never face this problem..

  • rds100rds100 Member
    edited November 2013

    Try


    chmod 000 `which NetworkManager`

    Then reboot.

  • done.. what it will do?

    I tried to find the files

    [root@vps network-scripts]# find / -name NetworkManager /var/run/NetworkManager /var/lock/subsys/NetworkManager /var/lib/NetworkManager /usr/lib64/NetworkManager /usr/share/NetworkManager /usr/sbin/NetworkManager /etc/rc.d/init.d/NetworkManager /etc/NetworkManager

    will it chmod all the files??

  • sudo sudo /sbin/chkconfig --levels 2345 NetworkManager off

  • /usr/sbin/NetworkManager it is

  • @Adduc said:
    sudo sudo /sbin/chkconfig --levels 2345 NetworkManager off

    it will disable from start at boot right?
    thanks :)

    @rds100 said:
    /usr/sbin/NetworkManager it is

    thank you soo much.. new knowledge for me :)

  • I don't think the chkconfig will disable it. It's started by the gnome desktop environment. Just chmod 000 it and be done with it :) But keep in mind that if there is some update that installs a new version of NetworkManager, it will probably reappear and you will have to chmod 000 again.

  • @rds100 said:
    I don't think the chkconfig will disable it. It's started by the gnome desktop environment. Just chmod 000 it and be done with it :) But keep in mind that if there is some update that installs a new version of NetworkManager, it will probably reappear and you will have to chmod 000 again.

    thanks.. I really appreciate it

Sign In or Register to comment.