Date: Fri, 29 Mar 2024 12:24:22 +0100 From: "Dave Cottlehuber" <dch@skunkwerks.at> To: =?UTF-8?Q?Dieter_Sch=C3=B6n?= <dieter@schoen.or.at>, questions@freebsd.org, odhiambo@gmail.com Subject: Re: Stange logs filling my /var/log/messages Message-ID: <db03b49a-6dfb-4913-9feb-e0aada34ec66@app.fastmail.com> In-Reply-To: <4F6A6002-2913-4E11-A12A-9E5E352D855D@schoen.or.at> References: <CAAdA2WNKnDXcaD1SL0696gWy1QkMgQL6vwPpvWMz2XYiTXPM9Q@mail.gmail.com> <4F6A6002-2913-4E11-A12A-9E5E352D855D@schoen.or.at>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 29 Mar 2024, at 11:39, Dieter Sch=C3=B6n wrote: > Hi, > > sasl is a component of Erlang OTP. > Maybe now you can make some connections? > CouchDB and some other packages are built with erlang. This SASL isn=E2=80=99t the erlang one, which lives under /usr/local/lib= /erlang*/lib/=E2=80=A6 > Am 29. M=C3=A4rz 2024 11:27:51 MEZ schrieb Odhiambo Washington <odhiam= bo@gmail.com>: >> Hello all, >>=20 >> I am suddenly seeing hundreds of log entries like the below in /var/l= og/messages: >>=20 >> Mar 29 00:01:01 gw python[45994]: unable to dlopen /usr/local/lib/sas= l2/libotp.so.3: Shared object "libopie.so.8" not found, required by "lib= otp.so.3" >> Mar 29 00:02:01 gw python[85428]: unable to dlopen /usr/local/lib/sas= l2/libotp.so.3: Shared object "libopie.so.8" not found, required by "lib= otp.so.3" >> Mar 29 00:02:01 gw python[86114]: unable to dlopen /usr/local/lib/sas= l2/libotp.so.3: Shared object "libopie.so.8" not found, required by "lib= otp.so.3" >> Mar 29 00:03:01 gw python[26886]: unable to dlopen /usr/local/lib/sas= l2/libotp.so.3: Shared object "libopie.so.8" not found, required by "lib= otp.so.3" >>=20 >> Given that I haven't installed anything new in the last several weeks= , I am wondering what it is that could be causing this. >>=20 This appears to be some python program failing. See=20 https://lists.freebsd.org/archives/freebsd-ports/2024-January/005169.htm= l it suggests you have partially updated libraries from FreeBSD 13.x or = earlier to FreeBSD 14.x=20 Why it started recently I can=E2=80=99t say without more info. To fix this make sure your Userland and ports match your kernel, and che= ck your ports are all up to date. A+ Dave
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?db03b49a-6dfb-4913-9feb-e0aada34ec66>