From owner-freebsd-bugs@freebsd.org Tue Oct 20 18:15:28 2015 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 00841A1ACBC for ; Tue, 20 Oct 2015 18:15:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C837DD75 for ; Tue, 20 Oct 2015 18:15:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t9KIFRsp096532 for ; Tue, 20 Oct 2015 18:15:27 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 203901] 'service local_unbound reload' stops name resolution inside jails (but not on host) Date: Tue, 20 Oct 2015 18:15:27 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: fre.fbsdpr@expertmaker.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Oct 2015 18:15:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203901 Bug ID: 203901 Summary: 'service local_unbound reload' stops name resolution inside jails (but not on host) Product: Base System Version: 10.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: fre.fbsdpr@expertmaker.com Created attachment 162258 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=162258&action=edit local_unbound verbosity 4 debug output Hi, I did some unbound config changes and, since this was on a critical production system, thought a 'reload' would be more safe than a 'restart'. This, however, bit me, since I did only check if name resolution was still working on the host. A 'service local_unbound restart' will make it work inside jails again. Jails are configured on a separate loopback interface (not lo0) and on a host local 10.x.x.x/28 network. Host has "nameserver 127.0.0.1" in /etc/resolv.conf and jails have "nameserver 10.x.x.1". Something that also caught my eye was, when doing a host# service local_unbound reload unbound-checkconf: no errors in /var/unbound/unbound.conf I see a "Restart" message in /var/log/messages, Oct 20 00:04:07 host unbound: [59371:0] notice: Restart of unbound 1.4.22. Oct 20 00:04:07 host unbound: [59371:0] notice: init module 0: validator Oct 20 00:04:07 host unbound: [59371:0] notice: init module 1: iterator whereas, for a host# service local_unbound restart Stopping local_unbound. Waiting for PIDS: 59371. Starting local_unbound. I do not, Oct 20 00:03:25 host unbound: [59371:0] notice: init module 0: validator Oct 20 00:03:25 host unbound: [59371:0] notice: init module 1: iterator For verbosity level 4 debug output for the 'reload'/SIGHUP and 'restart'/SIGTERM respectively, see attached file. There are some differences but, lacking time and resources, we have not investigated further. Instead we came to the conclusion that, for now, a 'service local_unbound reload' is unsafe and should never be used. -- You are receiving this mail because: You are the assignee for the bug.