-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Rainer,
On 1/13/15 4:56 PM, Rainer Jung wrote: > Am 13.01.2015 um 18:59 schrieb Christopher Schultz: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 >> >> All, >> >> On 1/10/15 2:56 PM, Christopher Schultz wrote: >>> I'm having a problem with mod_jk 1.2.40 under Apache 2.4.10. >>> After a successful start up, accessing the mod_jk status page >>> gives me a 500 error with no errors on the screen or in the >>> logs. >> >> Solved. >> >> The problem turned out to be authnz_ldap, which does not produce >> any errors when it can't reach the LDAP server. A bad iptables >> rule prevented this web server from reaching our LDAP server, and >> the behavior was "500 server error" with no messages in any log >> files for any resource protected by the module. >> >> I spent a great deal of time trying to figure out how this web >> server was configured differently than any of the others, which >> were of course still working just fine. Since the problem was >> with an external server (the LDAP server), it took quite a long >> time to track down, as the web servers were in fact configured >> identically :) > > Thanks for letting us know! It's frustrating that there are no errors or warnings logged about such things. You'd think "can't contact authentication server" would be a big deal... > Hopefully the status worker activation update problem in the other > thread will be fixed by a valid shm path. Otherwise analysis will > get nasty ... Yes, that fixed it all up. I'm polishing-up the code to post to the wiki, like I did with check_jmx_proxy.pl in the past. Then, people can take a look at it and give me feedback if they'd like. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJUt+KBAAoJEBzwKT+lPKRYTAAQAL7E87qx5A1Hzwpc4lsJ79Pp odv6L7O1HJzWEbBrAHbozJeOHifGsr+gc5zX5y2OBRyr6EdH69b0vNmp1bvn3jo0 h//VpUfSA77CMctsLa5Q3mS0AFKCEI513mLnwS00DRWcb6RnLHt7smJS+TJ/t1BH HHKjZGWn7uks0zkgUvgygLH7cpD0v9dYqqRDSDuxYu51UfSKVD+YfuyQg2H5atvm X0xyMF9XlcdHGzQvDbSoELxwcXzvYmVY1dEWuPCHx5Y6MR9cdjnyW9fjU5n71GpG uWzE6j+vOaRZsyImgzTgnin1B7EUJeW6caCbXPWxI7qzfAcqJ/xFgLAmMsEDBozC x9oR0FyCMxYPvtpxgQjcNJ1C/ecWK5YYToO6yLQ/ArW4Hz4DsOzNSs0lldefwsNH D0G/qdbussBBUKKXHk94mlCEnMlh2lWWDoVkh6Dsf7fqTFOc1pZ6DHTJ0Qb50otJ wXiAzThwbXnPGE+8B6R6QNcjl8fd++Cw1ORy0QqOHiaQfqo71AkEP7ewWZsHTLB2 PX0GNyoi7pmK6ht2Ufq/YaTgLaQvf+rP5vg5IBbY/4RYnESBH6faU7bFiy+Nyk+4 r1R/FF1FTsq6DtLAHWF17ru1DfADWBxWBbIk9EdJPUE0Y4E5pezPEy/Cq8zOKunf YiwcjIautCtsS95QaCOI =wFFN -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
