Re: Stange logs filling my /var/log/messages
- In reply to: Dave Cottlehuber: "Re: Stange logs filling my /var/log/messages"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 29 Mar 2024 11:42:14 UTC
On Fri, Mar 29, 2024 at 2:24 PM Dave Cottlehuber <dch@skunkwerks.at> wrote: > On Fri, 29 Mar 2024, at 11:39, Dieter Schön 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’t the erlang one, which lives under > /usr/local/lib/erlang*/lib/… > > > Am 29. März 2024 11:27:51 MEZ schrieb Odhiambo Washington < > odhiambo@gmail.com>: > >> Hello all, > >> > >> I am suddenly seeing hundreds of log entries like the below in > /var/log/messages: > >> > >> Mar 29 00:01:01 gw python[45994]: unable to dlopen > /usr/local/lib/sasl2/libotp.so.3: Shared object "libopie.so.8" not found, > required by "libotp.so.3" > >> Mar 29 00:02:01 gw python[85428]: unable to dlopen > /usr/local/lib/sasl2/libotp.so.3: Shared object "libopie.so.8" not found, > required by "libotp.so.3" > >> Mar 29 00:02:01 gw python[86114]: unable to dlopen > /usr/local/lib/sasl2/libotp.so.3: Shared object "libopie.so.8" not found, > required by "libotp.so.3" > >> Mar 29 00:03:01 gw python[26886]: unable to dlopen > /usr/local/lib/sasl2/libotp.so.3: Shared object "libopie.so.8" not found, > required by "libotp.so.3" > >> > >> Given that I haven't installed anything new in the last several weeks, > I am wondering what it is that could be causing this. > >> > > This appears to be some python program failing. > > See > https://lists.freebsd.org/archives/freebsd-ports/2024-January/005169.html > it suggests you have partially updated libraries from FreeBSD 13.x or > earlier to FreeBSD 14.x > > Why it started recently I can’t say without more info. > > To fix this make sure your Userland and ports match your kernel, and check > your ports are all up to date. > > A+ > Dave > Thanks for this response. I have been running 14-RELEASE for several months now and never saw these. Plus, I don't even know any use case for sasl2 on my system. I am running 'portupgrade -a` now to see if that will help. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]