View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010771 | Taler | deployment and operations | public | 2025-12-13 05:20 | 2026-02-05 19:31 |
| Reporter | vecirex | Assigned To | vecirex | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Summary | 0010771: taler-merchant v1.2.4 comes up with new warnings: check which of them are good predictors for more config needed | ||||
| Description | I will check with @sebasjm which of the new warnings (cf. https://bugs.gnunet.org/view.php?id=10770#c26948) we definitely should get rid of by doing additional config, if it's about to run a production env like it will exactly be done with setting my.taler-ops.ch live: 0010630. | ||||
| Tags | No tags attached. | ||||
| related to | 0010630 | closed | vecirex | Set my.taler-ops.ch live [done in principle by this morning: still solving deps; work parallelized] |
| related to | 0010770 | closed | vecirex | Upgrade existing TOPS/CHF test infra from v1.2.3 to v1.2.4 and do production-relevant tests [payment issue with iOS emerged] |
| related to | 0010785 | acknowledged | Stefan | Privacy Statement (link) missing |
| The new "WARNING" msg don't make it clear what to do, I would say. | |
| that's server side, @cg could explain better | |
| I don't understand. The logs show clearly that there are various configuration options that are simply not set and that probably should be. What else is there to say? | |
| I think we can state clearer that it's to about to serve the /terms and /privacy locations in a proper form with I18N support without having to use webserver location options, but I removed this ticket as a hard blocker for 0010630 for now. | |
| Not blocker still -- can be "fixed" in operation, just for completeness; I see four info messages and two warnings; taler-merchant v1.2.6, installed minutes ago; @stefan: do you see how the first four info values are set by now? 2025-12-16T20:27:57.366355+0000 taler-merchant-httpd-185368 INFO Configuration fails to specify option `DEFAULT_PAY_DELAY' in section `merchant'! 2025-12-16T20:27:57.366373+0000 taler-merchant-httpd-185368 INFO Configuration fails to specify option `DEFAULT_REFUND_DELAY' in section `merchant'! 2025-12-16T20:27:57.366381+0000 taler-merchant-httpd-185368 INFO Configuration fails to specify option `DEFAULT_WIRE_TRANSFER_DELAY' in section `merchant'! 2025-12-16T20:27:57.366390+0000 taler-merchant-httpd-185368 INFO Configuration fails to specify option `DEFAULT_WIRE_TRANSFER_ROUNDING_INTERVAL' in section `merchant'! 2025-12-16T20:27:57.366407+0000 taler-merchant-httpd-185368 WARNING Configuration fails to specify option `TERMS_ETAG' in section `merchant'! 2025-12-16T20:27:57.366416+0000 taler-merchant-httpd-185368 WARNING Terms of service not configured 2025-12-16T20:27:57.366422+0000 taler-merchant-httpd-185368 WARNING Configuration fails to specify option `PRIVACY_ETAG' in section `merchant'! 2025-12-16T20:27:57.366429+0000 taler-merchant-httpd-185368 WARNING Privacy policy not configured | |
| Messages in the logs got way clearer of what's needed / missing, and why; not in all cases those warnings play a role. Should a particular case appear, which is not understandable: create a specific ticket or (help to) fix in place. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-12-13 05:20 | vecirex | New Issue | |
| 2025-12-13 05:20 | vecirex | Status | new => assigned |
| 2025-12-13 05:20 | vecirex | Assigned To | => vecirex |
| 2025-12-13 05:21 | vecirex | Relationship added | child of 0010630 |
| 2025-12-13 05:22 | vecirex | Relationship added | related to 0010770 |
| 2025-12-16 12:21 | vecirex | Assigned To | vecirex => sebasjm |
| 2025-12-16 12:21 | vecirex | Note Added: 0027010 | |
| 2025-12-16 12:53 | sebasjm | Assigned To | sebasjm => Christian Grothoff |
| 2025-12-16 12:53 | sebasjm | Category | deployment and operations => merchant backend |
| 2025-12-16 12:53 | sebasjm | Note Added: 0027011 | |
| 2025-12-16 15:13 | Christian Grothoff | Note Added: 0027029 | |
| 2025-12-16 15:13 | Christian Grothoff | Assigned To | Christian Grothoff => vecirex |
| 2025-12-16 15:13 | Christian Grothoff | Status | assigned => feedback |
| 2025-12-16 16:09 | vecirex | Relationship replaced | related to 0010630 |
| 2025-12-16 16:12 | vecirex | Note Added: 0027031 | |
| 2025-12-16 16:24 | vecirex | Relationship added | related to 0010785 |
| 2025-12-16 20:57 | vecirex | Note Added: 0027045 | |
| 2025-12-16 20:57 | vecirex | Assigned To | vecirex => Stefan |
| 2025-12-17 12:01 | Stefan | Assigned To | Stefan => vecirex |
| 2026-01-26 06:52 | Christian Grothoff | Category | merchant backend => deployment and operations |
| 2026-02-05 19:31 | vecirex | Status | feedback => closed |
| 2026-02-05 19:31 | vecirex | Resolution | open => no change required |
| 2026-02-05 19:31 | vecirex | Note Added: 0027610 |