Date: Sun, 17 May 2020 23:25:02 +0200 From: Per Hedeland <per@hedeland.org> To: freebsd-questions@freebsd.org Subject: Re: Shared object "libnetgraph.so.4" not found, required by "netstat" Message-ID: <db3abb11-3789-49bf-123b-02f9aa6979b4@hedeland.org> In-Reply-To: <20200517120341.GE23072@bastion.zyxst.net> 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> <f512e435-b92b-ceaa-02ba-c5844b124ebe@hedeland.org> <20200517120341.GE23072@bastion.zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?db3abb11-3789-49bf-123b-02f9aa6979b4>