View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010313 | Taler | exchange | public | 2025-08-29 19:08 | 2025-08-29 19:17 |
| Reporter | sebasjm | Assigned To | Christian Grothoff | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Summary | 0010313: /keys keeps files open to secmods when setup is incompleted | ||||
| Description | reproduced by florian, original found in default trixie setup I had some wallet asking for /keys, the exchange was delete and re-setup. When the httpd server was started the numbers of open files started to increase $ ss | grep exchange | wc -l 411 to /run/taler-exchange/secmod-<any>/server.sock until 500 and then the logs have WARNING `accept' failed at secmod_common.c:432 with error: Too many open files And exchange services stop responding so is not possible to complete the setup with the `offline` tool. | ||||
| Tags | No tags attached. | ||||
|
|
Some further info: The sockets aren't just opened automatically, but whenever the exchange gets /keys requests (that subsequently hang). We'd expect that even then, the exchange only opens *one* connection to each secmod helper. But what *actually* happens is that the exchange opens a new connection to the secmod helpers on every (hanging) /keys request. |
|
|
(Easily reproducible locally via an exchange-httpd process and secmod processes, with a fresh DB, a coin config but without any offline setup. Just curl "/keys" and check number of open sockets.) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-08-29 19:08 | sebasjm | New Issue | |
| 2025-08-29 19:14 | Florian Dold | Assigned To | => Christian Grothoff |
| 2025-08-29 19:14 | Florian Dold | Status | new => assigned |
| 2025-08-29 19:15 | Florian Dold | Note Added: 0025743 | |
| 2025-08-29 19:17 | Florian Dold | Note Added: 0025744 |
