Uploaded to cosmic and bionic proposed queues, unapproved.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1836329
Title:
Regression running ssllabs.com/ssltest causes 2 apache process to
Public bug reported:
Up until 2.4.37-1, the d/t/run-test-suite test isn't running because it's
called as root:
(...)
make[1]: Leaving directory
'/tmp/autopkgtest.wAqieG/autopkgtest_tmp/perl-framework/c-modules/eat_post'
[ error] Apache cannot spawn child processes as root, therefore the test su
patched run-test-suite so that the suite actually runs, and this is the
output
** Attachment added: "log"
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1836898/+attachment/5277637/+files/log
--
You received this bug notification because you are a member of Ubuntu
Server, which is su
** Description changed:
[Impact]
With latest apache 2.4.29-1ubuntu4.7 published to 18.04 LTS bionic, when
running ssllabs.com/ssltest against it to verify the configuration it leaves 2
apache processes using 100% indefinitely.
Downgrading to 2.4.29-1ubuntu4.6 make it not reproducible an
Cosmic verification
First, reproducing the bug with:
*** 2.4.34-1ubuntu2.2 500
500 http://us.archive.ubuntu.com/ubuntu cosmic-updates/main amd64
Packages
Then I enabled the required modules, restarted apache, kept monitoring cpu
usage per process using top, and asked ssllabs for the
Thanks for filing this bug in Ubuntu.
I just repeated your steps on a xenial lxd, using apache2
2.4.18-2ubuntu3.10, and after rebooting the container, apache2 was not
started. I got the same warnings that you did, however.
Furthermore, status also shows it's inactive after the reboot:
$ systemctl
You can also check "sudo systemctl cat apache2.service", that will show
if any overrides are in place.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1787225
Title:
systemctl disable apa
Going over the details from comment #7
This is the state before the reload:
ubuntu@foo:~$ ps auxfwww | grep haproxy
root 1346 0.0 0.0 4356 684 ?Ss May22 0:00
/usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg -p
/run/haproxy.pid
haproxy 2210 0.0 0.2 42644 1
In other words, we are waiting for the SRU team to go through the queue.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ruby2.3 in Ubuntu.
https://bugs.launchpad.net/bugs/1834072
Title:
Puppet agent using 100% CPU, in sched_yield() loop.
No reply yet in the ML.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to dpdk in Ubuntu.
https://bugs.launchpad.net/bugs/1833713
Title:
Metadata is broken with dpdk bonding, jumbo frames and metadata from
qdhcp
To manage notifications a
With or without this line in /etc/dovecot/conf.d/10-ssl.conf, openssl s_client
-connect localhost:993 uses TLSv1.3:
ssl_protocols = !SSLv2 !SSLv3
Could you perhaps "grep ssl -r /etc/dovecot" and see if it's being
changed elsewhere? And perhaps paste this if you can (in terms of
sanitization):
#
11 matches
Mail list logo
