Ubuntu-fr

Nisaea

[RÉSOLU] Apache2 ne démarre pas sous Lucid

Bonjour à tous,

Je viens de faire une install toute neuve de Lucid, et j'ai installé Apache2. Or surprise, pas moyen d'ouvrir localhost/127.0.0.1 dans mon navigateur.

J'ai donc tapé les commandes suivantes:

pn@deudeuche:/etc/apache2$ sudo /etc/init.d/apache2 start
 * Starting web server apache2                                                  apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
                                                                         [ OK ]
pn@deudeuche:/etc/apache2$ sudo /etc/init.d/apache2 status
Apache is NOT running.
pn@deudeuche:/etc/apache2$ ping localhost
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.036 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.037 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.039 ms
^C
--- localhost ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.036/0.037/0.039/0.005 ms

Si j'ai tout suivi, je lui demande de démarrer Apache, il me dit que tout va bien. Je lui demande si c'est bien démarré, il me dit que non. Je lui demande de piguer localhost, ça fonctionne par miracle.

Soit j'ai rien compris (ce qui est plus que probable), soit il me prend pour un jambon!

Voici quelques uns de mes fichiers de config dans lesquels je patauge dans les grandes largeurs, je suis une vraie bille dès qu'il s'agit de réseaux...

127.0.0.1    localhost
127.0.1.1    deudeuche

# The following lines are desirable for IPv6 capable hosts
::1     localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

#
# Based upon the NCSA server configuration files originally by Rob McCool.
#
# 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.2/ for detailed information about
# the directives.
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned. 
#
# The configuration directives are grouped into three basic sections:
#  1. Directives that control the operation of the Apache server process as a
#     whole (the 'global environment').
#  2. Directives that define the parameters of the 'main' or 'default' server,
#     which responds to requests that aren't handled by a virtual host.
#     These directives also provide default values for the settings
#     of all virtual hosts.
#  3. Settings for virtual hosts, which allow Web requests to be sent to
#     different IP addresses or hostnames and have them handled by the
#     same Apache server process.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "/var/log/apache2/foo.log"
# with ServerRoot set to "" will be interpreted by the
# server as "//var/log/apache2/foo.log".
#

### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#

#
# 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 LockFile documentation (available
# at <URL:http://httpd.apache.org/docs-2.1/mod/mpm_common.html#lockfile>);
# 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.
#
#<IfModule !mpm_winnt.c>
#<IfModule !mpm_netware.c>
LockFile /var/lock/apache2/accept.lock
#</IfModule>
#</IfModule>

#
# 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 15

##
## Server-Pool Size Regulation (MPM specific)
##

# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_prefork_module>
    StartServers          5
    MinSpareServers       5
    MaxSpareServers      10
    MaxClients          150
    MaxRequestsPerChild   0
</IfModule>

# worker MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_worker_module>
    StartServers          2
    MinSpareThreads      25
    MaxSpareThreads      75
    ThreadLimit          64
    ThreadsPerChild      25
    MaxClients          150
    MaxRequestsPerChild   0
</IfModule>

# event MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_event_module>
    StartServers          2
    MaxClients          150
    MinSpareThreads      25
    MaxSpareThreads      75
    ThreadLimit          64
    ThreadsPerChild      25
    MaxRequestsPerChild   0
</IfModule>

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

#
# 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.
#
<Files ~ "^\.ht">
    Order allow,deny
    Deny from all
    Satisfy all
</Files>

#
# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value.  If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

#
# 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 /var/log/apache2/error.log

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

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

# Include all the user configurations:
Include /etc/apache2/httpd.conf

# Include ports listing
Include /etc/apache2/ports.conf

#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
# If you are behind a reverse proxy, you might want to change %h into %{X-Forwarded-For}i
#
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

#
# Define an access log for VirtualHosts that don't define their own logfile
CustomLog /var/log/apache2/other_vhosts_access.log vhost_combined

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

# Include generic snippets of statements
Include /etc/apache2/conf.d/

# Include the virtual host configurations:
Include /etc/apache2/sites-enabled/

L'un d'entre vous aurait-il une petite idée de ce qui ne tourne pas rond?

Merci d'avance pour vos lumières!

Dernière modification par Nisaea (Le 28/06/2010, à 18:00)

---

Chiastre!

gl38

Re : [RÉSOLU] Apache2 ne démarre pas sous Lucid

D'abord ping et apache n'ont rien à voir : ping indique juste que la connexion réseau fonctionne.
Pour apache, il y a des fichiers log dans /var/log qui devraient dire ce qui ne va pas.
Dans ton fichier /etc/hosts, il devrait y avoir une ligne avec un numero IP du genre 192.168.1.xxx pour ta machine.

Cordialement,
Guy

Dernière modification par gl38 (Le 28/06/2010, à 07:21)

Nisaea

Re : [RÉSOLU] Apache2 ne démarre pas sous Lucid

Bonjour gl38 et merci pour ta réponse! J'ai appris plein de trucs déjà

Voici quelques cat supplémentaires en accord avec tes suggestions:

127.0.0.1    localhost
127.0.1.1    deudeuche

# The following lines are desirable for IPv6 capable hosts
::1     localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

