Summary: | /usr/bin/ssh: Undefined symbol "ssh_lowercase" | ||
---|---|---|---|
Product: | Base System | Reporter: | Dan Busarow <dan> |
Component: | bin | Assignee: | freebsd-bugs (Nobody) <bugs> |
Status: | Closed FIXED | ||
Severity: | Affects Only Me | CC: | cperciva, dvl, emaste |
Priority: | --- | ||
Version: | 9.3-RELEASE | ||
Hardware: | Any | ||
OS: | Any |
Description
Dan Busarow
2015-01-15 17:40:52 UTC
What architecture is this? This appears to be related to this PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196760 I'm setting up environments to reproduce and debug this now. Also, can you provide the previous FreeBSD version, if possible? Old release was 9.3-RELEASE-p5 Problem has been resolved. there was no /usr/lib/private and therefore none of the libssh* files were in /usr/lib/private I copied those from another box and all is good now. My question now is where did /usr/lib/private go??? I ssh'd into the box in order to run freebsd-update so ssh was working before the freebsd-update install Were /usr/lib/private/libssh.a /usr/lib/private/libssh.so.5 /usr/lib/private/libssh_p.a not used in p5 or should I be looking for a flaky drive? Thanks, Dan Can you show output of 'file /bin/sh' ? It was discovered in another report that a prior upgrade to 9.3-RELEASE from 9.2-RELEASE was incomplete. 9.3-RELEASE (and all subsequent releases) should have /usr/lib/private, so if that is missing on your system, you will run into issues in the future. It's important to know what FreeBSD version sh(1) is. This was an upgrade from 9.2-RELEASE to 9.3-RELEASE done via freebsd-update -r 9.3-RELEASE upgrade I don't remember any problem with the upgrade but I guess I may have missed something in the install reboot install cycle Here's the file /bin/sh output doheny:/home/dan $ file /bin/sh /bin/sh: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically linked (uses shared libs), for FreeBSD 9.2, stripped Ahh, one of my others shows /bin/sh: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically linked (uses shared libs), for FreeBSD 9.3, stripped Suggestions? Thanks, Dan Ok, so this is the third of these exhibiting the exact same behavior. I'm doing an update on a VM from 9.2-RELEASE -> 9.3-RELEASE, skipping the userland update to try to identify a proper fix. In the meantime, I've CC'd cperciva@ for any input he could provide. Colin, it may be worth evaluating 'uname -K' and 'uname -U' upon freebsd-update(8) invocation and yell loudly when they do not match, so people do not shoot their foots off like this. Thoughts? Dan B: I am trying an upgrade method tested by others. I will get back with the results. Dan B: the ticket Glen references now has the update I did. Worked for me. Let us know. Dan L, You mean env UNAME_r=9.2-RELEASE freebsd-update upgrade -r 9.3-RELEASE freebsd-update install freebsd-update install and perhaps a third: freebsd-update install worked for you? Upgrade the upgrade? Force it to run by specifying UNAME? Thanks for following up. Dan Yes. That's what I did. Exactly. Cool. I'll test it out on a less critical machine and then go ahead and re-upgrade this one. Thanks, Dan Just to really close this ticket out I wanted to note that I did follow Dan L's advice and ran env UNAME_r=9.2-RELEASE freebsd-update upgrade -r 9.3-RELEASE freebsd-update install I tried it a couple of times on virtualbox and everything went fine. So I ran it on this production server and it ran fine here too. Didn't even need a reboot. Thanks all. Dan |