On 2020-08-22 12:13 p.m., Carlos E. R. wrote:
On 22/08/2020 19.46, Darryl Gregorash wrote:
On 2020-08-22 11:27 a.m., Per Jessen wrote:
Darryl Gregorash wrote:
Please recall that this problem has never occurred except during a reboot right after a kernel update. I have already rebooted once after my first post, and everything went fine. Do you wish to see the log from that boot?
It might be interesting to see, yes.
(With no apologies to Carlos for the line-wrap ;) )
Grr
0:)
2020-08-21T17:45:35.154532-06:00 hadron wickedd-dhcp4[1368]: eth0: Committed DHCPv4 lease with address 24.72.0.229 (lease time 172800 sec, renew in 86400 sec, rebind in 172500 sec) 2020-08-21T17:45:36.018340-06:00 hadron wicked[1419]: lo up 2020-08-21T17:45:36.018506-06:00 hadron wicked[1419]: eth0 up 2020-08-21T17:45:36.019048-06:00 hadron systemd[1]: Started wicked managed network interfaces.
That's nicer :-D Yes, and normal.
Maybe there is a timing issue that makes the other lease appear or not. I think that is what I have been saying -- the network interface is not yet properly set up.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org