Re: sshd failure following errata 007 for 5.8
On 2015-11-02, Stuart Henderson wrote: [...] > So I think your system is messed up somehow. Your symptoms are more > like what would happen if you'd copied some old libcrypto.so.XX file > to libcrypto.so.35.0 and locally built various apps against that. > > In your position I'd probably boot the 5.8 installer and do an > 'upgrade' install over the top of your current system to make sure the > files are correct for 5.8. Then forcibly reinstall all packages with > > # PKG_PATH=http://ftp.fr.openbsd.org/pub/OpenBSD/5.8/packages/amd64/ > pkg_add -u -D installed [...] Thank you Stuart. I: - rebooted on bsd.rd - launched upgrade - pkg_add -u -D installed - restarted applying patches : as before - 001 fails during make : sshd.o: In function `main': sshd.c:(.text+0x414e): undefined reference to `do_authentication' monitor.o: In function `mm_answer_rsa_response': monitor.c:(.text+0x9e0): undefined reference to `auth_rsa_verify_response' monitor.o: In function `mm_answer_rsa_challenge': monitor.c:(.text+0xbd7): undefined reference to `auth_rsa_generate_challenge' monitor.o: In function `mm_answer_rsa_keyallowed': monitor.c:(.text+0xe41): undefined reference to `auth_rsa_key_allowed' monitor.o: In function `mm_answer_keyallowed': monitor.c:(.text+0x1faf): undefined reference to `auth_rhosts_rsa_key_allowed' collect2: ld returned 1 exit status *** Error 1 in sshd (:87 'sshd') *** Error 1 in /usr/src/usr.bin/ssh (:48 'all') - 004 fails. I then stopped patching and started thinking. Last month, our firewall experienced three times some sort of freezing (no way to login), of which I couldn't find any other way out than cold booting and some fsck work in the case of the second freeze. Because of limited time to operate, I put it back to work, but I'm wondering now if I shouldn't reinstall it from scratch. Olivier Debré
Re: sshd failure following errata 007 for 5.8
Stuart Henderson writes: > I'm not sure what happened here, there's no way that patch 007 would > do this, and in any event EVP_mdc2 was removed before 5.8 so shouldn't > be referenced by that sshd binary. > > Where did your base58 file come from? Hello Stuart. Thanks for your help. I downloaded: - base58.tgz from http://ftp.fr.openbsd.org/pub/OpenBSD/5.8/amd64/ - cd-src.tar.gz from http://ftp.fr.openbsd.org/pub/OpenBSD/5.8/ It appears to me now that other apps are broken, for instance wget: wget:/usr/lib/libcrypto.so.35.0: undefined symbol 'ENGINE_load_rsax' As I wrote in a message that I now discover I never sent :-), though not being a developer, I thought that all executables dynamically linked with libcrypto would break. Wget behavior looks to me as a confirmation of that. So, once again, I choose to: - wipe out /usr/src/ - put in place a fresh cd-src.tar.gz - put in place base58.tgz - not apply patches that failed for me: 001, 004 and 007. Olivier Debré
Re: Failure to upgrade 5.2 to 5.3 with softraid
Hello. Thanks a lot, Joel, for your kind and detailed suggestions. Here's what I did since yesterday, yielding the following positive result: 5.3 upgrade successful, but with one of the two disks removed. I did: - retried boot: no way, same message 'Using drive 0, partition 3' - removed one disk (sd0), reboot: same message 'Using drive 0, partition 3' - replaced removed disk, removed the other one (sd1): boot success, install/shell/upgrade prompt - 'sh MAKEDEV sd0 sd1', root disk=sd1/SR RAID 1, upgrade successful, reboot, sysmerge, deleted files as detailed in the upgrade guide, reboot. Now, what lies ahead looks furiously like RAID rebuild. Here's what I intend to do : - reinsert the disk that was out during the upgrade - reboot - if successful, check RAID state with bioctl (I identified previously the serials, and put a sticker on them) - rebuild. As concerns the softraid documentation, the fault is entirely mine: it's just concepts I'm not enough familiar with to run things while leniently sipping a cuba libre :-) During 5.2 install, now that I reread my notes, I notice that I had the exact same problems of non existent devices, and the necessity to create them/verify their existence, which I did haphazardly. Once again, thanks a lot for your help. Olivier Debré Le 15/05/2013 18:27, Joel Sing a écrit : On Thu, 16 May 2013, Joel Sing wrote: On Wed, 15 May 2013, tichodr...@free.fr wrote: Hello everyone. I failed to upgrade my server from 5.2 to 5.3, probably because of a bad answer to the 'Root filesystem?' question. Setup: - HP ProLiant MicroServer N40L server, amd64, GENERIC kernel - Two disks (sd0, sd1) in softraid (sd2) - I followed the 'Upgrading by install kernel' process, with the 5.3 version of bsd.rd which I placed in /. - at the 'Root filesystem? [sd0]' question, instead of accepting the first physical disk detected, I answered 'sd2', thinking that I shouldn't indicate a particular disk among the two physical ones. I followed a similar advice found on a couple of blog pages [1, 2]. Result: - At the end of the upgrade process, following message : Failed to install bootblocks. You will not be able to boot OpenBSD from sd2 - Indeed, can't boot anymore, boot process stalled with the following message: Using drive 0, partition 3 Loading... Sorry, I missed this part. This is unexpected/unusual. This may indicate that it managed to update the boot loader (in the softraid boot area), even though it failed to update the boot block (I need to check which order this is done in to confirm). This would potentially cause this problem. Which disk were you booting from and have you tried booting from the other disk? There is a good chance that you'll be able to boot from the second disk - failing that, repeat the upgrade process and make the missing device nodes as mentioned previously. - Powered off the server. Questions : - did I break things irremediably, hense will have to reinstall everything from scratch and backups? Nope, highly unlikely. The system will most likely boot, if not just repeat the upgrade. If it does boot you can manually update the boot blocks/boot loader: /usr/mdec/installboot -v /usr/mdec/boot /usr/mdec/biosboot sd2 It is just an error that occurred when installboot was run against the softraid volume. This is most likely due to missing device nodes for sd1 (e.g. /dev/sd1*). There is a current discussion on bugs@ regarding the same issue - for some reason I thought the installer already handled this, however it appears that it does not currently. As a work around, prior to starting the upgrade drop to a shell (for example, type '!' at the Root filesystem question) and ensure the device nodes exist: # cd /dev # sh MAKEDEV sd0 sd1 sd2 # exit The upgrade should now complete normally. - alternatively, should I try something else like removing one disk or the other, then try to rebuild the RAID? Thanks in advance. I must confess that the first softraid building and 5.2 install was a real pain for me, and I still do not fully grasp softraid, and the way it may interact with the upgrade process. How can we make it clearer? I need to spend some time working on the softraid documentation (hopefully in the not too distant future) - what do you need to know? Olivier Debre Refs. [1] http://spiritedblowfish.wordpress.com/2012/07/19/installing-openbsd-5-1-a md 64-using-softraid/ [2] http://blog.cochard.me/2012/03/openbsd-51-installation-on-sofraid4.html
Re: Failure to upgrade 5.2 to 5.3 with softraid
I notice Peter's message just now. Thanks a lot to you too, Peter. I think what you write is coherent with what I experienced and what Joel suggested too. You were more careful than I was, when you didn't reboot but created the devices! I won't give it a try right now that I managed to crawl out of quicksand But I'll keep that in mind (and notes) for the next upgrade, for sure. Le 16/05/2013 12:28, tichodroma a écrit : Hello. Thanks a lot, Joel, for your kind and detailed suggestions. Here's what I did since yesterday, yielding the following positive result: 5.3 upgrade successful, but with one of the two disks removed. I did: - retried boot: no way, same message 'Using drive 0, partition 3' - removed one disk (sd0), reboot: same message 'Using drive 0, partition 3' - replaced removed disk, removed the other one (sd1): boot success, install/shell/upgrade prompt - 'sh MAKEDEV sd0 sd1', root disk=sd1/SR RAID 1, upgrade successful, reboot, sysmerge, deleted files as detailed in the upgrade guide, reboot. Now, what lies ahead looks furiously like RAID rebuild. Here's what I intend to do : - reinsert the disk that was out during the upgrade - reboot - if successful, check RAID state with bioctl (I identified previously the serials, and put a sticker on them) - rebuild. As concerns the softraid documentation, the fault is entirely mine: it's just concepts I'm not enough familiar with to run things while leniently sipping a cuba libre :-) During 5.2 install, now that I reread my notes, I notice that I had the exact same problems of non existent devices, and the necessity to create them/verify their existence, which I did haphazardly. Once again, thanks a lot for your help. Olivier Debré Le 15/05/2013 18:27, Joel Sing a écrit : On Thu, 16 May 2013, Joel Sing wrote: On Wed, 15 May 2013, tichodr...@free.fr wrote: Hello everyone. I failed to upgrade my server from 5.2 to 5.3, probably because of a bad answer to the 'Root filesystem?' question. Setup: - HP ProLiant MicroServer N40L server, amd64, GENERIC kernel - Two disks (sd0, sd1) in softraid (sd2) - I followed the 'Upgrading by install kernel' process, with the 5.3 version of bsd.rd which I placed in /. - at the 'Root filesystem? [sd0]' question, instead of accepting the first physical disk detected, I answered 'sd2', thinking that I shouldn't indicate a particular disk among the two physical ones. I followed a similar advice found on a couple of blog pages [1, 2]. Result: - At the end of the upgrade process, following message : Failed to install bootblocks. You will not be able to boot OpenBSD from sd2 - Indeed, can't boot anymore, boot process stalled with the following message: Using drive 0, partition 3 Loading... Sorry, I missed this part. This is unexpected/unusual. This may indicate that it managed to update the boot loader (in the softraid boot area), even though it failed to update the boot block (I need to check which order this is done in to confirm). This would potentially cause this problem. Which disk were you booting from and have you tried booting from the other disk? There is a good chance that you'll be able to boot from the second disk - failing that, repeat the upgrade process and make the missing device nodes as mentioned previously. - Powered off the server. Questions : - did I break things irremediably, hense will have to reinstall everything from scratch and backups? Nope, highly unlikely. The system will most likely boot, if not just repeat the upgrade. If it does boot you can manually update the boot blocks/boot loader: /usr/mdec/installboot -v /usr/mdec/boot /usr/mdec/biosboot sd2 It is just an error that occurred when installboot was run against the softraid volume. This is most likely due to missing device nodes for sd1 (e.g. /dev/sd1*). There is a current discussion on bugs@ regarding the same issue - for some reason I thought the installer already handled this, however it appears that it does not currently. As a work around, prior to starting the upgrade drop to a shell (for example, type '!' at the Root filesystem question) and ensure the device nodes exist: # cd /dev # sh MAKEDEV sd0 sd1 sd2 # exit The upgrade should now complete normally. - alternatively, should I try something else like removing one disk or the other, then try to rebuild the RAID? Thanks in advance. I must confess that the first softraid building and 5.2 install was a real pain for me, and I still do not fully grasp softraid, and the way it may interact with the upgrade process. How can we make it clearer? I need to spend some time working on the softraid documentation (hopefully in the not too distant future) - what do you need to know? Olivier Debre Refs. [1] http://spiritedblowfish.wordpress.com/2012/07/19/installing-openbsd-5-1-a md 64-using-softraid/ [2] http://blog.cochard.me/2012/03/openbsd-51-installation-on-sofraid4.html
Failure to upgrade 5.2 to 5.3 with softraid
Hello everyone. I failed to upgrade my server from 5.2 to 5.3, probably because of a bad answer to the 'Root filesystem?' question. Setup: - HP ProLiant MicroServer N40L server, amd64, GENERIC kernel - Two disks (sd0, sd1) in softraid (sd2) - I followed the 'Upgrading by install kernel' process, with the 5.3 version of bsd.rd which I placed in /. - at the 'Root filesystem? [sd0]' question, instead of accepting the first physical disk detected, I answered 'sd2', thinking that I shouldn't indicate a particular disk among the two physical ones. I followed a similar advice found on a couple of blog pages [1, 2]. Result: - At the end of the upgrade process, following message : Failed to install bootblocks. You will not be able to boot OpenBSD from sd2 - Indeed, can't boot anymore, boot process stalled with the following message: Using drive 0, partition 3 Loading... - Powered off the server. Questions : - did I break things irremediably, hense will have to reinstall everything from scratch and backups? - alternatively, should I try something else like removing one disk or the other, then try to rebuild the RAID? Thanks in advance. I must confess that the first softraid building and 5.2 install was a real pain for me, and I still do not fully grasp softraid, and the way it may interact with the upgrade process. Olivier Debre Refs. [1] http://spiritedblowfish.wordpress.com/2012/07/19/installing-openbsd-5-1-amd64-using-softraid/ [2] http://blog.cochard.me/2012/03/openbsd-51-installation-on-sofraid4.html
