Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 23 Feb 2015 15:44:25 -0600
From:      Mark Felder <feld@FreeBSD.org>
To:        freebsd-current@freebsd.org
Subject:   Re: Shared object "libsodium.so.13" not found, required by "dnscrypt-proxy"
Message-ID:  <1424727865.2482688.231426709.1C3F0A3A@webmail.messagingengine.com>
In-Reply-To: <CADGo8CURnvyLD55zs5m=hgrG9g6xct0q4ZMSNiY%2BzLA1GBi0Ug@mail.gmail.com>
References:  <CADGo8CURnvyLD55zs5m=hgrG9g6xct0q4ZMSNiY%2BzLA1GBi0Ug@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help


On Mon, Feb 23, 2015, at 12:43, Miguel Clara wrote:
> I don't think this is a 11-Current issue per say but probalby bad config,
> but since I'm using CURRENT I dicided to post to the list.
> 
> When my system boots dnscrypt fails to start with:
> 
> Shared object "libsodium.so.13" not found, required by "dnscrypt-proxy"
> 
> But manual start works without issue, I've resinstalled libsodium and
> dnscrypt from ports and I noticed "USE_LDCONFIG=   yes" is present in the
> Makefile for libsodium,
> 
> Running dmesg -a I see this relvant part:
> % dmesg -a | grep dns -A20
> Starting dnscrypt_proxy.
> Shared object "libsodium.so.13" not found, required by "dnscrypt-proxy"
> /etc/rc: WARNING: failed to start dnscrypt_proxy
> Starting local_unbound.
> Starting pflogd:
> Starting pflog.
> pflog0: promiscuous mode enabled
> Enabling pfNo ALTQ support in kernel
> ALTQ related functions disabled
> No ALTQ support in kernel
> ALTQ related functions disabled
> .
> add net fe80::: gateway ::1
> add net ff02::: gateway ::1
> add net ::ffff:0.0.0.0: gateway ::1
> add net ::0.0.0.0: gateway ::1
> add net default: gateway fe80::62a4:4cff:fe28:13c0%wlan0
> Waiting 30s for the default route interface: .....(no carrier)
> ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib
> /usr/local/lib/compat /usr/local/lib/gcc47 /usr/local/lib/libxul
> /usr/local/lib/nss /usr/local/llvm35/lib
> 32-bit compatibility ldconfig path: /usr/lib32 /usr/local/lib32/compat
> 
> So it seems that the issue is that ldconfig runs after the service is
> started and so when it starts I doens't know about the shared lib (or
> where
> to look for it)
> 
> How can I fix this behaviour?
> 

If you edit the dnscrypt-proxy rc script to say:

# REQUIRE: SERVERS cleanvar ldconfig

Does that help?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1424727865.2482688.231426709.1C3F0A3A>