Roberto and Kjell,
Thanks for your continued investigation into this issue. It sounds like
you've found an effective workaround by removing mod_per and using
fastcgi or similar. It is interesting to hear that upstream considers
mod_perl to not be a supportable configuration. For the Ubuntu Server
team, I also suspect mod_perl configurations are not going to be
priority issues for distro-level support. mod_perl is tricky and far
too easy for non-experts to misconfigure.
However, before closing this as a wontfix bug, one question. How did
the request-tracker4 package get configured to use mod_perl in the first
place? If the debian/ubuntu packaging set it up that way, then this may
be something worth us changing, whereas on the other hand if that was
something you've done manually yourself (e.g. following an installation
tutorial), then perhaps not.
** Changed in: apache2 (Ubuntu)
Importance: Undecided => Low
** Changed in: apache2 (Ubuntu)
Status: New => Incomplete
--
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
