[pkg-apparmor] Bug#905342: Bug#905342: apache fpm not working anymore

[Ivan Sergio Borgonovo]

Previously it was unset (default value, it should be 15s), now it is set 
to 120s (service generally start after 110s).

Surprisingly starting the service manually succeed immediately.

Doing some test (booting and rebooting to see what was going on) I 
noticed php-fpm may not start even with the previous version of apparmor 
(still with default setting but much less frequently than with the newer 
apparmor).

So probably apparmor isn't even the main culprit and just made it enough 
worse to make it noticeable.

I'm trying to review any package that was upgraded in the past month to 
see if anything other than apparmor could be related but the only 
candidate seems to be systemd that has been upgraded several time in the 
past 30 days.

If you've any suggestion on how to investigate the problem further so i 
can at least relate it to the correct package they will be welcome.

On 08/15/2018 03:14 AM, Seth Arnold wrote:
> On Tue, Aug 14, 2018 at 01:01:59AM +0200, Ivan Sergio Borgonovo wrote:
>> It seems that the new apparmor makes php-fpm start time sensibly higher and
>> systemd timeout.
>>
>> There is a correlation between php-fpm slowing down and the new version of
>> apparmor but at the moment I just increased systemd timeout
>> (TimeoutStartSec).
> 
> What was the old value, what is the new value?
> 
> Thanks
> 

-- 
Ivan Sergio Borgonovo
https://www.webthatworks.it https://www.borgonovo.net