This MAY be related to this bug, I'm not sure how... Symptomatically,
it would make sense. Not sure of the causal link though...
https://github.com/systemd/systemd/issues/13432
On Fri, 2021-01-08 at 11:59 -0500, Michael H. Warfield wrote:
Ed, et al...
[Excuse the top posting but this is just a prelim report]
Still too early to say for certain but...
Since taking your advice and eliminating that "resolve
[!UNAVAIL=return]" stanza from nsswitch.conf, I have only had one
failure in the afflicted systems and that was due to a hardware
problem
with a USB hub connection, and not at all related or
relevant. That's
almost 5 days on systems that would run into this problem in a matter
of hours to under 1 day, and we're now almost 5 days out.
My level of confidence is growing. I think you hit the nail square
on
the head. The
nsswitch.com problem may have been the issue. But the
cause may yet still be elsewhere. That file is owned by glibc. I'll
file a bugzilla report against that package for f33. I've had many
bugzilla reports under my belt. This one, against glib, will be a
first for me. I'll give it another week.
Many thanks sir!
Regards,
Mike
On Sun, 2021-01-03 at 12:06 +0800, Ed Greshko wrote:
> On 03/01/2021 11:52, Michael H. Warfield wrote:
>
> First thing..... Try not starting a line with "--". Some email
> client interpret that as the start of the
> signature block and screws up presentation and reply formatting.
>
>
> > But no... systemd-resolved is not running and is not
> > enabled. Not the problem. Which makes it even more perplexing.
> >
> > Not a symlink. Didn't work even when it was and redirected to
> > 127.0.0.253. One of the first things I check and tried. Also
> > checked
> > nsswitch.conf. Some differences but not that I could spot and
> > why
> > the
> > difference between "host" and "ping"? And why the
timeout???
> >
> > nsswitch.conf hosts: files mdns4_minimal [NOTFOUND=return]
> > resolve [!UNAVAIL=return] myhostname dns
>
> I don't know if this will have any effect, but since you're not
> running/using systemd-resolved then it may be
> a good idea to remove "resolve" from nsswitch.conf.
>
> An F32 system has....
>
> hosts: files mdns4_minimal [NOTFOUND=return] dns myhostnam
>
> ---
> The key to getting good answers is to ask good questions.
>
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
>
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
>
https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
>
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org --
Michael H. Warfield (AI4NB) | (o) +1 706 850-8773 | mhw(a)WittsEnd.com
/\/\|=mhw=|\/\/ | (c) +1 678 463-0932 |
http://www.wittsend.com/mhw/
ARIN whois: MHW9-ARIN | An optimist believes we live in the best of all
PGP Key: 0xC0EB9675674627FF | possible worlds. A pessimist is sure of it!