Re: Apache oddness on jessie => stretch upgrade

2017-08-22 Thread Bastien Durel
Le mardi 22 août 2017 à 03:58 -0500, Dave Sherohman a écrit : > [...] > Also, side question: I'm also manually running `systemctl enable > apache2` after upgrading. How can you tell whether something is > enabled > or not in systemd? `systemctl status` will tell you whether it's > currently runn

Re: Apache oddness on jessie => stretch upgrade

2017-08-22 Thread Dave Sherohman
On Tue, Aug 22, 2017 at 11:49:50AM +0200, Sven Hartge wrote: > Dave Sherohman wrote: > > Also, side question: I'm also manually running `systemctl enable > > apache2` after upgrading. > > You shouldn't need to do this, the maintainer scripts in the packages > will do this for you during the upgra

Re: Apache oddness on jessie => stretch upgrade

2017-08-22 Thread Sven Hartge
Dave Sherohman wrote: > Also, side question: I'm also manually running `systemctl enable > apache2` after upgrading. You shouldn't need to do this, the maintainer scripts in the packages will do this for you during the upgrade. *If* you need to do this to get a service started automatically dur

Apache oddness on jessie => stretch upgrade

2017-08-22 Thread Dave Sherohman
Yesterday, I started on upgrading my servers from jessie to stretch. It went mostly without incident at the time, but then apache failed to restart after logrotate did its thing overnight. Investigating the apache error log, it ended with: [Tue Aug 22 06:30:01.223322 2017] [mpm_prefork:notice] [