For those, you'll have to ask your distro community. You can start httpd with `apachectl start` in a normal environment.
On Sun, May 21, 2023 at 12:56 PM John Iliffe <john.ili...@iliffe.ca> wrote: > Hi Frank: > > I finally got Apache to start but it seems to be running in the > foreground. Not > sure why but the default httpd.service file results in: > > root 110531 110286 0 12:42 pts/0 00:00:00 systemctl start httpd > root 110533 1 0 12:42 ? 00:00:00 /usr/sbin/httpd > -DFOREGROUND > apache 110535 110533 0 12:42 ? 00:00:00 /usr/sbin/httpd > -DFOREGROUND > apache 110536 110533 0 12:42 ? 00:00:00 /usr/sbin/httpd > -DFOREGROUND > apache 110537 110533 0 12:42 ? 00:00:00 /usr/sbin/httpd > -DFOREGROUND > John 110768 110738 0 12:43 pts/1 00:00:00 grep --color=auto httpd > > I could diddle the service file I suppose to fix that, but what would they > likely by trying to accomplish with this command line on a service? Apache > seems to be active to the extent that I can connect to the default named > virtual > host. Eventually everything fails with the (Linux) error message: > > [root@prod02 conf]# systemctl status httpd > × httpd.service - The Apache HTTP Server > Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled; > vendor > preset: disabled) > Drop-In: /usr/lib/systemd/system/httpd.service.d > └─php-fpm.conf > Active: failed (Result: timeout) since Sun 2023-05-21 12:52:02 EDT; > 2min > 12s ago > Docs: man:httpd.service(8) > Process: 110818 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND > (code=exited, status=0/SUCCESS) > Main PID: 110818 (code=exited, status=0/SUCCESS) > CPU: 75ms > > May 21 12:50:31 prod02 systemd[1]: Starting The Apache HTTP Server... > May 21 12:52:01 prod02 systemd[1]: httpd.service: start operation timed > out. > Terminating. > May 21 12:52:02 prod02 systemd[1]: httpd.service: Failed with result > 'timeout'. > May 21 12:52:02 prod02 systemd[1]: Failed to start The Apache HTTP Server. > > > Regards, > > John > ====== > On Sat, 2023-05-20 at 18:46 -0400, Frank Gingras wrote: > > What is the new error? > > > > On Sat, May 20, 2023 at 5:24 PM John Iliffe <john.ili...@iliffe.ca> > wrote: > > > Thanks Frank. > > > > > > Hasn't started yet but at least the problem has moved to another line > :-) > > > > > > Regards, > > > > > > John > > > ====== > > > On Sat, 2023-05-20 at 14:48 -0400, Frank Gingras wrote: > > > > You need a mpm to start httpd. I recommend using the event mpm, so > just > > > > load > > > > the appropriate module. > > > > > > > > On Sat, May 20, 2023 at 2:27 PM John Iliffe <john.ili...@iliffe.ca> > wrote: > > > > > Rocky Linux 9.0, new install > > > > > Rocky distro version of Apache/httpd > > > > > > > > > > As recommended I used the distro's download httpd and that has > lead me > > > > > into > > > > > a > > > > > week's worth of chasing phantoms. > > > > > > > > > > Specifically, I copied the httpd.conf file from the old server > > > > > (Apache.2.4.25) > > > > > to the new server and after clearing all the path problems (Apache > is > > > > > spread > > > > > all > > > > > over the file tree instead of in one compact area under > /usr/apache... > > > > > as > > > > > previously) I still can't get httpd to start. The error I can't > seem to > > > > > resolve > > > > > is: > > > > > > > > > > AH00534: httpd: Configuration error: No MPM loaded. > > > > > May 20 13:42:22 prod02 systemd[1]: httpd.service: Main process > exited, > > > > > code=exited, status=1/FAILURE > > > > > May 20 13:42:22 prod02 systemd[1]: httpd.service: Failed with > result > > > > > 'exit- > > > > > code'. > > > > > May 20 13:42:22 prod02 systemd[1]: Failed to start The Apache HTTP > > > > > Server. > > > > > > > > > > As I understand it I shouldn't need an MPM running because > everything is > > > > > proxy'd > > > > > to php-fpm (which IS running and has created all necessary pools) > using > > > > > config > > > > > lines like: > > > > > "^/.*\.php(/.*)?$" fcgi://127.0.0.1:90xx/httpd/xxxx > > > > > one 'xxxx' for each virtual host. There are sockets 9002 - 9011 > in use, > > > > > excluding 9010 that originally refused to bind to php-fpm and I'll > try > > > > > to > > > > > debug > > > > > later. Also I have been informed that I should now be using Unix > Domain > > > > > sockets > > > > > and I will resolve that whenever I can get Apache running stably. > > > > > > > > > > The config file DOES load mod_proxy_fcgi so as I understand it this > > > > > should > > > > > work > > > > > properly: > > > > > 140:LoadModule proxy_module modules/mod_proxy.so > > > > > 141:LoadModule proxy_connect_module modules/mod_proxy_connect.so > > > > > 143:LoadModule proxy_http_module modules/mod_proxy_http.so > > > > > 144:LoadModule proxy_fcgi_module modules/mod_proxy_fcgi.so > > > > > > > > > > Apache's error log has nothing. Previously, the "It Works!" > version > > > > > provided by > > > > > the distro did log startup messages properly here. > > > > > > > > > > Has anyone any ideas where to look? Without Apache running it is > fairly > > > > > hard to > > > > > debug it as I can't ask it what it thinks it is doing! > > > > > > > > > > Help appreciated, > > > > > > > > > > John > > > > > ====== > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > > > > > For additional commands, e-mail: users-h...@httpd.apache.org > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > > > For additional commands, e-mail: users-h...@httpd.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > >
