From 3535408d7ef922b044afd7974b71084f65f9e69e Mon Sep 17 00:00:00 2001 From: Mohd Husaam Mehdi Date: Thu, 15 Jan 2026 12:40:38 +0530 Subject: [PATCH] logmngr: make sure fluent-bit keeps trying to respawn for example, if proto is udp in syslog output and url is not resolved then fluent-bit stops, we want to make sure that eventually when the url can be resolved then logging resumes --- logmngr/files/lib/logmngr/fluent-bit.sh | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/logmngr/files/lib/logmngr/fluent-bit.sh b/logmngr/files/lib/logmngr/fluent-bit.sh index e036a9f7a..5843becdf 100644 --- a/logmngr/files/lib/logmngr/fluent-bit.sh +++ b/logmngr/files/lib/logmngr/fluent-bit.sh @@ -544,6 +544,11 @@ logmngr_init() { procd_set_param command $PROG -c ${CONF_FILE} procd_set_param file ${CONF_FILE} fi - procd_set_param respawn + + # if process finishes later than respawn_threshold, it is restarted unconditionally, regardless of error code + # wait 5 seconds before respawning + # for example, if proto is udp in syslog output and url is not resolved then fluent-bit stops + # this is done to make sure that eventually when the url can be resolved then logging resumes + procd_set_param respawn ${respawn_threshold:-1} ${respawn_timeout:-5} procd_close_instance }