Solved upgrade to 12.0-RELEASE-p5 issue

R

roundkat

I recently upgrade from 12.0-RELEASE-p3 to 12.0-RELEASE-p5
Spamd is run in blacklist mode

rc.conf
Code: 
spamd_black="YES"
obspamd_enable="YES"
obspamlogd_enable="YES"

Ran into this issue

Starting obspamd.
ld-elf.so.1: Shared object "libcrypto.so.8" not found, required by "spamd"
/usr/local/etc/rc.d/obspamd: WARNING: failed to start obspamd

I found a bug that seemed related so I ran
Code: 
pkg upgrade -f
but that did not fix the issue
--
in /lib
libcrypto.so.8 did not exist
only
libcrypto.so.111
I created a symlink
My workaround - Experts please comment.
Code: 
 libcrypto.so.8 -> libcrypto.so.111

starting obspamd and obspamlogd did work..
Verified pf was working
Code: 
tcpdump -n -e -ttt -i pflog0
listening on pflog0, link-type PFLOG (OpenBSD pflog file), capture size 262144 bytes
00:00:00.000000 rule 22/0(match): block in on em0: 10.3.0.1.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 366
00:00:02.012971 rule 22/0(match): block in on em0: 10.3.0.1.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 366
00:00:19.146325 rule 22/0(match): block in on em0: 10.3.0.1.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 316
00:00:02.008546 rule 22/0(match): block in on em0: 10.3.0.1.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 316

4 packets captured
4 packets received by filter
0 packets dropped by kernel

thx
 
roundkat said:
I recently upgrade from 12.0-RELEASE-p3 to 12.0-RELEASE-p5
Spamd is run in blacklist mode

rc.conf
Code: 
spamd_black="YES"
obspamd_enable="YES"
obspamlogd_enable="YES"

Ran into this issue

Starting obspamd.
ld-elf.so.1: Shared object "libcrypto.so.8" not found, required by "spamd"
/usr/local/etc/rc.d/obspamd: WARNING: failed to start obspamd

I found a bug that seemed related so I ran
Code: 
pkg upgrade -f
but that did not fix the issue
--
in /lib
libcrypto.so.8 did not exist
only
libcrypto.so.111
I created a symlink
My workaround - Experts please comment.
Code: 
 libcrypto.so.8 -> libcrypto.so.111

starting obspamd and obspamlogd did work..
Verified pf was working
Code: 
tcpdump -n -e -ttt -i pflog0
listening on pflog0, link-type PFLOG (OpenBSD pflog file), capture size 262144 bytes
00:00:00.000000 rule 22/0(match): block in on em0: 10.3.0.1.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 366
00:00:02.012971 rule 22/0(match): block in on em0: 10.3.0.1.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 366
00:00:19.146325 rule 22/0(match): block in on em0: 10.3.0.1.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 316
00:00:02.008546 rule 22/0(match): block in on em0: 10.3.0.1.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 316

4 packets captured
4 packets received by filter
0 packets dropped by kernel


thx
Click to expand...

The libcrypto likely now has a new version. Update your system via ports/pkgs. That's another common case. Such a fix works but it is better to do an update.
 
Do 'freebsd-version -ku'
You may have different versions. Such a lib might require kernel update, not only userland, in order to be updated.
 
Code: 
12.0-RELEASE-p5
Fri May 31 05:32:08 /boot
root@-#freebsd-version -ku
12.0-RELEASE-p4
12.0-RELEASE-p5

This may be the issue ...
I will leave in place for now until the next update..
Thank you
 
I doubt that very much. -p4 and -p5 is the same kernel on e.g. amd64. And the kernel has nothing to do with versions of shared libraries.

FreeBSD 12 has OpenSSL 1.1.1 -- so there never was a /lib/libcrypto.so.8 in FreeBSD 12. The problem is with your package. If you install binary packages, you might somehow have a package that is meant for FreeBSD 11. If you compile yourself, it could be the same thing, or it was compiled to use an OpenSSL from ports and wasn't upgraded properly.
 
I just use packages and have found that spamd is not in FreeBSD 12.
Code: 
11.2-RELEASE-p10
Fri May 31 05:03:55 ~/scripts
root@-#pkg search  spamd-4.9.1_4
spamd-4.9.1_4                  Traps spammers with a very slow smtp-login and return 4xx error
found this thread about OpenBSD's spamd.
 
port is fixed, I will install the port and then wait for the package..
Thanks to all ...
This can be marked as Solved..
 
You must log in or register to reply here.
Back
Top