| 2019-02-15 05:15:46 |
Haw Loeung |
bug |
|
|
added bug |
| 2019-02-15 05:15:57 |
Haw Loeung |
bug |
|
|
added subscriber The Canonical Sysadmins |
| 2019-02-15 05:16:14 |
Haw Loeung |
nominated for series |
|
Ubuntu Cosmic |
|
| 2019-02-15 05:16:14 |
Haw Loeung |
bug task added |
|
squid (Ubuntu Cosmic) |
|
| 2019-02-15 05:16:14 |
Haw Loeung |
nominated for series |
|
Ubuntu Disco |
|
| 2019-02-15 05:16:14 |
Haw Loeung |
bug task added |
|
squid (Ubuntu Disco) |
|
| 2019-02-19 15:44:08 |
Andreas Hasenack |
bug |
|
|
added subscriber Ubuntu Server |
| 2019-02-19 15:45:00 |
Andreas Hasenack |
squid (Ubuntu Cosmic): status |
New |
Triaged |
|
| 2019-02-19 15:45:03 |
Andreas Hasenack |
squid (Ubuntu Disco): status |
New |
Triaged |
|
| 2019-02-19 15:45:46 |
Andreas Hasenack |
bug |
|
|
added subscriber Andreas Hasenack |
| 2019-02-20 10:09:33 |
Andreas Hasenack |
squid (Ubuntu Cosmic): importance |
Undecided |
High |
|
| 2019-02-20 10:09:37 |
Andreas Hasenack |
squid (Ubuntu Disco): importance |
Undecided |
High |
|
| 2019-02-20 10:30:11 |
Andreas Hasenack |
squid (Ubuntu Disco): assignee |
|
Andreas Hasenack (ahasenack) |
|
| 2019-02-20 10:30:16 |
Andreas Hasenack |
squid (Ubuntu Disco): status |
Triaged |
In Progress |
|
| 2019-02-22 04:23:33 |
Amos Jeffries |
bug task added |
|
squid (Debian) |
|
| 2019-02-22 04:23:53 |
Amos Jeffries |
squid (Debian): status |
New |
Fix Released |
|
| 2019-02-27 13:25:45 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/squid/+git/squid/+merge/363726 |
|
| 2019-02-28 17:40:31 |
Andreas Hasenack |
squid (Ubuntu Cosmic): status |
Triaged |
In Progress |
|
| 2019-02-28 17:40:33 |
Andreas Hasenack |
squid (Ubuntu Cosmic): assignee |
|
Andreas Hasenack (ahasenack) |
|
| 2019-02-28 18:36:57 |
Andreas Hasenack |
description |
Hi,
On squid service start up in Bionic, /var/run/squid is created by /etc/init.d/squid (create_run_dir()). This doesn't happen in Cosmic nor Disco and probably is related to the migration to systemd.
Squid needs to create the squid-kid-*.ipc UNIX sockets in /var/run/squid to function on SMP set ups (workers X).
Steps to reproduce:
* spin up fresh cosmic or bionic instance/machine
* install squid
* configure 'workers 5' or enable the Rock Store cache storage type
* reboot instance
* try start up squid.
Logging shows this:
| 2019/02/15 04:46:58 kid1| commBind Cannot bind socket FD 28 to [::]: (2) No such file or directory |
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Case]
* detailed instructions how to reproduce the bug
* these should allow someone who is not familiar with the affected
package to reproduce the bug and verify that the updated package fixes
the problem.
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
Hi,
On squid service start up in Bionic, /var/run/squid is created by /etc/init.d/squid (create_run_dir()). This doesn't happen in Cosmic nor Disco and probably is related to the migration to systemd.
Squid needs to create the squid-kid-*.ipc UNIX sockets in /var/run/squid to function on SMP set ups (workers X).
Steps to reproduce:
* spin up fresh cosmic or bionic instance/machine
* install squid
* configure 'workers 5' or enable the Rock Store cache storage type
* reboot instance
* try start up squid.
Logging shows this:
| 2019/02/15 04:46:58 kid1| commBind Cannot bind socket FD 28 to [::]: (2) No such file or directory |
|
| 2019-02-28 18:37:14 |
Andreas Hasenack |
description |
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Case]
* detailed instructions how to reproduce the bug
* these should allow someone who is not familiar with the affected
package to reproduce the bug and verify that the updated package fixes
the problem.
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
Hi,
On squid service start up in Bionic, /var/run/squid is created by /etc/init.d/squid (create_run_dir()). This doesn't happen in Cosmic nor Disco and probably is related to the migration to systemd.
Squid needs to create the squid-kid-*.ipc UNIX sockets in /var/run/squid to function on SMP set ups (workers X).
Steps to reproduce:
* spin up fresh cosmic or bionic instance/machine
* install squid
* configure 'workers 5' or enable the Rock Store cache storage type
* reboot instance
* try start up squid.
Logging shows this:
| 2019/02/15 04:46:58 kid1| commBind Cannot bind socket FD 28 to [::]: (2) No such file or directory |
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Case]
* install squid
sudo apt update && sudo apt install squid -y
* verify there is no /var/run/squid directory
$ sudo ls -la /var/run/squid
ls: cannot access '/var/run/squid': No such file or directory
* Due to bug #1815852, squid won't work correctly even after that directory is created, so let's consider the above enough to confirm this bug here.
With the updated packages, the directory exists, and, due to the restart done by the upgade, it is populated:
$ sudo ls -la /var/run/squid
total 0
drwxr-xr-x 2 proxy proxy 160 Feb 28 18:35 .
drwxr-xr-x 22 root root 820 Feb 28 18:35 ..
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-coordinator.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-1.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-2.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-3.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-4.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-5.ipc
* and the proxy works:
$ http_proxy=http://localhost:3128/ wget http://www.ubuntu.com -O /dev/null
--2019-02-28 18:35:59-- http://www.ubuntu.com/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:3128... connected.
Proxy request sent, awaiting response... 302 Found
Location: https://www.ubuntu.com/ [following]
--2019-02-28 18:36:00-- https://www.ubuntu.com/
Resolving www.ubuntu.com (www.ubuntu.com)... 91.189.89.115
Connecting to www.ubuntu.com (www.ubuntu.com)|91.189.89.115|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/null’
/dev/null [ <=> ] 129.75K 148KB/s in 0.9s
2019-02-28 18:36:02 (148 KB/s) - ‘/dev/null’ saved [132866]
$ echo $?
0
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
Hi,
On squid service start up in Bionic, /var/run/squid is created by /etc/init.d/squid (create_run_dir()). This doesn't happen in Cosmic nor Disco and probably is related to the migration to systemd.
Squid needs to create the squid-kid-*.ipc UNIX sockets in /var/run/squid to function on SMP set ups (workers X).
Steps to reproduce:
* spin up fresh cosmic or bionic instance/machine
* install squid
* configure 'workers 5' or enable the Rock Store cache storage type
* reboot instance
* try start up squid.
Logging shows this:
| 2019/02/15 04:46:58 kid1| commBind Cannot bind socket FD 28 to [::]: (2) No such file or directory |
|
| 2019-02-28 18:38:26 |
Andreas Hasenack |
description |
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Case]
* install squid
sudo apt update && sudo apt install squid -y
* verify there is no /var/run/squid directory
$ sudo ls -la /var/run/squid
ls: cannot access '/var/run/squid': No such file or directory
* Due to bug #1815852, squid won't work correctly even after that directory is created, so let's consider the above enough to confirm this bug here.
With the updated packages, the directory exists, and, due to the restart done by the upgade, it is populated:
$ sudo ls -la /var/run/squid
total 0
drwxr-xr-x 2 proxy proxy 160 Feb 28 18:35 .
drwxr-xr-x 22 root root 820 Feb 28 18:35 ..
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-coordinator.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-1.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-2.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-3.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-4.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-5.ipc
* and the proxy works:
$ http_proxy=http://localhost:3128/ wget http://www.ubuntu.com -O /dev/null
--2019-02-28 18:35:59-- http://www.ubuntu.com/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:3128... connected.
Proxy request sent, awaiting response... 302 Found
Location: https://www.ubuntu.com/ [following]
--2019-02-28 18:36:00-- https://www.ubuntu.com/
Resolving www.ubuntu.com (www.ubuntu.com)... 91.189.89.115
Connecting to www.ubuntu.com (www.ubuntu.com)|91.189.89.115|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/null’
/dev/null [ <=> ] 129.75K 148KB/s in 0.9s
2019-02-28 18:36:02 (148 KB/s) - ‘/dev/null’ saved [132866]
$ echo $?
0
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
Hi,
On squid service start up in Bionic, /var/run/squid is created by /etc/init.d/squid (create_run_dir()). This doesn't happen in Cosmic nor Disco and probably is related to the migration to systemd.
Squid needs to create the squid-kid-*.ipc UNIX sockets in /var/run/squid to function on SMP set ups (workers X).
Steps to reproduce:
* spin up fresh cosmic or bionic instance/machine
* install squid
* configure 'workers 5' or enable the Rock Store cache storage type
* reboot instance
* try start up squid.
Logging shows this:
| 2019/02/15 04:46:58 kid1| commBind Cannot bind socket FD 28 to [::]: (2) No such file or directory |
[Impact]
Squid in SMP mode, when "workers <N>" is set in squid.conf, uses /var/run/squid for several ipc sockets. This directory is not created by the packaging/service and as a result squid doesn't work in this situation.
[Test Case]
* install squid
sudo apt update && sudo apt install squid -y
* verify there is no /var/run/squid directory
$ sudo ls -la /var/run/squid
ls: cannot access '/var/run/squid': No such file or directory
* Due to bug #1815852, squid won't work correctly even after that directory is created, so let's consider the above enough to confirm this bug here.
With the updated packages, the directory exists, and, due to the restart done by the upgade, it is populated:
$ sudo ls -la /var/run/squid
total 0
drwxr-xr-x 2 proxy proxy 160 Feb 28 18:35 .
drwxr-xr-x 22 root root 820 Feb 28 18:35 ..
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-coordinator.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-1.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-2.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-3.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-4.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-5.ipc
* and the proxy works:
$ http_proxy=http://localhost:3128/ wget http://www.ubuntu.com -O /dev/null
--2019-02-28 18:35:59-- http://www.ubuntu.com/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:3128... connected.
Proxy request sent, awaiting response... 302 Found
Location: https://www.ubuntu.com/ [following]
--2019-02-28 18:36:00-- https://www.ubuntu.com/
Resolving www.ubuntu.com (www.ubuntu.com)... 91.189.89.115
Connecting to www.ubuntu.com (www.ubuntu.com)|91.189.89.115|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/null’
/dev/null [ <=> ] 129.75K 148KB/s in 0.9s
2019-02-28 18:36:02 (148 KB/s) - ‘/dev/null’ saved [132866]
$ echo $?
0
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
Hi,
On squid service start up in Bionic, /var/run/squid is created by /etc/init.d/squid (create_run_dir()). This doesn't happen in Cosmic nor Disco and probably is related to the migration to systemd.
Squid needs to create the squid-kid-*.ipc UNIX sockets in /var/run/squid to function on SMP set ups (workers X).
Steps to reproduce:
* spin up fresh cosmic or bionic instance/machine
* install squid
* configure 'workers 5' or enable the Rock Store cache storage type
* reboot instance
* try start up squid.
Logging shows this:
| 2019/02/15 04:46:58 kid1| commBind Cannot bind socket FD 28 to [::]: (2) No such file or directory |
|
| 2019-02-28 18:38:51 |
Andreas Hasenack |
description |
[Impact]
Squid in SMP mode, when "workers <N>" is set in squid.conf, uses /var/run/squid for several ipc sockets. This directory is not created by the packaging/service and as a result squid doesn't work in this situation.
[Test Case]
* install squid
sudo apt update && sudo apt install squid -y
* verify there is no /var/run/squid directory
$ sudo ls -la /var/run/squid
ls: cannot access '/var/run/squid': No such file or directory
* Due to bug #1815852, squid won't work correctly even after that directory is created, so let's consider the above enough to confirm this bug here.
With the updated packages, the directory exists, and, due to the restart done by the upgade, it is populated:
$ sudo ls -la /var/run/squid
total 0
drwxr-xr-x 2 proxy proxy 160 Feb 28 18:35 .
drwxr-xr-x 22 root root 820 Feb 28 18:35 ..
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-coordinator.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-1.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-2.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-3.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-4.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-5.ipc
* and the proxy works:
$ http_proxy=http://localhost:3128/ wget http://www.ubuntu.com -O /dev/null
--2019-02-28 18:35:59-- http://www.ubuntu.com/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:3128... connected.
Proxy request sent, awaiting response... 302 Found
Location: https://www.ubuntu.com/ [following]
--2019-02-28 18:36:00-- https://www.ubuntu.com/
Resolving www.ubuntu.com (www.ubuntu.com)... 91.189.89.115
Connecting to www.ubuntu.com (www.ubuntu.com)|91.189.89.115|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/null’
/dev/null [ <=> ] 129.75K 148KB/s in 0.9s
2019-02-28 18:36:02 (148 KB/s) - ‘/dev/null’ saved [132866]
$ echo $?
0
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
Hi,
On squid service start up in Bionic, /var/run/squid is created by /etc/init.d/squid (create_run_dir()). This doesn't happen in Cosmic nor Disco and probably is related to the migration to systemd.
Squid needs to create the squid-kid-*.ipc UNIX sockets in /var/run/squid to function on SMP set ups (workers X).
Steps to reproduce:
* spin up fresh cosmic or bionic instance/machine
* install squid
* configure 'workers 5' or enable the Rock Store cache storage type
* reboot instance
* try start up squid.
Logging shows this:
| 2019/02/15 04:46:58 kid1| commBind Cannot bind socket FD 28 to [::]: (2) No such file or directory |
[Impact]
Squid in SMP mode, when "workers <N>" is set in squid.conf, uses /var/run/squid for several ipc sockets. This directory is not created by the packaging/service and as a result squid doesn't work in this situation.
[Test Case]
* install squid
sudo apt update && sudo apt install squid -y
* verify there is no /var/run/squid directory
$ sudo ls -la /var/run/squid
ls: cannot access '/var/run/squid': No such file or directory
* Due to bug #1815852, squid won't work correctly even after that directory is created, so let's consider the above enough to confirm this bug here.
With the updated packages, which also fix #1815852, the directory exists, and, due to the restart done by the upgade, it is populated:
$ sudo ls -la /var/run/squid
total 0
drwxr-xr-x 2 proxy proxy 160 Feb 28 18:35 .
drwxr-xr-x 22 root root 820 Feb 28 18:35 ..
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-coordinator.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-1.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-2.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-3.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-4.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-5.ipc
* and the proxy works:
$ http_proxy=http://localhost:3128/ wget http://www.ubuntu.com -O /dev/null
--2019-02-28 18:35:59-- http://www.ubuntu.com/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:3128... connected.
Proxy request sent, awaiting response... 302 Found
Location: https://www.ubuntu.com/ [following]
--2019-02-28 18:36:00-- https://www.ubuntu.com/
Resolving www.ubuntu.com (www.ubuntu.com)... 91.189.89.115
Connecting to www.ubuntu.com (www.ubuntu.com)|91.189.89.115|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/null’
/dev/null [ <=> ] 129.75K 148KB/s in 0.9s
2019-02-28 18:36:02 (148 KB/s) - ‘/dev/null’ saved [132866]
$ echo $?
0
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
Hi,
On squid service start up in Bionic, /var/run/squid is created by /etc/init.d/squid (create_run_dir()). This doesn't happen in Cosmic nor Disco and probably is related to the migration to systemd.
Squid needs to create the squid-kid-*.ipc UNIX sockets in /var/run/squid to function on SMP set ups (workers X).
Steps to reproduce:
* spin up fresh cosmic or bionic instance/machine
* install squid
* configure 'workers 5' or enable the Rock Store cache storage type
* reboot instance
* try start up squid.
Logging shows this:
| 2019/02/15 04:46:58 kid1| commBind Cannot bind socket FD 28 to [::]: (2) No such file or directory |
|
| 2019-02-28 18:39:04 |
Andreas Hasenack |
description |
[Impact]
Squid in SMP mode, when "workers <N>" is set in squid.conf, uses /var/run/squid for several ipc sockets. This directory is not created by the packaging/service and as a result squid doesn't work in this situation.
[Test Case]
* install squid
sudo apt update && sudo apt install squid -y
* verify there is no /var/run/squid directory
$ sudo ls -la /var/run/squid
ls: cannot access '/var/run/squid': No such file or directory
* Due to bug #1815852, squid won't work correctly even after that directory is created, so let's consider the above enough to confirm this bug here.
With the updated packages, which also fix #1815852, the directory exists, and, due to the restart done by the upgade, it is populated:
$ sudo ls -la /var/run/squid
total 0
drwxr-xr-x 2 proxy proxy 160 Feb 28 18:35 .
drwxr-xr-x 22 root root 820 Feb 28 18:35 ..
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-coordinator.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-1.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-2.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-3.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-4.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-5.ipc
* and the proxy works:
$ http_proxy=http://localhost:3128/ wget http://www.ubuntu.com -O /dev/null
--2019-02-28 18:35:59-- http://www.ubuntu.com/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:3128... connected.
Proxy request sent, awaiting response... 302 Found
Location: https://www.ubuntu.com/ [following]
--2019-02-28 18:36:00-- https://www.ubuntu.com/
Resolving www.ubuntu.com (www.ubuntu.com)... 91.189.89.115
Connecting to www.ubuntu.com (www.ubuntu.com)|91.189.89.115|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/null’
/dev/null [ <=> ] 129.75K 148KB/s in 0.9s
2019-02-28 18:36:02 (148 KB/s) - ‘/dev/null’ saved [132866]
$ echo $?
0
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
Hi,
On squid service start up in Bionic, /var/run/squid is created by /etc/init.d/squid (create_run_dir()). This doesn't happen in Cosmic nor Disco and probably is related to the migration to systemd.
Squid needs to create the squid-kid-*.ipc UNIX sockets in /var/run/squid to function on SMP set ups (workers X).
Steps to reproduce:
* spin up fresh cosmic or bionic instance/machine
* install squid
* configure 'workers 5' or enable the Rock Store cache storage type
* reboot instance
* try start up squid.
Logging shows this:
| 2019/02/15 04:46:58 kid1| commBind Cannot bind socket FD 28 to [::]: (2) No such file or directory |
[Impact]
Squid in SMP mode, when "workers <N>" is set in squid.conf, uses /var/run/squid for several ipc sockets. This directory is not created by the packaging/service and as a result squid doesn't work in this situation.
[Test Case]
* install squid
sudo apt update && sudo apt install squid -y
* verify there is no /var/run/squid directory
$ sudo ls -la /var/run/squid
ls: cannot access '/var/run/squid': No such file or directory
* Due to bug #1815852, squid won't work correctly even after that directory is created, so let's consider the above enough to confirm this bug here.
With the updated packages, which also fix #1815852, the directory exists, and, due to the restart done by the upgrade, it is populated:
$ sudo ls -la /var/run/squid
total 0
drwxr-xr-x 2 proxy proxy 160 Feb 28 18:35 .
drwxr-xr-x 22 root root 820 Feb 28 18:35 ..
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-coordinator.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-1.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-2.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-3.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-4.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-5.ipc
* and the proxy works:
$ http_proxy=http://localhost:3128/ wget http://www.ubuntu.com -O /dev/null
--2019-02-28 18:35:59-- http://www.ubuntu.com/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:3128... connected.
Proxy request sent, awaiting response... 302 Found
Location: https://www.ubuntu.com/ [following]
--2019-02-28 18:36:00-- https://www.ubuntu.com/
Resolving www.ubuntu.com (www.ubuntu.com)... 91.189.89.115
Connecting to www.ubuntu.com (www.ubuntu.com)|91.189.89.115|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/null’
/dev/null [ <=> ] 129.75K 148KB/s in 0.9s
2019-02-28 18:36:02 (148 KB/s) - ‘/dev/null’ saved [132866]
$ echo $?
0
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
Hi,
On squid service start up in Bionic, /var/run/squid is created by /etc/init.d/squid (create_run_dir()). This doesn't happen in Cosmic nor Disco and probably is related to the migration to systemd.
Squid needs to create the squid-kid-*.ipc UNIX sockets in /var/run/squid to function on SMP set ups (workers X).
Steps to reproduce:
* spin up fresh cosmic or bionic instance/machine
* install squid
* configure 'workers 5' or enable the Rock Store cache storage type
* reboot instance
* try start up squid.
Logging shows this:
| 2019/02/15 04:46:58 kid1| commBind Cannot bind socket FD 28 to [::]: (2) No such file or directory |
|
| 2019-02-28 18:39:14 |
Andreas Hasenack |
description |
[Impact]
Squid in SMP mode, when "workers <N>" is set in squid.conf, uses /var/run/squid for several ipc sockets. This directory is not created by the packaging/service and as a result squid doesn't work in this situation.
[Test Case]
* install squid
sudo apt update && sudo apt install squid -y
* verify there is no /var/run/squid directory
$ sudo ls -la /var/run/squid
ls: cannot access '/var/run/squid': No such file or directory
* Due to bug #1815852, squid won't work correctly even after that directory is created, so let's consider the above enough to confirm this bug here.
With the updated packages, which also fix #1815852, the directory exists, and, due to the restart done by the upgrade, it is populated:
$ sudo ls -la /var/run/squid
total 0
drwxr-xr-x 2 proxy proxy 160 Feb 28 18:35 .
drwxr-xr-x 22 root root 820 Feb 28 18:35 ..
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-coordinator.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-1.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-2.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-3.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-4.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-5.ipc
* and the proxy works:
$ http_proxy=http://localhost:3128/ wget http://www.ubuntu.com -O /dev/null
--2019-02-28 18:35:59-- http://www.ubuntu.com/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:3128... connected.
Proxy request sent, awaiting response... 302 Found
Location: https://www.ubuntu.com/ [following]
--2019-02-28 18:36:00-- https://www.ubuntu.com/
Resolving www.ubuntu.com (www.ubuntu.com)... 91.189.89.115
Connecting to www.ubuntu.com (www.ubuntu.com)|91.189.89.115|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/null’
/dev/null [ <=> ] 129.75K 148KB/s in 0.9s
2019-02-28 18:36:02 (148 KB/s) - ‘/dev/null’ saved [132866]
$ echo $?
0
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
Hi,
On squid service start up in Bionic, /var/run/squid is created by /etc/init.d/squid (create_run_dir()). This doesn't happen in Cosmic nor Disco and probably is related to the migration to systemd.
Squid needs to create the squid-kid-*.ipc UNIX sockets in /var/run/squid to function on SMP set ups (workers X).
Steps to reproduce:
* spin up fresh cosmic or bionic instance/machine
* install squid
* configure 'workers 5' or enable the Rock Store cache storage type
* reboot instance
* try start up squid.
Logging shows this:
| 2019/02/15 04:46:58 kid1| commBind Cannot bind socket FD 28 to [::]: (2) No such file or directory |
[Impact]
Squid in SMP mode, when "workers <N>" is set in squid.conf, uses /var/run/squid for several ipc sockets. This directory is not created by the packaging/service and as a result squid doesn't work in this situation.
[Test Case]
* install squid
sudo apt update && sudo apt install squid -y
* verify there is no /var/run/squid directory
$ sudo ls -la /var/run/squid
ls: cannot access '/var/run/squid': No such file or directory
* Due to bug #1815852, squid won't work correctly even after that directory is created, so let's consider the above enough to confirm this bug here.
With the updated packages, which also fix #1815852, the directory exists, and, due to the restart done by the upgrade, is populated already:
$ sudo ls -la /var/run/squid
total 0
drwxr-xr-x 2 proxy proxy 160 Feb 28 18:35 .
drwxr-xr-x 22 root root 820 Feb 28 18:35 ..
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-coordinator.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-1.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-2.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-3.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-4.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-5.ipc
* and the proxy works:
$ http_proxy=http://localhost:3128/ wget http://www.ubuntu.com -O /dev/null
--2019-02-28 18:35:59-- http://www.ubuntu.com/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:3128... connected.
Proxy request sent, awaiting response... 302 Found
Location: https://www.ubuntu.com/ [following]
--2019-02-28 18:36:00-- https://www.ubuntu.com/
Resolving www.ubuntu.com (www.ubuntu.com)... 91.189.89.115
Connecting to www.ubuntu.com (www.ubuntu.com)|91.189.89.115|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/null’
/dev/null [ <=> ] 129.75K 148KB/s in 0.9s
2019-02-28 18:36:02 (148 KB/s) - ‘/dev/null’ saved [132866]
$ echo $?
0
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
Hi,
On squid service start up in Bionic, /var/run/squid is created by /etc/init.d/squid (create_run_dir()). This doesn't happen in Cosmic nor Disco and probably is related to the migration to systemd.
Squid needs to create the squid-kid-*.ipc UNIX sockets in /var/run/squid to function on SMP set ups (workers X).
Steps to reproduce:
* spin up fresh cosmic or bionic instance/machine
* install squid
* configure 'workers 5' or enable the Rock Store cache storage type
* reboot instance
* try start up squid.
Logging shows this:
| 2019/02/15 04:46:58 kid1| commBind Cannot bind socket FD 28 to [::]: (2) No such file or directory |
|
| 2019-02-28 18:43:33 |
Andreas Hasenack |
description |
[Impact]
Squid in SMP mode, when "workers <N>" is set in squid.conf, uses /var/run/squid for several ipc sockets. This directory is not created by the packaging/service and as a result squid doesn't work in this situation.
[Test Case]
* install squid
sudo apt update && sudo apt install squid -y
* verify there is no /var/run/squid directory
$ sudo ls -la /var/run/squid
ls: cannot access '/var/run/squid': No such file or directory
* Due to bug #1815852, squid won't work correctly even after that directory is created, so let's consider the above enough to confirm this bug here.
With the updated packages, which also fix #1815852, the directory exists, and, due to the restart done by the upgrade, is populated already:
$ sudo ls -la /var/run/squid
total 0
drwxr-xr-x 2 proxy proxy 160 Feb 28 18:35 .
drwxr-xr-x 22 root root 820 Feb 28 18:35 ..
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-coordinator.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-1.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-2.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-3.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-4.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-5.ipc
* and the proxy works:
$ http_proxy=http://localhost:3128/ wget http://www.ubuntu.com -O /dev/null
--2019-02-28 18:35:59-- http://www.ubuntu.com/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:3128... connected.
Proxy request sent, awaiting response... 302 Found
Location: https://www.ubuntu.com/ [following]
--2019-02-28 18:36:00-- https://www.ubuntu.com/
Resolving www.ubuntu.com (www.ubuntu.com)... 91.189.89.115
Connecting to www.ubuntu.com (www.ubuntu.com)|91.189.89.115|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/null’
/dev/null [ <=> ] 129.75K 148KB/s in 0.9s
2019-02-28 18:36:02 (148 KB/s) - ‘/dev/null’ saved [132866]
$ echo $?
0
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
Hi,
On squid service start up in Bionic, /var/run/squid is created by /etc/init.d/squid (create_run_dir()). This doesn't happen in Cosmic nor Disco and probably is related to the migration to systemd.
Squid needs to create the squid-kid-*.ipc UNIX sockets in /var/run/squid to function on SMP set ups (workers X).
Steps to reproduce:
* spin up fresh cosmic or bionic instance/machine
* install squid
* configure 'workers 5' or enable the Rock Store cache storage type
* reboot instance
* try start up squid.
Logging shows this:
| 2019/02/15 04:46:58 kid1| commBind Cannot bind socket FD 28 to [::]: (2) No such file or directory |
[Impact]
Squid in SMP mode, when "workers <N>" is set in squid.conf, uses /var/run/squid for several ipc sockets. This directory is not created by the packaging/service and as a result squid doesn't work in this situation.
[Test Case]
* install squid
sudo apt update && sudo apt install squid -y
* verify there is no /var/run/squid directory
$ sudo ls -la /var/run/squid
ls: cannot access '/var/run/squid': No such file or directory
* Due to bug #1815852, squid won't work correctly even after that directory is created, so let's consider the above enough to confirm this bug here.
With the updated packages, which also fix #1815852, the directory exists, and, due to the restart done by the upgrade, is populated already:
$ sudo ls -la /var/run/squid
total 0
drwxr-xr-x 2 proxy proxy 160 Feb 28 18:35 .
drwxr-xr-x 22 root root 820 Feb 28 18:35 ..
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-coordinator.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-1.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-2.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-3.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-4.ipc
srwxr-x--- 1 proxy proxy 0 Feb 28 18:35 squid-kid-5.ipc
* and the proxy works:
$ http_proxy=http://localhost:3128/ wget http://www.ubuntu.com -O /dev/null
--2019-02-28 18:35:59-- http://www.ubuntu.com/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:3128... connected.
Proxy request sent, awaiting response... 302 Found
Location: https://www.ubuntu.com/ [following]
--2019-02-28 18:36:00-- https://www.ubuntu.com/
Resolving www.ubuntu.com (www.ubuntu.com)... 91.189.89.115
Connecting to www.ubuntu.com (www.ubuntu.com)|91.189.89.115|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/null’
/dev/null [ <=> ] 129.75K 148KB/s in 0.9s
2019-02-28 18:36:02 (148 KB/s) - ‘/dev/null’ saved [132866]
$ echo $?
0
[Regression Potential]
The fix tells systemd to create the runtime directory /run/squid (to which /var/run is a symlink) via the tmpfiles.d mechanism, a solution used by many other services already as can be seen in "ls -la /usr/lib/tmpfiles.d". This only works for systemd systems, which is the case of cosmic and disco.
The fix is already in disco, but going through migration at the moment.
[Other Info]
Not at this time.
[Original Description]
Hi,
On squid service start up in Bionic, /var/run/squid is created by /etc/init.d/squid (create_run_dir()). This doesn't happen in Cosmic nor Disco and probably is related to the migration to systemd.
Squid needs to create the squid-kid-*.ipc UNIX sockets in /var/run/squid to function on SMP set ups (workers X).
Steps to reproduce:
* spin up fresh cosmic or bionic instance/machine
* install squid
* configure 'workers 5' or enable the Rock Store cache storage type
* reboot instance
* try start up squid.
Logging shows this:
| 2019/02/15 04:46:58 kid1| commBind Cannot bind socket FD 28 to [::]: (2) No such file or directory |
|
| 2019-02-28 18:47:04 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/squid/+git/squid/+merge/363809 |
|
| 2019-03-01 14:34:56 |
Timo Aaltonen |
squid (Ubuntu Cosmic): status |
In Progress |
Fix Committed |
|
| 2019-03-01 14:34:59 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-03-01 14:35:00 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2019-03-01 14:35:03 |
Timo Aaltonen |
tags |
|
verification-needed verification-needed-cosmic |
|
| 2019-03-05 21:42:46 |
Launchpad Janitor |
squid (Ubuntu Disco): status |
In Progress |
Fix Released |
|
| 2019-03-05 22:30:28 |
Haw Loeung |
tags |
verification-needed verification-needed-cosmic |
verification-done verification-done-cosmic |
|
| 2019-03-11 15:04:39 |
Launchpad Janitor |
squid (Ubuntu Cosmic): status |
Fix Committed |
Fix Released |
|
| 2019-03-11 15:04:49 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2019-05-18 17:40:56 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/squid/+git/squid/+merge/367609 |
|
| 2019-05-18 17:42:03 |
Andreas Hasenack |
merge proposal unlinked |
https://code.launchpad.net/~ahasenack/ubuntu/+source/squid/+git/squid/+merge/367609 |
|
|
