RE: Help: Error while opening the workers, jk will not work - (solved)

[Rob Cartier <rc...@snet.net>]

I found the problem while it worked before it wasnt working
anymore after upgrading to 4.1.24 from 4.1.18

I needed to add the modJk directive in the following lines as defined
in John Turners HowTo..

Thanks John
===================================================
<Listener className="org.apache.ajp.tomcat4.config.ApacheConfig"
modJk="/etc/httpd/modules/mod_jk.so" />

in the Host container add the following Listener directive (yes, it looks
very similar to the one above):

<Listener className="org.apache.ajp.tomcat4.config.ApacheConfig"
append="true" forwardAll="false" modJk="/etc/httpd/modules/mod_jk.so" />


> -----Original Message-----
> From: Rob Cartier [mailto:rcartier@snet.net]
> Sent: Sunday, June 01, 2003 10:49 AM
> To: 'tomcat-user@jakarta.apache.org'
> Subject: Help: Error while opening the workers, jk will not work
>
>
> Recently I have been seeing 'Error while opening the workers,
> jk will not work'
> show up in my httpd/error_log. And when that happens I get
> Error 500 codes
> and have to reboot my server. Stop and restarting tomcat or
> httpd doesnt help
>
> I have running
>
> rh 7.2
> tomcat 4.1.24
> apache 1.3.27
> I just upgraded the mod_jk connector to mod_jk.so.ap1.3.27-eapi.rh72
> thinking that was the problem . But that didnt help either.
>
> This system has been working flawlessly until recently.
>
> Is there anything else I can turn on in order to see a more
> verbose mod_jk
> error
>
> Also I have noticed that I can re-create the problem . If I shut down
> the apache server and restart it.
>
> Also after viewing the logs in mod_jk.log and catalina.out
> that it appears
> robots looking for files on my server has caused this problem
> as well :(
>
> here is an excerpt from my error_log file:
>
> [Sun Jun  1 08:44:52 2003] [notice] Apache/1.3.27 (Unix)
> (Red-Hat/Linux) mod_ssl/2.8.12 OpenSSL/0.9.6b DAV/1.0.2
> PHP/4.1.2 mod_perl/1.26 mod_jk/1.2.1 configured -- resuming
> normal operations
> [Sun Jun  1 08:44:52 2003] [notice] suEXEC mechanism enabled
> (wrapper: /usr/sbin/suexec)
> [Sun Jun  1 08:44:52 2003] [notice] Accept mutex: sysvsem
> (Default: sysvsem)
> [Sun Jun  1 08:50:34 2003] [notice] caught SIGTERM, shutting down
> [Sun Jun  1 08:50:36 2003] [error] (2)No such file or
> directory: Error while opening the workers, jk will not work
>
> [Sun Jun  1 08:50:36 2003] [error] (2)No such file or
> directory: Error while opening the workers, jk will not work
>
>
> Thanks in advance
>
>
> Rob Cartier
>



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

Re: Help: Error while opening the workers, jk will not work - (solved)

[John Turner <to...@johnturner.com>]

Glad you got it working!

John

On Mon, 2 Jun 2003 20:50:23 -0400, Rob Cartier <rc...@snet.net> wrote:

> I found the problem while it worked before it wasnt working
> anymore after upgrading to 4.1.24 from 4.1.18
>
> I needed to add the modJk directive in the following lines as defined
> in John Turners HowTo..
>
> Thanks John
> ===================================================
> <Listener className="org.apache.ajp.tomcat4.config.ApacheConfig"
> modJk="/etc/httpd/modules/mod_jk.so" />
>
> in the Host container add the following Listener directive (yes, it looks
> very similar to the one above):
>
> <Listener className="org.apache.ajp.tomcat4.config.ApacheConfig"
> append="true" forwardAll="false" modJk="/etc/httpd/modules/mod_jk.so" />
>
>
>> -----Original Message-----
>> From: Rob Cartier [mailto:rcartier@snet.net]
>> Sent: Sunday, June 01, 2003 10:49 AM
>> To: 'tomcat-user@jakarta.apache.org'
>> Subject: Help: Error while opening the workers, jk will not work
>>
>>
>> Recently I have been seeing 'Error while opening the workers,
>> jk will not work'
>> show up in my httpd/error_log. And when that happens I get
>> Error 500 codes
>> and have to reboot my server. Stop and restarting tomcat or
>> httpd doesnt help
>>
>> I have running
>>
>> rh 7.2
>> tomcat 4.1.24
>> apache 1.3.27
>> I just upgraded the mod_jk connector to mod_jk.so.ap1.3.27-eapi.rh72
>> thinking that was the problem . But that didnt help either.
>>
>> This system has been working flawlessly until recently.
>>
>> Is there anything else I can turn on in order to see a more
>> verbose mod_jk
>> error
>>
>> Also I have noticed that I can re-create the problem . If I shut down
>> the apache server and restart it.
>>
>> Also after viewing the logs in mod_jk.log and catalina.out
>> that it appears
>> robots looking for files on my server has caused this problem
>> as well :(
>>
>> here is an excerpt from my error_log file:
>>
>> [Sun Jun  1 08:44:52 2003] [notice] Apache/1.3.27 (Unix)
>> (Red-Hat/Linux) mod_ssl/2.8.12 OpenSSL/0.9.6b DAV/1.0.2
>> PHP/4.1.2 mod_perl/1.26 mod_jk/1.2.1 configured -- resuming
>> normal operations
>> [Sun Jun  1 08:44:52 2003] [notice] suEXEC mechanism enabled
>> (wrapper: /usr/sbin/suexec)
>> [Sun Jun  1 08:44:52 2003] [notice] Accept mutex: sysvsem
>> (Default: sysvsem)
>> [Sun Jun  1 08:50:34 2003] [notice] caught SIGTERM, shutting down
>> [Sun Jun  1 08:50:36 2003] [error] (2)No such file or
>> directory: Error while opening the workers, jk will not work
>>
>> [Sun Jun  1 08:50:36 2003] [error] (2)No such file or
>> directory: Error while opening the workers, jk will not work
>>
>>
>> Thanks in advance
>>
>>
>> Rob Cartier
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>



-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org