ZEO Strange Session KeyError When Load Balanced
Hello, I hope this is the correct place to post this question as I have not been able to resolve the problem via archives or Google. We have a setup with one ZEO server and two ZEO clients. The goal is to put a load balancer in front of the two clients and have them both operate off the same session data so that it appears as a single server to the end user. We setup the clients according to: http://longsleep.org/howto/sharesessionwithzeo However, when we run the setup whenever ZEO client 1 is hit for a page a KeyError is generated. I assume this is because ZEO client 2 set up the session and the data is not being shared. I upgraded us to Zope 2.7.4 last night in an attempt to fix the problem. Any help is greatly appreciated. Thank you in advance. Best Regards, Jason
Hi Jason, Coding errors causing this symptom were present in Zopes before 2.7.3 but none have been reported to my knowledge thereafter. Are you still having this issue with 2.7.4? On Thu, 2005-02-10 at 11:44, Jason J. W. Williams wrote:
Hello,
I hope this is the correct place to post this question as I have not been able to resolve the problem via archives or Google. We have a setup with one ZEO server and two ZEO clients. The goal is to put a load balancer in front of the two clients and have them both operate off the same session data so that it appears as a single server to the end user. We setup the clients according to: http://longsleep.org/howto/sharesessionwithzeo
However, when we run the setup whenever ZEO client 1 is hit for a page a KeyError is generated. I assume this is because ZEO client 2 set up the session and the data is not being shared. I upgraded us to Zope 2.7.4 last night in an attempt to fix the problem. Any help is greatly appreciated. Thank you in advance.
Best Regards, Jason _______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Jason J. W. Williams wrote at 2005-2-10 09:44 -0700:
... However, when we run the setup whenever ZEO client 1 is hit for a page a KeyError is generated. I assume this is because ZEO client 2 set up the session and the data is not being shared. I upgraded us to Zope 2.7.4 last night in an attempt to fix the problem. Any help is greatly appreciated. Thank you in advance.
This indicates that your trial to put the temporary folder into ZEO was unsuccessful. You probably should check this step again carefully. -- Dieter
Is there more to it than updating the client with the ZEO Temporary section in the zope.conf? On Thu, 10 Feb 2005 20:15:10 +0100, Dieter Maurer <dieter@handshake.de> wrote:
Jason J. W. Williams wrote at 2005-2-10 09:44 -0700:
... However, when we run the setup whenever ZEO client 1 is hit for a page a KeyError is generated. I assume this is because ZEO client 2 set up the session and the data is not being shared. I upgraded us to Zope 2.7.4 last night in an attempt to fix the problem. Any help is greatly appreciated. Thank you in advance.
This indicates that your trial to put the temporary folder into ZEO was unsuccessful.
You probably should check this step again carefully.
-- Dieter
How can I tell in the zope logs if all my ZEO stores are connecting properly? I have tried reconfiguring shared sessions according to: http://www.zopelabs.com/cookbook/1061234337 Unfortunately, I get the same result. -Jason On Thu, 10 Feb 2005 12:51:13 -0700, Jason J. W. Williams <jasonjwwilliams@gmail.com> wrote:
Is there more to it than updating the client with the ZEO Temporary section in the zope.conf?
On Thu, 10 Feb 2005 20:15:10 +0100, Dieter Maurer <dieter@handshake.de> wrote:
Jason J. W. Williams wrote at 2005-2-10 09:44 -0700:
... However, when we run the setup whenever ZEO client 1 is hit for a page a KeyError is generated. I assume this is because ZEO client 2 set up the session and the data is not being shared. I upgraded us to Zope 2.7.4 last night in an attempt to fix the problem. Any help is greatly appreciated. Thank you in advance.
This indicates that your trial to put the temporary folder into ZEO was unsuccessful.
You probably should check this step again carefully.
-- Dieter
Jason J. W. Williams wrote at 2005-2-10 12:51 -0700:
Is there more to it than updating the client with the ZEO Temporary section in the zope.conf?
I never tried your way (put sessions into ZEO). We use a different scheme (code session key (including a host id) into the URL and use Apache rewrites to ensure any requests goes to the host where the session started. -- Dieter
Am Freitag, den 11.02.2005, 19:55 +0100 schrieb Dieter Maurer:
Jason J. W. Williams wrote at 2005-2-10 12:51 -0700:
Is there more to it than updating the client with the ZEO Temporary section in the zope.conf?
I never tried your way (put sessions into ZEO).
We use a different scheme (code session key (including a host id) into the URL and use Apache rewrites to ensure any requests goes to the host where the session started.
Hehe. I remember reading many years ago about this technique is patented ;)
As a stop gap, we've got the load balancer doing persistent binding based on SSL ID. The problem being of course that if one server goes down all the logged in users have to re-login. If the session were persistent across servers via ZEO then the user wouldn't notice the down event. -J On Fri, 11 Feb 2005 21:35:07 +0100, Tino Wildenhain <tino@wildenhain.de> wrote:
Am Freitag, den 11.02.2005, 19:55 +0100 schrieb Dieter Maurer:
Jason J. W. Williams wrote at 2005-2-10 12:51 -0700:
Is there more to it than updating the client with the ZEO Temporary section in the zope.conf?
I never tried your way (put sessions into ZEO).
We use a different scheme (code session key (including a host id) into the URL and use Apache rewrites to ensure any requests goes to the host where the session started.
Hehe. I remember reading many years ago about this technique is patented ;)
Tino Wildenhain wrote at 2005-2-11 21:35 +0100:
... session id encoded in URL ... Hehe. I remember reading many years ago about this technique is patented ;)
Wow! Another stupid patent... Hopefully, we Europeans can prevent such stupidities in Europe :-) -- Dieter
participants (4)
-
Chris McDonough -
Dieter Maurer -
Jason J. W. Williams -
Tino Wildenhain