Re: Spurious "Internal Server Errors" accessing "jkmanager" after upgrading Apache, "mod_jk" and OpenSSL

2017-01-10 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Martin, On 1/9/17 9:01 AM, Martin Knoblauch wrote: > Hi everyone, > > just in case the "final" solution is of interest: the problem was > as usual in the configuration. We did not set the following > directive for the LDAP connection pool: > > LDA

Re: Spurious "Internal Server Errors" accessing "jkmanager" after upgrading Apache, "mod_jk" and OpenSSL

2017-01-09 Thread Martin Knoblauch
Hi everyone, just in case the "final" solution is of interest: the problem was as usual in the configuration. We did not set the following directive for the LDAP connection pool: LDAPConnectionPoolTTL #seconds If the directive is missing, a value of "-1" is implied, meaning "keep connections op

Re: Spurious "Internal Server Errors" accessing "jkmanager" after upgrading Apache, "mod_jk" and OpenSSL

2016-12-29 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Martin, On 12/29/16 3:47 AM, Martin Knoblauch wrote: > that is an interesting pointer. We are of course securing the > "jkmanager" app. And guess what we are using: LDAP. The funky thing > is that it is working most of the time. It fails just after

Re: Spurious "Internal Server Errors" accessing "jkmanager" after upgrading Apache, "mod_jk" and OpenSSL

2016-12-29 Thread tomcat
On 29.12.2016 16:26, Martin Knoblauch wrote: " [Thu Dec 29 15:55:31.129230 2016] [authnz_ldap:info] [pid 24939:tid 139865530685184] [client #:52181] AH01695: auth_ldap authenticate: user authentication failed; URI /jkmanager [ldap_search_ext_s() for user failed][Administrative lim

Re: Spurious "Internal Server Errors" accessing "jkmanager" after upgrading Apache, "mod_jk" and OpenSSL

2016-12-29 Thread Martin Knoblauch
Hi, after some more playing, I will take this of the Tomcat users list. I was able to reproduce the same problem with the previous setup: Server Version:Apache/2.4.18 (Unix) OpenSSL/1.0.2g mod_jk/1.2.41 It seems to take a bit longer to reproduce, but it happens with the same traces in the l

Re: Spurious "Internal Server Errors" accessing "jkmanager" after upgrading Apache, "mod_jk" and OpenSSL

2016-12-29 Thread Martin Knoblauch
Hi Andre, yup - I know that. My httpd is now running with LogLevel notice ldap:debug authz_core:debug authnz_ldap:debug And LDAPLibraryDebug 7 Will see what comes out. Thanks Martin On Thu, Dec 29, 2016 at 12:36 PM, André Warnier (tomcat) wrote: > On 29.12.2016 10:46, Martin Knoblauch wro

Re: Spurious "Internal Server Errors" accessing "jkmanager" after upgrading Apache, "mod_jk" and OpenSSL

2016-12-29 Thread tomcat
On 29.12.2016 10:46, Martin Knoblauch wrote: Hi, "mod_jk" is now clearly off the hook. Upping the httpd log level from "warn" to "info" (I was assuming an event leading to a 500 response would be at least "warn" :-( reveals: [Thu Dec 29 10:37:37.300421 2016] [authnz_ldap:info] [pid 20325:tid

Re: Spurious "Internal Server Errors" accessing "jkmanager" after upgrading Apache, "mod_jk" and OpenSSL

2016-12-29 Thread Martin Knoblauch
Hi, "mod_jk" is now clearly off the hook. Upping the httpd log level from "warn" to "info" (I was assuming an event leading to a 500 response would be at least "warn" :-( reveals: [Thu Dec 29 10:37:37.300421 2016] [authnz_ldap:info] [pid 20325:tid 139641195009792] [client xxx.xxx.xxx.xxx:49959]

Re: Spurious "Internal Server Errors" accessing "jkmanager" after upgrading Apache, "mod_jk" and OpenSSL

2016-12-29 Thread tomcat
On 29.12.2016 09:47, Martin Knoblauch wrote: Hi Christopher, that is an interesting pointer. We are of course securing the "jkmanager" app. And guess what we are using: LDAP. The funky thing is that it is working most of the time. It fails just after some time. Refreshing the URL cures it agai

Re: Spurious "Internal Server Errors" accessing "jkmanager" after upgrading Apache, "mod_jk" and OpenSSL

2016-12-29 Thread Martin Knoblauch
Hi Christopher, that is an interesting pointer. We are of course securing the "jkmanager" app. And guess what we are using: LDAP. The funky thing is that it is working most of the time. It fails just after some time. Refreshing the URL cures it again - for some time. What did you do to fix your p

Re: Spurious "Internal Server Errors" accessing "jkmanager" after upgrading Apache, "mod_jk" and OpenSSL

2016-12-29 Thread Martin Knoblauch
Hi Andre, upping the level to "debug" did not reveal much more about the effect. But you are right of course. Thanks Martin On Wed, Dec 28, 2016 at 5:02 PM, André Warnier (tomcat) wrote: > On 28.12.2016 16:38, Martin Knoblauch wrote: > >> Hi, >> >> today we updated our Devel/Integration env

Re: Spurious "Internal Server Errors" accessing "jkmanager" after upgrading Apache, "mod_jk" and OpenSSL

2016-12-28 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Martin, On 12/28/16 10:38 AM, Martin Knoblauch wrote: > Hi, > > today we updated our Devel/Integration environments from > > HTTPD 2.4.18/mod_jk 1.2.41/OpenSSL-1.0.2h > > to > > HTTPD 2.4.23/mod_jk 1.2.42/OpenSSL-1.0.2j > > > Since then we obs

Re: Spurious "Internal Server Errors" accessing "jkmanager" after upgrading Apache, "mod_jk" and OpenSSL

2016-12-28 Thread tomcat
On 28.12.2016 16:38, Martin Knoblauch wrote: Hi, today we updated our Devel/Integration environments from HTTPD 2.4.18/mod_jk 1.2.41/OpenSSL-1.0.2h to HTTPD 2.4.23/mod_jk 1.2.42/OpenSSL-1.0.2j Since then we observe on both systems spurious "500" messages when accessing the "jkmanager" pag

Spurious "Internal Server Errors" accessing "jkmanager" after upgrading Apache, "mod_jk" and OpenSSL

2016-12-28 Thread Martin Knoblauch
Hi, today we updated our Devel/Integration environments from HTTPD 2.4.18/mod_jk 1.2.41/OpenSSL-1.0.2h to HTTPD 2.4.23/mod_jk 1.2.42/OpenSSL-1.0.2j Since then we observe on both systems spurious "500" messages when accessing the "jkmanager" page. Unfortunately there isn't much info besides t