Pages : 1
#1 Le 05/09/2018, à 16:51
- cypher_ubuntu
[RÉSOLU]Problème de démarrage d'apache2
Bonjour
Je n'arrivais pas à accéder au phpmyadmin (http://localhost/phpmyadmin/) dont le message suivant :
Ce site est inaccessible
localhost n'autorise pas la connexion.
Essayez les suggestions ci-dessous :
Vérifier la connexion
Vérifier le proxy et le pare-feu
ERR_CONNECTION_REFUSED
Je vérifie donc le journal d'apache2
systemctl status apache2
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─apache2-systemd.conf
Active: failed (Result: exit-code) since Wed 2018-09-05 17:22:21 CEST; 2min 33s ago
Process: 27499 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)
sept. 05 17:22:21 EliteBook systemd[1]: Starting The Apache HTTP Server...
sept. 05 17:22:21 EliteBook apachectl[27499]: no listening sockets available, shutting down
sept. 05 17:22:21 EliteBook apachectl[27499]: AH00015: Unable to open logs
sept. 05 17:22:21 EliteBook apachectl[27499]: Action 'start' failed.
sept. 05 17:22:21 EliteBook apachectl[27499]: The Apache error log may have more information.
sept. 05 17:22:21 EliteBook systemd[1]: apache2.service: Control process exited, code=exited status=1
sept. 05 17:22:21 EliteBook systemd[1]: apache2.service: Failed with result 'exit-code'.
sept. 05 17:22:21 EliteBook systemd[1]: Failed to start The Apache HTTP Server.
ls -ll /var/log/apache2/
total 0
Pour info,
Ubuntu 18.04
Apache 2.4.29
mysql Ver 15.1 Distrib 10.1.34-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
J'ai passé tout l'après-midi à chercher la solution.
Je vous remercie beaucoup de vos réponses
Cordialement
Dernière modification par cypher_ubuntu (Le 06/09/2018, à 13:45)
Hors ligne
#2 Le 05/09/2018, à 17:39
- bruno
Re : [RÉSOLU]Problème de démarrage d'apache2
Bonjour,
Ton serveur apache ne démarre pas. Il y a sans doute une erreur de configuration, probablement sur l'emplacement des logs :
sept. 05 17:22:21 EliteBook apachectl[27499]: AH00015: Unable to open logs
Il faut que tu nous indiques ta configuration : les fichiers créés et modifiés et leur contenu.
sudo apache2ctl -t
peut donner des indications sur les erreurs de configuration.
#3 Le 06/09/2018, à 08:31
- cypher_ubuntu
Re : [RÉSOLU]Problème de démarrage d'apache2
Bonjour
voici sa réponse
sudo apache2ctl -t
Syntax OK
J'ai crée les logs error et access
ls -ll /var/log/apache2/
total 0
-rw-r--r-- 1 www-data www-data 0 sept. 6 09:26 access.log
-rw-r--r-- 1 www-data www-data 0 sept. 6 09:25 error.log
toujours le me problème
Encore merci
Cordialement
Hors ligne
#4 Le 06/09/2018, à 08:36
- bruno
Re : [RÉSOLU]Problème de démarrage d'apache2
Les fichiers de configuration que tu as créés et modifiés STP.
#5 Le 06/09/2018, à 08:59
- cypher_ubuntu
Re : [RÉSOLU]Problème de démarrage d'apache2
La config d'apache2
# 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
#
# The directory where shm and other runtime files will be stored.
#
DefaultRuntimeDir ${APACHE_RUN_DIR}
#
# 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 severity 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 debug
# 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 /home/cyphos/PROJETS/>
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
ServerName localhost:80
Hors ligne
#6 Le 06/09/2018, à 09:12
- bruno
Re : [RÉSOLU]Problème de démarrage d'apache2
Normalement on ne modifie pas le fichier apache2.conf.
Pourquoi as-tu commenté cette ligne :
#Include ports.conf
D'autre part cette partie devrait se trouver dans le configuration d'un hôte virtuel :
<Directory /home/cyphos/PROJETS/>
Options Indexes FollowSymLinks
AllowOverride None
Require all granted
</Directory>
#7 Le 06/09/2018, à 12:56
- cypher_ubuntu
Re : [RÉSOLU]Problème de démarrage d'apache2
oh j'ai honte mais je ne sais plus pourquoi cette ligne est commentée.
Maintenant, j'ai un autre problème
tail -f -n 5 /var/log/apache2/error.log
[Thu Sep 06 13:50:41.467608 2018] [authz_core:debug] [pid 18261] mod_authz_core.c(809): [client ::1:50004] AH01626: authorization result of <RequireAny>: denied (no authenticated user yet)
[Thu Sep 06 13:50:41.467683 2018] [authn_file:error] [pid 18261] (2)No such file or directory: [client ::1:50004] AH01620: Could not open password file: /etc/phpmyadmin/.htpasswd
[Thu Sep 06 13:50:45.162206 2018] [authz_core:debug] [pid 18260] mod_authz_core.c(809): [client ::1:50008] AH01626: authorization result of Require valid-user : denied (no authenticated user yet)
[Thu Sep 06 13:50:45.162281 2018] [authz_core:debug] [pid 18260] mod_authz_core.c(809): [client ::1:50008] AH01626: authorization result of <RequireAny>: denied (no authenticated user yet)
[Thu Sep 06 13:50:45.162326 2018] [authn_file:error] [pid 18260] (2)No such file or directory: [client ::1:50008] AH01620: Could not open password file: /etc/phpmyadmin/.htpasswd
Hors ligne
#8 Le 06/09/2018, à 13:06
- bruno
Re : [RÉSOLU]Problème de démarrage d'apache2
Tu as du bricoler la configuration de phpmyadmin, désinstalle complètement :
sudo apt purge phpmyadmln
en répondant oui à toutes les questions, puis réinsatlle :
sudo apt install phpmyadmin
#9 Le 06/09/2018, à 13:44
- cypher_ubuntu
Re : [RÉSOLU]Problème de démarrage d'apache2
c'est bon
je vous remercie beaucoup
vous m'avez bien aidé.
Je vous souhaite bonne journée
Cordialement
Hors ligne
Pages : 1