On Wed, Feb 9, 2011 at 10:57 PM, Miguel Landaeta 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
severity 609886 grave
tags 609886 - unreproducible - moreinfo + confirmed
thanks
Hello,
I really have to apologize, this is indeed a RC bug. I explain why:
Linux kernels older than 2.6.27 didn't support SOCK_CLOEXEC flag
with socket(2) syscall. The kernels supported in Lenny are under this
categ
Hi,
I did the same test as Nelson above, but I built on my laptop which
runs kubuntu 10.10, obviously not Debian.. The packages I built didn't
work, my server is running Debian though. I did notice the following
build dependency:
apt-file search /usr/bin/apxs2
apache2-prefork-dev: /usr/bin/apxs2
Hi,
I was also just testing it, all combinations I tried didn't work with
the built package you provided. Miguel do you want access into my
server, just so you can verify ? I should also note my server is a xen
domu, but that should make absolutely no difference.
I will also try compiling it / b
On Fri, Feb 4, 2011 at 7:39 PM, Miguel Landaeta wrote:
> I prepared a new package for 1.2.31.
> Would you please test it?
Your binary package itself did not work, BUT I took your sources and
created a debian package myself, and it works!
I downloaded the files:
libapache-mod-jk_1.2.31-0miguel1.
On Fri, Feb 04, 2011 at 02:48:09PM -0200, Nelson Lago wrote:
> I have exactly the same issue as the original poster:
Hello Nelson/Vamegh/Dariusz,
I prepared a new package for 1.2.31.
Would you please test it?
http://alioth.debian.org/~nomadium-guest/debian/unstable/libapache2-mod-jk_1.2.31-0migu
Hi,
I have exactly the same issue as the original poster:
1. Debian 6.0/amd64 running as a guest under OpenVZ
2. Host kernel: 2.6.26-2-openvz-amd64 (the host is debian lenny)
3. The connector is enabled in tomcat
4. Downgrading from 1:1.2.30-1 to 1:1.2.26-2+lenny1 solves the problem
5. Substituti
Processing commands for cont...@bugs.debian.org:
> tags 609886 unreproducible
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) unreproducible.
> thanks
Stopping processing here.
Please contact me if you need
tags 609886 unreproducible
thanks
On Fri, Jan 21, 2011 at 05:45:13PM -0430, Miguel Landaeta wrote:
> I'll work on this during the weekend and I'll let you know
> what I find.
I tried again to reproduce this in a KVM virtual machine
but I couldn't.
The only things I can do for this bug report are
-- Forwarded message --
From: Miguel Landaeta
Date: Fri, Jan 21, 2011 at 10:54 AM
Subject: Re: Bug#609886: libapache2-mod-jk: After upgrade from 1.2.26
to 1.2.30 mod_jk no longer connects to tomcats
To: Vamegh Hedayati
Thanks Vamegh,
I'll work on this during the weeken
-- Forwarded message --
From: Vamegh Hedayati
Date: Fri, Jan 21, 2011 at 8:03 AM
Subject: Re: Bug#609886: libapache2-mod-jk: After upgrade from 1.2.26
to 1.2.30 mod_jk no longer connects to tomcats
To: Miguel Landaeta
Hi Miguel,
I guess the best way I can replicate this is to
-- Forwarded message --
From: Vamegh Hedayati
Date: Thu, Jan 20, 2011 at 6:33 PM
Subject: Re: Bug#609886: libapache2-mod-jk: After upgrade from 1.2.26
to 1.2.30 mod_jk no longer connects to tomcats
To: Miguel Landaeta
Hi Miguel,
This I think is a definite bug, sorry I replied
On Mon, Jan 17, 2011 at 6:00 PM, Damien Raude-Morvan
wrote:
> I don't think it's properly documented in tomcat6 and/or libapache2-mod-jk
> Debian packages. Maybe you could add a note inside README.Debian (although
> it's not really specific to Debian).
Sure. Good idea.
I'll add that to my to-do l
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
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
> > >>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
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_co
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
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
19 matches
Mail list logo
