Tried with image ubuntu-minimal-2004-focal-v20200501 (systemd
245.4-4ubuntu3). No issues seen. I will then upgrade our project to
Focal, which also has LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
245.5-2upstream202005091618~ubuntu19.10.1 from your ppa seems to be fine:
May 11 18:32:54 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26):
REQUEST (renewing)
May 11 18:32:54 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): ACK
May 11 18:32:54 ct-prod systemd-networkd[435]: DHCP CLI
Do you have any suggestion on what to look at?
Systemd only tracks bugs for the two most recently released versions (which
should be 245 and 244) and I don't have the ressources to test those.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
After the weekend, I observed that the original MTU gets set on every second
renew:
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Saved original MTU: 1420
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1460
Apr 23 21:50:59 ct-prod systemd-networkd[1737]: ens4: Setting M
This is the full log:
Apr 23 09:51:00 ct-prod systemd[1]: Stopping Network Service...
Apr 23 09:51:00 ct-prod systemd[1]: systemd-networkd.service: Succeeded.
Apr 23 09:51:00 ct-prod systemd[1]: Stopped Network Service.
Apr 23 09:51:00 ct-prod systemd[1]: Starting Network Service...
Apr 23 09:51:00
Public bug reported:
I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd
242-7ubuntu3.7.
GCE has mtu 1460, set by dhcp. After having networking issues, I figured out
that the mtu on the interface was sometimes incorrectly set to 1500.
I manually changed it to 1420 to have
The test case is not checking for FQDN (i don't use $PreserveFQDN). The
upgrade to 5.8.6-1ubuntu8.3 was stuck because the restart triggered from
postinst did never return.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
The original patch has a bug which leads to "malloc(): memory corruption". A
fix can be found at
http://git.adiscon.com/?p=rsyslog.git;a=commitdiff_plain;h=9c54bf41d02ba236137859ea5f12d6f048647349
The fix is critical because rsyslog won't start anymore.
--
You received this bug notification be
