root@Programing-PC:~# journalctl -xeu apache2.service
░░ Subject: A start job for unit apache2.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit apache2.service has begun execution.
░░
░░ The job identifier is 42264.
mar 20 15:15:14 Programing-PC apachectl[570974]: AH00526: Syntax error on line 24 of /etc/apache2/sites-enabled/default-ssl.>
mar 20 15:15:14 Programing-PC apachectl[570974]: Invalid command 'SSLEngine', perhaps misspelled or defined by a module not >
mar 20 15:15:14 Programing-PC systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit apache2.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
mar 20 15:15:14 Programing-PC systemd[1]: apache2.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit apache2.service has entered the 'failed' state with result 'exit-code'.
mar 20 15:15:14 Programing-PC systemd[1]: Failed to start apache2.service - The Apache HTTP Server.
░░ Subject: A start job for unit apache2.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit apache2.service has finished with a failure.
░░
░░ The job identifier is 42264 and the job result is failed.
lines 964-994/994 (END)A workaround was on github.com were they added a check to the conf file alike in .htacces as in .default-ssl.conf for this dir:Note that if I add # SSLEngine apache2 is working with htttp and no https ...
We could try:When was broken I followed the steps from https://std.rocks/gnulinux_tftp.html
I used the IP 192.168.0.4 instead 192.168.1.10 and worked.
In sites-enabled we have default-ssl.conf and 000-default.conf ...
After commenting so the lines I get:
root@Programing-PC:~# journalctl -xeu apache2.service
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit apache2.service has begun execution.
░░
░░ The job identifier is 44535.
mar 20 17:50:12 Programing-PC apachectl[686785]: (98)Address already in use: AH00072: make_sock: could not bind to address [>
mar 20 17:50:12 Programing-PC apachectl[686785]: (98)Address already in use: AH00072: make_sock: could not bind to address 0>
mar 20 17:50:12 Programing-PC apachectl[686785]: no listening sockets available, shutting down
mar 20 17:50:12 Programing-PC apachectl[686785]: AH00015: Unable to open logs
mar 20 17:50:12 Programing-PC systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit apache2.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
mar 20 17:50:12 Programing-PC systemd[1]: apache2.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit apache2.service has entered the 'failed' state with result 'exit-code'.
mar 20 17:50:12 Programing-PC systemd[1]: Failed to start apache2.service - The Apache HTTP Server.
░░ Subject: A start job for unit apache2.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit apache2.service has finished with a failure.
░░
░░ The job identifier is 44535 and the job result is failed.
root@Programing-PC:~#
░░ Subject: A start job for unit apache2.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit apache2.service has begun execution.
░░
░░ The job identifier is 42264.
mar 20 15:15:14 Programing-PC apachectl[570974]: AH00526: Syntax error on line 24 of /etc/apache2/sites-enabled/default-ssl.>
mar 20 15:15:14 Programing-PC apachectl[570974]: Invalid command 'SSLEngine', perhaps misspelled or defined by a module not >
mar 20 15:15:14 Programing-PC systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit apache2.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
mar 20 15:15:14 Programing-PC systemd[1]: apache2.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit apache2.service has entered the 'failed' state with result 'exit-code'.
mar 20 15:15:14 Programing-PC systemd[1]: Failed to start apache2.service - The Apache HTTP Server.
░░ Subject: A start job for unit apache2.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit apache2.service has finished with a failure.
░░
░░ The job identifier is 42264 and the job result is failed.
lines 964-994/994 (END)
Code:
Volumul in unitatea z nu are eticheta.Numarul de serie al volumului este 240b-6525Directory of z:\etc\apache2\sites-available20.03.2024 15:31 <DIR> .20.03.2024 15:15 <DIR> ..20.09.2023 14:03 6,337 .default-ssl.conf20.09.2023 14:03 16,384 .default-ssl.conf.swp19.10.2023 12:52 1,286 000-default.conf19.10.2023 12:56 4,573 default-ssl.conf17.02.2023 15:12 656 openqa.conf.template17.02.2023 15:12 2,658 openqa-common.inc17.02.2023 15:12 807 openqa-ssl.conf.template20.03.2024 15:32 88 sites-available.txt 8 files 32,789 bytes 2 directories 177,706,688,512 bytes freeCode:
<IfModule mod_ssl.c><VirtualHost _default_:443>#</VirtualHost></IfModule># vim: syntax=apache ts=4 sw=4 sts=4 sr noetWe could try:
Code:
<IfModule mod_ssl.c>SSLEngine On</IfModule>I used the IP 192.168.0.4 instead 192.168.1.10 and worked.
In sites-enabled we have default-ssl.conf and 000-default.conf ...
After commenting so the lines I get:
root@Programing-PC:~# journalctl -xeu apache2.service
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit apache2.service has begun execution.
░░
░░ The job identifier is 44535.
mar 20 17:50:12 Programing-PC apachectl[686785]: (98)Address already in use: AH00072: make_sock: could not bind to address [>
mar 20 17:50:12 Programing-PC apachectl[686785]: (98)Address already in use: AH00072: make_sock: could not bind to address 0>
mar 20 17:50:12 Programing-PC apachectl[686785]: no listening sockets available, shutting down
mar 20 17:50:12 Programing-PC apachectl[686785]: AH00015: Unable to open logs
mar 20 17:50:12 Programing-PC systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit apache2.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
mar 20 17:50:12 Programing-PC systemd[1]: apache2.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit apache2.service has entered the 'failed' state with result 'exit-code'.
mar 20 17:50:12 Programing-PC systemd[1]: Failed to start apache2.service - The Apache HTTP Server.
░░ Subject: A start job for unit apache2.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit apache2.service has finished with a failure.
░░
░░ The job identifier is 44535 and the job result is failed.
root@Programing-PC:~#
Statistics: Posted by orynider — 2024-03-20 13:29 — Replies 0 — Views 33