Hallo!
Will mir nen Webserver auf ARCH Basis einrichten
Habe dieses Tutorial benutzt: Hier
Die Apache Installation und in Betriebnahme hat funktioniert, leider scheitere ich am
Sobald ich das bei den vorhandenen LoadModule anfüge (egal ob ganz oben oder unten) und den apache neustarte, bekomm ich folgende Fehlermeldung:
Code
[root@alarmpi ~]# systemctl restart httpd
Job for httpd.service failed. See 'systemctl status httpd.service' and 'journalctl -xn' for details.
Ausgabe von systemctl status httpd.service:
Code
[root@alarmpi ~]# systemctl status httpd.service
httpd.service - Apache Web Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled)
Active: failed (Result: exit-code) since Sun 2014-03-23 18:40:09 CET; 1min 9s ago
Process: 1234 ExecStop=/usr/bin/apachectl graceful-stop (code=exited, status=1/FAILURE)
Process: 1241 ExecStart=/usr/bin/apachectl start (code=exited, status=1/FAILURE)
Main PID: 1099 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/httpd.service
Mar 23 18:40:08 alarmpi systemd[1]: Unit httpd.service entered failed state.
Mar 23 18:40:08 alarmpi systemd[1]: Starting Apache Web Server...
Mar 23 18:40:09 alarmpi apachectl[1241]: [Sun Mar 23 18:40:09.737085 2014] [....
Mar 23 18:40:09 alarmpi apachectl[1241]: AH00013: Pre-configuration failed
Mar 23 18:40:09 alarmpi systemd[1]: httpd.service: control process exited, ...=1
Mar 23 18:40:09 alarmpi systemd[1]: Failed to start Apache Web Server.
Mar 23 18:40:09 alarmpi systemd[1]: Unit httpd.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.
Alles anzeigen
Ausgabe von journalctl -xn:
Code
journalctl -xn
-- Logs begin at Sun 2014-03-23 18:22:55 CET, end at Sun 2014-03-23 18:42:59 CET
Mar 23 18:42:56 alarmpi systemd[1]: Started Trigger Flushing of Journal to Persi
-- Subject: Unit systemd-journal-flush.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-journal-flush.service has finished starting up.
--
-- The start-up result is done.
Mar 23 18:42:58 alarmpi systemd[1]: systemd-logind.service watchdog timeout!
Mar 23 18:42:58 alarmpi systemd[1]: systemd-logind.service: main process exited,
Mar 23 18:42:58 alarmpi systemd[1]: Unit systemd-logind.service entered failed s
Mar 23 18:42:59 alarmpi systemd[1]: systemd-logind.service holdoff time over, sc
Mar 23 18:42:59 alarmpi systemd[1]: Stopping Login Service...
-- Subject: Unit systemd-logind.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-logind.service has begun shutting down.
Mar 23 18:42:59 alarmpi systemd[1]: Starting Login Service...
-- Subject: Unit systemd-logind.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-logind.service has begun starting up.
Mar 23 18:42:59 alarmpi systemd-logind[1267]: New seat seat0.
-- Subject: A new seat seat0 is now available
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new seat seat0 has been configured and is now available.
Mar 23 18:42:59 alarmpi systemd[1]: Started Login Service.
-- Subject: Unit systemd-logind.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
Alles anzeigen
Leider werde ich daraus nicht schlau.
Das vorgeschriebene Include funktioniert jedoch ohne Fehler beim restart.