Home directory for user haproxy or other permissible place had to be used
to start in order to store a core file. While running in the non daemon
mode killall -6 haproxy produced core. However editing /etc/init.d/haproxy
as below had no effect, i.e no core.
start() {
++ ulimit -c unlimited
++ cd /home/haproxy
quiet_check
if [ $? -ne 0 ]; then
echo "Errors found in configuration file, check it with '$BASENAME
check'."
return 1
fi
echo -n "Starting $BASENAME: "
daemon $BIN -D -f $CFG $EXTRAOPTS -p $PIDFILE
RETVAL=$?
echo
[ $RETVAL -eq 0 ] && touch $LOCKFILE
return $RETVAL
}
On Wed, May 18, 2016 at 7:34 AM, Willy Tarreau <w...@1wt.eu> wrote:
> On Wed, May 18, 2016 at 12:50:19PM +0200, Nenad Merdanovic wrote:
> > Hey,
> >
> > On 5/18/2016 8:28 AM, Sasha Litvak wrote:
> > > It is hard to reproduce, It took almost a week for it to crush and
> > > produced no core. I did ulimit -c unlimited before start. Does it
> make
> > > sense to go to back to 1.6.3 or try git source ?
> >
> > Make sure you set the fs.suid_dumpable=1 sysctl because you are not
> > running HAproxy as root. Also, after starting make sure to check
> > /proc/<pid>/limits and also that your core_pattern sysctl is set
> correctly.
>
> BTW, in order to validate the setup without having to wait for one week,
> simply send a kill -ABRT to the process. If you can't find the core,
> something is still missing.
>
> Regards,
> Willy
>
>
