View Issue Details

IDProjectCategoryView StatusLast Update
0005733Talermechant backendpublic2019-05-27 19:25
ReporterFlorian DoldAssigned ToMarcello Stanisci 
PrioritynormalSeverityminorReproducibilityhave not tried
Status assignedResolutionopen 
Product Version 
Target VersionFixed in Version 
Summary0005733: merchant does not recover from restarted postgres
DescriptionIf you restart the database while the merchant is running, the merchant does not seem to recover from it.

Additionally, there are a *lot* of subsequent log lines where the merchant is presumably trying to get keys from the exchange. Maybe this has to do with some retry logic that is going haywire?
TagsNo tags attached.

Activities

Florian Dold

2019-05-24 19:52

manager   ~0014438

Of course, a taler-deployment-restart "fixes" this, but the merchant backend must be able to recover from this on its own.

Marcello Stanisci

2019-05-27 19:25

manager   ~0014451

How exactly the merchant crashes?

Do you have any logs?

How can I reproduce this?

Issue History

Date Modified Username Field Change
2019-05-24 19:50 Florian Dold New Issue
2019-05-24 19:50 Florian Dold Status new => assigned
2019-05-24 19:50 Florian Dold Assigned To => Marcello Stanisci
2019-05-24 19:52 Florian Dold Note Added: 0014438
2019-05-27 19:25 Marcello Stanisci Note Added: 0014451