local_unbound segfaults at boot
Herbert J. Skuhra
herbert at gojira.at
Sun Jul 15 08:40:13 UTC 2018
On Sun, 15 Jul 2018 03:19:11 +0200, Lars Schotte wrote:
>
> I see segfaulting too:
>
> FreeBSD wasp.2km.casa 12.0-CURRENT FreeBSD 12.0-CURRENT #6 r336229: Fri Jul 13 01:51:31 CEST 2018 root at wasp.2km.casa:/usr/obj/usr/src/amd64.amd64/sys/GUSTIK amd64
> # service local_unbound restart
> local_unbound not running? (check /var/run/local_unbound.pid).
> Starting local_unbound.
> Segmentation fault (core dumped)
> /etc/rc.d/local_unbound: WARNING: failed to start local_unbound
>
> # du -sh unbound.core
> 23M unbound.core
unbound binaries were renamed to local-unbound.
https://svnweb.freebsd.org/base?view=revision&revision=333573
# ls -l /usr/sbin/*unbound*
-r-xr-xr-x 1 root wheel 150416 Jul 10 16:17 /usr/sbin/local-unbound
-r-xr-xr-x 1 root wheel 47944 Jul 10 16:17 /usr/sbin/local-unbound-anchor
-r-xr-xr-x 1 root wheel 35608 Jul 10 16:17 /usr/sbin/local-unbound-checkconf
-r-xr-xr-x 1 root wheel 39736 Jul 10 16:17 /usr/sbin/local-unbound-control
-r-xr-xr-x 1 root wheel 11030 Jul 10 16:17 /usr/sbin/local-unbound-setup
Did you forget to run mergemaster, 'make delete-old' and 'make
delete-old-libs' after the upgrade?
--
Herbert
More information about the freebsd-current
mailing list