View Issue Details

IDProjectCategoryView StatusLast Update
0010850Talerexchangepublic2026-02-04 19:00
Reportersebasjm Assigned ToChristian Grothoff Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Versiongit (master) 
Target Version1.4Fixed in Version1.4 
Summary0010850: wirewatch idle
DescriptionWithdrawing took forever.
Checking the logs seems to show that if wirewatch starts before libuefin is up then wirewatch hangs forever.

Restarting wirewatch works as expected, in the logs you ca

Untested but it should also consider reconnecting if libeufin dies and comes up after some time.

Jan 02 12:11:57 marvin taler-exchange-wirewatch[52507]: WARNING Request to `https://bank.taler/accounts/exchange/taler-wire-gateway/history/incoming?limit=1024&long_poll_ms=900000' was expected to return a body of type `application/json', got `text/html'
Jan 02 12:11:57 marvin taler-exchange-wirewatch[52507]: ERROR Unexpected response code 502
Jan 02 12:11:57 marvin taler-exchange-wirewatch[52507]: ERROR Error fetching history: The response we got from the server was not in the expected format. Most likely, the server does not speak the GNU Taler protocol. Check the URL and/or the network connection to the server. (502)
Jan 02 12:11:57 marvin taler-exchange-wirewatch[52507]: WARNING Server did not respect long-polling, enforcing client-side by sleeping for 14 m
Jan 02 12:11:57 marvin taler-exchange-wirewatch[52507]: INFO Will retry my shard (0,1024] of wirewatch-exchange-account-conversion in 14 m
Jan 02 12:11:57 marvin taler-exchange-wirewatch[52507]: DEBUG Adding task 0x61ae882faa00
Jan 02 12:11:57 marvin taler-exchange-wirewatch[52507]: INFO HTTP request for `https://bank.taler/accounts/exchange/taler-wire-gateway/history/incoming?limit=1024&long_poll_ms=900000' finished with 502 after 30 ms
Jan 02 12:11:57 marvin taler-exchange-wirewatch[52507]: DEBUG destroying task 0x61ae87c75400
Jan 02 12:11:57 marvin taler-exchange-wirewatch[52507]: DEBUG scheduler has more tasks ready!
Jan 02 12:11:57 marvin taler-exchange-wirewatch[52507]: DEBUG select timeout = Fri Jan 02 12:11:57 2026
Jan 02 12:11:57 marvin taler-exchange-wirewatch[52507]: DEBUG Running task 0x61ae88058fc0
Jan 02 12:11:57 marvin taler-exchange-wirewatch[52507]: DEBUG Adding task 0x61ae87c6e4a0
Jan 02 12:11:57 marvin taler-exchange-wirewatch[52507]: DEBUG destroying task 0x61ae88058fc0
Jan 02 12:11:57 marvin taler-exchange-wirewatch[52507]: DEBUG select timeout = Fri Jan 02 12:26:57 2026
Jan 02 12:16:10 marvin taler-exchange-wirewatch[52507]: DEBUG select timeout = Fri Jan 02 12:26:57 2026
Jan 02 12:16:10 marvin taler-exchange-wirewatch[52507]: DEBUG Running task 0x61ae87c57d70
Jan 02 12:16:10 marvin taler-exchange-wirewatch[52507]: DEBUG GNUNET_SCHEDULER_shutdown
Jan 02 12:16:10 marvin taler-exchange-wirewatch[52507]: DEBUG destroying task 0x61ae87c57d70
Jan 02 12:16:10 marvin taler-exchange-wirewatch[52507]: DEBUG Running task 0x61ae87c5f4b0
Jan 02 12:16:10 marvin taler-exchange-wirewatch[52507]: DEBUG Preparing SQL statement `UPDATE work_shards SET last_attempt=0 WHERE job_name=$1 AND start_row=$2 AND end_row=$3;' as `abort_shard'
Jan 02 12:16:10 marvin taler-exchange-wirewatch[52507]: DEBUG Running prepared statement `abort_shard' on 0x61ae87c58ac0
Jan 02 12:16:10 marvin taler-exchange-wirewatch[52507]: DEBUG Executing prepared SQL statement `abort_shard'
Jan 02 12:16:10 marvin systemd[3631]: Stopping taler-exchange-wirewatch.service - Taler Exchange Wirewatch...
Jan 02 12:16:10 marvin taler-exchange-wirewatch[52507]: DEBUG Execution of prepared SQL statement `abort_shard' finished (PGRES_COMMAND_OK)
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

Christian Grothoff

2026-01-04 15:39

manager   ~0027197

7f8aa41a2..72ade7bc9 makes the retry-timeout more aggressively (with exponential back-off) on HTTP failures.
That said: you must have passed some CLI option to set the timeout to 15 minutes, the default is *one* minute...

Issue History

Date ModifiedUsernameFieldChange
2026-01-02 15:23sebasjmNew Issue
2026-01-02 15:23sebasjmStatusnew => assigned
2026-01-02 15:23sebasjmAssigned To => Christian Grothoff
2026-01-04 15:39Christian GrothoffNote Added: 0027197
2026-01-04 15:39Christian GrothoffStatusassigned => informing
2026-01-04 15:39Christian GrothoffResolutionopen => fixed
2026-01-04 15:39Christian GrothoffFixed in Version => 1.4
2026-01-04 15:39Christian GrothoffProduct Version => git (master)
2026-01-04 15:39Christian GrothoffTarget Version => 1.4
2026-02-04 19:00Christian GrothoffStatusinforming => closed