ubuntuusers.de

Apache 2 Fehler

Status: Ungelöst | Ubuntu-Version: Ubuntu 16.04 (Xenial Xerus)
Antworten |

pipen

Anmeldungsdatum:
28. Mai 2017

Beiträge: Zähle...

Hallo,

ich bin gerade am konfigurieren einer PIM Umgebung. Dafür habe ich auf Ubuntu 16.04 den apache2, PHP 5.6 und mysql 5.6 installiert. Bis zur Konfiguration lief alles fehlerfrei. Ab dem einschalten des Virtual Hosts bekomme ich Fehlermeldungen und kann den Apache2 nicht mehr starten. Die Fehlermeldung ist:

akeneo@akeneo-pc:~$ sudo service apache2 start
Job for apache2.service failed because the control process exited with error code. See "systemctl status apache2.service" and "journalctl -xe" for details. 
akeneo@akeneo-pc:~$ systemctl status apache2.service
● apache2.service - LSB: Apache2 web server
   Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)
  Drop-In: /lib/systemd/system/apache2.service.d
           └─apache2-systemd.conf
   Active: failed (Result: exit-code) since Di 2017-06-06 08:25:50 CEST; 24min a
     Docs: man:systemd-sysv-generator(8)
  Process: 4174 ExecStart=/etc/init.d/apache2 start (code=exited, status=1/FAILU

Jun 06 08:25:50 akeneo-pc apache2[4174]:  *
Jun 06 08:25:50 akeneo-pc apache2[4174]:  * The apache2 configtest failed.
Jun 06 08:25:50 akeneo-pc apache2[4174]: Output of config test was:
Jun 06 08:25:50 akeneo-pc apache2[4174]: apache2: Syntax error on line 219 of /e
Jun 06 08:25:50 akeneo-pc apache2[4174]: Action 'configtest' failed.
Jun 06 08:25:50 akeneo-pc apache2[4174]: The Apache error log may have more info
Jun 06 08:25:50 akeneo-pc systemd[1]: apache2.service: Control process exited, c
Jun 06 08:25:50 akeneo-pc systemd[1]: Failed to start LSB: Apache2 web server.
Jun 06 08:25:50 akeneo-pc systemd[1]: apache2.service: Unit entered failed state
Jun 06 08:25:50 akeneo-pc systemd[1]: apache2.service: Failed with result 'exit-
lines 1-18/18 (END)

Kann mir jemand einen Tipp geben?

MFG Christian

Bearbeitet von redknight:

Codeblock eingefügt. Bitte nutze die Syntax und die Vorschau, um deine Beiträge lesbar zu halten.

redknight Team-Icon

Moderator & Supporter
Avatar von redknight

Anmeldungsdatum:
30. Oktober 2008

Beiträge: 21850

Wohnort: Lorchhausen im schönen Rheingau

Servus.

zunächst mal solltest Du

apache2ctl configtest

ausführen, bevor du den Server neustartest. Dann wirst Du auf grundlegende Probleme hingewiesen. In deinem Fall scheint eine Konfig (Pfad ist leider in deiner Ausgabe abgeschnitten in Zeile 219 fehlerhaft zu sein, also solltest Du mal die entsprechenden Blöcke herzeigen. Bitte aber in Codeblöcken

pipen

(Themenstarter)

Anmeldungsdatum:
28. Mai 2017

Beiträge: 8

Hier der configtest

akeneo@akeneo-pc:~$ sudo apache2ctl configtest
[sudo] Passwort für akeneo: 
apache2: Syntax error on line 219 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/sites-enabled/akeneo-pim.local.conf: </VirtualHost without matching <VirtualHost section
Action 'configtest' failed.
The Apache error log may have more information.

Und hier meine apache2.conf

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

Und hier mein Host file

</VirtualHost *:80>
    ServerName akeneo-pim.local

    DocumentRoot /var/www/html/pim-community-standard/web/
    <Directory /var/www/html/pim-community-standard/web/>
        AllowOverride All
        Require all granted
    </Directory>
    ErrorLog ${APACHE_LOG_DIR}/akeneo-pim_error.log

    LogLevel warn
    CustomLog ${APACHE_LOG_DIR}/akeneo-pim_access.log combined
</VirtualHost>

MFG Christian

seahawk1986

Anmeldungsdatum:
27. Oktober 2006

Beiträge: 11261

Wohnort: München

Der Slash (das zweite Zeichen in der ersten Zeile) in der Datei für die Host-Konfiguration ist zu viel.

pipen

(Themenstarter)

Anmeldungsdatum:
28. Mai 2017

Beiträge: 8

Manchmal könnte das Leben so einfach sein 😀 Vielen Dank das wars.

Ich habe noch eine Frage. Ich weiss jetzt nicht ob es hierher passt, oder ob ich da ein neues Thema aufmachen soll. Ich möchte jetzt diese akeneo-pim.local vom Netzwerk erreichbar machen. Wie kann ich das am Besten realisieren? Wie pflege ich den Ubuntu mit dem Apache2 sauber in mein Netz? Wir haben folgende Konfiguration:

VMWARE vSphere 5.5 Virtueller Server SBS 2011 mit Exchange und DNS auf 192.168.0.100 - Virtueller Ubuntu 16.04 mit 192.168.0.69 wo der Apache2 mit akeneo-pim.local 127.0.0.1 läuft

MFG Christian

pipen

(Themenstarter)

Anmeldungsdatum:
28. Mai 2017

Beiträge: 8

Jetzt habe ich es selbst lösen können.

Einfach in der /etc/hosts den Eintrag 192.168.0.248 akeneo-pim.local eingetragen. Ich hoffe das war die richtige Lösung. Funktionieren tut es auf alle Fälle.

MFG Christian

Antworten |