Hi all. I tried in another clean VM in a different server (Ubuntu rather than Debian btw) and this time worked like a charm.
I discovered later on some issues in the disk (thanks to S.M.A.R.T.) that can explain the segfault error. So unless I would reply to this thread let's consider this case as 'resolved'. Thanks. Javier 2012/12/20 Willy Tarreau <[email protected]>: > Hi Javi, > > On Tue, Dec 18, 2012 at 11:50:32AM +0100, Javi Legido wrote: >> Hi there. >> >> Brief history: >> >> 1. I compiled haproxy-1.5-dev15 >> >> sudo aptitude update; sudo aptitude install build-essential >> libpcre3-dev libssl-dev >> cd /usr/local; sudo wget -c --tries=0 >> http://haproxy.1wt.eu/download/1.5/src/devel/haproxy-1.5-dev15.tar.gz >> sudo tar xvfz haproxy-1.5-dev15.tar.gz; sudo ln -s haproxy-1.5-dev15 haproxy >> make TARGET=linux2628 USE_STATIC_PCRE=1 USE_OPENSSL=1 >> sudo make install >> >> 2. I copied a working config from another haproxy server (version >> 1.4.8-1) for testing purposes. If you think the config is relevant >> I'll post it >> >> 3. I tried to start haproxy: >> >> sudo /usr/local/sbin/haproxy -c -f /etc/haproxy/haproxy.cfg >> >> No output, no process running. I got this in the logs: >> >> ==> /var/log/messages <== >> Dec 18 11:48:31 balancer-2 kernel: [ 3732.683419] haproxy[8652]: >> segfault at 0 ip 0000000000443dfa sp 00007fffb13333c0 error 6 in >> haproxy[400000+a8000] >> >> Should I blame the compile process? Should I try a different version? > > It looks like a bug while parsing the config, it happens from time to time > (eg: missing check for a mandatory argument). Can you publish your config ? > Or can you at least narrow it down to just the part that causes the issue > and post it ? It's important that we find and fix this issue before issuing > another version. > > Thanks, > Willy >
