LAMP or index.php (was "Re: Apache and Php")

From: Curtis Vaughan (curtis_at_npc-usa.com)
Date: 03/31/05

  • Next message: James Scott: "shadow password"
    Date: Wed, 30 Mar 2005 15:31:23 -0800
    To: List Debian <debian-user@lists.debian.org>
    
    

    Ok, actually the problem was a little different than I originally
    thought.
    One problem was that php4-mysql wasn't compiled right. Actually just
    running dpkg-reconfigure php4-mysql fixed that.

    However! The original problem remains in a way. If I go just to the
    web site: http://www.vostok1.com
    then my browser downloads the index.php file. However, if I go to
    http://www.vostok1.com/index.php, the page comes up.

    So, this would lead me to believe that the problem was in my httpd.conf
    file. However, I do have a specific reference to index.php there:

    <IfModule mod_dir.c>
         DirectoryIndex index.html index.php index.htm index.shtml index.cgi
    </IfModule>

    So, why else could this be happening?

    Curtis

    On 30 Mar, 2005, at 09:30, Curtis Vaughan wrote:

    >
    > On 30 Mar, 2005, at 01:46, Alban Browaeys wrote:
    >
    >> Le Tue, 29 Mar 2005 21:27:05 -0800, Curtis Vaughan a écrit :
    >>
    >>> I don't get it.
    >>> Every time I do an apt-get update, upgrade the php functionality on
    >>> our
    >>> web server gets wacked. Then I spend time trying to get it back up
    >>> and
    >>> running right. Should I just put a hold on apache and php until I
    >>> feel
    >>> certain that I want to upgrade them, or is there some reason why they
    >>> always get wacked?
    >>>
    >>
    >> SOrry. apache modules (well php for example) are managed by debconf a
    >> debian registry. You can tweak /etc/apache/modules.conf by hand btu it
    >> should have this header:
    >>
    >> # Autogenerated file - do not edit!
    >> # This file is maintained by the apache package.
    >> # To update it, run the command:
    >> # /usr/sbin/apache-modconf apache
    >>
    >> was it only modules load that got broken by the upgrade ?
    >>
    >>
    > So, in reply to the many responses I got. Yes, I am using sarge.
    >
    > So, what I did was issue the following command:
    >
    > /usr/sbin/apache-modconf apache enable php
    > then:
    > apachectl restart
    >
    > Nonetheless php is not working.
    > My /etc/apache/modules.conf now reads:
    >
    > # Autogenerated file - do not edit!
    > # This file is maintained by the apache package.
    > # To update it, run the command:
    > # /usr/sbin/apache-modconf apache
    > ClearModuleList
    > AddModule mod_so.c
    > AddModule mod_macro.c
    > LoadModule config_log_module /usr/lib/apache/1.3/mod_log_config.so
    > LoadModule mime_magic_module /usr/lib/apache/1.3/mod_mime_magic.so
    > LoadModule mime_module /usr/lib/apache/1.3/mod_mime.so
    > LoadModule negotiation_module /usr/lib/apache/1.3/mod_negotiation.so
    > LoadModule status_module /usr/lib/apache/1.3/mod_status.so
    > LoadModule autoindex_module /usr/lib/apache/1.3/mod_autoindex.so
    > LoadModule dir_module /usr/lib/apache/1.3/mod_dir.so
    > LoadModule cgi_module /usr/lib/apache/1.3/mod_cgi.so
    > LoadModule userdir_module /usr/lib/apache/1.3/mod_userdir.so
    > LoadModule alias_module /usr/lib/apache/1.3/mod_alias.so
    > LoadModule rewrite_module /usr/lib/apache/1.3/mod_rewrite.so
    > LoadModule access_module /usr/lib/apache/1.3/mod_access.so
    > LoadModule auth_module /usr/lib/apache/1.3/mod_auth.so
    > LoadModule expires_module /usr/lib/apache/1.3/mod_expires.so
    > LoadModule unique_id_module /usr/lib/apache/1.3/mod_unique_id.so
    > LoadModule setenvif_module /usr/lib/apache/1.3/mod_setenvif.so
    > LoadModule dav_module /usr/lib/apache/1.3/libdav.so
    > LoadModule perl_module /usr/lib/apache/1.3/mod_perl.so
    > LoadModule ssl_module /usr/lib/apache/1.3/mod_ssl.so
    > LoadModule fastcgi_module /usr/lib/apache/1.3/mod_fastcgi.so
    > LoadModule php4_module /usr/lib/apache/1.3/libphp4.so
    > Loadmodule suphp_module /usr/lib/apache/1.3/mod_suphp.so
    >


  • Next message: James Scott: "shadow password"