[Bug 1796895] Re: Kernel 4.15.0-36 network performance regression
For the record: I've tracked this down to a pair of commmits, the first of which landed in -35 (released in -36) the second in -37. The first: https://lkml.org/lkml/2018/6/5/765 The second: https://lkml.org/lkml/2018/6/24/161 In the interim state, it was casting a u64 to a u32, which truncates to the least-significant 32 bits. This was, from what I could see using tcpdump and other tools, causing the TCP window size to truncate to a very small number, leading to hilariously slow network traffic. Further, it seems (although I haven't yet got the whole logic chain in my head) that the TCP algorithm could never get itself out of this state again, so the connection was then permanently stuck in a slow state. The two commits were originally from the one author, within a second of each other, back in Dec 2017. They really needed to be pulled in together. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796895 Title: Kernel 4.15.0-36 network performance regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745492] Re: Backport of Debian bug #785714 for Xenial to avoid unclean reboots
I believe this is solved by bug #1743529 backporting kexec-tools from bionic. What's the right way to close this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745492 Title: Backport of Debian bug #785714 for Xenial to avoid unclean reboots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1745492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745492] [NEW] Backport of Debian bug #785714 for Xenial to avoid unclean reboots
Public bug reported: Debian bug #785714 is a fairly substantial one, as it causes unclean shutdowns. In our case, KVM hosts with many guests will begin to partially shutdown a couple before kexec jumps the gun and reboots the machine. Without this fix, kexec is of only minimal use on Xenial ** Affects: kexec-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745492 Title: Backport of Debian bug #785714 for Xenial to avoid unclean reboots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1745492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1367899] Re: cloud-init rsyslog config uses deprecated syntax
Confirmed the fix looks good in 0.7.9-113-g513e99e0-0ubuntu1~16.04.1 for Xenial. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1367899 Title: cloud-init rsyslog config uses deprecated syntax To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1367899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642401] [NEW] Excessive syslog logging with use of Exec plugins
Public bug reported: Basically the issue reported and fixed at https://github.com/collectd/collectd/issues/664 is quite a problem on a production system. Would appreciate a backport of the 2-line fix. ** Affects: collectd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642401 Title: Excessive syslog logging with use of Exec plugins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1642401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295467] Re: bash crashes when attempting to run a X! where X is a single letter
** Attachment added: Crash report https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1295467/+attachment/4043616/+files/bash.crash.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295467 Title: bash crashes when attempting to run a X! where X is a single letter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1295467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295467] Re: bash crashes when attempting to run a X! where X is a single letter
The affected boxes are headless servers, on networks without outbound HTTP(S) access. Is the attached upload of the crash report sufficient? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295467 Title: bash crashes when attempting to run a X! where X is a single letter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1295467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295467] [NEW] bash crashes when attempting to run a X! where X is a single letter
Public bug reported: Attempting to run q! (yes, I was wrong-window typing vim commands into bash) causes: q!: command not found malloc: /usr/homes/chet/src/bash/src/parse.y:2314: assertion botched realloc: start and end chunk sizes differ Aborting...Connection to machinename closed. Occurs with any single letter followed by !, or a lone !. Does not occur with ! followed by one or more characters. It is not the command-not-found package (removing that was my first diagnosis attempt). I don't really know what else to try. It happens on the two Trusty Tahr servers available to me, but not Saucy or earlier. ** Affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295467 Title: bash crashes when attempting to run a X! where X is a single letter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1295467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1269979] [NEW] /etc/init.d/smokeping status does not find running process
Public bug reported: pidofproc assumes either a PID file in /var/run/smokeping.pid, or failing that uses pidof to find the PID. A running smokeping looks like this: root@myhost:~# ps uawx|grep smokeping 109 26838 0.0 0.5 141824 22296 ?Ss 11:41 0:00 /usr/sbin/smokeping [FPing] And 'pidof smokeping' doesn't find it (presumably due to the [FPing]). Can be fixed in the init script with the -p option to pidofproc: pidofproc -p $PIDFILE $DAEMON /dev/null Patch attached. ** Affects: smokeping (Ubuntu) Importance: Undecided Status: New ** Attachment added: Patch to /etc/init.d/smokeping https://bugs.launchpad.net/bugs/1269979/+attachment/3950484/+files/smokeping-init.d.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1269979 Title: /etc/init.d/smokeping status does not find running process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smokeping/+bug/1269979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192168] Re: zgrep does not correctly pass short options to grep
Looks like a regression in Precise: it was fine in Lucid. The line in question is 141 of zgrep.in, which only got the -h option added post gzip 1.4 (commit cc1c692e4cf115ece8391aaa5f45041065a0c64a, sSep 15th 2010). Lucid has 1.3.12 of gzip, but gzip_1.3.12-9ubuntu1.1.diff patches zgrep to add -h to line 108 of zgrep.in. Looks like that needs to be added as a patch in the Precise build (patch attached; just add to debian/patches dir and reference in debian/patches/series) NB: Until this makes it into a package, --no-filename will have the equivalent effect. ** Patch added: Patch to zgrep.in https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1192168/+attachment/3798494/+files/zgrep-h.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192168 Title: zgrep does not correctly pass short options to grep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1192168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 882874] Re: apt-cacher has poor childpid management
Slightly modified patch attached; deleting the childPid entry caused a rather odd perl panic: Sun Jan 1 19:11:13 2012|error [24236]: panic: attempt to copy value 1 to a freed scalar 107bfa8 at /usr/sbin/apt-cacher line 1912. Looks like some sort of child/parent race condition that is well beyond my ken. Setting the value to 0 instead of deleting, and checking for 1 in the kill loop seems to avoid the issue. ** Attachment added: Updated patch https://bugs.launchpad.net/ubuntu/+source/apt-cacher/+bug/882874/+attachment/2656221/+files/apt-cacher-childpids-bug-patch2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/882874 Title: apt-cacher has poor childpid management To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-cacher/+bug/882874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 732953] Re: can_connect function inside ec2.rb always return false
Confirmed here; same symptoms, breaking the puppet client. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to facter in Ubuntu. https://bugs.launchpad.net/bugs/732953 Title: can_connect function inside ec2.rb always return false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/732953/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 732953] Re: can_connect function inside ec2.rb always return false
Confirmed here; same symptoms, breaking the puppet client. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/732953 Title: can_connect function inside ec2.rb always return false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/732953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 882874] [NEW] apt-cacher has poor childpid management
Public bug reported: Apt-cacher keeps a list of the pids of any children it forks/spawns. At shutdown, it terminates them all with SIGTERM. Unfortunately, it doesn't catch SIGCHLD and remove a normal finished child from the list. So after it's been running for a while, that list of PIDs will be fairly long and rather comprehensive (on one recent server where I noticed it, the list had 25000 unique PIDs, i.e. about 3/4s of the available PID space :)). The only mitigating factor is that apt-cacher runs as www-data by default, although that doesn't help if you're running it on the same server as apache2, nginx or some other www-data running process. Patch attached fixes this; it uses a hash instead of an array, and traps SIGCHLD to catch when children finish. Seems to work ok in a short time running it here. ** Affects: apt-cacher (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/882874 Title: apt-cacher has poor childpid management To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-cacher/+bug/882874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 882874] Re: apt-cacher has poor childpid management
** Patch added: Patch to fix the problem https://bugs.launchpad.net/bugs/882874/+attachment/2576058/+files/apt-cacher-childpids-bug-patch.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/882874 Title: apt-cacher has poor childpid management To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-cacher/+bug/882874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
