Here's what we figured out the issue was, after MUCH research... I'm providing it into the mailing list in case others have issues with Apache and Tomcat connection getting the error:
Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong port. worker=p2 failed errno = 13 As it turns out errno=13 is a permissions error. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=161049 was found to be the issue. This could have been induced by an update that was put into effect when the server lost power and rebooted. To resolve, I disabled selinux. Details below: Modified /etc/selinix/config to: SELINUX=permissive From SELINUX=enforced Executed "/usr/sbin/setenforce" 0 to put this into effect immediately. It will persist across reboots. Thanks for the responses... Kim :-) On 10/27/06, Caldarale, Charles R <[EMAIL PROTECTED]> wrote:
> From: Kim Albee [mailto:[EMAIL PROTECTED] ] > Subject: Re: Question with the Apache/Tomcat interface... > > > Can you connect to the ip and port specified with p2 from your apache > > machine with telnet? > > e have telnet disabled on the server, as it is not > secure. That's not what he was asking. Can a telnet client on some other machine connect to the IP address and port your've specified? This doesn't require a telnet server on the target system, it just verifies that something is listening for connection requests on that IP/port combination. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
