[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [UNsolved] Re: bind9 logcheck



Am Dienstag 16 August 2005 19:49 schrieb gerhard:

> ~# /etc/init.d/bind9 restart
> Stopping domain name service: namedrndc: connect failed: connection
> refused
> .
> Starting domain name service: named.
> ~# rndc status
> number of zones: 6
> debug level: 0
> xfers running: 0
> xfers deferred: 0
> soa queries in progress: 0
> query logging is OFF
> server is up and running
>
> Jetzt muß ich nur noch herausfinden, wo in der logcheck Konfiguration
> sich dieser Eintrag ignorieren lässt, es handelt sich offensichtlich
> um einen bug:
>
> Aug 15 20:28:41 vserverxxx pam_limits[PID]: setrlimit limit #6 to
> soft=-1, hard=-1 failed: Operation not permitted; uid=0 euid=0
>
> openssh bug #171673 :
> http://bugs.debian.org/cgi-bin/bugreport.c...i?bug=%23171673
>
> Und ist angeblich ab openssh (1:3.8p1-1) unstable gelöst. Will ich
> aber nicht installieren.
>

Abgesehen von dem logcheck Problem wegen meiner Unfähigkeit 
funktionierende regex zu schreiben, ist das bind9 Problem doch nicht 
gelöst:

~# exec /etc/init.d/bind9 restart
Stopping domain name service: namedrndc: connection to remote host 
closed
This may indicate that the remote server is using an older version of
the command protocol, this host is not authorized to connect,
or the key is invalid.
.
Starting domain name service: named.

folgendes hilft nicht:
~# rndc-confgen -r /dev/urandom -a
~# rndc-config
bash: rndc-config: command not found
~# rndc status
rndc: connection to remote host closed
This may indicate that the remote server is using an older version of
the command protocol, this host is not authorized to connect,
or the key is invalid.

Lesbar ist er für bind jedenfalls:
# ls -l /etc/bind/rndc.key
-rw-r-----  1 bind bind 77 Aug 16 20:18 /etc/bind/rndc.key

Google findet da nur wenig (Leider spreche ich z.B. kein Portugiesisch):
http://groups.google.de/groups?q=%22stopping%20domain%20name%20service%3A%20namedrndc%3A%20connection%20to%20remote%20host%20closed%20%20This%20may%20indicate%20that%20the%20remote%20server%20is%20using%20an%20older%20version%20of%20%20the%20command%20protocol%2C%20this%20host%20is%20not%20authorized%20to%20connect%2C%20%20or%20the%20key%20is%20invalid.
%22&hl=de&lr=&sa=N&tab=wg



Reply to: