From owner-freebsd-ports-bugs@freebsd.org Thu Apr 7 13:25:39 2016 Return-Path: Delivered-To: freebsd-ports-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 E2248B06AE4 for ; Thu, 7 Apr 2016 13:25:39 +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 AA3741C66 for ; Thu, 7 Apr 2016 13:25:39 +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 u37DPdxP044607 for ; Thu, 7 Apr 2016 13:25:39 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 208529] Error setting up SSL_CTX client key and cert and control-enable: no Date: Thu, 07 Apr 2016 13:25:39 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: cyclaero@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2016 13:25:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208529 cyclaero@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cyclaero@gmail.com --- Comment #2 from cyclaero@gmail.com --- I found the culprit. It lies in the local_unbound_poststart() sub-routine in file /etc/rc.d/local_unbound. Said sub-routine has been newly introduced wi= th RELEASE-10.3. For checking the online status of Unbound the remote control tool unbound-control is utilized, which is disabled by default, and not properly setup on most machines. In my file /etc/rc.d/local_unbound I commented out he body of local_unbound_poststart(): Code: # # After starting, wait for Unbound to report that it is ready to avoid # race conditions with services which require functioning DNS. # local_unbound_poststart() { # local retry=3D5 # # echo -n "Waiting for nameserver to start..." # until "${command}-control" status | grep -q "is running" ; do # if [ $((retry -=3D 1)) -eq 0 ] ; then # echo " giving up" # return 1 # fi # echo -n "." # sleep 1 # done # echo " good" } This solved the problem for me. I am using Unbound since 2 years, and I nev= er saw any race conditions, anyway. If we really need to check whether Unbound= is running, why not simply run `drill localhost @127.0.0.1`, or something simi= lar along this line. The additional benefit of this would be, that the timing o= ut feature is built-in to the drill command. --=20 You are receiving this mail because: You are the assignee for the bug.=