[Sun Jun 27 23:27:48 2010] [notice] Apache/2.2.14 (Ubuntu) configured -- resuming normal operations
[Sun Jun 27 23:28:03 2010] [notice] Graceful restart requested, doing restart
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
[Sun Jun 27 23:28:04 2010] [notice] Apache/2.2.14 (Ubuntu) mod_perl/2.0.4 Perl/v5.10.1 configured -- resuming normal operations
[Sun Jun 27 23:28:19 2010] [notice] Graceful restart requested, doing restart
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
icecpp: error: cannot open `/usr/share/slice/Glacier2/Router.ice' for reading
PHP Fatal error:  Unable to start ice module in Unknown on line 0
icecpp: error: cannot open `/usr/share/slice/Glacier2/Router.ice' for reading
PHP Fatal error:  Unable to start ice module in Unknown on line 0
icecpp: error: cannot open `/usr/share/slice/Glacier2/Router.ice' for reading
PHP Fatal error:  Unable to start ice module in Unknown on line 0
icecpp: error: cannot open `/usr/share/slice/Glacier2/Router.ice' for reading
PHP Fatal error:  Unable to start ice module in Unknown on line 0
icecpp: error: cannot open `/usr/share/slice/Glacier2/Router.ice' for reading
PHP Fatal error:  Unable to start ice module in Unknown on line 0
icecpp: error: cannot open `/usr/share/slice/Glacier2/Router.ice' for reading
PHP Fatal error:  Unable to start ice module in Unknown on line 0
icecpp: error: cannot open `/usr/share/slice/Glacier2/Router.ice' for reading
PHP Fatal error:  Unable to start ice module in Unknown on line 0
icecpp: error: cannot open `/usr/share/slice/Glacier2/Router.ice' for reading
PHP Fatal error:  Unable to start ice module in Unknown on line 0
icecpp: error: cannot open `/usr/share/slice/Glacier2/Router.ice' for reading
PHP Fatal error:  Unable to start ice module in Unknown on line 0
icecpp: error: cannot open `/usr/share/slice/Glacier2/Router.ice' for reading
PHP Fatal error:  Unable to start ice module in Unknown on line 0

127.0.0.1 - - [27/Jun/2010:23:28:03 +0200] "OPTIONS * HTTP/1.0" 200 152 "-" "Apache/2.2.14 (Ubuntu) (internal dummy connection)"
127.0.0.1 - - [27/Jun/2010:23:28:03 +0200] "OPTIONS * HTTP/1.0" 200 152 "-" "Apache/2.2.14 (Ubuntu) (internal dummy connection)"
127.0.0.1 - - [27/Jun/2010:23:28:03 +0200] "OPTIONS * HTTP/1.0" 200 152 "-" "Apache/2.2.14 (Ubuntu) (internal dummy connection)"
127.0.0.1 - - [27/Jun/2010:23:28:03 +0200] "OPTIONS * HTTP/1.0" 200 152 "-" "Apache/2.2.14 (Ubuntu) (internal dummy connection)"
127.0.0.1 - - [27/Jun/2010:23:28:03 +0200] "OPTIONS * HTTP/1.0" 200 152 "-" "Apache/2.2.14 (Ubuntu) (internal dummy connection)"
127.0.0.1 - - [27/Jun/2010:23:28:19 +0200] "OPTIONS * HTTP/1.0" 200 152 "-" "Apache/2.2.14 (Ubuntu) (internal dummy connection)"
127.0.0.1 - - [27/Jun/2010:23:28:19 +0200] "OPTIONS * HTTP/1.0" 200 152 "-" "Apache/2.2.14 (Ubuntu) (internal dummy connection)"
127.0.0.1 - - [27/Jun/2010:23:28:19 +0200] "OPTIONS * HTTP/1.0" 200 152 "-" "Apache/2.2.14 (Ubuntu) (internal dummy connection)"
127.0.0.1 - - [27/Jun/2010:23:28:19 +0200] "OPTIONS * HTTP/1.0" 200 152 "-" "Apache/2.2.14 (Ubuntu) (internal dummy connection)"
127.0.0.1 - - [27/Jun/2010:23:28:19 +0200] "OPTIONS * HTTP/1.0" 200 152 "-" "Apache/2.2.14 (Ubuntu) (internal dummy connection)"

Étrangement, il n'y a rien qui date d'aujourd'hui... Pourtant j'ai redémarré apache 2 fois

---

Chiastre!

gl38

Re : [RÉSOLU] Apache2 ne démarre pas sous Lucid

Il y a des erreurs avec le paquet slice
On en parle ici

À vrai dire, je ne sais pas à quoi sert ce paquet, peut-être qu'il faudrait le mettre hors course pour voir si apache marche et consent à afficher "It works" quand tu demandes http://localhost

Cordialement,
Guy

Nisaea

Re : [RÉSOLU] Apache2 ne démarre pas sous Lucid

Merci beaucoup, je vais tester les solutions proposées par le gars et je vous tiens au courant.

---

Chiastre!

Nisaea

Re : [RÉSOLU] Apache2 ne démarre pas sous Lucid

Bon, bonne nouvelle, sa solution fonctionne!

Dans l'ordre:

- J'ai réinstallé ice33-slice et mumble-server (même si je ne suis pas persuadée que ce soit le maillon faible de l'histoire)

- J'ai ensuite créé les liens symboliques manquants (briques manquantes à l'install certainement):

sudo ln -s /usr/share/Ice-3.3.1/slice/Ice /usr/share/slice/
sudo ln -s /usr/share/Ice-3.3.1/slice/Glacier2 /usr/share/slice/

Et impeccable, apache2 status me dit qu'il tourne et j'ai accès à un beau "It Works" en tapant localhost dans mon navigateur.

Merci beaucoup gl38 pour ton aide, j'ai fait tout plein de recherches mais je suis vraiment passée à côté de ce truc!

---

Chiastre!