We use haproxy together with keepalived as an high available loadbalancer
The current versions are:
Linux: Ubuntu 16.04 LTS
We are using haproxy since summer of last year to deploy a http-site to customers. At the end of 2016, the problems connecting to the backend application began and the users are experiencing timeouts.
There are 4 backend servers and haproxy is deploying the users on one of the 4 servers depending on a cookie set by the application.
We’re not sure if the problems are coming from haproxy or the backend application servers. Our problem is, that we can’t reproduce the problem the users are reporting. And there is actually no possibility to let some users connect directly to a backend server without haproxy (vpn limitation).
So i need to be sure that the problem is coming from backend application server.
I’ve now activated deeper logging in haproxy config:
- option httplog
- option log-separate-errors
- option dontlog-normal
now, i have a lot of entries like the following in the logs:
May 16 15:31:29 xxxx haproxy: xx.xx.xx.xx:xxxx [16/May/2017:15:29:21.324] server_80 server_80/server4 7/0/128231/1/128239 200 499 - - --VN 1670/906/485/198/1 0/0 “GET /di… HTTP/1.1”
i am not sure, but the time shown is very strange. It seems, that the backend web server is not giving a response in an acceptable amount of time.
Is this true? Can the problem be isolated at the backend webserver with those log entries?
Or is there an other possibility for our problem?