Thanks. Is the JkShmfile something new? It worked when we had mod_jk
1.25. What is JkshmFile used for?

On Sun, Oct 25, 2009 at 8:42 AM, Rainer Jung <rainer.j...@kippdata.de> wrote:
> On 25.10.2009 16:00, Mohit Anchlia wrote:
>> I think I got it. It was JkShmFile that was missing.
>
> yes, and the default didn't work, see below.
>
>> Do you know how load balancing was working then if the status worker
>> wasn't running? During our perf test I did see that it was getting
>> load balanced.
>
> Each Apache process will be able to load balance for itself, but the
> result will not be coordinated between the various processes. So the
> result will be slightly worse and also each process will need to detect
> error situations independently.
>
>> On Sun, Oct 25, 2009 at 7:50 AM, Mohit Anchlia <mohitanch...@gmail.com> 
>> wrote:
>>> mod_jk 1.27 came with the rpm that we installed on linux. Later we got
>>> the binary for mod_jk 1.28 and followed the instructions of copying
>>> the .so. Below are the snippet from the properties file.
>>>
>>> Interesting thing is that setup looks fine. I get the JkStatus page on
>>> the browser and it lets me set it to stop. But then it never gets
>>> stopped or disabled. I also tried wget but didn't work. It definitely
>>> worked in mod_jk 1.25.
>>>
>>> From logs:
>>>
>>> --
>>> [Sun Oct 25 07:49:46.459 2009] [5261:3083893600] [error]
>>> init_jk::mod_jk.c (3166): Initializing
>>> shm:/usr/local/apache2/logs/jk-runtime-status.5261 errno=2. Load
>>> balancing workers will not function properly.
>
> That's the problem. You need to take "error" log lines seriously.
>
> Regards,
>
> Rainer
>
>>> [Sun Oct 25 07:49:46.481 2009] [5261:3083893600] [info]
>>> init_jk::mod_jk.c (3183): mod_jk/1.2.28 initialized
>>> [Sun Oct 25 07:49:46.614 2009] [5269:3083893600] [error]
>>> init_jk::mod_jk.c (3166): Initializing
>>> shm:/usr/local/apache2/logs/jk-runtime-status.5269 errno=2. Load
>>> balancing workers will not function properly.
>>> [Sun Oct 25 07:49:46.633 2009] [5269:3083893600] [info]
>>> init_jk::mod_jk.c (3183): mod_jk/1.2.28 initialized
>>> --
>>>
>>> We use:
>>>
>>> mod-jk.conf
>>> --
>>> JkWorkersFile conf/workers.properties
>>>
>>> # Where to put jk logs
>>> JkLogFile /var/log/apache2/mod_jk.log
>>>
>>> # Set the jk log level [debug/error/info]
>>> JkLogLevel error
>>>
>>> <Location /JkStatus>
>>> #    Order deny,allow
>>> #    Deny from all
>>> #    Allow from localhost
>>>     Allow from all
>>> </Location>
>>>
>>> httpd conf
>>> ---
>>> <IfModule jk_module>
>>> Include conf/mod-jk.conf
>>> </IfModule>
>>>
>>> LoadModule jk_module          modules/mod_jk.so
>>>
>>>
>>> On Sun, Oct 25, 2009 at 7:34 AM, Rainer Jung <rainer.j...@kippdata.de> 
>>> wrote:
>>>> What's you operating system and how exactly did you configure and make
>>>> mod_jk?
>>>>
>>>> What JK directives do you use in your httpd configuration?
>>>>
>>>> If you set JkLogLevel to info, are there any log messages during startup?
>>>>
>>>> Regards,
>>>>
>>>> Rainer
>>>>
>>>> On 25.10.2009 15:18, Mohit Anchlia wrote:
>>>>> I posted this earlier to old thread. I am posting it with new thread.
>>>>>
>>>>> Apache 2.2.11, mod_jk/1.2.28:
>>>>>
>>>>> There seems to be a problem with activation of status worker JkStatus.
>>>>> Even after explicitly saying "stopped" for one of the workers the
>>>>> "Act" keeps going back and forth. When I refresh that page it keeps
>>>>>
>>>>> switching between "OK" and "STP". I even tried using wget but that
>>>>> doesn't work either. And I still see traffic being sent
>>>>> to that worker.
>>>>>
>>>>> wget:
>>>>>
>>>>> http://host2535.pharos.in.com/JkStatus?cmd=update&from=list&w=tc&sw=host2532&vwa=2&wf=1&wn=host2532&wr=&wc=&wd=0&mime=txt";
>>>>>
>>>>> I have even tried vwa=s. I also tried opening one browser session
>>>>> stopping the worker (jkStatus) and then opening a new session to check
>>>>> the status. The status still keeps going back and forth. It shows
>>>>> "ACT" and then you refresh it shows "STP" and then you refresh again
>>>>> it shows "ACT". Nothing seems to be working.
>>>>>
>>>>>
>>>>> Is this a known bug?
>>>>>
>>>>>
>>>>> Earlier when we were on previous version of mod_jk this used to work
>>>>> fine. Attached is the screen shot
>>>>>
>>>>> worker.properties
>>>>>
>>>>> worker.list=jkstatus,tc
>>>>> worker.jkstatus.type=status
>>>>>
>>>>> worker.tc.type=lb
>>>>> worker.tc.balance_workers=host2532,host2533
>>>>> worker.tc.sticky_session=true
>>>>>
>>>>> worker.host2532.type=ajp13
>>>>> worker.host2532.port=8009
>>>>> worker.host2532.host=host2532
>>>>> worker.host2532.socket_timeout=5
>>>>> worker.host2532.socket_keepalive=true
>>>>> worker.host2532.prepost_timeout=5
>>>>> worker.host2532.connect_timeout=5000
>>>>> worker.host2532.retries=3
>>>>> worker.host2532.recycle_timeout=900
>>>>>
>>>>> worker.host2533.type=ajp13
>>>>> worker.host2533.port=8009
>>>>> worker.host2533.host=host2533
>>>>> worker.host2533.socket_timeout=5
>>>>> worker.host2533.socket_keepalive=true
>>>>> worker.host2533.prepost_timeout=5
>>>>> worker.host2533.connect_timeout=5000
>>>>> worker.host2533.retries=3
>>>>> worker.host2533.recycle_timeout=900
>>>>>
>>>>> httpd conf in VirtualHosts
>>>>>
>>>>>    JkMount /JkStatus jkstatus
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to