Date: Fri, 21 Dec 2018 05:29:28 +0100 From: Patrick Peterson <laskina@free.fr> To: questions@freebsd.org Subject: INV# 18532492629309601591764306518061967147404919947962337617160235777359595151087098695149 Message-ID: <a1cbc567105112e6162f68c97d85f647@free.fr>
next in thread | raw e-mail | index | archive | help
Please find attached remittance advice. If you require any further information please do not hesitate to contact us. Regards, Patrick Peterson T +44 2 3970 7451 F +44 2 7756 8746 From owner-freebsd-questions@freebsd.org Fri Dec 21 05:25:54 2018 Return-Path: <owner-freebsd-questions@freebsd.org> Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1EE57133DFAE for <freebsd-questions@mailman.ysv.freebsd.org>; Fri, 21 Dec 2018 05:25:54 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AC9F786E72 for <freebsd-questions@freebsd.org>; Fri, 21 Dec 2018 05:25:52 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.101.127]) by mrelayeu.kundenserver.de (mreue012 [212.227.15.167]) with ESMTPA (Nemesis) id 1MDeAZ-1gii2p0qUJ-00Ao4H; Fri, 21 Dec 2018 06:25:44 +0100 Date: Fri, 21 Dec 2018 06:25:43 +0100 From: Polytropon <freebsd@edvax.de> To: Scott Ballantyne <boyvalue@gmail.com> Cc: FreeBSD <freebsd-questions@freebsd.org> Subject: Re: Upgrade to 11.2 failure Message-Id: <20181221062543.d0d367c7.freebsd@edvax.de> In-Reply-To: <CAESeg0wTzdnatF0BNynCUTLXgN0wcke-=j8DMR8NTo+Y05LPHQ@mail.gmail.com> References: <CAESeg0wTzdnatF0BNynCUTLXgN0wcke-=j8DMR8NTo+Y05LPHQ@mail.gmail.com> Reply-To: Polytropon <freebsd@edvax.de> Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:jnRwYoAKJVK7oZ6WWCQqluQVb2+WYq5TGoPxXk1qOsRTFEDu7zt Sm5JzBFWBHHeedQd2Nkp86Y3MHW2Am+jRY30VL9m38z11aEL79uYC0Xg65jt6ouEtzHy9IV G0FzV5SP+ugg934x94mNwrOuSMCZqGXL07mumX2C+FFh5NdARnlpXofJJbVSGWBiPFNd+tH w6iBA3Z1A78Mf1Se5oapw== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:B6bn083S1m4=:FSmW+9IiStbJnFYZreeYKx kC6NoMVfcOibANuEKLnrlJ/x2nojOo5nfCDIqxnC6iaQqt0ovSY7jeG+WMxqenPrxoe/O+LcX P2/lZt4u6FRttiqh/ydUkz2JorrHu0aKC7BQ89WTcsA5vvPBVbzMctlGGbMWhBQ7wIpiaWexc gE5f/3ehRLptHuG+68niln14GK1OjT/xZBJjTK0UcVZhzmDZiIOdhDIVmh5A9yDg4TvFWu3f6 +fGDkKKDYj9Fx+5Gp3R67ph+CoUH8mCRQVL4sJ2c4Apj1gpGqOl5bpKFE2ZX8MKNaCYIAYjG9 Md/lGVyCjuNCxheN1gOFWA3tyLLFDcUEEBEiicndZubIdJ21KzA8xXe9JH8flvk1EYZqN5tCy 3IWv/7rhGbznjJtepHDZ1tm/rSfZW69706BkxtYvH847ALt5CphP0OM/c2okXRLtdC41MCdJe mB1S5cJDhFpVdhZavrbRRI9Sn6dUyo/HkNOkUWB6ntBi4EnkZUAEV74oZXsIUZidXBoV6/aY3 Dp8vkMI1W7xN9/DTA1uN47tu1N536BNm6ub7taNGdxNu4vfri7i93uEc8CXDWl4ZVrS0gyGYA do/aXpcrFa9G3C5H6p+sHcFd4fo22mYQxYYt0j4vJXRczIgsUHGrmy5LZUcf38Ek6QMn55hcD n7wqmU9GXdPOd4eWM6UMdEMqKQDApsaDnRTCVBAA3KL3K1LQsvopiUbX0GtAt/Gijf7EaOAXU dlVWHOt0u9y5lQ1mQg8TToYZO6FJbp9N3jNCewtD6rqoO3qsLwflAAWWjEg= X-Rspamd-Queue-Id: AC9F786E72 X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [3.55 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[freebsd@edvax.de]; MV_CASE(0.50)[]; HAS_ORG_HEADER(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[mx00.schlund.de,mx01.schlund.de]; RCPT_COUNT_TWO(0.00)[2]; FREEMAIL_TO(0.00)[gmail.com]; RECEIVED_SPAMHAUS_PBL(0.00)[127.101.195.92.zen.spamhaus.org : 127.0.0.10]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.16)[-0.158,0]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(0.81)[0.810,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[edvax.de]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.46)[0.465,0]; RCVD_IN_DNSWL_NONE(0.00)[131.126.227.212.list.dnswl.org : 127.0.5.0]; MID_CONTAINS_FROM(1.00)[]; R_SPF_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(0.04)[ipnet: 212.227.0.0/16(-0.30), asn: 8560(0.53), country: DE(-0.01)] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions <freebsd-questions.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>; List-Post: <mailto:freebsd-questions@freebsd.org> List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 21 Dec 2018 05:25:54 -0000 On Thu, 20 Dec 2018 13:51:59 -0500, Scott Ballantyne wrote: > I'm running 10.4, so the obvious thing to do (which a few people pointed > out) > was to upgrade to 11.2 or 12.x. Depends. In my (very individual) opinion, the obviois thing to do would be to install 12.0 directly, instead of using the freebsd-update tool. Allow me to share my experience so far: When updating FreeBSD _within_ a certain major version number, using freebsd-update usually does a wonderful job, especially on "boring servers", systems that do not run anything one would call "special", and especially not Firefox or Emacs. :-) But when switching from one major version to the next, or even worse, from version n to version n+2 or n+3 (yes, that can also happen!), doing a fresh install seems to be the easiest way. I make a list of "top ports", those software pieces I actually want to use, and I don't care about their dependencies as pkg can resolve them on its own. Then I install the fresh OS, and feed the list into pkg. Finally I pull configuration files from backup / CVS and make the neccessary adjustments. This of course only works when you can have scheduled downtime, but I usually make sure this is being arranged properly. Changes that require you to adjust configuration files can happen on two fronts: first the OS, then the software from ports you're using. Taking configurations and using them 1:1 doesn't always work. As it has been discussed in an earlier thread, dependencies also might change (new ones appearing, old ones disappearing, required version numbers changing), so having pkg deal with them is the most convenient thing. Of course, the OS libraries are different after a major version upgrade, so you will have to pay attention to that fact, especially as pkg is a port, and not really part of the OS (the base system); the /usr/sbin/pkg program is just a stub. So the first thing you need to do after the OS update is to update pkg, either by using the stub as "pkg-static upgrade -f", or you reinstall it from ports (after "portnap fetch extract"). It's also important to make sure that pkg's and portsnap's configuration files use the same source ("Latest" or "Quarterly", as the default source changed during FreeBSD 11, if I remember correctly). > I've used FreeBSD-update many times, no problems. So I proceeded to do this. > All went as expected until the pkg-static upgrade -f step, which core > dumped. i ran > a debugger on it, but it is compiled with no symbols, so I can't give much > more detail. There could be a simple explanation: If you call "pkg-static", /usr/local/sbin/pkg-static will be used, which is obsolete as it matches the previous OS version. You could try to explicitely use the OS-provided stub to upgrade the installed pkg first. > Out of curiosity, I ran pkg-static to update my emacs. That identified > hundreds of > binaries whose ABI had changed, so I updated those. Again, this is to be expected due to the OS version change. > pkg-static upgrade -f > still > seg faulted after that, so I tried pkg-static autoremove after which it > updated > a few files. I finished with the required final run of freebsd-install and > rebooted. What is "freebsd-install"? Do you mean "freebsd-update"? You should have completed all its steps _before_ turning to ports. > Now I couldn't login at all. The system wasn't recognizing my credentials. > I booted to single-user, thinking > that perhaps I had made an error in editing the password files during the > merge, but they were fine. Has the pkd_mkdb step been performed? It is required after the password text files get altered. > I also > discovered that even after the apparently successful runs of > freebsd-install and pkg-static upgrade -f that > there was software on the system that couldn't find the proper libraries to > run. Correct, as this software hasn't been upgraded yet. As I said before, starting with a clean ports tree often saves you from that kind of trouble (FreeBSD n.x -> n+1.y). You can either create the list yourself, or use "pkg info" as a source list, and trim it down to only contain what you're _really_ using (no version numbers!). That list can be fed into pkg after removing all installed software. As FreeBSD makes a difference between "the OS" and "everything else", it's safe to remove /usr/local altogether, use mtree to restore the directory tree, remove pkg databases, and checkout a new ports tree with portsnap; first thing to be done is to install pkg (by stub or by ports), and then go ahead and install what you need. The portsnap step is only required if you install something from source. Yes, I know, this procedure isn't written very well, and it's not even worthy being called a procedure, but I'm sure you can follow its basic idea. :-) By the way, as long as pkg is "somehow working", you can use pkg-delete to delete installed software. > This was obviously a disaster. Fortunately, I had taken zfs snapshots of > the filesystems prior to the upgrade > and was able to roll things back to the point where only the GUI was hosed. > So once again, thanks are > due to the creators and porters of ZFS. Yes, that was an excellent step to think about beforehand. > Obviously, many people have succeeded in doing this and perhaps I made some > error, although, as I have said > I have done this many, many times. It does seem that the freebsd-update/pkg > system is more fragile than > I have thought. This isn't a big deal for the stuff I have at homes, but I > have come to rely on this combo > to update systems to which I don't have physical access. Now I am a bit > concerned about doing that. I think you encountered a severe version mismatch here, resulting in strange behaviour and corrupted installs. > When I have more time, I will go back to my older method of building the > system from source. But for now > this will have to do. This is, in my opinion, not your problem. Your system has been updated binarily as expected, but your ports (which pkg belongs to) have not been treated properly. Personally, building OS from source is something I only do for very few exceptions. I have done so in the past regularly (and with custom kernels), but today, I prefer the convenience of using freebsd-update for everything that's not an exception. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a1cbc567105112e6162f68c97d85f647>