Describe the bug
Hi! with verbosity: 4, tls-cert-bundle: set and forward-addr: 9.9.9.9@853#dns.quad9.net an entry with a quad9 certificate does not appear in the syslog (other certificates such as dns.google appear as expected).
if I change the settings to use-syslog: no with logfile: then the entry in the file appears as expected.

this may be related to another problem: restart of the syslog after the unbound start (restart, not relod) with the specified settings (verb4, quad9 DoT upstream with TLS verify), the unbound stops responding to requests and does not respond to unbound-control connections. only kill -KILL helps
last record in log will be like "debug: comm point listen_for_rw 19 0"

thanks in advance!

To reproduce
Steps to reproduce the behavior:

1. Change verbosity: to 4
2. Add forward-addr: 9.9.9.9@853 with tls-cert-bundle: directive
3. try to resolve some names

Expected behavior
send upstream cert to syslog if verb 4 set, dont hang on syslogd/syslog-ng restart

System:

• Unbound version: 1.13.1
• OS: OPNsense 21.7.1-amd64 FreeBSD 12.1-RELEASE-p19-HBSD OpenSSL 1.1.1k 25 Mar 2021
• unbound -V output:
  Version 1.13.1

Configure line: --with-ssl=/usr/local --with-libexpat=/usr/local --disable-dnscrypt --disable-dnstap --with-libnghttp2 --enable-ecdsa --disable-event-api --enable-gost --with-libevent --with-pyunbound=yes --with-pythonmodule=yes LDFLAGS=-L/usr/local/lib ac_cv_path_SWIG=/usr/local/bin/swig --disable-subnet --disable-tfo-client --disable-tfo-server --with-pthreads --prefix=/usr/local --localstatedir=/var --mandir=/usr/local/man --infodir=/usr/local/share/info/ --build=amd64-portbld-freebsd12.1
Linked libs: libevent 2.1.12-stable (it uses kqueue), OpenSSL 1.1.1k 25 Mar 2021
Linked modules: dns64 python respip validator iterator

BSD licensed, see LICENSE in source package for details.
Report bugs to unbound-bugs@nlnetlabs.nl or https://github.com/NLnetLabs/unbound/issues

Additional information
Add any other information that you may have gathered about the issue here.