Hallo Holger,
Am 13.09.2014 um 11:30 schrieb Holger Baumhof:
> Läuft er wirklich nicht?
> Ich erinnere, dass ich ihn auch neu gestartet hatte, und dass er sagte:
> stopping bind
> und
> starting bind
> ohne Fehler.
> Wenn er nicht läuft kommt sowas:
> stopping bind ... no such prozess
auch mit einem laufenden Bind kann es passieren, dass dieser nicht wie
gewünscht arbeitet/auflöst.
Ich habe mehrere Ubuntu-Server neu aufgesetzt und hatte immer ein Problem mit
bind 9.8, dem ich mit ausführlichem Loggen auf die Schliche kam.
aus meiner named.conf
schnipp
logging {
channel default_file {
file "/var/log/named/default.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel general_file {
file "/var/log/named/general.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel database_file {
file "/var/log/named/database.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel security_file {
file "/var/log/named/security.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel config_file {
file "/var/log/named/config.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel resolver_file {
file "/var/log/named/resolver.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel xfer-in_file {
file "/var/log/named/xfer-in.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel xfer-out_file {
file "/var/log/named/xfer-out.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel notify_file {
file "/var/log/named/notify.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel client_file {
file "/var/log/named/client.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel unmatched_file {
file "/var/log/named/unmatched.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel queries_file {
file "/var/log/named/queries.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel network_file {
file "/var/log/named/network.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel update_file {
file "/var/log/named/update.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel dispatch_file {
file "/var/log/named/dispatch.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel dnssec_file {
file "/var/log/named/dnssec.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
channel lame-servers_file {
file "/var/log/named/lame-servers.log" versions 3 size 5m;
severity dynamic;
print-time yes;
};
category default { default_file; };
category general { general_file; };
category database { database_file; };
category security { security_file; };
category config { config_file; };
category resolver { resolver_file; };
category xfer-in { xfer-in_file; };
category xfer-out { xfer-out_file; };
category notify { notify_file; };
category client { client_file; };
category unmatched { unmatched_file; };
category queries { queries_file; };
category network { network_file; };
category update { update_file; };
category dispatch { dispatch_file; };
category dnssec { dnssec_file; };
category lame-servers { lame-servers_file; };
};
schnapp
$ ls -ld /var/log/named
drwxr-xr-x 2 bind bind 4096 Sep 12 12:36 /var/log/named
$ ls -l /etc/bind
-rw-r--r-- 1 bind bind 2389 Mär 24 18:06 bind.keys
-rw-r--r-- 1 bind bind 237 Mär 24 18:06 db.0
-rw-r--r-- 1 bind bind 271 Mär 24 18:06 db.127
-rw-r--r-- 1 bind bind 237 Mär 24 18:06 db.255
-rw-r--r-- 1 bind bind 353 Mär 24 18:06 db.empty
-rw-r--r-- 1 bind bind 271 Jun 17 09:38 db.local
-rw-r--r-- 1 bind bind 3057 Jun 19 21:27 db.root
-rw-r--r-- 1 bind bind 8274 Jul 30 09:05 db.ssi
-rw-rw-rw- 1 bind bind 1185 Aug 5 11:48 managed-keys.bind
-rw-rw-rw- 1 bind bind 1267172 Sep 13 11:11 managed-keys.bind.jnl
-rw-r--r-- 1 bind bind 4096 Jun 19 21:21 named.conf
-rw-r--r-- 1 bind bind 490 Mär 24 18:06 named.conf.default-zones
-rw-r--r-- 1 bind bind 349 Jun 19 16:09 named.conf.local
-rw-r--r-- 1 bind bind 1289 Jun 20 09:05 named.conf.options
-rw-r--r-- 1 bind bind 5007 Jul 30 09:06 named.ssi
-rw-r--r-- 1 bind bind 77 Jun 17 09:37 rndc.key
-rw-r--r-- 1 bind bind 1317 Jun 17 09:59 zones.rfc1918
Die Datei managed-keys.bind musste ich anlegen und füllen und
managed-keys.bind.jnl mit touch anlegen.
Zum Testen/weitere Fehleranalyse:
Meinen Logging-Block eintragen, bind starten, 20s warten, bind beenden. Logs
analysieren
Dirk
_______________________________________________
linuxmuster-user mailing list
[email protected]
https://mail.lehrerpost.de/mailman/listinfo/linuxmuster-user
