From 9cdef5d52180b3651b33e67de8648166ce463bc6 Mon Sep 17 00:00:00 2001 From: byrsapty Date: Wed, 22 Jul 2026 23:05:52 +0300 Subject: [PATCH] Bump wait_for_api_ready timeout from 60s to 180s Confirmed live: on a CI-triggered run, the REST API genuinely took longer than 60s to accept authenticated requests even though the container had already reported healthy - verified after the fact that both the API and the admin credentials were fine, this was purely insufficient margin (likely due to concurrent load during the run), not a logic bug. 180s matches the same order of magnitude as the existing 300s docker-health wait elsewhere in this script. Co-Authored-By: Claude Sonnet 5 --- install-graylog.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/install-graylog.sh b/install-graylog.sh index c30a016..4c4418d 100644 --- a/install-graylog.sh +++ b/install-graylog.sh @@ -219,9 +219,9 @@ wait_for_api_ready() { local waited=0 while true; do gcurl GET /system/indices/index_sets | python3 -c "import json,sys;json.load(sys.stdin)" 2>/dev/null && break - waited=$((waited + 3)) - [ "$waited" -ge 60 ] && die "Graylog REST API did not respond with valid JSON within 60s of the container reporting healthy." - sleep 3 + waited=$((waited + 5)) + [ "$waited" -ge 180 ] && die "Graylog REST API did not respond with valid JSON within 180s of the container reporting healthy." + sleep 5 done ok "Graylog REST API is ready" }