From b20fad10c5c01d770de927ac033ce62ffaab7526 Mon Sep 17 00:00:00 2001 From: juancarmore Date: Tue, 27 Oct 2026 09:30:52 +0100 Subject: [PATCH] openvidu-dashboard: the contract check stops the server as soon as it initializes the database The OpenVidu server no longer ignores a SIGTERM received while it starts (OpenVidu/openvidu-livekit 6d435287). --- .../dashboard-ce/typings/contract/writer-check.sh | 7 ------- 1 file changed, 7 deletions(-) diff --git a/openvidu-dashboard/dashboard-ce/typings/contract/writer-check.sh b/openvidu-dashboard/dashboard-ce/typings/contract/writer-check.sh index 8b18fb2d4..a53b6cc74 100755 --- a/openvidu-dashboard/dashboard-ce/typings/contract/writer-check.sh +++ b/openvidu-dashboard/dashboard-ce/typings/contract/writer-check.sh @@ -107,13 +107,6 @@ grep -q "analytics database initialized" "$WORK/server.log" || { cat "$WORK/server.log" >&2 fail "the OpenVidu server did not initialize the analytics database" } -# LiveKit's Start marks the server running 100 ms after it starts serving, and a SIGTERM before that is ignored until a -# second one: stop it only once it answers HTTP and that window has passed. -for _ in $(seq 1 30); do - curl -sf -o /dev/null "http://127.0.0.1:$SERVER_HTTP_PORT/" && break - sleep 1 -done -sleep 1 # Bounded, so that a server that does not stop on SIGTERM fails here with its log instead of at the job timeout. kill "$SERVER_PID" for _ in $(seq 1 20); do