On 06/14/2017 11:02 PM, Shelley Shostak wrote:
Aha. The problem is that the new haproxy.cfg file has hosts that are
not in the stat file. If there is no state file, the haproxy.cfg file
is perfectly valid.
I've attached a self-contained config file and state file that will
reproduce the seg fa
Hi Shelley, Willy,
I can confirm seeing similar on 1.7.1 on FreeBSD amd64, when there was a
discrepancy between the backends listed in the state file vs. the ones
configured for the new process. I never had time to sort out the precise
conditions, rather, shelved the use of the state file
Aha. The problem is that the new haproxy.cfg file has hosts that are not
in the stat file. If there is no state file, the haproxy.cfg file is
perfectly valid.
I've attached a self-contained config file and state file that will
reproduce the seg fault. Also the output of haproxy -c using those f
Hi,
On Tue, May 30, 2017 at 06:14:48PM -0700, Shelley Shostak wrote:
> BUG:
>
> Extra spaces inserted into the haproxy.cfg file cause haproxy reload with
> saved state to seg fault haproxy.
>
> WORKAROUND:
>
> Remove the existing state file OR remove save state from config.
>
> REPRODUCE:
>
>
BUG:
Extra spaces inserted into the haproxy.cfg file cause haproxy reload with
saved state to seg fault haproxy.
WORKAROUND:
Remove the existing state file OR remove save state from config.
REPRODUCE:
- Enable save state across reloads
- Reload and save state file
- Insert extra space be
5 matches
Mail list logo