On Mon, Nov 2, 2015, at 06:10 PM, Dutch Ingraham wrote: > Hi all: > > I just installed 5.8 on the x86_64 arch. Immediately after installing, > I upgraded to -current. Upon rebooting into the new -current, a number > of errors appeared in the dmesg after the network started. The first > error was: > > ssh-keygen: can't load library 'libcrypto.so.36.1' > > A cascade of errors followed: syslogd, pflogd, ntpd, and smtpd. > > In fact, I don't have 'libcrypto.so.36.1' but 'libcrypto.so.35.0.' > > Did I possibly miss something obvious in the upgrade (??) or should I > take this over to tech@?
I just experienced the same thing several hours ago. I’ve been using the Nov 1 and Nov 2 snapshots on several machines and VMs but I did a new install of the Nov 2 snapshot in a new VM and ran into this error. I don’t have libcrypto.so. at all but only libcrypto.a and one other form. Just to be sure something wasn’t wrong with install58.iso, I rebooted into bsd.rd and did an upgrade and pulled the sets from the master site and nothing changed. Still the same errors and no libcrypto.so.36.1. Bryan
