Andre - good information. Thanks but still in the weeds here.
> Depends how long Tomcat and your applications need to start up and be ready > to answer requests. makes sense. since httpd is NOT coming up on boot as it should, I will make it second with a preceding sleep and background the whole thing - maybe that will fix it: (sleep 10; S96httpd start) & THAT WORKS fine. httpd is now up correctly after a boot. YEA! Not surprising that it worked while being wrong, because these parameters are obsolete and just ignored. :=[ (thanks) >You don't seem to be using load balancing workers, so basically you don't care. >But the error message may indicate that Apache httpd is not able to write that >file, in that location. >Does that directory even exist ? (logfiles usually go to somewhere like >/var/log/*. /etc/hhtpd/logs is somewhat unusual.) Thanks again. It turns out that /etc/httpd/logs is a symbolic link to /var/httpd/log (feel better?). However as I did mention later in the original mail message- two files are created and are of size 0. So it can write, but is not happy. Without the new line about the shared memory in httpd.conf - httpd complained even more that it did not like it but would default. Will correct the line to point directly and not use the link. (no effect, but makes better sense to me) ls -l /var/log/httpd ... -rw-r--r--. 1 root root 0 Mar 23 09:27 jk-runtime-status.3686 -rw-r--r--. 1 root root 0 Mar 23 09:27 jk-runtime-status.3690 ... I did pull the mod_jk.so release suggested 1.2.32. It also needed to be stripped after the install. But it did not help - see below. THIS IS THE CRUX OF THE PROBLEM - STILL! >> [info] ajp_connect_to_endpoint::jk_ajp_common.c (992): Failed opening socket >> to (127.0.0.1:8009) (errno=13) >> [error] ajp_send_request::jk_ajp_common.c (1621): (wrkr) connecting to >> backend failed. Tomcat is probably not started or is listening on the wrong >> port (errno=13) >> [info] ajp_service::jk_ajp_common.c (2614): (wrkr) sending request to tomcat >> failed (recoverable), because of error during request sending (attempt=1) >> [info] jk_open_socket::jk_connect.c (627): connect to 127.0.0.1:8009 failed >> (errno=13) >That's probably because you start httpd before tomcat, as explained earlier. >Tomcat has not opened its AJP socket 8009 yet, so httpd+mod_jk cannot connect >to it. You could be right, but a) these MESSAGES do not happen until both tomcat and httpd are up and I try to get to the application in a browser b) under prior releases of fedora (14, 12, 8) I was able to start httpd hugely later and it worked - no complaints (sometimes it came up by itself, sometimes not - I like this rc.local way better) NOPE, in this case you did not hit the ball out of the park. I remain stuck with httpd thinking tomcat is NOT talking. Since I have done almost nothing to configure tomcat as you noticed with ssl, I am baffled. But thanks, you did solve one or two issues and explained a couple more.
