View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002211 | GNUnet | transport service | public | 2012-03-11 23:25 | 2012-06-02 17:15 |
| Reporter | Christian Grothoff | Assigned To | Matthias Wachs | Due Date | |
| Priority | urgent | Severity | major | Reproducibility | random |
| Status | closed | Resolution | fixed | ||
| Product Version | Git master | ||||
| Target Version | 0.9.3 | ||||
| Summary | 0002211: transport service sometimes hangs and then stops to process client requests | ||||
| Description | Specifically, once this happens gnunet-peerinfo -i (without -n) stops to resolve transport addresses. Similar problems arise with gnunet-peerinfo-gtk. Killing the transport service (and having it be restarted by arm) solves the problem. It is unclear if other functions of the transport service (such as message delivery, etc.) are affected or not. | ||||
| Tags | No tags attached. | ||||
| This simply happened now twice after I had a transport service run for a while. I don't know of a good specific way to trigger the problem (yet). | |
| IMHO: this is just a reverse lookup resolver timeout. timeout for gnunet-transport was quite long (1 min). Decreased the timeout and added functionality to gnunet-transport to print message | |
| fix for gnunet-transport in 20863. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-03-11 23:25 | Christian Grothoff | New Issue | |
| 2012-03-11 23:25 | Christian Grothoff | Status | new => assigned |
| 2012-03-11 23:25 | Christian Grothoff | Assigned To | => Matthias Wachs |
| 2012-03-11 23:25 | Christian Grothoff | Note Added: 0005600 | |
| 2012-04-02 14:48 | Matthias Wachs | Note Added: 0005683 | |
| 2012-04-02 14:48 | Matthias Wachs | Status | assigned => resolved |
| 2012-04-02 14:48 | Matthias Wachs | Resolution | open => fixed |
| 2012-04-02 14:48 | Matthias Wachs | Note Added: 0005684 | |
| 2012-06-02 17:15 | Christian Grothoff | Status | resolved => closed |