[dnstap] dnstap not writing to unix domain sockets with unbound 1.5.10 on FreeBSD 11-STABLE.

[Murray Stokely]

I'm having trouble getting anything out of dnstap with unbound 1.5.10 on
FreeBSD 11-STABLE with dustup gocode freshly installed.

I've run the fstrm 0.2.0 unit tests on this box to verify that
reading/writing to the unix domain sockets is working properly (has anyone
evaluated GRPC rather than fstrm now that google has released a transport
for protocol buffers?)

The dnstap section of my unbound.conf is:


dnstap:

  dnstap-enable: yes

  dnstap-socket-path: "/var/run/unbound/dnstap.sock"

  dnstap-send-identity: yes

  dnstap-send-version: yes

  dnstap-log-resolver-response-messages: yes

  dnstap-log-client-query-messages: yes


I'm running unbound in a chroot, but I can't find the socket either in or
out of the chroot :


server:

  directory: /usr/local/etc/unbound

  chroot: /usr/local/etc/unbound


First I run two dustup listeners (as I'm not sure if its supposed to be
inside the chroot or not):


dnstap -u /var/run/unbound/dnstap.sock -w /root/dnstap.1

dnstap -u /usr/local/etc/unbound/var/run/unbound/dnstap.sock -w
/root/dnstap.2


Then I start unbound:


# sh /usr/local/etc/rc.d/unbound start

Obtaining a trust anchor:.

Starting unbound.

[1477374748] unbound[10467:0] debug: creating udp4 socket 0.0.0.0 53

[1477374748] unbound[10467:0] debug: creating tcp4 socket 0.0.0.0 53

[1477374748] unbound[10467:0] debug: switching log to syslog


unbound works fine, but I am not seeing anything written out to my
/root/dnstap files.


I spent a little time playing around with ktrace and dtrace but I haven't
yet really figured out what is going on or why it is not writing out logs.


Any pointers for debugging why messages don't seem to be getting sent to
the domain socket?  Thanks,


       - Murray
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.redbarn.org/pipermail/dnstap/attachments/20161024/0b1cba62/attachment.html>