Re: local_unbound segfaults at boot
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 > r...@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 > 23Munbound.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 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: local_unbound segfaults at boot
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 r...@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 23Munbound.core On Sun, 3 Jun 2018 14:09:45 -0500 Patrick McMunn wrote: > I believe the problem of local_unbound segfaulting began after I > compiled the source after the large commit to unbound on Saturday, > May 12, 2018 (about 3 weeks ago). > > I assumed the problem was probably common if I was experiencing it, > but I've seen no other mentions of it. I'm not sure what info I need > to provide, but will do so upon request. > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscr...@freebsd.org" -- Lars Schotte Mudroňova 13 92101 Piešťany ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
local_unbound segfaults at boot
I believe the problem of local_unbound segfaulting began after I compiled the source after the large commit to unbound on Saturday, May 12, 2018 (about 3 weeks ago). I assumed the problem was probably common if I was experiencing it, but I've seen no other mentions of it. I'm not sure what info I need to provide, but will do so upon request. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
