View Issue Details

IDProjectCategoryView StatusLast Update
0011782Talermerchant backendpublic2026-09-18 11:28
Reportervecirex Assigned Tovecirex 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
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0011782: mytops Stage: KYC status not updating after exchange ToS accept; hang until taler-merchant.target restart
DescriptionOliver tried to sign in on mytops Stage; everything fine until accepting the exchange ToS, then it hung -- merchant did not update KYC status anymore.

Restarting taler-merchant.target manually made it work again (acc. to fdold).

Hypothesis: too many accounts that are not KYC-authed.
Tagsmytops, quality, srv-betel

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

vecirex

2026-09-10 15:25

administrator   ~0029936

Last edited: 2026-09-10 15:26

Stresstesting (in acc. w/ fdold, backup-first) to start soon; then try new merchant from Taler APT label
trixie-testing
w/ potential fix (if hypothesis true); all things in progress now.

vecirex

2026-09-10 22:34

administrator   ~0029938

mytops-admin-log.git master ac225b8 — docs: STAGE_ENV temporary — will go away after 0011782 restore/upgrade priority

cf. mytops-admin-log.git, ops-manual.md (section STAGE_ENV — directly at top of the file).

Commit marks STAGE_ENV as short-lived (will be removed); restore+upgrade were prioritized first. Daylogs cross-ref the same section.

Repo: ssh://git@git.gnunet.org/mytops-admin-log.git
Ticket assigned to me via Florian.

Florian Dold

2026-09-10 22:42

manager   ~0029939

Possibly fixed by this:

commit de3eab29eebec8d1c1b1bf0ea2adc39ba647691a (HEAD -> master, origin/master, origin/HEAD)
Author: Florian Dold <dold@taler.net>
Date: Thu Sep 10 23:30:20 2026 +0200

    kyccheck: stop refresh loops and scans across all instances
    
    KYC long-poll wakeups forced another exchange check, whose result
    notified the pollers even when nothing changed. These notifications
    also woke other instances, and each refresh scanned every instance
    schema, multiplying the work as instance count grew.
    
    Refresh once per HTTP request and target notifications and refresh
    work to the affected instance.
    
    Requires updating SQL procedures and restarting HTTPD and kyccheck
    together because their internal APIs and notification formats change.

Issue History

Date ModifiedUsernameFieldChange
2026-09-09 13:41vecirexNew Issue
2026-09-09 13:41vecirexStatusnew => assigned
2026-09-09 13:41vecirexAssigned To => vecirex
2026-09-09 13:45vecirexTag Attached: quality
2026-09-09 13:45vecirexTag Attached: taler-am
2026-09-09 13:47vecirexStatusassigned => acknowledged
2026-09-09 13:47vecirexSummarymytops Stage: merchant KYC status not updated after exchange ToS acceptance (hang until merchant restart) => mytops Stage: KYC status not updating after exchange ToS accept; hang until taler-merchant.target restart
2026-09-09 13:47vecirexDescription Updated
2026-09-09 13:47vecirexTag Attached: mytops
2026-09-09 13:47vecirexTag Attached: srv-betel
2026-09-09 13:47vecirexTag Detached: taler-am
2026-09-09 13:49vecirexDescription Updated
2026-09-10 15:25vecirexNote Added: 0029936
2026-09-10 15:26vecirexNote Edited: 0029936
2026-09-10 15:26vecirexNote Edited: 0029936
2026-09-10 22:34vecirexNote Added: 0029938
2026-09-10 22:42Florian DoldNote Added: 0029939
2026-09-18 11:28vecirexStatusacknowledged => closed
2026-09-18 11:28vecirexResolutionopen => fixed
2026-09-18 11:28vecirexDescription Updated