mpm itk support broken in maintainter script

Bug #1678131 reported by Josip Rodin on 2017-03-31
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Apache2 Web Server
Fix Released
apache2 (Ubuntu)

Bug Description


I'm seeing the symptoms described in on trusty on every upgrade of libapache2-mod-php5, when ITK is used.

  There is more than one MPM loaded. Do not proceed due to undefined results
  There is more than one MPM loaded. Do not proceed due to undefined results
  There is more than one MPM loaded. Do not proceed due to undefined results
  /var/lib/dpkg/info/libapache2-mod-php5.postinst: 291: [: !=: unexpected operator

Would it be possible to backport that fix to 14 LTS?



Josip Rodin (joy) on 2017-03-31
description: updated
Changed in apache2:
status: Unknown → Fix Released

These changes went into 2.4.17-1 which is >=Xenial.
So as requested only Trusty is needed.

The changes once isolated look rather small =>

2.4.7-1ubuntu4.14 was burnt by, so preparing a 2.4.7-1ubuntu4.15 might be the right thing to do.

The first two chunks somewhat apply, yet the third one does not.
There is no execute_deferred_actions (nor similar) in the old postinst.
If anything there is a line like
> for link in /etc/apache2/mods-enabled/*.load ; do
IMHO this section is not needed as it is about disabling outdated modules that are no more provided and not the MPM switch this is about.

So chunk 2/3 should do it IMHO.
I hope on Wednesday on the next USBSD [1] (this wedenesday) somebody with more apache experience might help otherwise I might try.


tags: added: server-next

If you could find the time to prepare all that is needed for an SRU process here by adding a SRU Template [1] that will help a lot.

Otherwise if you are willing to drive this on your own but with guidance on USBSD (see above) or at least would be around to help verifying that would be great - let me know in that case.


Changed in apache2 (Ubuntu):
status: New → Fix Released
Changed in apache2 (Ubuntu Trusty):
status: New → Triaged
importance: Undecided → Medium

I'd be thankful if you could help creating a verification testcase.
You said you see it "on trusty on every upgrade of libapache2-mod-php5, when ITK is used."
Could you outline the minimum config changes from a clean trusty system that you need to do to run into this?
I'd guess you need to install the fixed apache version and then upgrade libapache2-mod packages right to be able to confirm a fix?
I can create fake libapache2-mod-php5 version bumps if needed to trigger, but I want to make sure I match your setup to actually cause the issue.

Until then for you or others affected I prepared a testing ppa at [1].
If you could test if that resolves your issues it would be great to provide me the confidence going on further on this.


It seems I screwed up the versioning - let me double check and re-push to the PPA if needed.

No was a false-positive warning on the tooling against trusty-backports, should be fine as-is.

Adding bitesize to make it more likely to be picked up soon.
FYI - another update is out so the ppa we had so far has its version number burned.

tags: added: bitesize
Bryce Harrington (bryce) wrote :

Trusty ended standard support April 2019

Changed in apache2 (Ubuntu Trusty):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.