Re: HAproxy 1.3 + Solaris - Hot reconfiguration problem, Please help

I got the following behaviour which is inconsistent between versions

OS: SunOS sunexplor 5.9 Generic_122300-15 sun4u sparc SUNW,UltraAX-i2

haproxy-1.2.17:

    kill -TTOU $(cat ./haproxy.pid)
    #This signal shutdown haproxy, no process after this signal, no sesion active during this signal

haproxy-1.3.15.2:

    kill -TTOU $(cat ./haproxy.pid)
    #This signal stop listening but process remain alive

    kill -TIN $(cat ./haproxy.pid)
    #The process does not take control again, no stats available      haproxy -p ./haproxy.pid -f ${CONFIG} -D     [ALERT] 231/131337 (15524) : [/export/home/msoto/haproxy.main()] Some protocols failed to start their listeners! Exiting.

    # the new haproxy does not start

   I've to kill TERM and start again

2008/8/18 Manuel Soto <haproxy.20.micorreo#spamgourmet.com>:
> Hello List,
>
> I'm moving from 1.2 to 1.3 and found that -sf/st does not works like 1.3.
>
> In 1.2 I did
>
> ${HAPROXY} -p ${PIDFILE} -f ${CONFIG} ${HAPROXY_OPT} -sf $(cat ${PIDFILE})
>
> and it works, haproxy start and keep old sessions running, but in 1.3
> I got this erros..
>
>
> + /export/home/haproxy/haproxy -p /export/home/haproxy/haproxy.pid -f
> /export/haproxy/msoto/haproxy.cfg -D -st 15137
> [ALERT] 230/095721 (15163) : [/export/home/msoto/haproxy.main()] Some
> protocols failed to start their listeners! Exiting.
>
>
> 1.3 Architecture document doesn't mention -sf/st it uses kill
> -TTOU/-TTIN schema
>
> What is the recommended way to reload configuration in 1.3?
>
> Later,
> Manuel Soto
>
Received on 2008/08/19 20:26