On Mon, 02 Mar 2015 11:24:18 +0000
Jean-Michel Nirgal Vourgère <jmv_...@nirgal.com> wrote:
> Do you know how you came to have that module disabled? Do you remember
> if you disabled it as an admin?
I can't imagine why I would have done so.
> Can you check for apache related package you installed that would
> disable that mod_dir or at least post the list of apache/php related
> packages you are using?
# deborphan apache2
apache2
libapache2-mod-php5
phppgadmin
phppgadmin
analog
analog
info2www
info2www
javascript-common
javascript-common
man2html
man2html
(I don't know why deborphan sometimes repeats items.)
As for php, phppgadmin is the only thing that needs it.
> Can you give us an history of that server? I mean: Was it installed as
> a Wheezy (Debian 7) then upgraded?
That is almost certainly what happened, which would mean that the
installation started off as Apache-2.2, and was then upgraded to
Apache-2.4 .
Just now, I tried purging all the Apache packages, and then reinstalling
them. "mod_dir" is now enabled by default, so the problem has not
reappeared. Apart from the above, I don't know how it could have arisen.
HOWEVER: phppgadmin still doesn't work. The "README.Debian" file advises
that "The application is available at http://localhost/phppgadmin/ after
installation." This is not so. From the access log:
::1 - - [02/Mar/2015:05:00:57 -0800] "GET /phppgadmin/ HTTP/1.1" 404 501 "-"
Oddly, the Apache configuration file goes into
/etc/apache2/conf.d/phppgadmin, instead of
/etc/apache2/conf-{available,enabled}, like everything else. It does say
"Alias /phppgadmin /usr/share/phppgadmin", but "a2enconf" doesn't know
about it. Is that how it's supposed to be? If so, why doesn't it work?
-- Ian Bruce
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
