Ticket #330 (closed defect: fixed)

Opened 3 years ago

Last modified 18 months ago

pdns-recursor doesn't respond to rec_control after reloading erroneous ACL file

Reported by: anon Owned by: ahu
Priority: normal Milestone:
Component: recursor Version:
Severity: normal Keywords:
Cc: gimre@…

Description

First we check with a correct ACL file:

gimre@voy:~$ cat /tmp/foo.lst 127.0.0.1 gimre@voy:~$ grep foo /tmp/recursor.conf allow-from-file=/tmp/foo.lst

gimre@voy:~$ sudo /tmp/pdns-recursor-3.3.1/rec_control --config-dir=/tmp reload-acls ok

Then we write something in the ACL file, which cannot be parsed:

gimre@voy:/tmp/pdns-recursor-3.3.1$ echo "uuuuu" > /tmp/foo.lst gimre@voy:/tmp/pdns-recursor-3.3.1$ sudo ./rec_control --config-dir=/tmp reload-acls Fatal: Unable to receive message over control channel: Success

In the logs we see the following error message:

Dec 15 00:10:37 Exception: Unable to convert 'uuuuu' to a netmask

After this, the recursor does not respond to any rec_control commands OR USR1 signal (for stats). Only a restart seems to work.

gimre@voy:~$ echo "127.0.0.1" > /tmp/foo.lst gimre@voy:~$ sudo /tmp/pdns-recursor-3.3.1/rec_control --config-dir=/tmp reload-acls Fatal: Unable to receive message over control channel: Success

Change History

Changed 18 months ago by peter

3.4-pre just exits when this happens (also note that it would not start up when this happens, either).

Changed 18 months ago by peter

  • status changed from new to closed
  • resolution set to fixed

Fixed in r2323!

Note: See TracTickets for help on using tickets.