Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 13 May 2020 19:01:58 +0100
From:      tech-lists <tech-lists@zyxst.net>
To:        freebsd-questions@freebsd.org
Subject:   Re: Shared object "libnetgraph.so.4" not found, required by "netstat"
Message-ID:  <20200513180158.GA23072@bastion.zyxst.net>
In-Reply-To: <20200512154502.GH59811@bastion.zyxst.net>
References:  <20200512154502.GH59811@bastion.zyxst.net>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

--3V7upXqbjpZ4EhLz
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, May 12, 2020 at 04:44:35PM +0100, tech-lists wrote:
>Hi,
>
>I'm getting this error in my daily reports:
>
>ld-elf.so.1: Shared object "libnetgraph.so.4" not found, required by "nets=
tat"
>
>seems to hapen when daily cron runs network interface totals.
>
>This is a freebsd bhyve vm running on a freebsd host:
>
>vm: FreeBSD 12.1-RELEASE-p3 GENERIC  amd64
>
># freebsd-version -kru
>12.1-RELEASE-p3
>12.1-RELEASE-p3
>12.1-RELEASE-p4
>
>it's kept up-to-date with freebsd-update. The messages I get from
>freebsd-update are a little odd:
>
># freebsd-update fetch
>src component not installed, skipped
>Looking up update.FreeBSD.org mirrors... 3 mirrors found.
>Fetching metadata signature for 12.1-RELEASE from update1.freebsd.org... d=
one.
>Fetching metadata index... done.
>Inspecting system... done.
>Preparing to download files... done.
>
>No updates needed to update system to 12.1-RELEASE-p4.
># freebsd-update install
>src component not installed, skipped
>No updates are available to install.
>Run '/usr/sbin/freebsd-update fetch' first.
>
>I thought netgraph etc would be taken care of by freebsd-update? How can I
>fix?
>
>thanks,

I upgraded again today with freebsd-update and rebooted.

% freebsd-version -kru
12.1-RELEASE-p5
12.1-RELEASE-p5
12.1-RELEASE-p5

same error:

Network interface status:
ld-elf.so.1: Shared object "libnetgraph.so.4" not found, required by "netst=
at"

What's odd is it's only this one bhyve vm with it. There are other bhyve vms
on the same host at the same revision without this issue. There's no
/etc/src.conf or /etc/make.conf. It's otherwise working fine.
--=20
J.

--3V7upXqbjpZ4EhLz
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAl68NicACgkQs8o7QhFz
NAVXBhAAjU43JBJUg0D2BUrlZz0sY1Lp8m7GsUjcYdmngAugcw5f+uvSLSlVGG9j
YtHJg0XRTifHAmjHrZo9N4UCHJ8FX7QYEOd0QyvFwgTSQvu9NBzhr4Q5cBiRfPKW
+s5Cicpf7EZM/HfZiC1k8k3qvQI3axXEddXRm8+qfPxBVZYsVnWAkEUaRst4iozb
3Ir2Qnr4jiWYpBjOSi13VF2PW69V3PX5cV5Ddh8SSWxbpZMAWRY3zHLnxu+UMgE7
ctyUrUW3hABMtopJ/Ytskm3TpMfwY63i9fkC7/9f2Sjz2leGrXqu2KPiFgPgu9YX
FlfVy/iMQ2IkwAhu8fMo8ur4bA4rfgW2R6FJuiefsUYT6ppWZ7rxM8G7mJaf1mVj
3defGzRAF/eGe40tueHOT7ea28g/CJtzzwyruZnKU0eT3ZqZq63MQ2ooVOUz+Fd4
HytY3j8ojMx9eUdWcFKAPgRIuwFVNLunqMAe27KJ9XrU5t6hHHL5tH1aLkaLGBft
EdVbpb11UbL4hCNNJj8W5IstiaAu4sFNJxC0vOulmqaBRI9YsaLt+BNdNK/Z3+c7
D2rErqRD/AG9BYLLvDJ3WCh1hDOA9Y+k0OcsL1VeqRzPPiLpZn44n7oBXExgZSdF
i43g/uNAXggjZVbvKNvb7J2FdcUNY9EQSbSpUWK06wxACy65FZc=
=T3rc
-----END PGP SIGNATURE-----

--3V7upXqbjpZ4EhLz--



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20200513180158.GA23072>