I'm hoping for some help is solving this problem. An excellent discussion of the installation of WebMO is www/webmo.net
-------- Forwarded Message -------- Subject: Re: Problem Installing WebMO.23.0.17 Date: Thu, 21 Dec 2023 12:36:54 -0500 From: Stephen P. Molnar <s.mol...@sbcglobal.net> To: JR Schmidt <schm...@webmo.net> CC: William Polik <polikwe...@gmail.com> JR Thanks for the quick response. (base) comp@AbNormal:~$ sudo apt-get install apache2 apache2-suexec-custom libcgi-pm-perl [sudo] password for comp: Reading package lists... Done Building dependency tree... Done Reading state information... Done apache2 is already the newest version (2.4.57-2). apache2-suexec-custom is already the newest version (2.4.57-2). libcgi-pm-perl is already the newest version (4.55-1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. To address the question if Apache is running: (base) comp@AbNormal:~$ sudo service apache2 stop (base) comp@AbNormal:~$ sudo service apache2 start Job for apache2.service failed because the control process exited with error code. See "systemctl status apache2.service" and "journalctl -xeu apache2.service" for details. (base) comp@AbNormal:~$ sudo systemctl status apache2.service × apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Thu 2023-12-21 12:34:04 EST; 14s ago Docs: https://httpd.apache.org/docs/2.4/ Process: 35373 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE) CPU: 18ms Dec 21 12:34:04 AbNormal systemd[1]: Starting apache2.service - The Apache HTTP Server... Dec 21 12:34:04 AbNormal apachectl[35379]: (2)No such file or directory: AH02291: Cannot access directory '/var/log/apache2/' for main error log Dec 21 12:34:04 AbNormal apachectl[35379]: (2)No such file or directory: AH02291: Cannot access directory '/var/log/apache2/' for error log of vhost d> Dec 21 12:34:04 AbNormal apachectl[35379]: AH00014: Configuration check failed Dec 21 12:34:04 AbNormal apachectl[35373]: Action 'start' failed. Dec 21 12:34:04 AbNormal apachectl[35373]: The Apache error log may have more information. Dec 21 12:34:04 AbNormal systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE Dec 21 12:34:04 AbNormal systemd[1]: apache2.service: Failed with result 'exit-code'. Dec 21 12:34:04 AbNormal systemd[1]: Failed to start apache2.service - The Apache HTTP Server. (base) comp@AbNormal:~$ sudo journalctl -xeu apache2.service Dec 21 12:34:04 AbNormal apachectl[35373]: Action 'start' failed. Dec 21 12:34:04 AbNormal apachectl[35373]: The Apache error log may have more information. Dec 21 12:34:04 AbNormal 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. Dec 21 12:34:04 AbNormal 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'. Dec 21 12:34:04 AbNormal 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 4943 and the job result is failed. On 12/21/2023 11:05 AM, JR Schmidt wrote:
I probably cannot be of much help, since it doesn't look like Apache is even started: Dec 21 06:42:27 AbNormal apachectl[4457]: (2)No such file or directory: AH02291: Cannot access directory '/var/log/apache2/' for main error log Dec 21 06:42:27 AbNormal apachectl[4457]: (2)No such file or directory: AH02291: Cannot access directory '/var/log/apache2/' for error log of vhost defined at /etc/apache2/sites-enabled/000-default.conf:1 It appears that Apache was not installed correctly, since the log directory doesn't even exist. I wouldn't be surprised if there were more fundamental issues as well. You can try removing/reinstalling APACHE itself. If you cannot connect to Apache (just http:// abnormal.att.net) then Apache isn't even running. Although I double Apache has started, even if it HAS, it it likely not using SSL. Thus the right URL would be: http://abnormal.att.net/~comp/cgi-bin/webmo/login.cgi -----Original Message----- From: Stephen P. Molnar <s.mol...@sbcglobal.net> Sent: Thursday, December 21, 2023 6:20 AM To: supp...@webmo.net Subject: Problem Installing WebMO.23.0.17 Due to an increasing number of show stopping questions, I have reinstalled Debian 12 on my main Linux platform. Once again, the same reoccurring problem: https://abnormal.att.net/~comp/cgi-bin/webmo/login.cgi generates the dreaded 'Unable to connect'. No errors were generated during the installation problem. Both diagnose.html and the installation.log are attached. The userdir.conf file was edited: UserDir public_html UserDir disabled root <Directory /home/*/public_html> AllowOverride FileInfo AuthConfig Limit Indexes Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec Require method GET POST OPTIONS </Directory> <Directory /home/*/public_html/cgi-bin> Options +ExecCGI AddHandler cgi-script .cgi </Directory> Finally, I checked the installation of Apache2 and found a problem, please see the attached Apache2Status.log. At this point, I acknowledge that a little bit of knowledge is (in my case, a very great) dangerous thing. I am sure that, if I were to bumble my way towards a solution I, would completely destroy the platform. I would very much appreciate a solution. Thanks in advance. -- Stephen P. Molnar, Ph.D. https://insilicochemistry.net (614)312-7528 (c) Skype: smolnar1
-- Stephen P. Molnar, Ph.D. https://insilicochemistry.net (614)312-7528 (c) Skype: smolnar1
