Debian Apache startet nicht

Lockslay

New Member
Hallo Linuxfreunde,

Ich habe auf meinem Debian 8 den Apache neu installiert und nun Problem diesen zu starten.

Den Fehler, kann ich schon einkreisen. Laut google gab es Probleme beim
Update vom Apache Webserver von Version 2.2 auf 2.4.

http://httpd.apache.org/docs/2.4/upgrading.html#run-time

Code:
Directives AcceptMutex, LockFile, RewriteLock, SSLMutex, SSLStaplingMutex, and WatchdogMutexPath have been replaced with a single Mutex directive. You will need to evaluate any use of these removed directives in your 2.2 configuration to determine if they can just be deleted or will need to be replaced using Mutex


/etc/init.d/apache2 start
Code:
[....] Starting apache2 (via systemctl): apache2.serviceJob for apache2.service failed. See 'systemctl status apache2.service' and 'journalctl -xn' for details.
 failed!

systemctl status httpd.service
Code:
● httpd.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

Hier bekomme ich zahlreiche Meldungen :
journalctl –xe

Code:
Feb 15 07:51:48 debianserver dhclient[2115]: send_packet: Operation not permitte
Feb 15 07:51:48 debianserver dhclient[2115]: dhclient.c:2243: Failed to send 300
Feb 15 07:51:50 debianserver dhclient[700]: DHCPREQUEST on eth0 to 192.168.0.1 p
Feb 15 07:51:50 debianserver dhclient[700]: send_packet: Operation not permitted
Feb 15 07:51:50 debianserver dhclient[700]: dhclient.c:2243: Failed to send 300
Feb 15 07:51:58 debianserver dhclient[700]: DHCPREQUEST on eth0 to 192.168.0.1 p
Feb 15 07:51:58 debianserver dhclient[700]: send_packet: Operation not permitted
Feb 15 07:51:58 debianserver dhclient[700]: dhclient.c:2243: Failed to send 300
Feb 15 07:51:59 debianserver dhclient[2115]: DHCPREQUEST on eth0 to 192.168.0.1
Feb 15 07:51:59 debianserver dhclient[2115]: send_packet: Operation not permitte
Feb 15 07:51:59 debianserver dhclient[2115]: dhclient.c:2243: Failed to send 300
Feb 15 07:52:07 debianserver dhclient[2115]: DHCPREQUEST on eth0 to 192.168.0.1
Feb 15 07:52:07 debianserver dhclient[2115]: send_packet: Operation not permitte
Feb 15 07:52:07 debianserver dhclient[2115]: dhclient.c:2243: Failed to send 300
Feb 15 07:52:15 debianserver dhclient[2115]: DHCPREQUEST on eth0 to 192.168.0.1
Feb 15 07:52:15 debianserver dhclient[2115]: send_packet: Operation not permitte
Feb 15 07:52:15 debianserver dhclient[2115]: dhclient.c:2243: Failed to send 300
Feb 15 07:52:18 debianserver dhclient[700]: DHCPREQUEST on eth0 to 192.168.0.1 p
Feb 15 07:52:18 debianserver dhclient[700]: send_packet: Operation not permitted
Feb 15 07:52:18 debianserver dhclient[700]: dhclient.c:2243: Failed to send 300
Feb 15 07:52:26 debianserver dhclient[2115]: DHCPREQUEST on eth0 to 192.168.0.1
Feb 15 07:52:26 debianserver dhclient[2115]: send_packet: Operation not permitte
Feb 15 07:52:26 debianserver dhclient[2115]: dhclient.c:2243: Failed to send 300
lines 1035-1057/1057 (END)
Feb 15 07:51:48 debianserver dhclient[2115]: send_packet: Operation not permitted
Feb 15 07:51:48 debianserver dhclient[2115]: dhclient.c:2243: Failed to send 300 byte long packet over fallback interface.
Feb 15 07:51:50 debianserver dhclient[700]: DHCPREQUEST on eth0 to 192.168.0.1 port 67
Feb 15 07:51:50 debianserver dhclient[700]: send_packet: Operation not permitted
Feb 15 07:51:50 debianserver dhclient[700]: dhclient.c:2243: Failed to send 300 byte long packet over fallback interface.
Feb 15 07:51:58 debianserver dhclient[700]: DHCPREQUEST on eth0 to 192.168.0.1 port 67
Feb 15 07:51:58 debianserver dhclient[700]: send_packet: Operation not permitted
Feb 15 07:51:58 debianserver dhclient[700]: dhclient.c:2243: Failed to send 300 byte long packet over fallback interface.
Feb 15 07:51:59 debianserver dhclient[2115]: DHCPREQUEST on eth0 to 192.168.0.1 port 67
Feb 15 07:51:59 debianserver dhclient[2115]: send_packet: Operation not permitted
Feb 15 07:51:59 debianserver dhclient[2115]: dhclient.c:2243: Failed to send 300 byte long packet over fallback interface.
Feb 15 07:52:07 debianserver dhclient[2115]: DHCPREQUEST on eth0 to 192.168.0.1 port 67
Feb 15 07:52:07 debianserver dhclient[2115]: send_packet: Operation not permitted
Feb 15 07:52:07 debianserver dhclient[2115]: dhclient.c:2243: Failed to send 300 byte long packet over fallback interface.
Feb 15 07:52:15 debianserver dhclient[2115]: DHCPREQUEST on eth0 to 192.168.0.1 port 67
Feb 15 07:52:15 debianserver dhclient[2115]: send_packet: Operation not permitted
Feb 15 07:52:15 debianserver dhclient[2115]: dhclient.c:2243: Failed to send 300 byte long packet over fallback interface.
Feb 15 07:52:18 debianserver dhclient[700]: DHCPREQUEST on eth0 to 192.168.0.1 port 67
Feb 15 07:52:18 debianserver dhclient[700]: send_packet: Operation not permitted
Feb 15 07:52:18 debianserver dhclient[700]: dhclient.c:2243: Failed to send 300 byte long packet over fallback interface.
Feb 15 07:52:26 debianserver dhclient[2115]: DHCPREQUEST on eth0 to 192.168.0.1 port 67
Feb 15 07:52:26 debianserver dhclient[2115]: send_packet: Operation not permitted
Feb 15 07:52:26 debianserver dhclient[2115]: dhclient.c:2243: Failed to send 300 byte long packet over fallback interface.

