Opened 6 years ago

Closed 6 years ago

#701 closed incident (fixed)

HybridRustdam2 -dns: service check timed out

Reported by: mbreet Owned by:
Keywords: Zoeterwoude Cc:
Location: Generiek

Description

Rustdam2 dns probleem of ligt die melding (5 dagen+) aan monitoring?

Change History (3)

comment:1 Changed 6 years ago by ed

De DNS server op de node is niet actief/ wil niet starten.

HybridRustdam2# sh /usr/local/etc/rc.d/dnsmasq status
Cannot 'status' dnsmasq. Set dnsmasq_enable to YES in /etc/rc.conf or use 'onestatus' instead of 'status'.
HybridRustdam2# sh /usr/local/etc/rc.d/dnsmasq start
HybridRustdam2# cat /etc/rc.conf | grep 'dnsmasq_enable'
dnsmasq_enable="YES"
HybridRustdam2# sh /usr/local/etc/rc.d/dnsmasq onestart
Starting dnsmasq.

dnsmasq: failed to bind DHCP server socket: Address already in use
/usr/local/etc/rc.d/dnsmasq: WARNING: failed to start dnsmasq
HybridRustdam2# sockstat -4
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS      
root     sshd       64821 5  tcp4   172.17.95.1:22        172.25.90.68:15116
nobody   tinyproxy  29932 0  tcp4   *:3128                *:*
nobody   tinyproxy  29931 0  tcp4   *:3128                *:*
nobody   tinyproxy  29930 0  tcp4   *:3128                *:*
nobody   tinyproxy  29172 0  tcp4   *:3128                *:*
nobody   tinyproxy  29157 0  tcp4   *:3128                *:*
nobody   tinyproxy  28676 0  tcp4   *:3128                *:*
nobody   tinyproxy  28674 0  tcp4   *:3128                *:*
nobody   tinyproxy  28673 0  tcp4   *:3128                *:*
nobody   tinyproxy  28672 0  tcp4   *:3128                *:*
nobody   tinyproxy  28671 0  tcp4   *:3128                *:*
nobody   tinyproxy  28670 0  tcp4   *:3128                *:*
nobody   tinyproxy  28669 0  tcp4   *:3128                *:*
nobody   tinyproxy  24219 0  tcp4   *:3128                *:*
nobody   tinyproxy  18714 0  tcp4   *:3128                *:*
nobody   tinyproxy  18500 0  tcp4   *:3128                *:*
nobody   tinyproxy  18497 0  tcp4   *:3128                *:*
root     sshd       1947  5  tcp4   *:22                  *:*
root     snmpd      1927  8  udp4   *:161                 *:*
root     snmpd      1927  9  tcp4   *:199                 *:*
root     thttpd     1920  2  tcp4   *:80                  *:*
nobody   tinyproxy  1916  0  tcp4   *:3128                *:*
nobody   tinyproxy  1913  0  tcp4   *:3128                *:*
nobody   tinyproxy  1912  0  tcp4   *:3128                *:*
nobody   tinyproxy  1911  0  tcp4   *:3128                *:*
nobody   tinyproxy  1909  0  tcp4   *:3128                *:*
nobody   tinyproxy  1905  0  tcp4   *:3128                *:*
dhcpd    dhcpd      1895  7  udp4   *:67                  *:*
dhcpd    dhcpd      1895  20 udp4   *:56199               *:*
root     ntpd       1829  20 udp4   *:123                 *:*
root     ntpd       1829  22 udp4   192.168.178.5:123     *:*
root     ntpd       1829  23 udp4   172.16.7.100:123      *:*
root     ntpd       1829  24 udp4   172.17.95.1:123       *:*
root     ntpd       1829  27 udp4   127.0.0.1:123         *:*
root     ntpd       1829  28 udp4   172.31.255.1:123      *:*
root     iperf      1762  3  tcp4   *:5001                *:*
root     tcpserver  1753  3  tcp4   172.31.255.1:8081     *:*
root     syslogd    1614  7  udp4   *:514                 *:*
root     lvrouted   1569  3  udp4   *:12345               *:*

Lijkt er op dat er iets in de configuratie is veranderd / verkeerd is.
DNSMASQ start niet omdat de poort reeds in gebruik is.

In /etc/rc.conf wordt DNSMASQ aangeroepen

# low-memory footprint DHCP and non-autoritive recursive DNS resolver
dnsmasq_enable="YES"

# Explicitly disable the memory-hungry alternatives
dhcpd_enable="NO"
dhcpd_flags="-q"
named_enable="NO"
named_chrootdir=""
named_auto_forward="YES"

Maar in /etc/rc.conf.local wordt DHCPD en NAMED gestart.

#
# ''Fat'' configuration, board has 256MB RAM
#
dnsmasq_enable="NO"
named_enable="YES"
dhcpd_enable="YES"
dhcpd_flags="$dhcpd_flags vr2"
defaultrouter="192.168.178.1"

Last edited 6 years ago by ed (previous) (diff)

comment:2 Changed 6 years ago by ed

Foutje in de config file?

HybridRustdam2# sh /etc/rc.d/named start
/etc/namedb/named.conf:302: missing ';' before '}'
/etc/namedb/named.conf:307: missing ';' before '}'
/etc/namedb/named.conf:312: missing ';' before '}'
/etc/namedb/named.conf:317: missing ';' before '}'
/etc/namedb/named.conf:322: missing ';' before '}'
/etc/namedb/named.conf:327: missing ';' before '}'
/etc/namedb/named.conf:332: missing ';' before '}'
/etc/namedb/named.conf:337: missing ';' before '}'
/etc/namedb/named.conf:342: missing ';' before '}'
/etc/namedb/named.conf:347: missing ';' before '}'
/etc/namedb/named.conf:352: missing ';' before '}'
/etc/namedb/named.conf:357: missing ';' before '}'
/etc/namedb/named.conf:362: missing ';' before '}'
/etc/namedb/named.conf:367: missing ';' before '}'
/etc/namedb/named.conf:372: missing ';' before '}'
/etc/namedb/named.conf:377: missing ';' before '}'
/etc/namedb/named.conf:382: missing ';' before '}'
/etc/rc.d/named: ERROR: named-checkconf for $named_conf failed

Aangepast op de node maar waar komt deze fout vandaan?

comment:3 Changed 6 years ago by huub

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.