If the nisdomain is not responding, I would claim the system should still boot, so I would think that is a bug. But if systemd/pam is not timing out on the non-responding nisdomain or the timeout is too high then I would think that might screw up a significant part of the system because lookups of passwd/hosts/group access may not work, depending on where else nis pieces are setup. I would think if file was first and there is a valid entry in the file that it should not go to nisdomain, but that may depend on what the order is in /etc/nsswitch.conf.
On Sun, Dec 18, 2022 at 10:03 AM Terry Barnaby <ter...@beam.ltd.uk> wrote: > A strange one this. I was just updating a Fedora35 server to Fedora37, > using a full reinstall and then copying configuration files from the old > system. > > The system failed to boot with lots of strange issues with systemd. It > started with console messages like: > > [ TIME ] Timeout waiting for device dev-zram0.device - /dev/zram0. > > Some further issues with zram, followed by some other services starting > fine then the system gets in a loop: > > [ FAILED] Failed to start systemd-udevd.service - ... > > [ FAILED] Failed to start systemd-oomd.service - ... > > None of this was logged in /var/log/messages. > > After some tracking down on a VM, I found the issue was somehow caused > by having "NISDOMAIN=kingnet" in the file /etc/sysconfig/network. This > came from an old client configuration ,setting the NIS domain. This was > not actually needed on the server and in fact not needed on the clients > now as the DHCP does this on our systems, it was a hangback from 20 > years or so. > > I have no idea why this has caused the boot fail though, I thought I'd > mention it in case anyone else sees it. I will report it as a "bug" > against systemd although I'm not sure it is really a systemd issue or > really a bug at all, but a bit nasty as the system fails to boot. > > Terry > _______________________________________________ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@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 > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue >
_______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
