Date: Thu, 07 Apr 2016 13:25:39 +0000 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 Message-ID: <bug-208529-13-u39jupPFaj@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-208529-13@https.bugs.freebsd.org/bugzilla/> References: <bug-208529-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-208529-13-u39jupPFaj>