Re: [Resin-interest] mod_caucho failure on CentOS 5.2/Apache 2.2
OK, there is a solution. It was not APR which was high on our suspect list. Mea culpa. The test servers built to evaluate upgrading from 3.1.3 to 3.1.8 were built on CentOS 5 with SELinux enabled. There, I've said it. Self inflicted. We don't use SELinux, not sure how it was missed on the test servers, but not its obvious it should have made the troubleshooting list. During the build so much focus was poured into C, Apache, and potential effects of breaking the mod_caucho build we never went further. Once I switched my focus to implementing without mod_caucho I focussed on Apache logs rather than stack traces and debug. Error logs during mod_caucho testing were along these lines: mod_caucho.c:934:caucho_request(): no connection: cluster(0x89a0350) But with only Apache and reverse proxy to deal with, this output provided a huge lead: [error] proxy: HTTP: disabled connection for (192.168.1.2) [error] (13)Permission denied: proxy: HTTP: attempt to connect to localhost:8080 (192.168.1.2) failed [error] ap_proxy_connect_backend disabling worker for (192.168.1.2) That led me to SELinux, and the rest of the tale quickly revealed itself. It has led me to evaluate using mod_proxy, and potentially resin.xml for rewrites which will loosen the tying of our various apps to the one instance of Apache. So its not all bad news. David ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] mod_caucho failure on CentOS 5.2/Apache 2.2
Interesting. FWIW, I am using Resin for about 10 web-apps on a single machine, where each web-app has different criteria for logging, virtual hosts, rewriting etc. I know a couple of the posters pointed out that that was a good reason to use Apache as a front-end, but I haven't found it necessary at all. I used to be a big Apache fan about 5 years ago, but since I have decoupled Apache from Resin and went exclusively with Resin I have had no regrets. In fact I am much happier with the more simple configuration. Aaron -Original Message- From: resin-interest-boun...@caucho.com [mailto:resin-interest-boun...@caucho.com] On Behalf Of david day Sent: Friday, March 13, 2009 11:18 AM To: General Discussion for the Resin application server Subject: Re: [Resin-interest] mod_caucho failure on CentOS 5.2/Apache 2.2 OK, there is a solution. It was not APR which was high on our suspect list. Mea culpa. The test servers built to evaluate upgrading from 3.1.3 to 3.1.8 were built on CentOS 5 with SELinux enabled. There, I've said it. Self inflicted. We don't use SELinux, not sure how it was missed on the test servers, but not its obvious it should have made the troubleshooting list. During the build so much focus was poured into C, Apache, and potential effects of breaking the mod_caucho build we never went further. Once I switched my focus to implementing without mod_caucho I focussed on Apache logs rather than stack traces and debug. Error logs during mod_caucho testing were along these lines: mod_caucho.c:934:caucho_request(): no connection: cluster(0x89a0350) But with only Apache and reverse proxy to deal with, this output provided a huge lead: [error] proxy: HTTP: disabled connection for (192.168.1.2) [error] (13)Permission denied: proxy: HTTP: attempt to connect to localhost:8080 (192.168.1.2) failed [error] ap_proxy_connect_backend disabling worker for (192.168.1.2) That led me to SELinux, and the rest of the tale quickly revealed itself. It has led me to evaluate using mod_proxy, and potentially resin.xml for rewrites which will loosen the tying of our various apps to the one instance of Apache. So its not all bad news. David ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.0.237 / Virus Database: 270.11.9/1992 - Release Date: 03/13/09 05:59:00 ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] mod_caucho failure on CentOS 5.2/Apache 2.2
On Fri, Mar 13, 2009 at 1:43 PM, Aaron Freeman wrote: I used to be a big Apache fan about 5 years ago, but since I have decoupled Apache from Resin and went exclusively with Resin I have had no regrets. Good to know. I've done the majority of site management via Apache, so transitioning quickly into Resin is painful. Nice to know the list has participants who have implemented both approaches. David ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] mod_caucho failure on CentOS 5.2/Apache 2.2
On Feb 25, 2009, at 2:52 PM, david day wrote: On Thu, Feb 19, 2009 at 2:00 PM, Scott Ferguson f...@caucho.com wrote: Can you check with the current 3.1.8 snapshot? I downloaded and installed resin-pro-3.1.s090218 but get the same results. What options do I have with debugging mod_caucho? Good. In that case, you're not hitting the alignment bug, because that bug wouldn't try to connect to Resin. What does the /caucho-status show? The message is saying that mod_caucho can't connect to the Resin instance. The /caucho-status should show the IP:port that mod_caucho is trying to use to connect to Resin. -- Scott My current environment is: CentOS release 5.2 (Final) httpd-devel-2.2.3-11.el5_2.centos.4 httpd-2.2.3-11.el5_2.centos.4 mod_ssl-2.2.3-11.el5_2.centos.4 apr-devel-1.2.7-11 apr-1.2.7-11 apr-util-1.2.7-7.el5 apr-util-devel-1.2.7-7.el5 with: ./configure --prefix=/opt/resin-31snap --enable-debug --enable-jni --with-apxs=/usr/sbin/apxs This output now appears in Apache log [02/Feb/2009:16:05:58 -0600] 1707_-1219740784: config.c:1291:cse_update_host(): complete :0(0x9165388) old:0 now:1235599558() [02/Feb/2009:16:05:58 -0600] 1707_-1219740784: config.c:1683:cse_match_request(): entry qa4b.kpiint.com / match:yes [02/Feb/2009:16:05:58 -0600] 1707_-1219740784: mod_caucho.c:1288:cse_dispatch(): [1707] match qa4b.kpiint.com:/ [02/Feb/2009:16:05:58 -0600] 1707_-1219740784: mod_caucho.c:911:caucho_request(): session index: -1 [02/Feb/2009:16:05:58 -0600] 1707_-1219740784: mod_caucho.c:923:caucho_request(): no connection: cluster(0x91653c8) ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] mod_caucho failure on CentOS 5.2/Apache 2.2
On Wed, Feb 25, 2009 at 5:37 PM, Scott Ferguson f...@caucho.com wrote: Good. In that case, you're not hitting the alignment bug, because that bug wouldn't try to connect to Resin. What does the /caucho-status show? Status : Caucho Servlet Engine Start Time Wed Feb 25 16:01:29 2009 Now Wed Feb 25 17:52:18 2009 Session Cookie 'JSESSIONID' Session URL ';jsessionid=' Config Check Interval 15s Config Cache File /tmp/localhost_6800 Configuration Cluster Host Active Pooled Connect Timeout Idle Time Recover Time 1. localhost:6800 (ok) 0 02 1020 Unconfigured Default Virtual Host Source: unconfigured Last-Update: Wed Dec 31 18:00:00 1969 ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] mod_caucho failure on CentOS 5.2/Apache 2.2
I have test against another 32 bit server running 2.6.18-92.1.22.el5.centos.plusPAE with same installed packages as the older 32 bit server running 2.6.18-92.1.22.el5.centos.plus also fails. Another test on a new 64 bit CentOS release 5.2 (Final) build running 2.6.18-92.el5 yields same results. To take RedHat's Apache 2.2.3 out of the mix, source httpd-2.2.11-1/httpd-devel-2.2.11-1 was built/installed with same caucho-status result Unconfigured Default Virtual Host. At this point, a functional mod_caucho cannot be built on any new CentOS server. David ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] mod_caucho failure on CentOS 5.2/Apache 2.2
On Feb 19, 2009, at 11:15 AM, david day wrote: I have test against another 32 bit server running 2.6.18-92.1.22.el5.centos.plusPAE with same installed packages as the older 32 bit server running 2.6.18-92.1.22.el5.centos.plus also fails. Another test on a new 64 bit CentOS release 5.2 (Final) build running 2.6.18-92.el5 yields same results. To take RedHat's Apache 2.2.3 out of the mix, source httpd-2.2.11-1/httpd-devel-2.2.11-1 was built/installed with same caucho-status result Unconfigured Default Virtual Host. Can you check with the current 3.1.8 snapshot? We introduced a compile-time error where one of the CFLAGS (the large file defines), was messing up an internal Apache data structure, causing mod_caucho's configuration to be skipped. The 3.1.8 snapshot reverts those flags to the ones returned by Apache's apr info. If you're still having trouble with the snapshot, then this may be a different issue. -- Scott At this point, a functional mod_caucho cannot be built on any new CentOS server. David ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] mod_caucho failure on CentOS 5.2/Apache 2.2
We recently had problems building resin-pro-3.1.8 for Apache and applied the solution in 0003698 of removing line CFLAGS=$CFLAGS from the configure file. That change allowed a successful build in a test environment. Using this same method on our new production server results in Service Temporarily Unavailable through Apache, but success direct to Resin. I thought this was related to the previous build bug, but I have gone back to 3.1.3 and have the same issue. The new server is CentOS rel 5.2 with httpd/devel 2.2.3-11, libgcc/gcc 4.1.2 and built with: ./configure --prefix=/opt/resin-318pro --enable-jni –with-apxs=/usr/sbin/apxs Caucho-status returns a positive Configuration Cluster but Unconfigured Default Virtual Host. Changing configure arguments, e.g. --with-apache-cflags=-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -pthread --enable-debug –enable-static=no has the same results, as does changing Apache conf between ResinConfigServer and CauchoHost. Apache and Resin confs have been edited from basic post install to fully mimic our production confs. All variations have given the same result. Has anyone else seen this behavior with new builds of CentOS? Can someone suggest a method to isolate the problem to the mod_caucho build or conf file. David ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
