From owner-freebsd-stable@freebsd.org Tue Nov 27 15:10:29 2018 Return-Path: Delivered-To: freebsd-stable@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 F10AB114FC58 for ; Tue, 27 Nov 2018 15:10:28 +0000 (UTC) (envelope-from freebsd-lists@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.49.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 507C97FBA0; Tue, 27 Nov 2018 15:10:28 +0000 (UTC) (envelope-from freebsd-lists@gromit.dlib.vt.edu) Received: from pmather.lib.vt.edu (pmather.lib.vt.edu [128.173.51.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 8745B12C; Tue, 27 Nov 2018 10:10:22 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: "sockstat: struct xinpgen size mismatch" in 11.2-p4 jail on 12-STABLE host From: Paul Mather In-Reply-To: <20181126234450.GB52181@spindle.one-eyed-alien.net> Date: Tue, 27 Nov 2018 10:10:22 -0500 Cc: FreeBSD Stable Content-Transfer-Encoding: quoted-printable Message-Id: <684C956B-3600-45D3-A527-3E6E4F223564@gromit.dlib.vt.edu> References: <20181126234450.GB52181@spindle.one-eyed-alien.net> To: Brooks Davis X-Mailer: Apple Mail (2.3445.9.1) X-Rspamd-Queue-Id: 507C97FBA0 X-Spamd-Result: default: False [-1.11 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; DMARC_POLICY_SOFTFAIL(0.10)[vt.edu : No valid SPF, No valid DKIM,none]; NEURAL_HAM_MEDIUM(-0.54)[-0.543,0]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_LONG(-0.88)[-0.879,0]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[chumby.dlib.vt.edu,gromit.dlib.vt.edu]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.16)[-0.160,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; IP_SCORE(-0.02)[country: US(-0.09)]; ASN(0.00)[asn:1312, ipnet:128.173.0.0/16, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Nov 2018 15:10:29 -0000 On Nov 26, 2018, at 6:44 PM, Brooks Davis wrote: > On Sat, Nov 24, 2018 at 09:17:23AM -0500, Paul Mather wrote: >> I updated a system yesterday to the latest 12-STABLE as part of the = upcoming 12-RELEASE cycle. I've installed several BETA and at least one = RC of 12 since updating from 11-STABLE as part of the 12 cycle and have = had no problems up to now. Currently, I am at FreeBSD 12.0-PRERELEASE = r340834 GENERIC amd64. >>=20 >> Since the most recent update, I have been getting this error when I = invoke "sockstat" in any of the jails running on the system: >>=20 >> sockstat: struct xinpgen size mismatch >>=20 >> The jails are managed via iocage and all are running 11.2-RELEASE-p4, = which is the most up-to-date version of 11.2-RELEASE. >>=20 >> Has anyone encountered this error? Unfortunately, it means that it = breaks Salt, which is what I use to help manage the jails. Sockstat = works fine on the host, just not in the jails. >>=20 >> I am using a GENERIC kernel which includes "options = COMPAT_FREEBSD11". I assumed this would allow FreeBSD 11 binaries to = work on a FreeBSD 12 kernel, which it has done up to now. >=20 > We broke this system management ABI months ago. I'm not sure why = you're > only bumping into this now. >=20 > We don't provide backward compatibility for these interfaces. To make > this configuration work, I'd suggest replacing the sockstat in > the jail with a statically linked version built for FreeBSD 12. Thank you for the response and the advice. I'm not sure why/if I'm only bumping into this now. It may be that I = only looked deeper into why Salt was breaking this time around and saw = the problem to be an invocation of "sockstat" by a Python module. Salt = has temporarily broken for me in the past due to updates, but usually = mends itself on a subsequent rebuild/reinstall of the packages. When the 12.0-RC2 announcement came out shortly after I reported the = above I decided to upgrade to it. That seemed to fix the problem with = Salt (or at least coincide with the problem going away), which is my = main concern. I still get the same error as reported above when I = invoke "sockstat" in the 11.2 jail, but as long as Salt is working again = then that's all I really need. :-) When 12.0-RELEASE comes out I will most likely just upgrade the 11.2 = jails to 12.0. The main reason for not updating now is that iocage = doesn't appear to recognise the existence of any release more recent = than 11.2. Thanks again. Cheers, Paul.