Hi,
First of all, I really like haproxy and I'm really exited about the
keep-alive support! So I gave the new 1.4-dev6 spin, but I'm getting a
segfault.
When I run haproxy (with -d) in gdb I get:
Program received signal SIGSEGV, Segmentation fault.
0x0000000000433cf9 in manage_server_side_cookies (t=0x25dd1f0,
rtr=0x25e1ae0) at src/proto_http.c:5929
5929 if ((t->sessid =
pool_alloc2(apools.sessid)) == NULL) {
(gdb)
(gdb)
(gdb) bt
#0 0x0000000000433cf9 in manage_server_side_cookies (t=0x25dd1f0,
rtr=0x25e1ae0) at src/proto_http.c:5929
#1 0x00000000004306f4 in http_process_res_common (t=0x25dd1f0,
rep=0x25e1ae0, an_bit=262144, px=0x2554230) at src/proto_http.c:4587
#2 0x000000000044c0ba in process_session (t=0x25dd660) at src/session.c:982
#3 0x0000000000409e6b in process_runnable_tasks (next=0x7fff914ba01c)
at src/task.c:234
#4 0x00000000004045bd in run_poll_loop () at src/haproxy.c:935
#5 0x0000000000404d1f in main (argc=4, argv=0x7fff914ba188) at
src/haproxy.c:1210
So it looks like something goes wrong with the session cookie
handling. The relevant part in my config (do you need my complete
config?):
backend cms
mode http
balance leastconn
appsession JSESSIONID len 20 timeout 12h
option httpchk GET /ping/ HTTP/1.1\r\nHost:\ cms.mycompany.com
server cms1 172.16.1.33:80 check inter 3s weight 100
server cms2 172.16.1.34:80 check inter 3s weight 100
Any help would be really welcome!
Regards,
Bart
On Fri, Jan 8, 2010 at 8:05 AM, Willy Tarreau <[email protected]> wrote:
> Hi all,
>
> well, some of you have encountered issues with 1.4-dev5
> with sessions left in CLOSE_WAIT state or with memory leaks.
>
> With the help of Cyril Bonté and Hank A. Paulson who have sent
> a lot of feedback and tested almost all intermediate versions,
> we finally managed to nail all the problems down and to reach
> a working state. Of course that does not mean there is no bug
> left, but it's working reliably on two servers here (including
> haproxy.1wt.eu) without any of those issues.
>
> Also, after some thinking I realized that the changes had affected
> the behaviour of "option httpclose" to mimmic a bit "option
> forceclose" and I realized that there was no reason for this.
> So the behaviour of "option httpclose" has been restored so that
> it only ensures the headers are correct and relies on both ends
> to agree on when to close. Option forceclose must be used if you
> want haproxy to follow the request/response and enforce the close
> at the right moment. This is important, because some issues that
> people have been facing with 1.4-dev5 should not have impacted
> them if this change had not been performed (though it helped to
> spot the bugs faster).
>
> As usual, Krzysztof has sent a bunch of nice improvements for the
> checks and the stats interface, and a new very cool feature :
> "default-server". This will make it possible to move almost all
> of the server settings to a central place so that you won't have
> to copy/paste them all for all servers.
>
> So it was time to release 1.4-dev6 so that you have a better
> experience with it and can test the keep-alive mode without the
> fear of a degraded service.
>
> It's available at the usual place :
>
> http://haproxy.1wt.eu/download/1.4/src/
>
> I hope we won't have to run after the bugs as we did this week,
> it has been quite painful, but very useful.
>
> Thanks to all those who helped, and thanks in advance to all
> those who will test this one.
>
> Willy
>
>
>
