Apache lässt sich nicht starten

[webmystar]

Hallo,

nachdem ich das letsencrypt - Zertifikat unter ISPConfig 3.1 für eine Domain aktivieren wollte, stürzte der apache ab.

root@server-01:/usr/src# apache2ctl configtest && apache2ctl start
AH00548: NameVirtualHost has no effect and will be removed in the next release /etc/apache2/sites-enabled/000-ispconfig.conf:69
Syntax OK
AH00548: NameVirtualHost has no effect and will be removed in the next release /etc/apache2/sites-enabled/000-ispconfig.conf:69
Action 'start' failed.
The Apache error log may have more information.

000-ispconfig.conf

Alias /.well-known/acme-challenge /usr/local/ispconfig/interface/acme/.well-known/acme-challenge

<Directory /usr/local/ispconfig/interface/acme/.well-known/acme-challenge>
Require all granted
</Directory>
NameVirtualHost *:80 -> Zeile 69
NameVirtualHost *:443
NameVirtualHost IP:80
NameVirtualHost IP:443

error.log
[Sat Oct 22 16:16:02.004308 2016] [ssl:error] [pid 3667] AH02567: Unable to configure certificate server:8080:0 for stapling
[ 2016-10-22 16:16:02.0133 4400/7f9f14e5f740 agents/Watchdog/Main.cpp:538 ]: Options: { 'analytics_log_user' => 'nobody', 'default_group' => 'nogroup', 'default_python' => 'python', 'default_ruby' => '/usr/bin/ruby', 'default_user' => 'nobody', 'log_level' => '0', 'max_pool_size' => '6', 'passenger_root' => '/usr/lib/ruby/vendor_ruby/phusion_passenger/locations.ini', 'passenger_version' => '4.0.53', 'pool_idle_time' => '300', 'temp_dir' => '/tmp', 'union_station_gateway_address' => 'gateway.unionstationapp.com', 'union_station_gateway_port' => '443', 'user_switching' => 'true', 'web_server_passenger_version' => '4.0.53', 'web_server_pid' => '3667', 'web_server_type' => 'apache', 'web_server_worker_gid' => '33', 'web_server_worker_uid' => '33' }
[ 2016-10-22 16:16:02.0199 4403/7f84580b1740 agents/HelperAgent/Main.cpp:650 ]: PassengerHelperAgent online, listening at unix:/tmp/passenger.1.0.3667/generation-1/request
[ 2016-10-22 16:16:02.0362 4411/7f4d2aa1d780 agents/LoggingAgent/Main.cpp:321 ]: PassengerLoggingAgent online, listening at unix:/tmp/passenger.1.0.3667/generation-1/logging
[ 2016-10-22 16:16:02.0365 4400/7f9f14e5f740 agents/Watchdog/Main.cpp:728 ]: All Phusion Passenger agents started!
[Sat Oct 22 16:16:02.079061 2016] [:error] [pid 3667] python_init: Python version mismatch, expected '2.7.5+', found '2.7.9'.
[Sat Oct 22 16:16:02.079194 2016] [:error] [pid 3667] python_init: Python executable found '/usr/bin/python'.
[Sat Oct 22 16:16:02.079202 2016] [:error] [pid 3667] python_init: Python path being used '/usr/lib/python2.7/:/usr/lib/python2.7/plat-x86_64-linux-gnu:/usr/lib/python2.7/lib-tk:/usr/lib/python2.7/lib-old:/usr/lib/python2.7/lib-dynload'.
[Sat Oct 22 16:16:02.079218 2016] [:notice] [pid 3667] mod_python: Creating 8 session mutexes based on 150 max processes and 0 max threads.
[Sat Oct 22 16:16:02.079228 2016] [:notice] [pid 3667] mod_python: using mutex_directory /tmp
[Sat Oct 22 16:16:02.089699 2016] [mpm_prefork:notice] [pid 3667] AH00163: Apache/2.4.10 (Debian) mod_fastcgi/mod_fastcgi-SNAP-0910052141 OpenSSL/1.0.1t mod_fcgid/2.3.9 Phusion_Passenger/4.0.53 mod_python/3.3.1 Python/2.7.9 configured -- resuming normal operations
[Sat Oct 22 16:16:02.089726 2016] [core:notice] [pid 3667] AH00094: Command line: '/usr/sbin/apache2'
[Sat Oct 22 16:16:02.089763 2016] [mpm_prefork:warn] [pid 3667] AH00167: long lost child came home! (pid 3670)
[Sat Oct 22 16:18:02.710177 2016] [mpm_prefork:notice] [pid 3667] AH00169: caught SIGTERM, shutting down
AH00016: Configuration Failed
AH00016: Configuration Failed
AH00016: Configuration Failed
AH00016: Configuration Failed
AH00016: Configuration Failed
AH00016: Configuration Failed
AH00016: Configuration Failed

Über einen Tipp würde ich mich sehr freuen.

Danke und Grüße,
Sven

 

[Till]

Deaktiviere den vhost bei dem Du letsencrypt aktiviert hast indem Du den symlink im apache sites-enabled verzeichnis löschst, danach starte apache neu. Mit der ispconfig.conf Datei die Du oben gepostet hast hat das nichts zu tun.

Das Problem tritt auf wenn der ssl key und das ssl cert nicht zusammen passen in der website in der Du ssl per letsencrypt aktiviert hast. vermutlich gab es da schon ein manuell erstelltes ssl cert.

 

[webmystar]

Danke Till, läuft jetzt alles wieder!