View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005764 | Taler | deployment and operations | public | 2019-06-13 16:38 | 2021-08-24 16:23 |
| Reporter | Marcello Stanisci | Assigned To | MS | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | no change required | ||
| Target Version | 0.8 | Fixed in Version | 0.8 | ||
| Summary | 0005764: Wire response from the exchange seems to disappear sometimes. | ||||
| Description | It happened a few times that the "[exchange]/wire_response" file suddenly disappears from the disk at Gv. This might be due to some BB side effect, or some other non-obvious logic, or ultimately to some manual intervention from a sysadmin. If a real problem exists, it should show up after a few blue/green switches from the 'test' setup. This bug is mostly a monitor for that to happen again than a claim that a problem exists (yet). | ||||
| Tags | No tags attached. | ||||
|
|
Definitively a bug. The file disappears when the inactive color builds Taler. Jun 13 15:58:28-268737 taler-exchange-httpd-31999 ERROR Failed to parse `/home/test-green/shared-data/exchange/wire/test.json': unable to open /home/test-green/shared-data/exchange/wire/test.json: No such file or directory at -1:-1 (0) Jun 13 15:58:28-268784 taler-exchange-httpd-31999 ERROR Failed to find properly configured wire transfer method Jun 13 15:58:28-403460 taler-exchange-httpd-32008 ERROR Failed to parse `/home/test-green/shared-data/exchange/wire/test.json': unable to open /home/test-green/shared-data/exchange/wire/test.json: No such file or directory at -1:-1 (0) Jun 13 15:58:28-403500 taler-exchange-httpd-32008 ERROR Failed to find properly configured wire transfer method |
|
|
This might explain it: https://buildbot.taler.net/#/builders/1/builds/284/steps/4/logs/stdio |
|
|
4749a118d9e4720fadd (@ deployment.git) makes sure that the deployment script does not brutally override the wire response file while the active color is still running (and possibly using it or having some "handle" on it). This might not be the ultimate fix, but sure an improvement. Putting as feedback to see how it evolves. |
|
|
The problem didn't show up anymore. But more importantly, the build system is very different now respect to when this problem was reported. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-06-13 16:38 | Marcello Stanisci | New Issue | |
| 2019-06-13 16:38 | Marcello Stanisci | Description Updated | |
| 2019-06-13 17:14 | Marcello Stanisci | Assigned To | => Marcello Stanisci |
| 2019-06-13 17:14 | Marcello Stanisci | Status | new => feedback |
| 2019-06-13 19:45 | Marcello Stanisci | Note Added: 0014547 | |
| 2019-06-13 19:45 | Marcello Stanisci | Status | feedback => assigned |
| 2019-06-13 19:46 | Marcello Stanisci | Note Added: 0014548 | |
| 2019-06-14 22:48 | Marcello Stanisci | Note Added: 0014550 | |
| 2019-06-14 22:48 | Marcello Stanisci | Status | assigned => feedback |
| 2019-06-14 22:49 | Marcello Stanisci | Note Edited: 0014550 | |
| 2020-09-04 14:41 | MS | Assigned To | Marcello Stanisci => MS |
| 2020-09-04 16:23 | MS | Note Added: 0016855 | |
| 2020-09-04 16:25 | MS | Status | feedback => resolved |
| 2020-09-04 16:25 | MS | Resolution | open => no change required |
| 2020-10-03 14:08 | Christian Grothoff | Fixed in Version | => 0.8 |
| 2020-10-03 14:10 | Christian Grothoff | Target Version | => 0.8 |
| 2021-08-24 16:23 | Christian Grothoff | Status | resolved => closed |
