hernani/taler-monitoring
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix 1.23.2: max-ladder RUN_TIMEOUT 3h (not 600s from env)

Browse source 
Force MAX_LADDER_RUN_TIMEOUT/10800 in run-max-ladder-monitoring.sh so
shared ~/.config/taler-monitoring/env cannot shrink the daily hunt.
Install uses systemctl --no-block for long oneshots.
This commit is contained in:
Hernâni Marques 2026-07-19 15:15:04 +02:00
parent db8e673cf5
commit c2309ba4f2
No known key found for this signature in database
4 changed files with 9 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

4
host-agent/run-max-ladder-monitoring.sh
View file

@ -20,8 +20,8 @@ export INSIDE_MODE="${INSIDE_MODE:-local-podman}"
export LOCAL_STACK="${LOCAL_STACK:-1}"
export SKIP_SSH="${SKIP_SSH:-0}"
export CONTINUE_ON_ERROR="${CONTINUE_ON_ERROR:-1}"
# max-search probes + pay hunt
export RUN_TIMEOUT="${RUN_TIMEOUT:-10800}"
# max-search probes + pay hunt — force high wall clock (koopa env often has RUN_TIMEOUT=600)
export RUN_TIMEOUT="${MAX_LADDER_RUN_TIMEOUT:-10800}"
export PHASES="max-ladder monpages"
export MON_HOSTS="${MON_HOSTS:-bank.hacktivism.ch exchange.hacktivism.ch taler.hacktivism.ch}"