Hi List,
I'm using Pound 1.9 with FreeBSD 6.1 on two dedicated carped
(Master/Backup) Loadbalancers. For the Backends I'm using two Apache
Webservers. My configuration looks like:
User www
Group www
LogLevel 1
Alive 30
ListenHTTP *,80
ListenHTTPS 195.225.xxx.yyy,443 /usr/local/etc/ssl/bla.crt
UrlGroup "www1.*"
BackEnd 10.0.0.1,80,1
EndGroup
UrlGroup "www2.*"
BackEnd 10.0.0.2,80,1
EndGroup
UrlGroup ".*"
BackEnd 10.0.0.1,80,1
BackEnd 10.0.0.2,80,1
Session URL "PHPSESSID" 300
EndGroup
Everything works fine, but session handling seems to be buggy when some
load occurs.
When I visit a website via the loadbalancers I start a Session which
SessionID is written as a parameter within the URL. For Example:
http://www.bla.dom/index.php?PHPSESSID=808as0d809qwe78
I'm clicking around and session handling works fine, I'm served always
from the same webserver. But when there is some load on the webservers,
or I'm hitting Reload again and again rapidly fast, then I'll be served
from the other webserver, too. But there isn't any session with my id,
so I'm running into a session handling error.
Is the loadbalancing mechanism in Pound called before the session
handling takes effect? Or do I have an error in my configuration file?
Will an upgrade to Pound 2.x avoid this behavior? I hope someone can
give me the one or other answer :-)
Thanks,
Falk
|
