avm/hassio-addons
1
0
Fork 0
mirror of https://github.com/alexbelgium/hassio-addons.git synced 2026-08-19 03:17:19 +02:00
Code Issues Packages Projects Releases Wiki Activity

fix(komga): bound the readiness probes and log an exhausted wait

Browse Source 
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
alexbelgium
2026-08-11 18:57:32 +02:00
parent 4f9cbd0e90
commit 805f225618
1 changed files with 12 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
komga/rootfs/etc/services.d/nginx/run
View File

@@ -8,12 +8,23 @@ set -e
# bashio::net.wait_for : bashio takes (port host timeout) while the bundled # bashio::net.wait_for : bashio takes (port host timeout) while the bundled
# bashio-standalone.sh takes (host port timeout), and picking the wrong one # bashio-standalone.sh takes (host port timeout), and picking the wrong one
# would either fail instantly or block for the whole timeout. # would either fail instantly or block for the whole timeout.
# The per probe timeouts keep the 15 minute ceiling real : without them a
# half open connection would hang a single probe, and the loop, forever.
komga_ready=false
for _ in $(seq 1 180); do for _ in $(seq 1 180); do
if curl -sf -o /dev/null "http://127.0.0.1:25600/komga/"; then if curl -sf --connect-timeout 2 --max-time 5 -o /dev/null "http://127.0.0.1:25600/komga/"; then
komga_ready=true
break break
fi fi
sleep 5 sleep 5
done done
# Deliberately not fatal : nginx serving a 502 tells the user something is wrong
# and starts working by itself once komga finally answers, while refusing to
# start would take ingress down for good after ha_entrypoint gives up retrying.
if [ "$komga_ready" != true ]; then
bashio::log.warning "Komga did not answer within 15 minutes. Starting NGinx anyway : ingress will return 502 until it does."
fi
bashio::log.info "Starting NGinx..." bashio::log.info "Starting NGinx..."
exec nginx exec nginx