❦ 16 novembre 2015 16:51 +0100, SL :
> Process: 3751 ExecStartPre=/usr/local/sbin/haproxy -f ${CONFIG} -c -q
> (code=exited, status=2)
Execute this command manually. This is the one checking if the
configuration is correct.
--
Every cloud engenders not a storm.
-- William Shake
Hmm, it seems to be working again now - not sure what has changed, but will
investigate. Thanks for the response, and sorry for wasting your time.
On 16 November 2015 at 17:02, Marco Corte wrote:
> Hi!
>
> Does haproxy start manually? Is it only a systemd issue?
>
>
> Il 16/11/2015 16:51, SL h
Hi!
Does haproxy start manually? Is it only a systemd issue?
Il 16/11/2015 16:51, SL ha scritto:
systemctl status haproxy.service
systemctl status haproxy.service -l
.marcoc
Hi,
Today I cloned a server which is running haproxy 1.6 on a debian8 server
without problems. However, for some reason the clone refuses to start
haproxy (IPs and hostname have been updated of course).
Probably I'm missing something simple, but I can't think what it is. I
have very little expe
4 matches
Mail list logo
