[Touch-packages] [Bug 2029930] Re: wget crash when printing download rate
I have just been able to reproduce it by running this on the same server the website example.org is hosted: cd /tmp while true; do rm -rf www.example.org/ && wget --mirror --page-requisites https://www.example.org 2>&1 | grep -F GB/s; done The 'grep GB/s' makes a point of showing the improbable speeds. It's not unusual to see several dozens or hundreds of GB/s there, like this: 2023-11-19 19:33:57 (116 GB/s) - ‘www.example.org/wp- json/oembed/1.0/embed?url=https:%2F%2Fwww.example.org%2F2023%2F06%2F05%2Fredacted’ saved [2362/2362] That's 2 kB, downloaded at 116 GB/s. Obviously a timer issue. This illustrates it's not hard to occasionally hit some super high TB/s value, which would trigger the crash. With the PPA, running this grepping on TB/s, it took about 30 minutes, but eventually: 2023-11-19 19:34:16 (4.00 TB/s) - ‘www.example.org/wp- json/oembed/1.0/embed?url=https:%2F%2Fwww.example.org%2F2023%2F08%2F19%2Fredacted%2F’ saved [2201/2201] This is all crawling a Wordpress site. There seems to be a higher chance of crawling a dynamic site vs static files, possibly because it doesn't start counting bytes until it has seen the first, and dynamic sites tend to only operate from memory at that point. That's probably also the reason it tends to happen on 2 kB-ish files, because it fits in one or two TCP packets. Probably a simple PHP scripts that prints a few kBytes is enough. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/2029930 Title: wget crash when printing download rate Status in wget package in Ubuntu: Confirmed Status in wget source package in Noble: Confirmed Status in wget package in Debian: Confirmed Bug description: All supported versions of Ubuntu suffer from crashes in wget in printing of the download speed. I've been getting this on various servers. It's been fixed upstream and should probably be included in 'updates' of all supported Ubuntu versions. https://git.savannah.gnu.org/git/wget.git Commit 04ab35666997fbb3cd5d72497415fb3dfd62dcc5 https://lists.gnu.org/archive/html/bug-wget/2023-08/msg1.html Patch attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/2029930/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2029930] Re: wget crash when printing download rate
I'm still getting a bunch of wget crashes from cron jobs I have. Is there any progress on this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/2029930 Title: wget crash when printing download rate Status in wget package in Ubuntu: Confirmed Status in wget package in Debian: Confirmed Bug description: All supported versions of Ubuntu suffer from crashes in wget in printing of the download speed. I've been getting this on various servers. It's been fixed upstream and should probably be included in 'updates' of all supported Ubuntu versions. https://git.savannah.gnu.org/git/wget.git Commit 04ab35666997fbb3cd5d72497415fb3dfd62dcc5 https://lists.gnu.org/archive/html/bug-wget/2023-08/msg1.html Patch attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/2029930/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2029930] Re: wget crash when printing download rate
Is there any progress in getting it fixed in 'updates'? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/2029930 Title: wget crash when printing download rate Status in wget package in Ubuntu: Confirmed Status in wget package in Debian: Unknown Bug description: All supported versions of Ubuntu suffer from crashes in wget in printing of the download speed. I've been getting this on various servers. It's been fixed upstream and should probably be included in 'updates' of all supported Ubuntu versions. https://git.savannah.gnu.org/git/wget.git Commit 04ab35666997fbb3cd5d72497415fb3dfd62dcc5 https://lists.gnu.org/archive/html/bug-wget/2023-08/msg1.html Patch attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/2029930/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881533] [NEW] Remove expired AddTrust_External_Root.crt because it breaks software
Public bug reported: The AddTrust_External_Root.crt certificate has expired: Data: Version: 3 (0x2) Serial Number: 1 (0x1) Signature Algorithm: sha1WithRSAEncryption Issuer: C=SE, O=AddTrust AB, OU=AddTrust External TTP Network, CN=AddTrust External CA Root Validity Not Before: May 30 10:48:38 2000 GMT Not After : May 30 10:48:38 2020 GMT Subject: C=SE, O=AddTrust AB, OU=AddTrust External TTP Network, CN=AddTrust External CA Root Subject Public Key Info: Public Key Algorithm: rsaEncryption Public-Key: (2048 bit) Modulus: This causes various client-side errors on Ubuntu 16.04 machines, about SSL certificate expiration, using (lib)curl for instance. Ubuntu 18.04 and up seem OK. Removing 'mozilla/AddTrust_External_Root.crt' from /etc/ca- certificates.conf and running 'update-ca-certificates -f -v' helps. I'm not sure if removing it is universally the best solution, but I can't find any other bug reports about this on Launchpad, and this seems the quickest way to fix all clients. ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1881533 Title: Remove expired AddTrust_External_Root.crt because it breaks software Status in ca-certificates package in Ubuntu: New Bug description: The AddTrust_External_Root.crt certificate has expired: Data: Version: 3 (0x2) Serial Number: 1 (0x1) Signature Algorithm: sha1WithRSAEncryption Issuer: C=SE, O=AddTrust AB, OU=AddTrust External TTP Network, CN=AddTrust External CA Root Validity Not Before: May 30 10:48:38 2000 GMT Not After : May 30 10:48:38 2020 GMT Subject: C=SE, O=AddTrust AB, OU=AddTrust External TTP Network, CN=AddTrust External CA Root Subject Public Key Info: Public Key Algorithm: rsaEncryption Public-Key: (2048 bit) Modulus: This causes various client-side errors on Ubuntu 16.04 machines, about SSL certificate expiration, using (lib)curl for instance. Ubuntu 18.04 and up seem OK. Removing 'mozilla/AddTrust_External_Root.crt' from /etc/ca- certificates.conf and running 'update-ca-certificates -f -v' helps. I'm not sure if removing it is universally the best solution, but I can't find any other bug reports about this on Launchpad, and this seems the quickest way to fix all clients. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1881533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822776] Re: [SRU] Apply Bash 4.4.20 to fix cpu spinning on built-in wait
Sorry for the delay. I had to write a bash script that increased the hit-chance of the bug. I now have 13 spinning bash on a non-updated test server. The one with bash 4.20 is working fine. Bash is also working without issues. The new script is attached. So, all good. ** Attachment added: "Script to reproduce the bash crash" https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1822776/+attachment/5275112/+files/bash-crash-test.sh -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1822776 Title: [SRU] Apply Bash 4.4.20 to fix cpu spinning on built-in wait Status in bash package in Ubuntu: Fix Released Status in bash source package in Bionic: Fix Committed Status in bash source package in Cosmic: Fix Committed Bug description: [Impact] Long running bash loops that create and reap processes will crash, hanging at 100% CPU. [Test Case] A PPA with the proposed fix included is at: https://launchpad.net/~bryce/+archive/ubuntu/bash-sru-19-010-1 Install the PPA with the fix via: sudo add-apt-repository ppa:bryce/bash-sru-19-010-1 sudo apt-get update sudo apt-get install bash Run this loop for a few days/weeks: #!/bin/bash while true; do sleep 0.5 & wait done It will eventually cause the 'wait' statement to hang, consuming 100% after some indeterminate amount of time, dependent on how fast PIDs are cycled in the machine. The Bash bug report mentions longer running loops, but it seems hash collisions are the cause, meaning it's just a matter of chance, influenced by how fast PIDs are cycled on the machine. [Regression Potential] The fix has been reviewed and accepted upstream. The patch adds a test at time of pid determination for if the pid is already in use and if so, skip it and pick a different one. This does change behavior slightly in that different pid numbers will be generated in rare cases, but nothing should depend on how pids are generated, as the behavior is not specified to be anything but random. The patch adds a new warning message, "bgp_delete: LOOP: psi (%d) == storage[psi].bucket_next", but this only shows when the original bug would have been triggered. Using 'apt-get source bash' to get the original source version, I created a deb that includes the 4.4.20 patch and have been running it since April 2nd. The 100% CPU spinning is solved, and no other regressions have been observed. Ubuntu 18.04 is already at 4.4.19, which is one patch level behind, so this involves linearly progressing to the next version (so not skipping patches). [Fix] Official patch to fix, and to bump to 4.4.20: http://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 The newest Ubuntu tar.xz with patches I could find at: http://archive.ubuntu.com/ubuntu/pool/main/b/bash/ also didn't have the 4.4.20 patch, so it seems no Ubuntu release has the fix yet. Although not completely sure, this problem seems to have been introduced in the 4.4 version of Bash, so in term of LTS versions, 18.04 and up are affected. [Original Report] Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops when spawning sub processes and waiting for them. There is a fix: https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 Our application started being affected (locking up) by this since migrating from Ubuntu 14.04 to 18.04. Ubuntu 14.04 has bash 4.3.11(1), Ubuntu 18.04 has bash 4.4.19 (that is, when running 'bash --version', because of their unusual versions as patches, apt shows it as 4.4.18-2ubuntu1). The 4.4-020 version needs to be included. I think it's actually quite critical. A justification for including the fix would be that a standard language feature in a script language is broken, and that it's indeterminate when it breaks. Considering the wide spread use of bash, I'm surprised not more people have reported issues. My and a client started having issues with independently of each other very soon after upgrading to an affected version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1822776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822776] Re: [SRU] Apply Bash 4.4.20 to fix cpu spinning on built-in wait
I installed bash from 'proposed' on a test server, and am running some tests on it, and parallel also on normal 18.04 servers. I'll expand this soon, and report back with the results. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1822776 Title: [SRU] Apply Bash 4.4.20 to fix cpu spinning on built-in wait Status in bash package in Ubuntu: Fix Released Status in bash source package in Bionic: Fix Committed Status in bash source package in Cosmic: Fix Committed Bug description: [Impact] Long running bash loops that create and reap processes will crash, hanging at 100% CPU. [Test Case] A PPA with the proposed fix included is at: https://launchpad.net/~bryce/+archive/ubuntu/bash-sru-19-010-1 Install the PPA with the fix via: sudo add-apt-repository ppa:bryce/bash-sru-19-010-1 sudo apt-get update sudo apt-get install bash Run this loop for a few days/weeks: #!/bin/bash while true; do sleep 0.5 & wait done It will eventually cause the 'wait' statement to hang, consuming 100% after some indeterminate amount of time, dependent on how fast PIDs are cycled in the machine. The Bash bug report mentions longer running loops, but it seems hash collisions are the cause, meaning it's just a matter of chance, influenced by how fast PIDs are cycled on the machine. [Regression Potential] The fix has been reviewed and accepted upstream. The patch adds a test at time of pid determination for if the pid is already in use and if so, skip it and pick a different one. This does change behavior slightly in that different pid numbers will be generated in rare cases, but nothing should depend on how pids are generated, as the behavior is not specified to be anything but random. The patch adds a new warning message, "bgp_delete: LOOP: psi (%d) == storage[psi].bucket_next", but this only shows when the original bug would have been triggered. Using 'apt-get source bash' to get the original source version, I created a deb that includes the 4.4.20 patch and have been running it since April 2nd. The 100% CPU spinning is solved, and no other regressions have been observed. Ubuntu 18.04 is already at 4.4.19, which is one patch level behind, so this involves linearly progressing to the next version (so not skipping patches). [Fix] Official patch to fix, and to bump to 4.4.20: http://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 The newest Ubuntu tar.xz with patches I could find at: http://archive.ubuntu.com/ubuntu/pool/main/b/bash/ also didn't have the 4.4.20 patch, so it seems no Ubuntu release has the fix yet. Although not completely sure, this problem seems to have been introduced in the 4.4 version of Bash, so in term of LTS versions, 18.04 and up are affected. [Original Report] Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops when spawning sub processes and waiting for them. There is a fix: https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 Our application started being affected (locking up) by this since migrating from Ubuntu 14.04 to 18.04. Ubuntu 14.04 has bash 4.3.11(1), Ubuntu 18.04 has bash 4.4.19 (that is, when running 'bash --version', because of their unusual versions as patches, apt shows it as 4.4.18-2ubuntu1). The 4.4-020 version needs to be included. I think it's actually quite critical. A justification for including the fix would be that a standard language feature in a script language is broken, and that it's indeterminate when it breaks. Considering the wide spread use of bash, I'm surprised not more people have reported issues. My and a client started having issues with independently of each other very soon after upgrading to an affected version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1822776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822776] Re: Apply Bash 4.4.20 to fix cpu spinning on built-in wait
Thanks; it's not about getting it done yesterday so to speak, so I'll patiently await next week. I suspect you'll be able to reproduce it faster if you lower sysctl kernel.pid_max. With 32k PIDs, one of my apps spawning about a process every two seconds, needed about a week of running to hit it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1822776 Title: Apply Bash 4.4.20 to fix cpu spinning on built-in wait Status in bash package in Ubuntu: New Status in bash source package in Bionic: New Status in bash source package in Cosmic: New Bug description: [Impact] Long running bash loops that create and reap processes will crash, hanging at 100% CPU. [Test Case] Run this loop for a few days/weeks: #!/bin/bash while true; do sleep 0.5 & wait done It will eventually cause the 'wait' statement to hang, consuming 100% after some indeterminate amount of time, dependent on how fast PIDs are cycled in the machine. The Bash bug report mentions longer running loops, but it seems hash collisions are the cause, meaning it's just a matter of chance, influenced by how fast PIDs are cycled on the machine. [Regression Potential] The fix has been reviewed and accepted upstream. The patch adds a test at time of pid determination for if the pid is already in use and if so, skip it and pick a different one. This does change behavior slightly in that different pid numbers will be generated in rare cases, but nothing should depend on how pids are generated, as the behavior is not specified to be anything but random. The patch adds a new warning message, "bgp_delete: LOOP: psi (%d) == storage[psi].bucket_next", but this only shows when the original bug would have been triggered. Using 'apt-get source bash' to get the original source version, I created a deb that includes the 4.4.20 patch and have been running it since April 2nd. The 100% CPU spinning is solved, and no other regressions have been observed. Ubuntu 18.04 is already at 4.4.19, which is one patch level behind, so this involves linearly progressing to the next version (so not skipping patches). [Fix] Official patch to fix, and to bump to 4.4.20: http://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 The newest Ubuntu tar.xz with patches I could find at: http://archive.ubuntu.com/ubuntu/pool/main/b/bash/ also didn't have the 4.4.20 patch, so it seems no Ubuntu release has the fix yet. Although not completely sure, this problem seems to have been introduced in the 4.4 version of Bash, so in term of LTS versions, 18.04 and up are affected. [Original Report] Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops when spawning sub processes and waiting for them. There is a fix: https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 Our application started being affected (locking up) by this since migrating from Ubuntu 14.04 to 18.04. Ubuntu 14.04 has bash 4.3.11(1), Ubuntu 18.04 has bash 4.4.19 (that is, when running 'bash --version', because of their unusual versions as patches, apt shows it as 4.4.18-2ubuntu1). The 4.4-020 version needs to be included. I think it's actually quite critical. A justification for including the fix would be that a standard language feature in a script language is broken, and that it's indeterminate when it breaks. Considering the wide spread use of bash, I'm surprised not more people have reported issues. My and a client started having issues with independently of each other very soon after upgrading to an affected version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1822776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822776] Re: Apply Bash 4.4.20 to fix cpu spinning on built-in wait
I added more info (edited the original description) hoping it covers everything the SRU requires. ** Description changed: Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops when spawning sub processes and waiting for them. There is a fix: https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 Our application started being affected (locking up) by this since migrating from Ubuntu 14.04 to 18.04. Ubuntu 14.04 has bash 4.3.11(1), Ubuntu 18.04 has bash 4.4.19 (that is, when running 'bash --version', because of their unusual versions as patches, apt shows it as 4.4.18-2ubuntu1). The 4.4-020 version needs to be included. I think it's actually quite - critical, also for older Ubuntus. + critical. The Bash bug report mentions longer running loops, but it seems hash collisions are the cause, meaning it's just a matter of chance, influenced by how fast PIDs are cycled on the machine. + + Edit as per the SRU procedure: + +[Impact] + + Long running bash loops that create and reap processes will crash, + hanging at 100% CPU. + + A justification for including the fix would be that a standard language + feature in a script language is broken, and that it's indeterminate when + it breaks. Considering the wide spread use of bash, I'm surprised not + more people have reported issues. My and a client started having issues + with independently of each other very soon after upgrading to an + affected version. + +[Test Case] + + Run this loop for a few days/weeks: + + #!/bin/bash + while true; do + sleep 0.5 & + wait + done + + + It will cause the 'wait' statement to hang, consuming 100% after some indeterminate amount of time, dependent on how fast PIDs are cycled in the machine. + +[Regression Potential] + + Using 'apt-get source bash' to get the original source version, I + created a deb that includes the 4.4.20 patch and have been running it + since April 2nd. The 100% CPU spinning is solved, and no other + regressions have been observed. + + Ubuntu 18.04 is already at 4.4.19, which is one patch level behind, so + this involves linearly progressing to the next version (so not skipping + patches). + +[Other Info] + + Official patch to fix, and to bump to 4.4.20: + + http://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 + + The newest Ubuntu tar.xz with patches I could find at: + + http://archive.ubuntu.com/ubuntu/pool/main/b/bash/ + + also didn't have the 4.4.20 patch, so it seems no Ubuntu release has the + fix yet. + + Although not completely sure, this problem seems to have been introduced + in the 4.4 version of Bash, so in term of LTS versions, 18.04 and up are + affected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1822776 Title: Apply Bash 4.4.20 to fix cpu spinning on built-in wait Status in bash package in Ubuntu: New Bug description: Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops when spawning sub processes and waiting for them. There is a fix: https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 Our application started being affected (locking up) by this since migrating from Ubuntu 14.04 to 18.04. Ubuntu 14.04 has bash 4.3.11(1), Ubuntu 18.04 has bash 4.4.19 (that is, when running 'bash --version', because of their unusual versions as patches, apt shows it as 4.4.18-2ubuntu1). The 4.4-020 version needs to be included. I think it's actually quite critical. The Bash bug report mentions longer running loops, but it seems hash collisions are the cause, meaning it's just a matter of chance, influenced by how fast PIDs are cycled on the machine. Edit as per the SRU procedure: [Impact] Long running bash loops that create and reap processes will crash, hanging at 100% CPU. A justification for including the fix would be that a standard language feature in a script language is broken, and that it's indeterminate when it breaks. Considering the wide spread use of bash, I'm surprised not more people have reported issues. My and a client started having issues with independently of each other very soon after upgrading to an affected version. [Test Case] Run this loop for a few days/weeks: #!/bin/bash while true; do sleep 0.5 & wait done It will cause the 'wait' statement to hang, consuming 100% after some indeterminate amount of time, dependent on how fast PIDs are cycled in the machine. [Regression Potential] Using 'apt-get source bash' to get the original source version, I created a deb that includes the 4.4.20 patch and have been running it since April 2nd. The 100% CPU spinning is solved, and no other regressions have been observed. Ubuntu 18.04 is already at 4.4.19, which is one patch level behind, so this
[Touch-packages] [Bug 1822776] Re: Apply Bash 4.4.20 to fix cpu spinning on built-in wait
I see this bug hasn't gotten attention, but isn't this quite critical? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1822776 Title: Apply Bash 4.4.20 to fix cpu spinning on built-in wait Status in bash package in Ubuntu: New Bug description: Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops when spawning sub processes and waiting for them. There is a fix: https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 Our application started being affected (locking up) by this since migrating from Ubuntu 14.04 to 18.04. Ubuntu 14.04 has bash 4.3.11(1), Ubuntu 18.04 has bash 4.4.19 (that is, when running 'bash --version', because of their unusual versions as patches, apt shows it as 4.4.18-2ubuntu1). The 4.4-020 version needs to be included. I think it's actually quite critical, also for older Ubuntus. The Bash bug report mentions longer running loops, but it seems hash collisions are the cause, meaning it's just a matter of chance, influenced by how fast PIDs are cycled on the machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1822776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822776] [NEW] Apply Bash 4.4.20 to fix cpu spinning on built-in wait
Public bug reported: Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops when spawning sub processes and waiting for them. There is a fix: https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 Our application started being affected (locking up) by this since migrating from Ubuntu 14.04 to 18.04. Ubuntu 14.04 has bash 4.3.11(1), Ubuntu 18.04 has bash 4.4.19 (that is, when running 'bash --version', because of their unusual versions as patches, apt shows it as 4.4.18-2ubuntu1). The 4.4-020 version needs to be included. I think it's actually quite critical, also for older Ubuntus. The Bash bug report mentions longer running loops, but it seems hash collisions are the cause, meaning it's just a matter of chance, influenced by how fast PIDs are cycled on the machine. ** Affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1822776 Title: Apply Bash 4.4.20 to fix cpu spinning on built-in wait Status in bash package in Ubuntu: New Bug description: Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops when spawning sub processes and waiting for them. There is a fix: https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 Our application started being affected (locking up) by this since migrating from Ubuntu 14.04 to 18.04. Ubuntu 14.04 has bash 4.3.11(1), Ubuntu 18.04 has bash 4.4.19 (that is, when running 'bash --version', because of their unusual versions as patches, apt shows it as 4.4.18-2ubuntu1). The 4.4-020 version needs to be included. I think it's actually quite critical, also for older Ubuntus. The Bash bug report mentions longer running loops, but it seems hash collisions are the cause, meaning it's just a matter of chance, influenced by how fast PIDs are cycled on the machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1822776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 998223] Re: Turns on IPv6 privacy extensions regardless of settings in 10-ipv6-privacy.conf
I seem to be getting the same behavior in Ubuntu 18.04 with the new Netplan. I configured a static address, and regardless of the sysctl settings, I'm getting a privacy extensions address, which is undesirable on (my) servers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/998223 Title: Turns on IPv6 privacy extensions regardless of settings in 10-ipv6-privacy.conf Status in network-manager package in Ubuntu: Fix Released Bug description: After installing the latest network-manager package that fixes bug 990011, I noticed that my IPv6 address was suddenly different because IPv6 privacy extensions had been turned on. Turning them off in /etc/sysctl.d/10-ipv6-privacy.conf doesn't stop network-manager from enabling it. I'm using the default automatically generated wired connection, so there are no connection settings in /etc/NetworkManager /system-connections. If I change some settings so that NM writes the connection to system- connections and then add ip6-privacy=0 to the configuration the privacy extensions are turned off, but it would be nice if that was also the case when it is turned of using /etc/sysctl.d/10-ipv6-privacy.conf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/998223/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673717] Re: rsyslog GnuTLS error -50
** Bug watch added: Debian Bug tracker #832995 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832995 ** Also affects: rsyslog (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832995 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1673717 Title: rsyslog GnuTLS error -50 Status in rsyslog package in Ubuntu: New Status in rsyslog package in Debian: Unknown Bug description: Exactly the same as this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832995 Error: > rsyslogd-2078: unexpected GnuTLS error -50 in nsd_gtls.c:530: The > request is invalid. [v8.16.0 try http://www.rsyslog.com/e/2078 ] Provided patch in https://github.com/rsyslog/rsyslog/issues/732 works. Please apply patch or upgrade rsyslog. Ubuntu 16.04 AMD64 Rsyslog 8.16.0-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1673717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673717] Re: rsyslog GnuTLS error -50
What is this bug's destiny? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1673717 Title: rsyslog GnuTLS error -50 Status in rsyslog package in Ubuntu: New Bug description: Exactly the same as this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832995 Error: > rsyslogd-2078: unexpected GnuTLS error -50 in nsd_gtls.c:530: The > request is invalid. [v8.16.0 try http://www.rsyslog.com/e/2078 ] Provided patch in https://github.com/rsyslog/rsyslog/issues/732 works. Please apply patch or upgrade rsyslog. Ubuntu 16.04 AMD64 Rsyslog 8.16.0-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1673717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673717] [NEW] rsyslog GnuTLS error -50
Public bug reported: Exactly the same as this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832995 Error: > rsyslogd-2078: unexpected GnuTLS error -50 in nsd_gtls.c:530: The > request is invalid. [v8.16.0 try http://www.rsyslog.com/e/2078 ] Provided patch in https://github.com/rsyslog/rsyslog/issues/732 works. Please apply patch or upgrade rsyslog. Ubuntu 16.04 AMD64 Rsyslog 8.16.0-1ubuntu3 ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1673717 Title: rsyslog GnuTLS error -50 Status in rsyslog package in Ubuntu: New Bug description: Exactly the same as this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832995 Error: > rsyslogd-2078: unexpected GnuTLS error -50 in nsd_gtls.c:530: The > request is invalid. [v8.16.0 try http://www.rsyslog.com/e/2078 ] Provided patch in https://github.com/rsyslog/rsyslog/issues/732 works. Please apply patch or upgrade rsyslog. Ubuntu 16.04 AMD64 Rsyslog 8.16.0-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1673717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1652755] Re: Resolvconf multiple nameservers and search domains only first is used - quote bug
Ha, you're right, I introduced a bug to my advantage. Can I propose this other patch instead? Some clear output would be nice. ** Patch added: "Print messages when discarding nameservers" https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1652755/+attachment/4797448/+files/resolvconf-messages.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1652755 Title: Resolvconf multiple nameservers and search domains only first is used - quote bug Status in resolvconf package in Ubuntu: Incomplete Bug description: Having more than one 'nameserver' or 'search' entry in any of the source files results in only the first one being used. The cause is a quote bug in /etc/resolvconf/update.d/libc. Patch attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1652755/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1652755] [NEW] Resolvconf multiple nameservers and search domains only first is used - quote bug
Public bug reported: Having more than one 'nameserver' or 'search' entry in any of the source files results in only the first one being used. The cause is a quote bug in /etc/resolvconf/update.d/libc. Patch attached. ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Patch added: "Fix quote bug" https://bugs.launchpad.net/bugs/1652755/+attachment/4796999/+files/libc.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1652755 Title: Resolvconf multiple nameservers and search domains only first is used - quote bug Status in resolvconf package in Ubuntu: New Bug description: Having more than one 'nameserver' or 'search' entry in any of the source files results in only the first one being used. The cause is a quote bug in /etc/resolvconf/update.d/libc. Patch attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1652755/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
