Bryce,

In my case when I re-set it up in the container I had to do it manually
(method wasn't chosen by the package).

I would assume mod_perl often gets chosen because of https://rt-
wiki.bestpractical.com/wiki/ManualApacheConfig which has examples for
mod_perl but not for the others, as well as lack of warnings there.

As for mod_perl the default config was not touched to my knowledge, FWIW
(but yes, it is tricky)

I suspect that having this set up and doing a release-upgrade (or
perhaps two) might not have helped. To my knowledge I configured the
container as close to our production system as I could, and I was not
able to replicate the issue. I am sure I missed something, I just don't
know what and I don't have cycles to dig deeper.

Since there are effective workarounds available I would be OK with this
getting closed as wontfix.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854395

Title:
  apachectl configtest segfault with request-tracker4 + mod_perl

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1854395/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to