Apache reloading before package setup

Bug #1355253 reported by ñull
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
php5 (Ubuntu)
Fix Released
High
Unassigned

Bug Description

I don't know if this is specific for php5-curl or that it occurs with all php modules. When I install this module I see that first the apache server is reloaded and then the module is set-up. Shouldn't the order be reversed? Wasn't it the idea that Apache is reloaded automatically after an update in PHP? :

Unpacking php5-curl (from .../php5-curl_5.3.10-1ubuntu3.13_amd64.deb) ...
Processing triggers for libapache2-mod-php5 ...
 * Reloading web server config apache2 [ OK ]
Setting up php5-curl (5.3.10-1ubuntu3.13) ...

Now I needed to reload Apache manually for it to work.

Revision history for this message
Robie Basak (racb) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

This sounds like a valid bug and something we should fix, so I'm assigning my team to take a look when we can. This is open-ended though - if anybody else can help with this, please do.

Changed in php5 (Ubuntu):
assignee: nobody → Ubuntu Server Team (ubuntu-server)
importance: Undecided → High
Revision history for this message
cooolman (coolman) wrote :

Please update packages
ubuntu server 15.04
php 5.6.4 -> php 5.6.7

Revision history for this message
ñull (erniecom) wrote :

Just to confirm this is not isolated to Ubuntu or php5-curl. Yesterday I de-installed php5-ffmpeg in Debian and Apache was not restarted either.
 May be (de-)install script should check if mod_php is active and only then restart Apache?

Revision history for this message
Robie Basak (racb) wrote :

Unassigning as no progress has been made by the assignee. It's still on the server team's list, but I want to clean the assignee list to the set of bugs that are actively being worked on.

Changed in php5 (Ubuntu):
assignee: Ubuntu Server Team (ubuntu-server) → nobody
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

I don't know when/where this was changed.
But triggers now behave correctly (in general) in regard to the order of unpack/setup/trigger.
Here 18.04 on the reported package:

Preparing to unpack .../php7.2-curl_7.2.1-1ubuntu2_amd64.deb ...
Unpacking php7.2-curl (7.2.1-1ubuntu2) ...
Setting up php7.2-curl (7.2.1-1ubuntu2) ...

Creating config file /etc/php/7.2/mods-available/curl.ini with new version
Processing triggers for libapache2-mod-php7.2 (7.2.1-1ubuntu2) ...

This will call "apache2_reload restart" as it can be seen in /var/lib/dpkg/info/libapache2-mod-php7.2.postinst

Random other example:
Selecting previously unselected package php7.2-soap.
(Reading database ... 67852 files and directories currently installed.)
Preparing to unpack .../php7.2-soap_7.2.1-1ubuntu2_amd64.deb ...
Unpacking php7.2-soap (7.2.1-1ubuntu2) ...
Setting up php7.2-soap (7.2.1-1ubuntu2) ...

Creating config file /etc/php/7.2/mods-available/soap.ini with new version
Processing triggers for libapache2-mod-php7.2 (7.2.1-1ubuntu2) ...

So at least for the most recent (and maybe even quite some time back) - Fix Released

Changed in php5 (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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