View Issue Details

IDProjectCategoryView StatusLast Update
0008030Talerexchangepublic2024-03-07 19:47
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
PrioritynormalSeveritytweakReproducibilityalways
Status closedResolutionfixed 
Product Versiongit (master) 
Target Version0.9.4Fixed in Version0.9.4 
Summary0008030: define a list of error exist status that should not restart the service
Descriptionto use on systemd service definition, see https://www.commandlinux.com/man-page/man5/systemd.service.5.html

one code or set of codes that means fail but "safe to restart" (SuccessExitStatus)
one code or set of codes that means fail but "do not dare to restart" (RestartPreventExitStatus)
one code or set of codes that means fail but "off course you should restart" (RestartForceExitStatus)

hopefully, this error code will be implemented by all exchange merchant and bank services
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Relationships

related to 0008031 closedChristian Grothoff have a run-and-exit flag in CLI for wirewatch, transfer, aggregator, closer and expire services 

Activities

Christian Grothoff

2024-01-02 22:52

manager   ~0020818

When we do this, we should *also* cause taler-exchange-{wirewatch, transfer, closer, aggregator, router, expire} to self-terminate after handling a certain number of DB requests.

Christian Grothoff

2024-01-08 15:32

manager   ~0020829

#define EXIT_NO_RESTART 9 added as the exit code to use when the process should NOT be restarted.

Christian Grothoff

2024-01-08 15:36

manager   ~0020830

Modified all *.service files to include "RestartPreventExitStatus=9".

Christian Grothoff

2024-01-28 17:56

manager   ~0021062

eddf1b2..964365e starts using

RestartMode=direct
RestartPreventExitStatus=2 3 4 5 6 9

in merchant, plus consistent update to all the services to use the new exit codes correctly.

Christian Grothoff

2024-01-28 18:42

manager   ~0021063

Went through all exchange, merchant, sync and challenger services, should all be fine now.

Issue History

Date ModifiedUsernameFieldChange
2024-01-02 20:10sebasjmNew Issue
2024-01-02 20:10sebasjmStatusnew => assigned
2024-01-02 20:10sebasjmAssigned To => Christian Grothoff
2024-01-02 20:14sebasjmRelationship addedrelated to 0008031
2024-01-02 22:48Christian GrothoffSeverityminor => tweak
2024-01-02 22:52Christian GrothoffNote Added: 0020818
2024-01-08 15:32Christian GrothoffNote Added: 0020829
2024-01-08 15:36Christian GrothoffNote Added: 0020830
2024-01-28 17:56Christian GrothoffNote Added: 0021062
2024-01-28 18:42Christian GrothoffStatusassigned => informing
2024-01-28 18:42Christian GrothoffResolutionopen => fixed
2024-01-28 18:42Christian GrothoffFixed in Version => 0.9.4
2024-01-28 18:42Christian GrothoffNote Added: 0021063
2024-01-28 18:43Christian GrothoffTarget Version0.10 => 0.9.4
2024-03-07 19:47Christian GrothoffStatusinforming => closed