nux-dextop error solved

[rbrick49]

does any one know whats going on with nux-dextop it was working yesterday morning here then it started giving this error
failure: repodata/repomd.xml from nux-dextop: [Errno 256] No more mirrors to try.
http://mirror.li.nux.ro/li.nux.ro/nux/d ... repomd.xml: [Errno 14] curl#6 - "Could not resolve host: mirror.li.nux.ro; No address associated with hostname"
http://li.nux.ro/download/nux/dextop/el ... repomd.xml: [Errno 14] curl#6 - "Could not resolve host: li.nux.ro; No address associated with hostname
I uninstalled it and reinstalled but no luck
regards Ron

[TrevorH]

That's a name resolution error but it works fine from here, I can resolve that name to an ip from two separate locations which use completely separate name servers. Also Google's 8.8.8.8 can do so too. I suggest you check your resolv.conf and make sure that it points to working name servers.

[rbrick49]

Heres my resol.conf I added gogle nameserver its still giving me the same error
# Generated by NetworkManager
nameserver 124.40.225.53
nameserver 124.40.225.58
nameserver 8.8.8.8
I was trying to install smplayer it worked ok yesterday except for one dependency then nux-dextop started giving me ths error

[rbrick49]

Heres the error message I get now
oot@localhost ~]# yum update
Loaded plugins: fastestmirror, langpacks
adobe-linux-x86_64 | 951 B 00:00
base | 3.6 kB 00:00
epel/x86_64/metalink | 5.3 kB 00:00
epel-debuginfo/x86_64/metalink | 5.2 kB 00:00
epel-debuginfo | 3.0 kB 00:00
epel-source/x86_64/metalink | 5.3 kB 00:00
epel-source | 3.0 kB 00:00
extras | 3.3 kB 00:00
nux-dextop | 2.9 kB 00:00
updates | 3.4 kB 00:00
(1/9): base/7/x86_64/group_gz | 157 kB 00:06
(2/9): epel-debuginfo/x86_64/primary_db | 295 kB 00:06
(3/9): extras/7/x86_64/primary_db | 15 kB 00:01
nux-dextop/x86_64/primary_db FAILED
http://mirror.li.nux.ro/li.nux.ro/nux/d ... sqlite.bz2: [Errno 14] curl#6 - "Could not resolve host: mirror.li.nux.ro; No address associated with hostname"
Trying other mirror.
(4/9): epel-source/x86_64/primary_db | 738 kB 00:16
(5/9): epel/x86_64/group_gz | 163 kB 00:24
nux-dextop/x86_64/primary_db FAILED
http://li.nux.ro/download/nux/dextop/el ... sqlite.bz2: [Errno 14] curl#6 - "Could not resolve host: li.nux.ro; No address associated with hostname"
Trying other mirror.
(6/9): updates/7/x86_64/primary_db | 1.5 MB 00:50
(7/9): epel/x86_64/primary_db | 2.0 MB 01:01
(8/9): base/7/x86_64/primary_db | 4.9 MB 01:26
adobe-linux-x86_64/primary | 1.2 kB 00:01
Determining fastest mirrors
* base: mirrors.thzhost.com
* epel: mirrors.thzhost.com
* epel-debuginfo: kartolo.sby.datautama.net.id
* epel-source: mirrors.thzhost.com
* extras: mirrors.thzhost.com
* nux-dextop: mirror.li.nux.ro
* updates: mirror1.ku.ac.th
nux-dextop/x86_64/primary_db FAILED
http://mirror.li.nux.ro/li.nux.ro/nux/d ... sqlite.bz2: [Errno 14] curl#6 - "Could not resolve host: mirror.li.nux.ro; No address associated with hostname"
Trying other mirror.
nux-dextop/x86_64/primary_db FAILED
http://li.nux.ro/download/nux/dextop/el ... sqlite.bz2: [Errno 14] curl#6 - "Could not resolve host: li.nux.ro; No address associated with hostname"
Trying other mirror.
adobe-linux-x86_64 2/2
http://mirror.li.nux.ro/li.nux.ro/nux/d ... sqlite.bz2: [Errno 14] curl#6 - "Could not resolve host: mirror.li.nux.ro; No address associated with hostname"
Trying other mirror.
http://li.nux.ro/download/nux/dextop/el ... sqlite.bz2: [Errno 14] curl#6 - "Could not resolve host: li.nux.ro; No address associated with hostname"
Trying other mirror.


One of the configured repositories failed (Nux.Ro RPMs for general desktop use),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Disable the repository, so yum won't use it by default. Yum will then
just ignore the repository until you permanently enable it again or use
--enablerepo for temporary usage:

yum-config-manager --disable nux-dextop

4. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=nux-dextop.skip_if_unavailable=true

failure: repodata/9d79026c1d39a703a11dd804c06ae5882f36479834cfd4d02f88a8e2753f6186-primary.sqlite.bz2 from nux-dextop: [Errno 256] No more mirrors to try.
http://mirror.li.nux.ro/li.nux.ro/nux/d ... sqlite.bz2: [Errno 14] curl#6 - "Could not resolve host: mirror.li.nux.ro; No address associated with hostname"
http://li.nux.ro/download/nux/dextop/el ... sqlite.bz2: [Errno 14] curl#6 - "Could not resolve host: li.nux.ro; No address associated with hostname"
[root@localhost ~]#
Iwill try another isp providor and see what happens

