Your message dated Sun, 22 Oct 2017 13:19:11 +0200
with message-id 
<1508671151.815349.1146906880.773a8...@webmail.messagingengine.com>
and subject line Closing bugs in old-old-stable bind9 versions
has caused the Debian Bug report #608571,
regarding nsupdate reads from wrong file for -k
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
608571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608571
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dnsutils
Version: 1:9.6.ESV.R1+dfsg-0+lenny2
Severity: minor

Hello Maintainer,

while checking my VServer admin scripts for errors  I  have  encountered
WHY I can not connect to my NameServer using nsupdate:

----[ command 'strace nsupdate -k /etc/rndc.conf ]----------------------
execve("/usr/bin/nsupdate", ["nsupdate", "-k", "/etc/rndc.conf"], [/* 75 vars 
*/]) = 0

<snip>

socket(PF_INET6, SOCK_DGRAM, IPPROTO_UDP) = 8
fcntl64(8, F_DUPFD, 20)                 = 20
close(8)                                = 0
fcntl64(20, F_GETFL)                    = 0x2 (flags O_RDWR)
fcntl64(20, F_SETFL, O_RDWR|O_NONBLOCK) = 0
uname({sys="Linux", node="michelle1", ...}) = 0
futex(0xb75e691c, FUTEX_WAKE_PRIVATE, 2147483647) = 0
setsockopt(20, SOL_SOCKET, SO_TIMESTAMP, [1], 4) = 0
setsockopt(20, SOL_IPV6, 0x31 /* IPV6_??? */, [1], 4) = 0
getsockopt(20, SOL_SOCKET, SO_RCVBUF, [111616], [4]) = 0
setsockopt(20, SOL_IPV6, IPV6_V6ONLY, [1], 4) = 0
bind(20, {sa_family=AF_INET6, sin6_port=htons(21174), inet_pton(AF_INET6, "::", 
&sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = 0
socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 8
fcntl64(8, F_DUPFD, 20)                 = 21
close(8)                                = 0
fcntl64(21, F_GETFL)                    = 0x2 (flags O_RDWR)
fcntl64(21, F_SETFL, O_RDWR|O_NONBLOCK) = 0
setsockopt(21, SOL_SOCKET, SO_TIMESTAMP, [1], 4) = 0
setsockopt(21, SOL_IP, IP_MTU_DISCOVER, [0], 4) = 0
getsockopt(21, SOL_SOCKET, SO_RCVBUF, [111616], [4]) = 0
bind(21, {sa_family=AF_INET, sin_port=htons(2590), 
sin_addr=inet_addr("0.0.0.0")}, 16) = 0
open("/etc/rndc.conf.key", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or 
directory)
write(2, "could not read key from /etc/rndc"..., 55could not read key from 
/etc/rndc.conf: file not found) = 55
futex(0xb7008048, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0xb7008044, {FUTEX_OP_SET, 0, 
FUTEX_OP_CMP_GT, 1}) = 1
rt_sigaction(SIGHUP, {0xb75c6160, ~[RTMIN RT_1], 0}, NULL, 8) = 0
rt_sigsuspend([]>  <unfinished ...>
------------------------------------------------------------------------

The two lines do not sound very funny:

open("/etc/rndc.conf.key", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or 
directory)
write(2, "could not read key from /etc/rndc"..., 55could not read key from 
/etc/rndc.conf: file not found) = 55

I gave the order to use /etc/rndc.conf but nsupdat use /etc/rndc.conf.key
and tell me /etc/rndc.conf not found.

This has now broken any scripts in my "dyndns" service  (under  ETCH  it
was working and now since 5 weeks it has stoped)

Thanks, Greetings and nice Day/Evening
    Michelle Konzack
    Systemadministrator


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
Michelle Konzack   Apt. 917                  ICQ #328449886
+49/177/9351947    50, rue de Soultz         MSN LinuxMichi
+33/6/61925193     67100 Strasbourg/France   IRC #Debian (irc.icq.com)

Attachment: signature.pgp
Description: Digital signature


--- End Message ---
--- Begin Message ---
Version: 1:9.10.3.dfsg.P4-12.3

Hi,

the bind9 bug list grew too much and the Debian BIND team cannot
simply test all the reported bugs against versions not in stable, so
this is mass bug close, as either the version is no longer relevant
(because of old-old-stable 9.8.x or old-stable 9.9.5 or even older
version of bind9) or the bug was already fixed.

However, if you can reproduce the bug with a current version in stable,
please use Debian BTS 'found <bug> <version_you_reproduced_the_issue>'
command to retag the bug and reopen it.

Cheers,
Ondrej

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to