Add
WSGIDaemonProcess example.com processes=2 threads=15
display-name=%{GROUP}
WSGIProcessGroup example.com
to /etc/apache2/sites-enabled/000-default.conf of a default install.
Processes:
# ps axlf | grep wsg
0 0 26860 25750 20 0 14856 1100 pipe_w S+ ? 0:00 \_ grep
--color=auto wsg
5 33 26765 26764 20 0 356176 12428 poll_s Sl ? 0:00 \_
(wsgi:example.com -k start
5 33 26766 26764 20 0 356168 12448 poll_s Sl ? 0:00 \_
(wsgi:example.com -k start
Looping over apache2ctl graceful triggers a crash.
I tried to get a better backtrace with more debug packages and such -
attaching that...
This is from cosmic using 4.5.17-1 there is a changelog of wsgi 4.1 reading
much like it at [1].
Good issues come back.
Never the less I'd ask you to report also upstream and mention the bug
URL you created to track their activity on it as well.Especially since
they already fixed the same in 4.1 they might be interested.
[1]: http://modwsgi.readthedocs.io/en/develop/release-
notes/version-4.1.0.html
** Changed in: mod-wsgi (Ubuntu)
Status: New => Confirmed
** Changed in: mod-wsgi (Ubuntu)
Importance: Undecided => Medium
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2007-1742
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712589
Title:
Apache2 mod-wsgi segfault on double reload
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mod-wsgi/+bug/1712589/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
