[root@nethserver ~]# cat /etc/resolv.conf
# ================= DO NOT MODIFY THIS FILE =================
#
# Manual changes will be lost when this file is regenerated.
#
# Please read the developer's guide, which is available
# at NethServer official site: https://www.nethserver.org
#
#
domain info2.unicentrobogota.com
search info2.unicentrobogota.com
# dnsmasq is enabled on this machine:
nameserver 127.0.0.1
No I couldn’t solve the problem, DNS querys are not working I’m planning to format the machine, Until 20 days I can’t touch the machine for that pourpose (web aplication working).
I have Ntop misterious Traffic in the machine I think that it is hijacked, dont know what to do.
One of the configured repositories failed (Unknown),
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. Run the command with the repository temporarily disabled
yum --disablerepo=<repoid> ...
4. Disable the repository permanently, 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 <repoid>
or
subscription-manager repos --disable=<repoid>
5. 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=<repoid>.skip_if_unavailable=true
Cannot find a valid baseurl for repo: base/7/x86_64
Format the machine!!! in few words for 20 days I can’t move it, now is serving a web applicatión for information with public clients, 20 days and I can disable the machine and setup NethServer 7.5.1804 to fix this strange hijack.
This machine is so important, It Will show the benefits of NethServer to future clients, i Will demmand Crostino plan for support them.
; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> www.nethserver.org@8.8.8.8
;; global options: +cmd
;; connection timed out; no servers could be reached
[root@nethserver ~]# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=59 time=1.88 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=59 time=1.83 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=59 time=7.29 ms
Just to recap the issue: DNS queries return time out. The error in server-manager can be caused by it.
As you exclude 100% an issue with the configured DNS forwarder or with the LAN firewall, let’s try to understand what’s wrong in that NethServer installation.
This is OK (if that works…)
This is OK.
dnsmasq daemon is running. I’m assuming from above that dnsmasq.conf has not been tweaked.
It runs its own instances of dnsmasq. Maybe for some unknown reasons they interfere. You could try to stop it
[root@nethserver ~]# tracepath 8.8.8.8
1?: [LOCALHOST] pmtu 1500
1: gateway 0.742ms
1: gateway 0.648ms
2: 186.28.228.241 1.312ms asymm 3
3: 10.244.1.5 1.796ms
4: 10.5.4.42 2.949ms asymm 5
5: no reply
6: no reply
7: no reply
8: no reply
9: no reply
10: no reply
11: no reply
12: no reply
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
Too many hops: pmtu 1500
Resume: pmtu 1500
I can Ping it, as showed above; the firewall is opened for “any” protocol.
I’m excited with your knoweleged, I’m learning a lot.