[nbritton]

Did you turn on the network interface? What happens when you try to ping or nslookup mirror.li.nux.ro? If nslookup mirror.li.nux.ro 8.8.8.8 works but ping fails then try commenting out nameserver 124.40.225.53 and nameserver 124.40.225.58 so that just google's DNS is enabled in /etc/resolv.conf

[root@localhost system]# nslookup mirror.li.nux.ro 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: mirror.li.nux.ro
Address: 85.13.241.50

[root@localhost system]# ping mirror.li.nux.ro
PING mirror.li.nux.ro (85.13.241.50) 56(84) bytes of data.
64 bytes from mirrors.coreix.net (85.13.241.50): icmp_seq=1 ttl=50 time=110 ms
64 bytes from mirrors.coreix.net (85.13.241.50): icmp_seq=2 ttl=50 time=111 ms
64 bytes from mirrors.coreix.net (85.13.241.50): icmp_seq=3 ttl=50 time=110 ms
64 bytes from mirrors.coreix.net (85.13.241.50): icmp_seq=4 ttl=50 time=111 ms
^C
--- mirror.li.nux.ro ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 110.542/111.063/111.513/0.499 ms
[root@localhost system]#

[rbrick49]

here you go
[root@localhost ~]# nslookup mirror.li.nux.ro 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: mirror.li.nux.ro
Address: 85.13.241.50

[root@localhost ~]# ping mirror.li.nux.ro
PING mirror.li.nux.ro (85.13.241.50) 56(84) bytes of data.
64 bytes from mirrors.coreix.net (85.13.241.50): icmp_seq=1 ttl=41 time=329 ms
64 bytes from mirrors.coreix.net (85.13.241.50): icmp_seq=2 ttl=41 time=339 ms
64 bytes from mirrors.coreix.net (85.13.241.50): icmp_seq=3 ttl=41 time=369 ms
64 bytes from mirrors.coreix.net (85.13.241.50): icmp_seq=4 ttl=41 time=349 ms
64 bytes from mirrors.coreix.net (85.13.241.50): icmp_seq=5 ttl=41 time=339 ms
64 bytes from mirrors.coreix.net (85.13.241.50): icmp_seq=6 ttl=41 time=339 ms
64 bytes from mirrors.coreix.net (85.13.241.50): icmp_seq=7 ttl=41 time=329 ms
64 bytes from mirrors.coreix.net (85.13.241.50): icmp_seq=8 ttl=41 time=339 ms
64 bytes from mirrors.coreix.net (85.13.241.50): icmp_seq=9 ttl=41 time=339 ms

[nbritton]

ifup exyz123_youcantscriptthisnow?_wtf
then change ONBOOT=no to ONBOOT=yes in /etc/sysconfig/network-scripts/ifcfg-exyz123_youcantscriptthisnow?_wtf

[rbrick49]

what is this I dont understand
ifup exyz123_youcantscriptthisnow?_wtf
then change ONBOOT=no to ONBOOT=yes in /etc/sysconfig/network-scripts/ifcfg-exyz123_youcantscriptthisnow?_wtf

[nbritton]

what is this I dont understand
ifup exyz123_youcantscriptthisnow?_wtf
then change ONBOOT=no to ONBOOT=yes in /etc/sysconfig/network-scripts/ifcfg-exyz123_youcantscriptthisnow?_wtf

They changed the network interface naming standard in el7 so now the interface names are basically randomly assigned. I was going to tell you to run sed -i 's/ONBOOT=no/ONBOOT=yes/' /etc/sysconfig/network-scripts/ifcfg-eth0; but that won't work anymore. Hence xyz123_YouCantScriptThisNow?_wtf. They also changed it so you have to manually enable the network interface at the beginning of each startup. Hence you need to add ONBOOT=yes to your network startup scripts and then, presumably, ifup your network interface to bring it up.

[rbrick49]

Hi I found this,is this what has to be changed
/bin/bash
# Network Interface Configuration System
# Copyright (c) 1996-2009 Red Hat, Inc. all rights reserved.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License, version 2,
# as published by the Free Software Foundation.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.

unset WINDOW # defined by screen, conflicts with our usage

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

[ -z "${CONFIG}" ] && {
echo $"Usage: ifup <configuration>" >&2
exit 1
}

need_config "${CONFIG}"

[ -f "${CONFIG}" ] || {
echo $"$0: configuration for ${1} not found." >&2
echo $"Usage: ifup <configuration>" >&2
exit 1
}

if [ ${UID} != 0 ]; then
if [ -x /usr/sbin/usernetctl ]; then
source_config
if /usr/sbin/usernetctl ${CONFIG} report ; then
exec /usr/sbin/usernetctl ${CONFIG} up
fi
fi
echo $"Users cannot control this device." >&2
exit 1
fi

source_config

if [ "foo$2" = "fooboot" ] && [ "${ONBOOT}" = "no" -o "${ONBOOT}" = "NO" ]
then
exit 0