View Issue Details

IDProjectCategoryView StatusLast Update
0005668Talerotherpublic2019-04-20 13:01
ReporterMarcello Stanisci 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 closedResolutionwon't fix 
Product Versiongit (master) 
Target Version0.6Fixed in Version0.6 
Summary0005668: taler-auditor-exchange starts with NULL as config file
DescriptionThis command doesn't check if any config file was given on the command line, or does use some logic to pick a default config file (like say ~/.config/taler.conf) either. To be fixed.

TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

Marcello Stanisci

2019-03-29 18:29

reporter   ~0014240

As a result, it uses the defaults from <prefix>/share/taler/config.d/ and often ends up trying to access non-existent databases.

demo-blue@gv:~$ taler-deployment-keyup
Mar 29 19:24:54-587764 taler-auditor-exchange-9941 ERROR Database connection failed: FATAL: database "taler" does not exist

Christian Grothoff

2019-04-02 17:36

manager   ~0014257

Eh, that's a feature. -c should be optional, and defaults to ~/.config/taler.conf, which is allowed to not exist (in which case the defaults take over, which ideally should be sufficient to run the tools to setup the rest.

Naturally, we should probably have more automation:
- taler-exchange-dbinit could try to setup the 'taler' database with PostGres
- taler-exchange-keyup could require a --currency option and automatically configure denominations
- taler-exchange-bank could be created to help the user configure the bank account details

As a result, the user might not have to edit ~/.config/taler.conf by hand ever, just run the above commands in the right order.

Regardless, making -c mandatory would be a regression IMO.

Issue History

Date ModifiedUsernameFieldChange
2019-03-27 15:32Marcello StanisciNew Issue
2019-03-27 15:33Marcello StanisciDescription Updated
2019-03-29 18:29Marcello StanisciNote Added: 0014240
2019-04-02 17:36Christian GrothoffNote Added: 0014257
2019-04-20 13:01Christian GrothoffAssigned To => Christian Grothoff
2019-04-20 13:01Christian GrothoffReproducibilityhave not tried => always
2019-04-20 13:01Christian GrothoffStatusnew => closed
2019-04-20 13:01Christian GrothoffResolutionopen => won't fix
2019-04-20 13:01Christian GrothoffProduct Version => git (master)
2019-04-20 13:01Christian GrothoffFixed in Version => 0.6
2019-04-20 13:01Christian GrothoffTarget Version => 0.6