View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002182 | GNUnet | transport service | public | 2012-02-27 22:37 | 2012-06-02 19:15 |
| Reporter | Christian Grothoff | Assigned To | Matthias Wachs | ||
| Priority | urgent | Severity | major | Reproducibility | have not tried |
| Status | closed | Resolution | open | ||
| Product Version | Git master | ||||
| Target Version | 0.9.3 | Fixed in Version | 0.9.3 | ||
| Summary | 0002182: Assertion failed at transport_api.c:506. after Assertion failed at gnunet-service-core_kx.c:1158. | ||||
| Description | The core assertion killed the core process, causing a new one to be created, which then presumably connected to a running transport service. The transport service then generates a 'disconnect' event without a matching 'connect' event. | ||||
| Steps To Reproduce | http://gnunet.org:8010/builders/lenny-sparc64-wachs/builds/921/steps/tests%20mesh/logs/stdio | ||||
| Tags | No tags attached. | ||||
|
|
Easiest way: remove the break and just do not forward the disconnect |
|
|
2nd possibility: have a list for every client which peers he knows, just notify about peers this client knows imho: no benefit over easy solution |
|
|
Right now, I get (rarely): Mar 12 12:37:15-914862 core-28754 WARNING External protocol violation detected at gnunet-service-core_kx.c:1383. (update: fixed in SVN 21269 as part of 0001969). Still, the original issue remains. |
|
|
Ok I double checked the code ... It's implemented as intended: When a new client connects, transport iterates over all nodes, and puts the connect notfications in the send queue to transmit it to the client |
|
|
Tested transport_api connect and reconnect: - Connected with watchdog to transport and got notified about connected peers - Killed transport service - watchdog reconnected and got notifoed about core and transprot connections Everything works as expected... |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-02-27 22:37 | Christian Grothoff | New Issue | |
| 2012-02-27 23:07 | Christian Grothoff | Assigned To | => Matthias Wachs |
| 2012-02-27 23:07 | Christian Grothoff | Priority | high => urgent |
| 2012-02-27 23:07 | Christian Grothoff | Status | new => assigned |
| 2012-02-27 23:07 | Christian Grothoff | Category | core service => transport service |
| 2012-02-27 23:07 | Christian Grothoff | Description Updated | |
| 2012-02-28 09:16 | Matthias Wachs | Note Added: 0005526 | |
| 2012-02-28 09:19 | Matthias Wachs | Note Added: 0005527 | |
| 2012-02-28 09:19 | Matthias Wachs | Status | assigned => feedback |
| 2012-02-28 09:56 | Christian Grothoff | Status | feedback => assigned |
| 2012-03-12 13:15 | Christian Grothoff | Note Added: 0005602 | |
| 2012-05-04 14:43 | Christian Grothoff | Note Edited: 0005602 | |
| 2012-05-04 14:48 | Matthias Wachs | Target Version | => 0.9.3 |
| 2012-05-04 16:08 | Matthias Wachs | Note Added: 0005780 | |
| 2012-05-04 16:32 | Matthias Wachs | Note Added: 0005781 | |
| 2012-05-06 14:00 | Christian Grothoff | Status | assigned => resolved |
| 2012-05-06 14:00 | Christian Grothoff | Fixed in Version | => 0.9.3 |
| 2012-06-02 19:15 | Christian Grothoff | Status | resolved => closed |
