freebsd stable - Jun 2015 - ssh install with freebsd-update

>> # uname -a FreeBSD foux.psg.com 10.1-RELEASE-p10 FreeBSD
>> 10.1-RELEASE-p10 #0: Tue May 12 19:33:13 UTC 2015
>> root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
>> i386
>> 
>> it's really p11 now
>> 
>> if i run freebsd-update install of p11.  all looks well until the 
>> reboot, when i get
>> 
>> Performing sanity check on sshd configuration. Shared object
>> "libgssapi_krb5.so.10" not found, required by
"sshd" /etc/rc:
>> WARNING: failed precmd routine for sshd
> 
> This is VERY strange!  Did you ever have an incomplete upgrade from
> older FreeBSD releases (9.x) on the affected systems?  What was the
> version before you update/upgrade to the latest one?
this is one of a dozen systems upgraded fom 9.3-stable to 10.1-release
p10 using a recipe in https://wiki.rg.net/wiki/FreeBSD9to10.  they all
show the same symptom.

it was consistent for all of them.  i was waiting for p11 to see if it
would fix it.  it did not, at least for this first system i tried.

randy

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 06/09/15 17:21, Randy Bush wrote:
>>> # uname -a FreeBSD foux.psg.com 10.1-RELEASE-p10 FreeBSD 
>>> 10.1-RELEASE-p10 #0: Tue May 12 19:33:13 UTC 2015 
>>> root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
>>>
>>> 
i386
>>> 
>>> it's really p11 now
>>> 
>>> if i run freebsd-update install of p11.  all looks well until
>>> the reboot, when i get
>>> 
>>> Performing sanity check on sshd configuration. Shared object 
>>> "libgssapi_krb5.so.10" not found, required by
"sshd" /etc/rc:
>>> WARNING: failed precmd routine for sshd
>> 
>> This is VERY strange!  Did you ever have an incomplete upgrade
>> from older FreeBSD releases (9.x) on the affected systems?  What
>> was the version before you update/upgrade to the latest one?
> 
> this is one of a dozen systems upgraded fom 9.3-stable to
> 10.1-release p10 using a recipe in
> https://wiki.rg.net/wiki/FreeBSD9to10.  they all show the same
> symptom.
My guess is that there was some fetched 'freebsd-update' upgrade data
that was not applied, and the freebsd-update install have somehow
confused by that.

BTW. the supported errata branch is releng/10.1, not release/10.1,
which is probably why the svn co failed in step 1.

Cheers,
- -- 
Xin LI <delphij at delphij.net>    https://www.delphij.net/
FreeBSD - The Power to Serve!           Live free or die
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.1.4 (FreeBSD)

iQIcBAEBCgAGBQJVd4XpAAoJEJW2GBstM+ns1PkQAICofy0/pvNXSEVnYsHh4pdM
PP1XKj4PwzORlujwM1T3pjuyjxDgro7H1Hy+OTl2oU5da2c2pu3AoGGxIN9dkQii
0C4mvTQEv87Z5+AI2sGY3dTchk8QRB9EkUAp1wkENiu2Th/cM7Kgt0MA66UfAd6U
Gc4QxSFEu681gPBUQeTapUR4bC6NG4++0yBrFOtGZBiLA8IeSL+Y1uCcpupjMZJ5
qzYQsChFw0f47/WC05ZjfBbwB3ckuDJnN6G+GKRz7tWuQCRSRqGWqEMzrHTiOcvH
+dXW++4h8rb6nQFzPPCTaAJP9YvlvyHMumUDN52Lm4lNxMWFklHYe8AfF4f8kbU/
r7yZgmEjwBo2dN1hQnylvn9cwEaRpn/mNYYwjW3ih90HrINmMFXfrcQyD3I2WfLe
evLZoMdoJ1dJrq/9h3B0Ak7NAfoInXKVfEVHZ1arOGFmXhqbfIlVbzxrlfe5rxaT
3Vi5jL+3n4EgO/X3Fn3dWAH6Y4jf4a3OopA1h+peBEuCJWVFkR+loYsCr9g27s+R
PQBjrpiUnGYSa8WkFnK5XYTUcTVVdKJ+0XevTKnjZ44LaPJkj599fo92E5gqWUfe
eoqTaxPly/VTFqInpiR3ARG4Mmfot7UxdQv/rG6E4c3boWIV9P06JdQKocUnT2vO
gzSOOPm/aCsvq6TZju0q
=dsJf
-----END PGP SIGNATURE-----