From 5d1e1317c2a35b9e98b787945b6b00cd539f9c95 Mon Sep 17 00:00:00 2001 From: William Lallemand Date: Fri, 14 Oct 2022 15:41:55 +0200 Subject: [PATCH] DOC: management: "show startup-logs" for master CLI "show startup-logs" on the master CLI has a slighly different behavior. No backport needed. --- doc/management.txt | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/doc/management.txt b/doc/management.txt index 63b20a411f..05033beccb 100644 --- a/doc/management.txt +++ b/doc/management.txt @@ -3439,6 +3439,9 @@ show startup-logs Dump all messages emitted during the startup of the current haproxy process, each startup-logs buffer is unique to its haproxy worker. + This keyword also exists on the master CLI, which shows the latest startup or + reload tentative. + show table Dump general information on all known stick-tables. Their name is returned (the name of the proxy which holds them), their type (currently zero, always @@ -3951,6 +3954,18 @@ show proc worker is still running and survived 3 reloads. You could access the CLI of this worker to understand what's going on. +show startup-logs + HAProxy needs to be compiled with USE_SHM_OPEN=1 to be used correctly on the + master CLI or all messages won't be visible. + + Like its counterpart on the stats socket, this command is able to show the + startup messages of HAProxy. However it does not dump the startup messages + of the current worker, but the startup messages of the latest startup or + reload, which means it is able to dump the parsing messages of a failed + reload. + + Those messages are also dumped with the "reload" command. + 10. Tricks for easier configuration management ---------------------------------------------- -- 2.47.3