On Mon 06 May 2019 at 17:29:01 -0400, Gene Heskett wrote: > On Monday 06 May 2019 04:06:43 pm Dan Ritter wrote: > > > Ulf Volmer wrote: > > > On 06.05.19 20:10, Gene Heskett wrote: > > > > On Sunday 05 May 2019 12:56:27 pm Gene Heskett wrote: > > > > > > > > I had other problems that overshadowed this, but much of that has > > > > been resolved, so can we start over with this? > > > > > > There was already a reply from me. You have to explain why you have > > > a 2.2 apache config on a debian stretch system. > > > > That's easy: because the system was configured in wheezy or > > earlier, was upgraded to jessie and continued working, and was > > upgraded to stretch and stopped working. > > > > -dsr- > > No jessie. New stretch install on a new drive, data all copied over from > the old drive. And data apparently included /etc/apache2 since I did > want to keep the .conf file there. There are some things in it that help > put it in a rights sandbox.
Wholesale copying of data from one machine to another has caused trouble for this user in the past. Some more documentation to criticise: http://httpd.apache.org/docs/trunk/en/upgrading.html > These modules have been removed: mod_authn_default, > mod_authz_default, mod_mem_cache. If you were using > mod_mem_cache in 2.2, look at mod_cache_disk in 2.4. -- Brian.
