View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008005 | Taler | exchange | public | 2023-12-12 20:10 | 2024-03-07 20:49 |
| Reporter | sebasjm | Assigned To | sebasjm | ||
| Priority | normal | Severity | trivial | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 0.9.4 | ||||
| Target Version | 0.9.4 | Fixed in Version | 0.9.4 | ||
| Summary | 0008005: wirewatch aborted after lost connection with db | ||||
| Description | every other component kept working 2023-12-08T06:34:48.273180-0300 taler-exchange-wirewatch-192292 INFO Change in PQ event FD to -1 2023-12-08T06:34:48.273192-0300 taler-exchange-wirewatch-192292 INFO New poll FD is -1 2023-12-08T06:34:48.273676-0300 pq-192292 ERROR Database connection to 'postgresql://localhost:5432/exchange' failed: connection to s erver at "localhost" (::1), port 5432 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? connection to server at "localhost" (127.0.0.1), port 5432 failed: Connection refused Is the server running on that host and accepting TCP/IP connections? 2023-12-08T06:34:48.273696-0300 taler-exchange-wirewatch-192292 INFO Starting transaction `begin_shard' 2023-12-08T06:34:48.273709-0300 pq-192292 ERROR Failed to execute `START TRANSACTION ISOLATION LEVEL SERIALIZABLE': (null)/(null)//PGRES_FATAL_ERROR/ connection pointer is NULL 2023-12-08T06:34:48.273718-0300 taler-exchange-wirewatch-192292 ERROR Failed to start transaction 2023-12-08T06:34:48.273725-0300 taler-exchange-wirewatch-192292 ERROR Assertion failed at pg_start.c:51. 2023-12-08T06:34:48.273733-0300 taler-exchange-wirewatch-192292 ERROR Assertion failed at pg_begin_shard.c:48. 2023-12-08T06:34:48.273740-0300 taler-exchange-wirewatch-192292 ERROR Failed to obtain starting point for montoring from database! 2023-12-08T06:34:48.273757-0300 pq-192292 ERROR PQprepare (`UPDATE work_shards SET last_attempt=0 WHERE job_name=$1 AND start_row=$2 AND end_ro w=$3;' as `abort_shard') failed with error: connection pointer is NULL 2023-12-08T06:34:48.273770-0300 taler-exchange-wirewatch-192292 ERROR Assertion failed at pg_abort_shard.c:43. 2023-12-08T06:34:48.273784-0300 taler-exchange-wirewatch-192292 WARNING Failed to abort work shard on shutdown | ||||
| Tags | No tags attached. | ||||
|
|
Eh, this looks like perfectly expected behavior. Note that we *expect* all components to be automatically re-started by systemd, and here we seem to have had a mid-shard hard transaction failure, which actually likely requires manual repair via taler-exchange-dbinit -s to resume nicely in a timely fashion. So I'm not sure any change is needed here. |
|
|
(oh, and this is not a crash: the program merely shuts down, and as it cannot cleanly tell the DB that it is done, it complains ;)) |
|
|
ACK |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-12-12 20:10 | sebasjm | New Issue | |
| 2023-12-12 20:10 | sebasjm | Status | new => assigned |
| 2023-12-12 20:10 | sebasjm | Assigned To | => Christian Grothoff |
| 2023-12-13 05:05 | Christian Grothoff | Note Added: 0020746 | |
| 2023-12-13 05:05 | Christian Grothoff | Assigned To | Christian Grothoff => sebasjm |
| 2023-12-13 05:05 | Christian Grothoff | Status | assigned => feedback |
| 2023-12-13 05:42 | Christian Grothoff | Note Added: 0020748 | |
| 2023-12-13 05:42 | Christian Grothoff | Severity | crash => trivial |
| 2023-12-13 12:31 | sebasjm | Status | feedback => resolved |
| 2023-12-13 12:31 | sebasjm | Resolution | open => fixed |
| 2023-12-13 12:31 | sebasjm | Note Added: 0020750 | |
| 2023-12-22 14:39 | Christian Grothoff | Target Version | => 0.9.4 |
| 2024-01-12 14:05 | Christian Grothoff | Category | exchange Postgres DB backend => exchange |
| 2024-02-10 23:31 | Christian Grothoff | Fixed in Version | => 0.9.4 |
| 2024-03-07 20:49 | Christian Grothoff | Status | resolved => closed |
