Bug#609886: libapache2-mod-jk: After upgrade from 1.2.26 to 1.2.30 mod_jk no longer connects to tomcats
On Wed, Feb 9, 2011 at 10:57 PM, Miguel Landaeta mig...@miguel.cc wrote: I will disable that flag until upstream sort this out and I'll prepare a fix for this right away. I guess this should be included in Squeeze 6.0.1 since it's a true RC bug. Just to clarify, there is nothing wrong with the SOCK_CLOEXEC flag which is supported only in recent kernels. This bug only appears if the package is built using a Linux kernel = 2.6.27 but the JK module is deployed on a server running a Linux kernel 2.6.27. -- Miguel Landaeta, miguel at miguel.cc secure email with PGP 0x7D8967E9 available at http://keyserver.pgp.com/ Faith means not wanting to know what is true. -- Nietzsche -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609886: libapache2-mod-jk: After upgrade from 1.2.26 to 1.2.30 mod_jk no longer connects to tomcats
severity 609886 normal thanks On Mon, Jan 17, 2011 at 12:26:15AM +0100, eyck wrote: This was detected on soon-to-become-production server, and then reproduced by using clean template, performing upgrade of libapache2_mod_jk, and then downgrade fixes the problem. Both machines came from the same template, I need some time to verify whether the problem is related to the template or not. In a clean lenny chroot I installed apache2, tomcat5.5, tomcat5.5-webapps, and libapache2-mod-jk. After that The problem was detected with tomcat6, but I tried connecting to tomcat5.5 running on another machine, and this confusing 'failed opening socket' Hi Dariusz, I'm convinced this is not a bug. I explain: I was able to reproduce this issue installing apache2, tomcat6 and libapache2-mod-jk but I noticed that tomcat6 by default doesn't listen on port 8009 so libapache2-mod-jk fails to connect with tomcat6. After I enabled that port on tomcat6 configuration (server.xml) libapache2-mod-jk was able to connect with tomcat6 and the upgrade from 1.2.26 to 1.2.30 happened without any issue. I'm downgrading the severity of this bug and I'll close it after you confirm this issue is solved. Cheers, -- Miguel Landaeta, miguel at miguel.cc secure email with PGP 0x7D8967E9 available at http://keyserver.pgp.com/ Faith means not wanting to know what is true. -- Nietzsche -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#609886: libapache2-mod-jk: After upgrade from 1.2.26 to 1.2.30 mod_jk no longer connects to tomcats
Processing commands for cont...@bugs.debian.org: severity 609886 normal Bug #609886 [libapache2-mod-jk] libapache2-mod-jk: After upgrade from 1.2.26 to 1.2.30 mod_jk no longer connects to tomcats Severity set to 'normal' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 609886: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609886 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609886: libapache2-mod-jk: After upgrade from 1.2.26 to 1.2.30 mod_jk no longer connects to tomcats
From mod_jk.log: [Thu Jan 13 15:05:34 2011] [441:140327941527312] [error] jk_open_socket::jk_connect.c (444): socket() failed (errno=22) [Thu Jan 13 15:05:34 2011] [441:140327941527312] [info] ajp_connect_to_endpoint::jk_ajp_common.c (959): Failed opening socket to (172.17.231.57:8009) (errno=22) [Thu Jan 13 15:05:34 2011] [441:140327941527312] [error] ajp_send_request::jk_ajp_common.c (1585): (ajp13) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=22) [Thu Jan 13 15:05:34 2011] [441:140327941527312] [info] ajp_service::jk_ajp_common.c (2540): (ajp13) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1) [Thu Jan 13 15:05:34 2011] [441:140327941527312] [error] ajp_service::jk_ajp_common.c (2559): (ajp13) connecting to tomcat failed. although logs suggest that port 8009 is unreachable, one can connect to it using telnet, or by replacing libapache2_mod_jk with version 1.2.26 I tried to reproduce this error and I couldn't. This was detected on soon-to-become-production server, and then reproduced by using clean template, performing upgrade of libapache2_mod_jk, and then downgrade fixes the problem. Both machines came from the same template, I need some time to verify whether the problem is related to the template or not. In a clean lenny chroot I installed apache2, tomcat5.5, tomcat5.5-webapps, and libapache2-mod-jk. After that The problem was detected with tomcat6, but I tried connecting to tomcat5.5 running on another machine, and this confusing 'failed opening socket' Note: my workstation is an amd64. Same platform - opteron running 64bit kernel. best regards, Dariusz Pietrzak -- Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 75CC 50D9 Total Existance Failure -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#609886: libapache2-mod-jk: After upgrade from 1.2.26 to 1.2.30 mod_jk no longer connects to tomcats
Processing commands for cont...@bugs.debian.org: tags 609886 + moreinfo Bug #609886 [libapache2-mod-jk] libapache2-mod-jk: After upgrade from 1.2.26 to 1.2.30 mod_jk no longer connects to tomcats Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 609886: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609886 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609886: libapache2-mod-jk: After upgrade from 1.2.26 to 1.2.30 mod_jk no longer connects to tomcats
tags 609886 + moreinfo thanks On Thu, Jan 13, 2011 at 03:49:12PM +0100, eyck wrote: Package: libapache2-mod-jk Version: 1.2.30 Severity: grave Justification: renders package unusable From mod_jk.log: [Thu Jan 13 15:05:34 2011] [441:140327941527312] [error] jk_open_socket::jk_connect.c (444): socket() failed (errno=22) [Thu Jan 13 15:05:34 2011] [441:140327941527312] [info] ajp_connect_to_endpoint::jk_ajp_common.c (959): Failed opening socket to (172.17.231.57:8009) (errno=22) [Thu Jan 13 15:05:34 2011] [441:140327941527312] [error] ajp_send_request::jk_ajp_common.c (1585): (ajp13) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=22) [Thu Jan 13 15:05:34 2011] [441:140327941527312] [info] ajp_service::jk_ajp_common.c (2540): (ajp13) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1) [Thu Jan 13 15:05:34 2011] [441:140327941527312] [error] ajp_service::jk_ajp_common.c (2559): (ajp13) connecting to tomcat failed. although logs suggest that port 8009 is unreachable, one can connect to it using telnet, or by replacing libapache2_mod_jk with version 1.2.26 I tried to reproduce this error and I couldn't. In a clean lenny chroot I installed apache2, tomcat5.5, tomcat5.5-webapps, and libapache2-mod-jk. After that I setup a trivial test website. I upgraded libapache2-mod-jk to 1.2.30-1 and the website keeps working. There were not errors at mod_jk.log. In another clean lenny chroot configured in the same way and after doing a dist-upgrade to squeeze (and also upgrading libapache2-mod-jk to 1.2.30-1), the website keeps working. There were not errors at mod_jk.log. Note: my workstation is an amd64. Cheers, -- Miguel Landaeta, miguel at miguel.cc secure email with PGP 0x7D8967E9 available at http://keyserver.pgp.com/ Faith means not wanting to know what is true. -- Nietzsche -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609886: libapache2-mod-jk: After upgrade from 1.2.26 to 1.2.30 mod_jk no longer connects to tomcats
Package: libapache2-mod-jk Version: 1.2.30 Severity: grave Justification: renders package unusable From mod_jk.log: [Thu Jan 13 15:05:34 2011] [441:140327941527312] [error] jk_open_socket::jk_connect.c (444): socket() failed (errno=22) [Thu Jan 13 15:05:34 2011] [441:140327941527312] [info] ajp_connect_to_endpoint::jk_ajp_common.c (959): Failed opening socket to (172.17.231.57:8009) (errno=22) [Thu Jan 13 15:05:34 2011] [441:140327941527312] [error] ajp_send_request::jk_ajp_common.c (1585): (ajp13) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=22) [Thu Jan 13 15:05:34 2011] [441:140327941527312] [info] ajp_service::jk_ajp_common.c (2540): (ajp13) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1) [Thu Jan 13 15:05:34 2011] [441:140327941527312] [error] ajp_service::jk_ajp_common.c (2559): (ajp13) connecting to tomcat failed. although logs suggest that port 8009 is unreachable, one can connect to it using telnet, or by replacing libapache2_mod_jk with version 1.2.26 -- System Information: Debian Release: 5.0.7 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-openvz-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=pl_PL (charmap=ISO-8859-2) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
