Fri, 8 Nov 2024 23:14:57 +0000 Barry <ba...@barrys-emacs.org> kirjoitti:
> > On 8 Nov 2024, at 13:19, jarmo <oh1...@nic.fi> wrote: > > > > Had to install inxi first :) > > Thanks for the info. > > Do you see systemd-resolved failing immediately after you first login? > Or does if fail after you have been using the system for a little > while? After it fails do you see any journal logs about the oom > killer running? > > Barry I see no network, after starting computer, which I do very seldom, only when there comes kernel update. So network does not start at all and when doing journal query I get this, what I sent before... journalctl -xeu systemd-resolved.service ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ An ExecStart= process belonging to unit systemd-resolved.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ The unit systemd-resolved.service has entered the 'failed' state with result 'exit-code'. marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution. ░░ Subject: A start job for unit systemd-resolved.service has failed ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit systemd-resolved.service has finished with a failure. ░░ ░░ The job identifier is 12559 and the job result is failed. marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at> ░░ Subject: Automatic restarting of a unit has been scheduled ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ Automatic restarting of the unit systemd-resolved.service has been scheduled, as the result for ░░ the configured Restart= setting for the unit. marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: systemd-resolved.service: Start request repeated too quickly. marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ The unit systemd-resolved.service has entered the 'failed' state with result 'exit-code'. marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution. ░░ Subject: A start job for unit systemd-resolved.service has failed ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit systemd-resolved.service has finished with a failure. ░░ ░░ The job identifier is 12590 and the job result is failed. What is strange, I have two laptops and there all is ok... I wish I could "speak nerd" :):) Jarmo -- _______________________________________________ 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
