Hi Frank: Looks like I have path problems because I am now getting the error: [Sun May 21 12:21:45.613390 2023] [mime:error] [pid 110214:tid 110214] (2)No such file or directory: AH01597: could not open mime types config file /etc/httpd/conf/mime.types. The problem here, and in retrospect I should have recreated the config file, is that the old server had everything under /usr/apache-2.4.25/ so it was easy to find everything related to Apache. As I mentioned in a previous post, Rocky has everything spread around the directory tree so I have to first find it is missing and then do a search. Since server maintenance really isn't my job, or core skill, I am having to do it in such "spare time" as I have. That's why getting a reply to your very prompt answers sometimes is a bit slow for which I apologize. I also have Selinux giving me the gears periodically. Doesn't help that I have two httpd/config directories, /etc/httpd/conf/ and /etc/httpd/conf.d/ and I'm not certain which one is being used so I'm keeping them both identical. Thanks for your patience. 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.iliffe@xxxxxxxxx> 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.iliffe@xxxxxxxxx> 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-unsubscribe@xxxxxxxxxxxxxxxx > > > > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|