| 2020-02-14 10:46:47 |
Dariusz Gadomski |
bug |
|
|
added bug |
| 2020-02-14 10:47:15 |
Dariusz Gadomski |
nominated for series |
|
Ubuntu Bionic |
|
| 2020-02-14 10:47:15 |
Dariusz Gadomski |
bug task added |
|
mod-wsgi (Ubuntu Bionic) |
|
| 2020-02-14 10:47:15 |
Dariusz Gadomski |
nominated for series |
|
Ubuntu Xenial |
|
| 2020-02-14 10:47:15 |
Dariusz Gadomski |
bug task added |
|
mod-wsgi (Ubuntu Xenial) |
|
| 2020-02-14 10:47:28 |
Dariusz Gadomski |
mod-wsgi (Ubuntu): status |
New |
Fix Released |
|
| 2020-02-14 10:47:38 |
Dariusz Gadomski |
mod-wsgi (Ubuntu Bionic): status |
New |
In Progress |
|
| 2020-02-14 10:47:38 |
Dariusz Gadomski |
mod-wsgi (Ubuntu Bionic): assignee |
|
Dariusz Gadomski (dgadomski) |
|
| 2020-02-14 10:47:49 |
Dariusz Gadomski |
mod-wsgi (Ubuntu Xenial): status |
New |
In Progress |
|
| 2020-02-14 10:47:49 |
Dariusz Gadomski |
mod-wsgi (Ubuntu Xenial): assignee |
|
Dariusz Gadomski (dgadomski) |
|
| 2020-02-14 14:49:57 |
Dariusz Gadomski |
tags |
|
sts |
|
| 2020-02-14 15:01:49 |
Dariusz Gadomski |
description |
On Apache reloads the daemon tries to rotate wsgi sockets causing unnecessary log entries, especially in OpenStack context.
This has been addressed in mod-wsgi upstream (4.6.0) and could be backported to Ubuntu. |
[Impact]
* Lack of option for disabling wsgi socket rotation leads to errors on graceful restarts, making them not as graceful.
* This change introduces a new config option WSGISocketRotation that allows to disable the rotation.
[Test Case]
* Setup apache2 with mod-wsgi.
* Make sure there are some wsgi sockets open.
* Reload apache gracefully.
Expected result:
No errors related to sockets in the logs
Actual result:
There are error messages related to sockets in the logs.
[Regression Potential]
* Since the value is set to On by default any regressions would manifest only after explicitly setting it to Off.
* After it's set to off WSGI application behavior will change on reloads - connections should be resumed instead of cancelled.
[Other Info]
* Original bug description:
On Apache reloads the WSGI daemon tries to rotate wsgi sockets causing unnecessary log entries, especially in OpenStack context.
This has been addressed in mod-wsgi upstream (4.6.0) and could be backported to Ubuntu. |
|
| 2020-02-14 15:02:22 |
Dariusz Gadomski |
attachment added |
|
xenial_mod-wsgi_4.3.0-1.1ubuntu1.debdiff https://bugs.launchpad.net/ubuntu/+source/mod-wsgi/+bug/1863232/+attachment/5328184/+files/xenial_mod-wsgi_4.3.0-1.1ubuntu1.debdiff |
|
| 2020-02-14 15:02:40 |
Dariusz Gadomski |
attachment added |
|
bionic_mod-wsgi_4.5.17-1ubuntu1.debdiff https://bugs.launchpad.net/ubuntu/+source/mod-wsgi/+bug/1863232/+attachment/5328185/+files/bionic_mod-wsgi_4.5.17-1ubuntu1.debdiff |
|
| 2020-02-14 15:06:04 |
Dariusz Gadomski |
bug |
|
|
added subscriber Ubuntu SRU developers |
| 2020-02-14 15:08:26 |
Eric Desrochers |
bug |
|
|
added subscriber Eric Desrochers |
| 2020-02-14 16:06:41 |
Eric Desrochers |
bug |
|
|
added subscriber STS Sponsors |
| 2020-02-14 16:07:22 |
Eric Desrochers |
removed subscriber Ubuntu SRU developers |
|
|
|
| 2020-02-14 17:31:46 |
Mauricio Faria de Oliveira |
tags |
sts |
sts sts-sponsor-mfo |
|
| 2020-02-14 17:34:15 |
Mauricio Faria de Oliveira |
bug |
|
|
added subscriber Mauricio Faria de Oliveira |
| 2020-02-18 15:00:52 |
Mauricio Faria de Oliveira |
attachment added |
|
lp1863232_bionic_mod-wsgi.debdiff https://bugs.launchpad.net/ubuntu/+source/mod-wsgi/+bug/1863232/+attachment/5329326/+files/lp1863232_bionic_mod-wsgi.debdiff |
|
| 2020-02-18 15:01:08 |
Mauricio Faria de Oliveira |
attachment added |
|
lp1863232_xenial_mod-wsgi.debdiff https://bugs.launchpad.net/ubuntu/+source/mod-wsgi/+bug/1863232/+attachment/5329327/+files/lp1863232_xenial_mod-wsgi.debdiff |
|
| 2020-02-18 15:13:13 |
Mauricio Faria de Oliveira |
description |
[Impact]
* Lack of option for disabling wsgi socket rotation leads to errors on graceful restarts, making them not as graceful.
* This change introduces a new config option WSGISocketRotation that allows to disable the rotation.
[Test Case]
* Setup apache2 with mod-wsgi.
* Make sure there are some wsgi sockets open.
* Reload apache gracefully.
Expected result:
No errors related to sockets in the logs
Actual result:
There are error messages related to sockets in the logs.
[Regression Potential]
* Since the value is set to On by default any regressions would manifest only after explicitly setting it to Off.
* After it's set to off WSGI application behavior will change on reloads - connections should be resumed instead of cancelled.
[Other Info]
* Original bug description:
On Apache reloads the WSGI daemon tries to rotate wsgi sockets causing unnecessary log entries, especially in OpenStack context.
This has been addressed in mod-wsgi upstream (4.6.0) and could be backported to Ubuntu. |
[Impact]
* Lack of option for disabling wsgi socket rotation leads to errors on graceful restarts, making them not as graceful.
* Specifically, when mod-wsgi is running in daemon mode (which uses
sockets), and a graceful restart ('sudo systemctl reload apache2')
happens, the socket filename changes, and upcoming HTTP requests
in a keep-alive connection (i.e., same connection is re-utilized
for multiple HTTP requests) initiated before the graceful restart
are failed (HTTP 503 error) because the socket file is not found.
* This change introduces a new config option WSGISocketRotation that allows to disable the rotation.
* The option is disabled by default, so the default behavior remains
consistent with the previous versions (ie, socket rotation occurs.)
* This is actually desired, and designed that way by upstream,
because disabling socket rotation requires no _wsgi_ config changes,
as they can impact/alter the upcoming HTTP requests (see patch link.)
[Test Case]
* Setup apache2 with mod-wsgi.
* Make sure there are some wsgi sockets open.
* Reload apache gracefully.
* (Detailed steps are provided in comments #9 and #10)
Expected result:
No errors related to sockets in the logs
Actual result:
There are error messages related to sockets in the logs.
[Regression Potential]
* Since the value is set to On by default any regressions would manifest only after explicitly setting it to Off.
* After it's set to off WSGI application behavior will change on reloads - connections should be resumed instead of cancelled.
[Other Info]
* Original bug description:
On Apache reloads the WSGI daemon tries to rotate wsgi sockets causing unnecessary log entries, especially in OpenStack context.
This has been addressed in mod-wsgi upstream (4.6.0) and could be backported to Ubuntu. |
|
| 2020-02-18 15:13:22 |
Mauricio Faria de Oliveira |
description |
[Impact]
* Lack of option for disabling wsgi socket rotation leads to errors on graceful restarts, making them not as graceful.
* Specifically, when mod-wsgi is running in daemon mode (which uses
sockets), and a graceful restart ('sudo systemctl reload apache2')
happens, the socket filename changes, and upcoming HTTP requests
in a keep-alive connection (i.e., same connection is re-utilized
for multiple HTTP requests) initiated before the graceful restart
are failed (HTTP 503 error) because the socket file is not found.
* This change introduces a new config option WSGISocketRotation that allows to disable the rotation.
* The option is disabled by default, so the default behavior remains
consistent with the previous versions (ie, socket rotation occurs.)
* This is actually desired, and designed that way by upstream,
because disabling socket rotation requires no _wsgi_ config changes,
as they can impact/alter the upcoming HTTP requests (see patch link.)
[Test Case]
* Setup apache2 with mod-wsgi.
* Make sure there are some wsgi sockets open.
* Reload apache gracefully.
* (Detailed steps are provided in comments #9 and #10)
Expected result:
No errors related to sockets in the logs
Actual result:
There are error messages related to sockets in the logs.
[Regression Potential]
* Since the value is set to On by default any regressions would manifest only after explicitly setting it to Off.
* After it's set to off WSGI application behavior will change on reloads - connections should be resumed instead of cancelled.
[Other Info]
* Original bug description:
On Apache reloads the WSGI daemon tries to rotate wsgi sockets causing unnecessary log entries, especially in OpenStack context.
This has been addressed in mod-wsgi upstream (4.6.0) and could be backported to Ubuntu. |
[Impact]
* Lack of option for disabling wsgi socket rotation leads to errors on graceful restarts, making them not as graceful.
* Specifically, when mod-wsgi is running in daemon mode (which uses
sockets), and a graceful restart ('sudo systemctl reload apache2')
happens, the socket filename changes, and upcoming HTTP requests
in a keep-alive connection (i.e., same connection is re-utilized
for multiple HTTP requests) initiated before the graceful restart
are failed (HTTP 503 error) because the socket file is not found.
* This change introduces a new config option WSGISocketRotation that allows to disable the rotation.
* The option is disabled by default, so the default behavior remains
consistent with the previous versions (ie, socket rotation occurs.)
* This is actually desired, and designed that way by upstream,
because disabling socket rotation requires no _wsgi_ config changes,
as they can impact/alter the upcoming HTTP requests (see patch link.)
[Test Case]
* Setup apache2 with mod-wsgi.
* Make sure there are some wsgi sockets open.
* Reload apache gracefully.
* (Detailed steps are provided in comments #9 and #10)
Expected result:
No errors related to sockets in the logs
Actual result:
There are error messages related to sockets in the logs.
[Regression Potential]
* Since the value is set to On by default any regressions would manifest only after explicitly setting it to Off.
* After it's set to off WSGI application behavior will change on reloads - connections should be resumed instead of cancelled.
[Other Info]
* Original bug description:
On Apache reloads the WSGI daemon tries to rotate wsgi sockets causing unnecessary log entries, especially in OpenStack context.
This has been addressed in mod-wsgi upstream (4.6.0) and could be backported to Ubuntu. |
|
| 2020-02-18 15:21:44 |
Mauricio Faria de Oliveira |
mod-wsgi (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2020-02-18 15:21:46 |
Mauricio Faria de Oliveira |
mod-wsgi (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2020-02-18 15:21:59 |
Mauricio Faria de Oliveira |
mod-wsgi (Ubuntu): importance |
Low |
Undecided |
|
| 2020-02-18 15:23:23 |
Mauricio Faria de Oliveira |
description |
[Impact]
* Lack of option for disabling wsgi socket rotation leads to errors on graceful restarts, making them not as graceful.
* Specifically, when mod-wsgi is running in daemon mode (which uses
sockets), and a graceful restart ('sudo systemctl reload apache2')
happens, the socket filename changes, and upcoming HTTP requests
in a keep-alive connection (i.e., same connection is re-utilized
for multiple HTTP requests) initiated before the graceful restart
are failed (HTTP 503 error) because the socket file is not found.
* This change introduces a new config option WSGISocketRotation that allows to disable the rotation.
* The option is disabled by default, so the default behavior remains
consistent with the previous versions (ie, socket rotation occurs.)
* This is actually desired, and designed that way by upstream,
because disabling socket rotation requires no _wsgi_ config changes,
as they can impact/alter the upcoming HTTP requests (see patch link.)
[Test Case]
* Setup apache2 with mod-wsgi.
* Make sure there are some wsgi sockets open.
* Reload apache gracefully.
* (Detailed steps are provided in comments #9 and #10)
Expected result:
No errors related to sockets in the logs
Actual result:
There are error messages related to sockets in the logs.
[Regression Potential]
* Since the value is set to On by default any regressions would manifest only after explicitly setting it to Off.
* After it's set to off WSGI application behavior will change on reloads - connections should be resumed instead of cancelled.
[Other Info]
* Original bug description:
On Apache reloads the WSGI daemon tries to rotate wsgi sockets causing unnecessary log entries, especially in OpenStack context.
This has been addressed in mod-wsgi upstream (4.6.0) and could be backported to Ubuntu. |
[Impact]
* Lack of option for disabling wsgi socket rotation leads to errors on graceful restarts, making them not as graceful.
* Specifically, when mod-wsgi is running in daemon mode (which uses
sockets), and a graceful restart ('sudo systemctl reload apache2')
happens, the socket filename changes, and upcoming HTTP requests
in a keep-alive connection (i.e., same connection is re-utilized
for multiple HTTP requests) initiated before the graceful restart
are failed (HTTP 503 error) because the socket file is not found.
* This change introduces a new config option WSGISocketRotation that allows to disable the rotation.
* The option is disabled by default, so the default behavior remains
consistent with the previous versions (ie, socket rotation occurs.)
* This is actually desired, and designed that way by upstream,
because disabling socket rotation requires no _wsgi_ config changes,
as they can impact/alter the upcoming HTTP requests (see patch link.)
[Test Case]
* Setup apache2 with mod-wsgi.
* Make sure there are some wsgi sockets open.
* Reload apache gracefully.
* (Detailed steps are provided in comments #9 and #10)
Expected result:
No errors related to sockets in the logs
Actual result:
There are error messages related to sockets in the logs.
[Regression Potential]
* Since the value is set to On by default any regressions would manifest only after explicitly setting it to Off.
* After it's set to off WSGI application behavior will change on reloads - connections should be resumed instead of cancelled.
[Other Info]
* The fix has been introduced in mod-wsgi 4.6.0,
thus already present in Disco/Eoan/Focal,
only needed in Xenial/Bionic.
* Original bug description:
On Apache reloads the WSGI daemon tries to rotate wsgi sockets causing unnecessary log entries, especially in OpenStack context.
This has been addressed in mod-wsgi upstream (4.6.0) and could be backported to Ubuntu. |
|
| 2020-02-20 13:15:54 |
Łukasz Zemczak |
mod-wsgi (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2020-02-20 13:15:56 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-02-20 13:15:59 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2020-02-20 13:16:03 |
Łukasz Zemczak |
tags |
sts sts-sponsor-mfo |
sts sts-sponsor-mfo verification-needed verification-needed-bionic |
|
| 2020-02-20 13:23:45 |
Łukasz Zemczak |
mod-wsgi (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2020-02-20 13:23:49 |
Łukasz Zemczak |
tags |
sts sts-sponsor-mfo verification-needed verification-needed-bionic |
sts sts-sponsor-mfo verification-needed verification-needed-bionic verification-needed-xenial |
|
| 2020-02-20 14:13:03 |
Dariusz Gadomski |
tags |
sts sts-sponsor-mfo verification-needed verification-needed-bionic verification-needed-xenial |
sts sts-sponsor-mfo verification-done-bionic verification-needed verification-needed-xenial |
|
| 2020-02-20 15:17:03 |
Dariusz Gadomski |
tags |
sts sts-sponsor-mfo verification-done-bionic verification-needed verification-needed-xenial |
sts sts-sponsor-mfo verification-done verification-done-bionic verification-done-xenial |
|
| 2020-02-26 19:08:30 |
Eric Desrochers |
removed subscriber STS Sponsors |
|
|
|
| 2020-03-02 10:20:17 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-03-02 10:30:23 |
Launchpad Janitor |
mod-wsgi (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2020-03-02 12:31:43 |
Launchpad Janitor |
mod-wsgi (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2020-09-22 16:41:09 |
Mauricio Faria de Oliveira |
tags |
sts sts-sponsor-mfo verification-done verification-done-bionic verification-done-xenial |
sts verification-done verification-done-bionic verification-done-xenial |
|
