From owner-freebsd-questions@freebsd.org Sun May 17 21:25:07 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A45022F6F91 for ; Sun, 17 May 2020 21:25:07 +0000 (UTC) (envelope-from per@hedeland.org) Received: from mailout.easydns.com (mailout.easydns.com [64.68.202.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49QFXy44SGz3WY5 for ; Sun, 17 May 2020 21:25:06 +0000 (UTC) (envelope-from per@hedeland.org) Received: from localhost (localhost [127.0.0.1]) by mailout.easydns.com (Postfix) with ESMTP id 40341A0606 for ; Sun, 17 May 2020 21:25:05 +0000 (UTC) Received: from mailout.easydns.com ([127.0.0.1]) by localhost (emo13-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iQMUVOXxlDET for ; Sun, 17 May 2020 21:25:05 +0000 (UTC) Received: from hedeland.org (81-228-157-209-no289.tbcn.telia.com [81.228.157.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mailout.easydns.com (Postfix) with ESMTPSA id 073139FE46 for ; Sun, 17 May 2020 21:25:04 +0000 (UTC) Received: from pluto.hedeland.org (pluto.hedeland.org [10.1.1.5]) by tellus.hedeland.org (8.15.2/8.15.2) with ESMTPS id 04HLP2re081772 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO) for ; Sun, 17 May 2020 23:25:02 +0200 (CEST) (envelope-from per@hedeland.org) Subject: Re: Shared object "libnetgraph.so.4" not found, required by "netstat" To: freebsd-questions@freebsd.org References: <20200512154502.GH59811@bastion.zyxst.net> <20200513180158.GA23072@bastion.zyxst.net> <70cc3458-237f-847c-03f0-0767c26f6b89@fastmail.com> <8570e125-f34d-840a-5803-376d43bc9723@hedeland.org> <20200514011537.GC23072@bastion.zyxst.net> <0278cb1e-8084-6dce-5ac7-1e5297ff40d5@hedeland.org> <20200514110619.GD23072@bastion.zyxst.net> <20200517120341.GE23072@bastion.zyxst.net> From: Per Hedeland Message-ID: Date: Sun, 17 May 2020 23:25:02 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1 MIME-Version: 1.0 In-Reply-To: <20200517120341.GE23072@bastion.zyxst.net> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 49QFXy44SGz3WY5 X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of per@hedeland.org has no SPF policy when checking 64.68.202.10) smtp.mailfrom=per@hedeland.org X-Spamd-Result: default: False [1.33 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; RECEIVED_SPAMHAUS_PBL(0.00)[81.228.157.209:received]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.53)[0.527]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[hedeland.org]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16686, ipnet:64.68.200.0/22, country:CA]; RCVD_TLS_LAST(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[64.68.202.10:from] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 May 2020 21:25:07 -0000 On 2020-05-17 14:03, tech-lists wrote: > > I've found the same issue on another VM on another FreeBSD host, completely > different hardware in a different geographical location, completely different > VM, only similarity is it's kept up-to-date with freebsd-update. In this case > the server hosts 2x bhyve VMs. Both were brought up to 12.1-RELEASE-p5 with > freebsd-update. Only one shows the problem. > This is definitely a FreeBSD problem. I don't have a clue what could be > causing it though. It certainly seems so from the information you have provided - but on the other hand, a general problem that rendered 'netstat' unusable would probably have gained a lot more attention, since 'netstat' isn't just something that is run in the "daily report", but a very fundamental tool for examining all kinds of network properties. Personally I have 3 hosts with 12.1-RELEASE and one with 12-STABLE post 12.1-RELEASE, and none of them exhibit this problem. I don't use freebsd-update though, so one possibility might be that it caused this breakage - but a lot of people do use it, and AFAIK none of them have reported a problem like this. Additionally, AFAICS there hasn't been any updates to libnetgraph after 12.1-RELEASE - the last libnetgraph update on the 12 branch seems to be at svn r348827, while 12.1-RELEASE was at r354233 - i.e. it seems extremely unlikely that a broken freebsd-update update is the cause. I.e. it might be a FreeBSD problem, but if so, there is something specific to your environment that is triggering it... --Per