apache2 -t
Code:
[Wed Feb 15 07:55:01.780506 2017] [core:warn] [pid 22065] AH00111: Config variable ${APACHE_LOCK_DIR} is not defined
[Wed Feb 15 07:55:01.780739 2017] [core:warn] [pid 22065] AH00111: Config variable ${APACHE_PID_FILE} is not defined
[Wed Feb 15 07:55:01.780842 2017] [core:warn] [pid 22065] AH00111: Config variable ${APACHE_RUN_USER} is not defined
[Wed Feb 15 07:55:01.780923 2017] [core:warn] [pid 22065] AH00111: Config variable ${APACHE_RUN_GROUP} is not defined
[Wed Feb 15 07:55:01.781064 2017] [core:warn] [pid 22065] AH00111: Config variable ${APACHE_LOG_DIR} is not defined
[Wed Feb 15 07:55:01.912429 2017] [core:warn] [pid 22065] AH00111: Config variable ${APACHE_RUN_DIR} is not defined
[Wed Feb 15 07:55:01.914654 2017] [core:warn] [pid 22065] AH00111: Config variable ${APACHE_LOG_DIR} is not defined
[Wed Feb 15 07:55:01.916453 2017] [core:warn] [pid 22065] AH00111: Config variable ${APACHE_LOG_DIR} is not defined
[Wed Feb 15 07:55:01.916575 2017] [core:warn] [pid 22065] 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}

Code:
Syntax error on line 74 of /etc/apache2/apache2.conf
Mutex file:${APACHE_LOCK_DIR} default
Steht in der Zeile, ein Kommentieren der Zeile brachte nichts.

Hier sehe ich das eigentliche Problem,


apachectl configtest
Code:
Syntax OK

apachectl restart
Code:
httpd not running, trying to start
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:443

apachectl -V
Code:
Server version: Apache/2.4.10 (Debian)
Server built:   Sep 15 2016 20:44:43
Server's Module Magic Number: 20120211:37
Server loaded:  APR 1.5.1, APR-UTIL 1.5.4
Compiled using: APR 1.5.1, APR-UTIL 1.5.4
Architecture:   64-bit
Server MPM:     prefork
  threaded:     no
    forked:     yes (variable process count)
Server compiled with....
 -D APR_HAS_SENDFILE
 -D APR_HAS_MMAP
 -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
 -D APR_USE_SYSVSEM_SERIALIZE
 -D APR_USE_PTHREAD_SERIALIZE
 -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
 -D APR_HAS_OTHER_CHILD
 -D AP_HAVE_RELIABLE_PIPED_LOGS
 -D DYNAMIC_MODULE_LIMIT=256
 -D HTTPD_ROOT="/etc/apache2"
 -D SUEXEC_BIN="/usr/lib/apache2/suexec"
 -D DEFAULT_PIDLOG="/var/run/apache2.pid"
 -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
 -D DEFAULT_ERRORLOG="logs/error_log"
 -D AP_TYPES_CONFIG_FILE="mime.types"
 -D SERVER_CONFIG_FILE="apache2.conf"

Hier habe ich nochmal die neue apache.conf http://paste.debian.net/914516/

Kann mir einer helfen, den Apache wieder zum laufen zu bekommen, da auf dem Rechner nextcloud läuft kann ich die cloud ohne Apache nicht nutzen.

Gruß
Lockslay
 

GwenDragon

Registered User
Dan grep doch mal im Sytemlog nach iptables und REJECT oder DROP und schau dir DPT und SPT an.
Dann siehst doch wo was blockiert wird.
 
Top