[Bug 1022545] Re: Backport upstream bugfix $PreserveFQDN on not working properly
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022545 Title: Backport upstream bugfix $PreserveFQDN on not working properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1022545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022545] Re: Backport upstream bugfix $PreserveFQDN on not working properly
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.launchpad.net/bugs/1022545 Title: Backport upstream bugfix $PreserveFQDN on not working properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1022545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp
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 MTU: 1420 Apr 24 09:50:59 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1460 Apr 24 21:50:58 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1420 Apr 25 09:50:59 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1460 Apr 25 21:50:59 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1420 Apr 26 09:51:00 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1460 Apr 26 21:50:59 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1420 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874661 Title: networkd sometimes doesn't set mtu received by dhcp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1874661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874661] [NEW] networkd sometimes doesn't set mtu received by dhcp
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 a working system again and enabled debugging for systemd-networkd. Log (filtered for ens4, some columns removed for better readability): 09:51:00 ens4: New device has no master, continuing without 09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST 09:51:00 ens4: Link 2 added 09:51:00 ens4: udev initialized link 09:51:00 ens4: Saved original MTU: 1420 09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever) 09:51:00 ens4: Gained IPv6LL 09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Link state is up-to-date 09:51:00 ens4: found matching network '/run/systemd/network/10-netplan-ens4.network' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0' 09:51:00 ens4: Started LLDP. 09:51:00 ens4: Setting address genmode for link 09:51:00 ens4: Setting address genmode done. 09:51:00 ens4: Removing address 10.164.0.2 09:51:00 ens4: Acquiring DHCPv4 lease 09:51:00 ens4: Discovering IPv6 routers 09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 09:51:00 ens4: Setting MTU: 1460 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 09:51:00 ens4: IPv6 successfully enabled 09:51:00 ens4: Setting MTU done. 09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d) 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Configured 21:50:59 ens4: DHCP lease lost 21:50:59 ens4: Removing address 10.164.0.2 21:50:59 ens4: Setting MTU: 1420 21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 21:50:59 ens4: IPv6 successfully enabled 21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s) 21:50:59 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Setting MTU done. 21:50:59 ens4: Adding address: 10.164.0.2/32 (valid for 1d) 21:50:59 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Configured On dhcp renew (09:51:00), mtu got properly changed to 1460. On next dhcp renew (21:50:59) it got changed back to previous value 1420. In all cases, /run/systemd/netif/leases/2 correctly contained MTU=1460. There have been some changes to mtu handling in the past, I assume this is a regression, potentially from https://github.com/systemd/systemd/issues/12552 or https://github.com/systemd/systemd/issues/6593. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: 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 a working system again and enabled debugging for systemd-networkd. - Log (filtered for ens4): - Apr 23 09:51:00 host systemd-networkd[1737]: ens4: New device
[Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp
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 ct-prod systemd-networkd[1737]: Bus bus-api-network: changing state UNSET → OPENING Apr 23 09:51:00 ct-prod systemd-networkd[1737]: Bus bus-api-network: changing state OPENING → AUTHENTICATING Apr 23 09:51:00 ct-prod systemd-networkd[1737]: timestamp of '/etc/systemd/network' changed Apr 23 09:51:00 ct-prod systemd-networkd[1737]: timestamp of '/run/systemd/network' changed Apr 23 09:51:00 ct-prod systemd-networkd[1737]: No virtualization found in DMI Apr 23 09:51:00 ct-prod systemd-networkd[1737]: Virtualization found, CPUID=KVMKVMKVM Apr 23 09:51:00 ct-prod systemd-networkd[1737]: Found VM virtualization kvm Apr 23 09:51:00 ct-prod systemd-networkd[1737]: /usr/lib/systemd/network/80-container-host0.network: Conditions in the file do not match the system environment, skipping. Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: Link 18378 added Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: udev initialized link Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: Saved original MTU: 1500 Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: Link 18376 added Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: udev initialized link Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: Saved original MTU: 1500 Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: Link 18374 added Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: udev initialized link Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: Saved original MTU: 1500 Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: New device has no master, continuing without Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: Link 18372 added Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: udev initialized link Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: Saved original MTU: 1500 Apr 23 09:51:00 ct-prod systemd-networkd[1737]: docker0: New device has no master, continuing without Apr 23 09:51:00 ct-prod systemd-networkd[1737]: docker0: Flags change: +UP +MULTICAST +BROADCAST Apr 23 09:51:00 ct-prod systemd-networkd[1737]: docker0: Link 3 added Apr 23 09:51:00 ct-prod systemd-networkd[1737]: docker0: udev initialized link Apr 23 09:51:00 ct-prod systemd-networkd[1737]: docker0: Saved original MTU: 1500 Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: New device has no master, continuing without Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Link 2 added Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: udev initialized link 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]: lo: New device has no master, continuing without Apr 23 09:51:00 ct-prod systemd-networkd[1737]: lo: Flags change: +LOOPBACK +UP +LOWER_UP +RUNNING Apr 23 09:51:00 ct-prod systemd-networkd[1737]: lo: Link 1 added Apr 23 09:51:00 ct-prod systemd-networkd[1737]: lo: udev initialized link Apr 23 09:51:00 ct-prod systemd-networkd[1737]: lo: Saved original MTU: 65536 Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: Adding address: fe80::c0e2:b6ff:fec5:c370/64 (valid forever) Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: Gained IPv6LL Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: Adding address: fe80::bc1c:baff:fedf:f0ef/64 (valid forever) Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: Gained IPv6LL Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: Adding address: fe80::d84f:edff:fe33:55a0/64 (valid forever) Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: Gained IPv6LL Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: Adding address: fe80::42:45ff:fed1:a3c2/64 (valid forever) Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: Gained IPv6LL Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever) Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Gained IPv6LL Apr 23 09:51:00 ct-prod
[Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp
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 CLIENT (0x8c68da26): lease expires in 23h 59min 57s May 11 18:32:54 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): T2 expires in 20h 59min 57s May 11 18:32:54 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): T1 expires in 11h 59min 59s May 11 18:32:54 ct-prod systemd-networkd[435]: ens4: Remembering updated address: 10.164.0.2/32 (valid for 1d) May 11 18:32:54 ct-prod systemd-networkd[435]: ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2, scope: link, table: main, proto: dhcp, type: unicast May 11 18:32:54 ct-prod systemd-networkd[435]: ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2, scope: global, table: main, proto: dhcp, type: unicast May 12 06:32:53 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): REQUEST (renewing) May 12 06:32:53 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): ACK May 12 06:32:53 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): lease expires in 23h 59min 57s May 12 06:32:53 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): T2 expires in 20h 59min 58s May 12 06:32:53 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): T1 expires in 11h 59min 59s May 12 06:32:53 ct-prod systemd-networkd[435]: ens4: Remembering updated address: 10.164.0.2/32 (valid for 1d) May 12 06:32:53 ct-prod systemd-networkd[435]: ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2, scope: link, table: main, proto: dhcp, type: unicast May 12 06:32:53 ct-prod systemd-networkd[435]: ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2, scope: global, table: main, proto: dhcp, type: unicast -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874661 Title: networkd sometimes doesn't set mtu received by dhcp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1874661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp
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/bugs/1874661 Title: networkd sometimes doesn't set mtu received by dhcp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1874661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp
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 Ubuntu. https://bugs.launchpad.net/bugs/1874661 Title: networkd sometimes doesn't set mtu received by dhcp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1874661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
