Contenu | Rechercher | Menus

Annonce

DVD, clés USB et t-shirts Ubuntu-fr disponibles sur la boutique En Vente Libre

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

#1 Le 19/10/2013, à 13:45

Alf68fr

[RESOLU]Configuration apache cassée par mise à niveau 13.04 vers 13.10

Bonjour,

je viens de précéder à la mise à niveau d'une 13.04 vers la 13.10.
Apache ne peut redémarrer à cause d'un fichier introuvable (/usr/lib/apache2/modules/mod_authz_default.so).

sudo service apache2 restart 
 * Restarting web server apache2                                                                                                                        [fail] 
 * The apache2 configtest failed.
Output of config test was:
apache2: Syntax error on line 140 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/authz_default.load: Cannot load /usr/lib/apache2/modules/mod_authz_default.so into server: /usr/lib/apache2/modules/mod_authz_default.so: cannot open shared object file: No such file or directory
Action 'configtest' failed.
The Apache error log may have more information.

Il n'y a rien de spécial dans ma configuration d'Apache, c'est le fichier de conf fourni par la distribution :

# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
#	/etc/apache2/
#	|-- apache2.conf
#	|	`--  ports.conf
#	|-- mods-enabled
#	|	|-- *.load
#	|	`-- *.conf
#	|-- conf-enabled
#	|	`-- *.conf
# 	`-- sites-enabled
#	 	`-- *.conf
#
#
# * apache2.conf is the main configuration file (this 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
#   supposed to determine listening ports for incoming connections which 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.

# Global configuration
#

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
Mutex file:${APACHE_LOCK_DIR} default

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5


# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog ${APACHE_LOG_DIR}/error.log

#
# LogLevel: Control the number of messages logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# "LogLevel info ssl:warn"
#
LogLevel warn

# Include module configuration:
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf

# Include list of ports to listen on
Include ports.conf

# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.
<Directory />
	Options FollowSymLinks
	AllowOverride None
	Require all denied
</Directory>

<Directory /usr/share>
	AllowOverride None
	Require all granted
</Directory>

<Directory /var/www/>
	Options Indexes FollowSymLinks
	AllowOverride None
	Require all granted
</Directory>

#<Directory /srv/>
#	Options Indexes FollowSymLinks
#	AllowOverride None
#	Require all granted
#</Directory>

# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
	Require all denied
</FilesMatch>


#
# The following directives define some format nicknames for use with
# a CustomLog directive.
#
# These deviate from the Common Log Format definitions in that they use %O
# (the actual bytes sent including headers) instead of %b (the size of the
# requested file), because the latter makes it impossible to detect partial
# requests.
#
# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
# Use mod_remoteip instead.
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf

# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

Idem pour le fichier appelé (/etc/apache2/mods-enabled/authz_default.load) :

LoadModule authz_default_module /usr/lib/apache2/modules/mod_authz_default.so

Le fichier appelé par ce deuxième (mod_authz_default.so) est introuvable :

sudo updatedb && locate mod_authz_default.so
-> ne renvoie rien

La réinstallation du paquet apache2 n'y change rien.
J'ai installé apt-file pour faire une recherche dans les paquets :

sudo apt-get install apt-file
sudo apt-file update
sudo apt-file search mod_authz_default
-> aucun résultat

Est-ce un bug dû à ma configuration ou d'autres ont-il / auront-ils le même problème ?

Merci

Dernière modification par Alf68fr (Le 19/10/2013, à 23:00)

Hors ligne

#2 Le 19/10/2013, à 13:50

Kooothor

Re : [RESOLU]Configuration apache cassée par mise à niveau 13.04 vers 13.10

Salut, essaie de commenter la ligne LoadModule authz_default_module

Hors ligne

#3 Le 19/10/2013, à 22:33

Alf68fr

Re : [RESOLU]Configuration apache cassée par mise à niveau 13.04 vers 13.10

Salut,

merci pour la réponse. En fait, j'ai passé l'après-midi là dessus.
J'ai effectivement solutionné le problème en supprimant le fichier /etc/apache2/mods-enabled/authz_default.load

J'aurais mieux fait de commenter la ligne le chargeant, mais quand on cherche...

Bref, ça fonctionne, mais je n'avais plus accès aux sites installés en local sur la machine.

J'ai revérifié les fichiers de config dans /etc/apache2/sites-available/, la présence des sites dans le fichier /etc/hosts, la présence des liens symboliques dans le fichier /var/www, la présence du module RewriteEngine, bref, tout le fatras habituel.

Et puis en recréant le lien symbolique dans /etc/apache2/sites-enabled avec la commande a2ensite, j'avais une erreur "site XXX does not exist" !
J'ai alors constaté que la version d'Apache livrée dans la 13.10 ne reconnaissait que les fichiers de déclaration avec un ".conf" dans /etc/apache2/sites-available/ alors que ça fonctionnait sans l'extension .conf avec la version précédente...

Renaud

Hors ligne

#4 Le 24/10/2013, à 16:00

vivienfr

Re : [RESOLU]Configuration apache cassée par mise à niveau 13.04 vers 13.10

Ubuntu 13.10 est passé à Apache 2.4. C'est une nouvelle version majeure et il faut mettre en conformité les fichiers de configuration.

J'invite tous ceux qui vont upgrader leur serveur en 13.10 ou 14.04 a lire attentivement http://httpd.apache.org/docs/trunk/fr/upgrading.html
Il y a de nombreuses modifications à faire, même pour un hébergement assez simple.

Outre les modification listé sur le site d'Apache, il y a celles prope a debian / ubuntu. Par exemple les fichiers Apache dans  /etc/apache2/sites-available/ doivent avoir maintenant l'extension .conf

Autre nouveauté, l'apparition d'un dossier /etc/apache2/conf-available/ et /etc/apache2/conf-enabled/ pour des option de configuration.
Activation de la conf "security" : sudo a2enconf security
Désactivation de la conf "security" : sudo a2disconf security

Bref l'idéal est de tester sur un PC de test la configuration apache2.4 avant de faire l'upgarde d'ubuntu qui entraîne un changement apache2.2 => apache 2.4.
Attention également, le changement de version de PHP oblige à revoir certains scripts (regardez les warning)


fr.archive.ubuntu.com : Statistiques sur les versions d'Ubuntu en France

Hors ligne