Am Sun, Feb 26, 2023 at 10:33:19PM +0700 schrieb Max Nikulin:
> On 25/02/2023 19:49, Christoph Brinkhaus wrote:
> > Now there are no messages reported by journald as above.
>
> I am curious if fixing unbound and so network-online.target helped to avoid
> 169.254.x.y address in your case. Can fetchmail work without a kludge you
> added to achieve some delay? My expectation is that unbound.service may be
> dropped from Requires= and After= in fetchmail.service, but both fields
> should have network-online.target.
>
> I forgot that debugging of such issues should be started with "systemctl
> --failed".
I have tried that and found the next issue.
systemd-networkd-wait-online runs into a time out after the default
timeout of 2 minutes.
# systemctl status systemd-networkd-wait-online
● systemd-networkd-wait-online.service - Wait for Network to be Configured
Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service;
enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2023-02-26 17:10:28 CET; 1h
47min ago
Docs: man:systemd-networkd-wait-online.service(8)
Process: 472 ExecStart=/lib/systemd/systemd-networkd-wait-online
(code=exited, status=1/FAILURE)
Main PID: 472 (code=exited, status=1/FAILURE)
CPU: 25ms
Feb 26 17:08:28 lenovo systemd[1]: Starting Wait for Network to be Configured...
Feb 26 17:10:28 lenovo systemd-networkd-wait-online[472]: Event loop failed:
Connection timed out
Feb 26 17:10:28 lenovo systemd[1]: systemd-networkd-wait-online.service: Main
process exited, code=exited, status=1/FAILURE
Feb 26 17:10:28 lenovo systemd[1]: systemd-networkd-wait-online.service: Failed
with result 'exit-code'.
Feb 26 17:10:28 lenovo systemd[1]: Failed to start Wait for Network to be
Configured.
Strange, I will have a look. But I think further discussion would exceed the
topic
of the thread. I will have to read a lot of man pages the next days.
You have helped my already a lot :-), thanks for that kind support!
Kind regards,
Christoph
--
Ist die Katze gesund
schmeckt sie dem Hund.
