Re: Apache2+jk+tomcat5.028+uri utf-8 [NOT] SOLVED
I'm using Fedora Core 4. I enabled port 8009 on my firewall. Here's the relevant line from iptables -L -- 0 0 ACCEPT tcp -- anyany anywhere anywhere state NEW tcp dpt:8009 -- I used the lokkit utility to add it. Rebooted. Nothing. I had a typo in a config file, but correcting that didn't work. I still get the browser error -- The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. -- They call it a 503 error. And I'm still getting the same error in my mod_jk log file. Quoting Bruno Georges <[EMAIL PROTECTED]>: > Hi > Depending on your configuration and operating system, you may have some > firewall restriction which prevents connecting to the port 8009. > Please check this first, especially if you use XP SP2. > > Best Regards > Bruno Georges > > Glencore International AG > Tel. +41 41 709 3204 > Fax +41 41 709 3000 > > > > Paul George > Constantine To: Tomcat Users List > > <[EMAIL PROTECTED] cc: > d.edu> Subject: Re: > Apache2+jk+tomcat5.028+uri utf-8 SOLVED > > 01.07.05 09:35 Distribute: > Please respond Personal? |---| > to "Tomcat Users | [ ] x | > List"|---| > > > > > > > I've essentially done all of this, but I still get the following error in > the browser: > --- > Internal Server Error > > The server encountered an internal error or misconfiguration and was > unable > to complete your request. > > Please contact the server administrator, [EMAIL PROTECTED] and inform them > of > the time the error occurred, and anything you might have done that may > have > caused the error. > > More information about this error may be available in the server error > log. > --- > > But there was no error in the server error log. In the jk log I get: > --- > [Sun Jun 26 15:55:45 2005] [info] jk_open_socket::jk_connect.c (433): > connect to 127.0.0.1:8009 failed with errno=13 > [Sun Jun 26 15:55:45 2005] [info] > ajp_connect_to_endpoint::jk_ajp_common.c > (880): Failed opening socket to (127.0.0.1:8009) with (errno=13) > [Sun Jun 26 15:55:45 2005] [info] ajp_send_request::jk_ajp_common.c > (1239): > Error connecting to the Tomcat process. > [Sun Jun 26 15:55:45 2005] [info] ajp_service::jk_ajp_common.c (1737): > Sending request to tomcat failed, recoverable operation attempt=1 > [Sun Jun 26 15:55:45 2005] [info] jk_open_socket::jk_connect.c (433): > connect to 127.0.0.1:8009 failed with errno=13 > [Sun Jun 26 15:55:45 2005] [info] > ajp_connect_to_endpoint::jk_ajp_common.c > (880): Failed opening socket to (127.0.0.1:8009) with (errno=13) > [Sun Jun 26 15:55:45 2005] [info] ajp_send_request::jk_ajp_common.c > (1239): > Error connecting to the Tomcat process. > [Sun Jun 26 15:55:45 2005] [info] ajp_service::jk_ajp_common.c (1737): > Sending request to tomcat failed, recoverable operation attempt=2 > [Sun Jun 26 15:55:45 2005] [info] jk_open_socket::jk_connect.c (433): > connect to 127.0.0.1:8009 failed with errno=13 > [Sun Jun 26 15:55:45 2005] [info] > ajp_connect_to_endpoint::jk_ajp_common.c > (880): Failed opening socket to (127.0.0.1:8009) with (errno=13) > [Sun Jun 26 15:55:45 2005] [info] ajp_send_request::jk_ajp_common.c > (1239): > Error connecting to the Tomcat process. > [Sun Jun 26 15:55:45 2005] [info] ajp_service::jk_ajp_common.c (1737): > Sending request to tomcat failed, recoverable operation attempt=3 > [Sun Jun 26 15:55:45 2005] [error] ajp_service::jk_ajp_common.c (1746): > Error connecting to tomcat. Tomcat is probably not started or is > listening > on the wrong port. worker=ajp13w failed > [Sun Jun 26 15:55:45 2005] ajp13w ill-conditioned 0.002938 > > I know that Tomcat is both started and listening on the correct port. I > think it might have to do with permissions (errno=13 is a permission > denied > error), but I don't know what I need to change. > > > > Quoting Luis Sánchez Sánchez <[EMAIL PROTECTED]>: > > > Install mod_jk. I downloaded it from > > > http://www.apache.org/dist/jakarta/tomcat-connectors/jk/binaries/linux/jk-1.2.10 > / > > > > > Copy the jakarta-connector*.so to your apache2 modules directory. > > > > Activate your new module: > > > > I used this two files in /etc/apache/mods-avaliable: > > > > +---+ > > mod_jk.conf > > +---+ > > # Where to find workers.properties > > # Update this path to match your conf directory location (put > > workers.properties next to httpd.conf) > > JkWorkersFile /etc/apache2/workers. > > properties > > > > # Where to put jk logs > > # Update this path to match your logs directory location (put > mod_jk.log > > next to access_log) > > JkLogF
Re: Apache2+jk+tomcat5.028+uri utf-8 [NOT] SOLVED
Paul: I got the same error as you did and I posted my problem the other day but no response at all. Seems not many people have this problem. I have two machines both running fedora 3 and use the same configuration but strangly, one of them have no problem using jk but the other just keep giving same error. The only difference is the hardware but I doubt hardware would cause jk malfunctioning. I attached the post I sent few days back for you reference. Maybe we can discuss more about this later. Regards Steve Here is my post: I have searched every where and I don't find many people having the same problem as me and I have installed JK and jboss on many machines and only this one has problem. Here is the problem description: I installed mod_jk1.2.10 on apache 2 to redirect dynamic contenet to jboss 4. I followed a guide on jboss site and it works well on other machine but this specific machine running fedora 3 just does not work. I have verified that tomcat works well if I add port 8080 to the web address. (for example http://localhost:8080/jspPage works but not http://localhost/jspPage. The directory mapping is defied in uriworkermap.properties) I attached all the configuration files and error log in this post and hope some one can give me some idea. Sorry for the long email ;) and thanks for your help Steve The jk error log message is as follows: [Mon Jun 27 15:58:23 2005][info] jk_open_socket::jk_connect.c (433): connect to 127.0.0.1:8009 failed with errno=13 [Mon Jun 27 15:58:23 2005][info] ajp_connect_to_endpoint::jk_ajp_common.c (877): Failed connecting to tomca t. Tomcat is probably not started or is listening on the wrong host/port (127.0.0.1:8009). Failed errno = 13 [Mon Jun 27 15:58:23 2005][info] ajp_send_request::jk_ajp_common.c (1227): Error connecting to the Tomcat p rocess. [Mon Jun 27 15:58:23 2005][info] ajp_service::jk_ajp_common.c (1724): Sending request to tomcat failed, re coverable operation attempt=3 [Mon Jun 27 15:58:23 2005][error] ajp_service::jk_ajp_common.c (1733): Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong port. worker=node2 failed [Mon Jun 27 15:58:23 2005][info] service::jk_lb_worker.c (627): service failed, worker node2 is in error st ate [Mon Jun 27 15:58:23 2005][info] service::jk_lb_worker.c (677): All tomcat instances are busy or in error s tate [Mon Jun 27 15:58:23 2005]loadbalancer localhost 0.001220 [Mon Jun 27 15:58:23 2005][info] jk_handler::mod_jk.c (1975): Service error=0 for worker=loadbalancer httpd conf file: # Include mod_jk configuration file Include conf/mod-jk.conf mod_jk.conf file # Load mod_jk module # Specify the filename of the mod_jk lib LoadModule jk_module modules/mod_jk.so # Where to find workers.properties JkWorkersFile conf/workers.properties # Where to put jk logs JkLogFile logs/mod_jk.log # Set the jk log level [debug/error/info] JkLogLevel info # Select the log format JkLogStampFormat "[%a %b %d %H:%M:%S %Y]" # JkOptions indicates to send SSK KEY SIZE JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories # JkRequestLogFormat JkRequestLogFormat "%w %V %T" # Mount your applications JkMount /application/* loadbalancer # You can use external file for mount points. # It will be checked for updates each 60 seconds. # The format of the file is: /url=worker # /examples/*=loadbalancer JkMountFile conf/uriworkermap.properties # Add shared memory. # This directive is present with 1.2.10 and # later versions of mod_jk, and is needed for # for load balancing to work properly JkShmFile logs/jk.shm# Add jkstatus for managing runtime data JkMount status Order deny,allow Deny from all Allow from 127.0.0.1 *workers.properties file * # Define list of workers that will be used # for mapping requests worker.list=loadbalancer,status # Define Node1 worker.node1.port=8009 worker.node1.host=localhost worker.node1.type=ajp13 worker.node1.lbfactor=1 #worker.node1.local_worker=1 (1) worker.node1.cachesize=10 # Define Node2 worker.node2.port=8009 worker.node2.host= localhost worker.node2.type=ajp13 worker.node2.lbfactor=1 #worker.node2.local_worker=1 (1) worker.node2.cachesize=10 # Load-ba
Re: Apache2+jk+tomcat5.028+uri utf-8 [NOT] SOLVED
Hello, Sorry for not replying to the thread referenced in my subject (See July 1st, 2005), I'm new to the list and didn't have the email to reply to. I am having the same trouble that Paul and Steve encountered. (Error connecting to tomcat from mod_jk). Like Steve I have two similarly configured machines, one works, one doesn't. I can provide configuration files and more detailed logs but the errors I get are similar. Maybe I can peek someone's interest or jog a memory by proviging more detail. I'm running two identically configured Fedora Core 4 boxes. The one that works is running on a Pentium II 450mhz running (FC4 i386), the one that doesn't work is running on a Xeon 2.8ghz (FC4 x86_64). I've compiled mod_jk v1.2.14.1 from source on each box configured everything with simple settings from the tomcat connector HOWTOs. I'm running apache 2.0.54-10. I also tried downloading a precompiled binary (jakarta-tomcat-connectors-jk-1.2.10-linux-sles9-x86_64-prefork.so) but didn't have any better results. I tried pointing the working box's workers.properties file to the other boxes tomcat to confirm tomcat was in fact listening on port 8009. That worked. I turned off my firewall to ensure that wasn't the issue. below is the log from mod_jk. I can provide one with debug message but thought I'd start with the shorter version. Thanks for any help on this matter, I'm stumped. Chris Brown [Thu Jul 21 00:18:16 2005] [error] init_jk::mod_jk.c (2356): Initializing shm:/etc/httpd/logs/jk-runtime-status errno=13 [Thu Jul 21 00:18:17 2005] [error] init_jk::mod_jk.c (2356): Initializing shm:/etc/httpd/logs/jk-runtime-status errno=13 [Thu Jul 21 00:18:17 2005] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13 [Thu Jul 21 00:18:17 2005] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13 [Thu Jul 21 00:18:17 2005] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13 [Thu Jul 21 00:18:17 2005] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13 [Thu Jul 21 00:18:17 2005] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13 [Thu Jul 21 00:18:17 2005] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13 [Thu Jul 21 00:18:17 2005] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13 [Thu Jul 21 00:18:17 2005] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13 [Thu Jul 21 00:18:21 2005] [info] jk_open_socket::jk_connect.c (444): connect to 127.0.0.1:8009 failed with errno=13 [Thu Jul 21 00:18:21 2005] [info] ajp_connect_to_endpoint::jk_ajp_common.c (889): Failed opening socket to (127.0.0.1:8009) with (errno=13) [Thu Jul 21 00:18:21 2005] [info] ajp_send_request::jk_ajp_common.c (1248): Error connecting to the Tomcat process. [Thu Jul 21 00:18:21 2005] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=1 [Thu Jul 21 00:18:21 2005] [info] jk_open_socket::jk_connect.c (444): connect to 127.0.0.1:8009 failed with errno=13 [Thu Jul 21 00:18:21 2005] [info] ajp_connect_to_endpoint::jk_ajp_common.c (889): Failed opening socket to (127.0.0.1:8009) with (errno=13) [Thu Jul 21 00:18:21 2005] [info] ajp_send_request::jk_ajp_common.c (1248): Error connecting to the Tomcat process. [Thu Jul 21 00:18:21 2005] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=2 [Thu Jul 21 00:18:21 2005] [info] jk_open_socket::jk_connect.c (444): connect to 127.0.0.1:8009 failed with errno=13 [Thu Jul 21 00:18:21 2005] [info] ajp_connect_to_endpoint::jk_ajp_common.c (889): Failed opening socket to (127.0.0.1:8009) with (errno=13) [Thu Jul 21 00:18:21 2005] [info] ajp_send_request::jk_ajp_common.c (1248): Error connecting to the Tomcat process. [Thu Jul 21 00:18:21 2005] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=3 [Thu Jul 21 00:18:21 2005] [error] ajp_service::jk_ajp_common.c (1758): Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong port. worker=ajp13w failed [Thu Jul 21 00:18:21 2005] [info] service::jk_lb_worker.c (662): service failed, worker ajp13w is in error state [Thu Jul 21 00:18:21 2005] [info] service::jk_lb_worker.c (712): All tomcat instances are busy or in error state [Thu Jul 21 00:18:21 2005] wlb 192.168.0.10 0.001245 [Thu Jul 21 00:18:21 2005] [info] jk_handler::mod_jk.c (1971): Service error=0 for worker=wlb
Re: Apache2+jk+tomcat5.028+uri utf-8 [NOT] SOLVED
An update on the problem Reading through some other posts I got the suspicion that errno=13 was privilege related. On a hunch turned off SELINUX (http://fedora.redhat.com/docs/selinux-faq-fc3/index.html#id2825232) and everything worked great! The next step is to figure out how to run with it back on, but that got me going again. - Original Message - From: "Chris Brown" <[EMAIL PROTECTED]> To: "Tomcat Users List" Sent: Thursday, July 21, 2005 4:06 PM Subject: Re: Apache2+jk+tomcat5.028+uri utf-8 [NOT] SOLVED Hello, Sorry for not replying to the thread referenced in my subject (See July 1st, 2005), I'm new to the list and didn't have the email to reply to. I am having the same trouble that Paul and Steve encountered. (Error connecting to tomcat from mod_jk). Like Steve I have two similarly configured machines, one works, one doesn't. I can provide configuration files and more detailed logs but the errors I get are similar. Maybe I can peek someone's interest or jog a memory by proviging more detail. I'm running two identically configured Fedora Core 4 boxes. The one that works is running on a Pentium II 450mhz running (FC4 i386), the one that doesn't work is running on a Xeon 2.8ghz (FC4 x86_64). I've compiled mod_jk v1.2.14.1 from source on each box configured everything with simple settings from the tomcat connector HOWTOs. I'm running apache 2.0.54-10. I also tried downloading a precompiled binary (jakarta-tomcat-connectors-jk-1.2.10-linux-sles9-x86_64-prefork.so) but didn't have any better results. I tried pointing the working box's workers.properties file to the other boxes tomcat to confirm tomcat was in fact listening on port 8009. That worked. I turned off my firewall to ensure that wasn't the issue. below is the log from mod_jk. I can provide one with debug message but thought I'd start with the shorter version. Thanks for any help on this matter, I'm stumped. Chris Brown [Thu Jul 21 00:18:16 2005] [error] init_jk::mod_jk.c (2356): Initializing shm:/etc/httpd/logs/jk-runtime-status errno=13 [Thu Jul 21 00:18:17 2005] [error] init_jk::mod_jk.c (2356): Initializing shm:/etc/httpd/logs/jk-runtime-status errno=13 [Thu Jul 21 00:18:17 2005] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13 [Thu Jul 21 00:18:17 2005] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13 [Thu Jul 21 00:18:17 2005] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13 [Thu Jul 21 00:18:17 2005] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13 [Thu Jul 21 00:18:17 2005] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13 [Thu Jul 21 00:18:17 2005] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13 [Thu Jul 21 00:18:17 2005] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13 [Thu Jul 21 00:18:17 2005] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13 [Thu Jul 21 00:18:21 2005] [info] jk_open_socket::jk_connect.c (444): connect to 127.0.0.1:8009 failed with errno=13 [Thu Jul 21 00:18:21 2005] [info] ajp_connect_to_endpoint::jk_ajp_common.c (889): Failed opening socket to (127.0.0.1:8009) with (errno=13) [Thu Jul 21 00:18:21 2005] [info] ajp_send_request::jk_ajp_common.c (1248): Error connecting to the Tomcat process. [Thu Jul 21 00:18:21 2005] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=1 [Thu Jul 21 00:18:21 2005] [info] jk_open_socket::jk_connect.c (444): connect to 127.0.0.1:8009 failed with errno=13 [Thu Jul 21 00:18:21 2005] [info] ajp_connect_to_endpoint::jk_ajp_common.c (889): Failed opening socket to (127.0.0.1:8009) with (errno=13) [Thu Jul 21 00:18:21 2005] [info] ajp_send_request::jk_ajp_common.c (1248): Error connecting to the Tomcat process. [Thu Jul 21 00:18:21 2005] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=2 [Thu Jul 21 00:18:21 2005] [info] jk_open_socket::jk_connect.c (444): connect to 127.0.0.1:8009 failed with errno=13 [Thu Jul 21 00:18:21 2005] [info] ajp_connect_to_endpoint::jk_ajp_common.c (889): Failed opening socket to (127.0.0.1:8009) with (errno=13) [Thu Jul 21 00:18:21 2005] [info] ajp_send_request::jk_ajp_common.c (1248): Error connecting to the Tomcat process. [Thu Jul 21 00:18:21 2005] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=3 [Thu Jul 21 00:18:21 2005] [error] ajp_service::jk_ajp_common.c (1758): Error connecting to tomcat. Tomcat is probably not starte
