apache2 -V renvoit le message d’erreur ci-dessus.
Apache est donc bien lancé. Le problème vient des changements de conf qu’on doit réaliser au niveau d’apache en sid. Pour info la page http://127.0.0.1 renvoit le message d’informations ci-dessous.
J’ai passé la config apache de wims dans le fichier apache2.conf mais cela n’est pas suffisant. Le répertoire http://127.0.0.1/wims/ n’est toujours pas accessible.
You don’t have permission to access /wims/ on this server.

Si quelqu’un à une solution je suis toujours preneur.

Debian Logo Apache2 Debian Default Page
It works!

This is the default welcome page used to test the correct operation of the Apache2 server after installation on Debian systems. If you can read this page, it means that the Apache HTTP server installed at this site is working properly. You should replace this file (located at /var/www/html/index.html) before continuing to operate your HTTP server.

If you are a normal user of this web site and don’t know what this page is about, this probably means that the site is currently unavailable due to maintenance. If the problem persists, please contact the site’s administrator.
Configuration Overview

Debian’s Apache2 default configuration is different from the upstream default configuration, and split into several files optimized for interaction with Debian tools. The configuration system is fully documented in /usr/share/doc/apache2/README.Debian.gz. Refer to this for the full documentation. Documentation for the web server itself can be found by accessing the manual if the apache2-doc package was installed on this server.

The configuration layout for an Apache2 web server installation on Debian systems is as follows:

/etc/apache2/
|– apache2.conf
| `– ports.conf
|– mods-enabled
| |– *.load
| `– *.conf
|– conf-enabled
| `– *.conf
|– sites-enabled
| `– *.conf

apache2.conf is the main configuration file. It puts the pieces together by including all remaining configuration files when starting up the web server.
ports.conf is always included from the main configuration file. It is used to determine the listening ports for incoming connections, and this file can be customized anytime.
Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/ directories contain particular configuration snippets which manage modules, global configuration fragments, or virtual host configurations, respectively.
They are activated by symlinking available configuration files from their respective *-available/ counterparts. These should be managed by using our helpers a2enmod, a2dismod, a2ensite, a2dissite, and a2enconf, a2disconf . See their respective man pages for detailed information.
The binary is called apache2. Due to the use of environment variables, in the default configuration, apache2 needs to be started/stopped with /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not work with the default configuration.

Document Roots

By default, Debian does not allow access through the web browser to any file apart of those located in /var/www, public_html directories (when enabled) and /usr/share (for web applications). If your site is using a web document root located elsewhere (such as in /srv) you may need to whitelist your document root directory in /etc/apache2/apache2.conf.

The default Debian document root is /var/www/html. You can make your own virtual hosts under /var/www. This is different to previous releases which provides better security out of the box.
Reporting Problems

Please use the reportbug tool to report bugs in the Apache2 package with Debian. However, check existing bug reports before reporting a new bug.

Please report bugs specific to modules (such as PHP and others) to respective packages, not to the web server itself.

apache2 -V donne ce résultat :

[Wed Mar 05 17:57:23.802994 2014] [core:warn] [pid 3438] AH00111: Config variable ${APACHE_LOCK_DIR} is not defined
[Wed Mar 05 17:57:23.803103 2014] [core:warn] [pid 3438] AH00111: Config variable ${APACHE_PID_FILE} is not defined
[Wed Mar 05 17:57:23.803150 2014] [core:warn] [pid 3438] AH00111: Config variable ${APACHE_RUN_USER} is not defined
[Wed Mar 05 17:57:23.803161 2014] [core:warn] [pid 3438] AH00111: Config variable ${APACHE_RUN_GROUP} is not defined
[Wed Mar 05 17:57:23.803184 2014] [core:warn] [pid 3438] AH00111: Config variable ${APACHE_LOG_DIR} is not defined
[Wed Mar 05 17:57:23.807160 2014] [core:warn] [pid 3438:tid 139774541744000] AH00111: Config variable ${APACHE_LOG_DIR} is not defined
[Wed Mar 05 17:57:23.807377 2014] [core:warn] [pid 3438:tid 139774541744000] AH00111: Config variable ${APACHE_LOG_DIR} is not defined
[Wed Mar 05 17:57:23.807403 2014] [core:warn] [pid 3438:tid 139774541744000] AH00111: Config variable ${APACHE_LOG_DIR} is not defined
AH00526: Syntax error on line 74 of /etc/apache2/apache2.conf:
Invalid Mutex directory in argument file:${APACHE_LOCK_DIR}

Voili voilou

• Cette réponse a été modifiée le il y a 10 années et 1 mois par Julien.