Hi,
I've set up two identical instances of haproxy, using a peer table. I know
they are identical because I cloned them from the same EC2 image. (I
edited the config file by hand, but ran a diff to be sure it's the same).
The problem is that while one instance starts up fine, the other starts,
but immediately crashes. This one shows normal start up messages in the
logs (but no errors). It creates the /var/run/haproxy.pid file and the
/tmp/haproxy socket, and then the process apparently exits.
Oddly, editing out the reference to the peers in the stick table definition
makes it start up fine.
Here's my peers...
peers mypeers
peer www1-new 10.0.2.85:1024
peer www2-new 10.0.3.174:1024
...
...
backend simulate
option httpchk OPTIONS /simulate/api/status
stick-table type string len 40 size 5M expire 30m peers mypeers
stick store-response set-cookie(SIMULATE_STICKY_SESSION) table simulate
stick on cookie(SIMULATE_STICKY_SESSION) table simulate
stick on url_param(SIMULATE_STICKY_SESSION,;) table simulate
server app1 10.0.2.11:8080 cookie app1 check inter 10000
server app2 10.0.3.11:8080 cookie app2 check inter 10000
------------
When I change the stick-table line to read:
stick-table type string len 40 size 5M expire 30m
It starts up fine.
I've verified
* port 1024 is accessible between the two servers
* the haproxy.cfg files are identical
* they are being run by user haproxy.
Any other suggestions?
I'm running dev18 release on Ubuntu 12.04.
WILL
--
Forio Online Simulations
Will Glass-Husain
415 440-7500x89
wgl...@forio.com
www.forio.com
