In my case on the OpenIndiana system I run physical:nwam the physical network interface autoconfiguration.
# svcs -a | grep physical disabled 7:44:29 svc:/network/physical:default online 7:44:33 svc:/network/physical:nwam See man nwamd (choice between "manual" and "auto-magic" mode). Did you have some events logged in the current "volatile" /etc/svc/volatile/network-physical:nwam.log or in the (permanent) copy in /var/svc/log/network-physical:nwam.log Anyway the error seems not so unusual, for example I had it many times when adding host IP addresses manually to /etc/hosts and then you could get hostname resolution errors in some cases. It could be something transient in the hostname resolution / network automagic setup. Of course it can be something else as well, checking the nwam.log file is perhaps a good start to troubleshoot this. David Stes ----- Op 13 jul 2021 om 23:41 schreef gary mills gary_mi...@fastmail.fm: > On Tue, Jul 13, 2021 at 08:20:43PM +0200, s...@pandora.be wrote: >> >> I installed some software (pkg install squeak) today and had no problems; > >> E_COULDNT_RESOLVE_HOST (6) reason: Could not resolve host: >> pkg.openindiana.org > >> I've seen this error quite a few times when there is DNS resolving >> problem, for example when /etc/nsswitch.conf has an issue. > > It certainly was transient. Both "host" and "getent" could resolve > the hostname to an IP address immediately afterward. I also did not > get the error message a few minutes ago when I did an install. > > > -- > -Gary Mills- -refurb- -Winnipeg, Manitoba, Canada- > > _______________________________________________ > oi-dev mailing list > oi-dev@openindiana.org > https://openindiana.org/mailman/listinfo/oi-dev _______________________________________________ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
