aMule Bug Tracker - aMule |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001311 | aMule | External Conn | public | 2008-04-29 13:09 | 2008-08-30 13:11 |
|
| Reporter | wild_oscar | |
| Assigned To | Wuischke | |
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | |
| Platform | | OS | | OS Version | |
| Product Version | SVN | |
| Target Version | | Fixed in Version | | |
| Fixed in Revision | |
| Operating System | Any |
|
| Summary | 0001311: Amulegui cannot connect to amuled after a few hours |
| Description | Deleting the .aMule directory and starting from scratch (but keeping the config and credits files), amuled will start to hash the shared files. Amulegui can connect without a problem right after amuled starts. However, after a few hours of amuled connection, amulegui will not show download/upload files, connection status, D/U speed and search won't work. At the same time, amulecmd and amuleweb work without a problem, only amulegui is affected. |
| Steps To Reproduce | |
| Additional Information | http://forum.amule.org/index.php?topic=14876.0 [^] |
| Tags | No tags attached. |
| Relationships | | related to | 0001146 | resolved | Wuischke | Very unstable "content" in connection from amulegui(win32) to amuled(linux) |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2008-04-29 13:09 | wild_oscar | New Issue | |
| 2008-04-29 13:09 | wild_oscar | Operating System | => Any |
| 2008-04-30 02:56 | wild_oscar | Note Added: 0002794 | |
| 2008-05-03 12:18 | sturedman | Note Added: 0002795 | |
| 2008-05-05 12:41 | wild_oscar | Note Added: 0002806 | |
| 2008-05-08 16:20 | wild_oscar | Note Added: 0002808 | |
| 2008-08-30 13:11 | Wuischke | Relationship added | related to 0001146 |
| 2008-08-30 13:11 | Wuischke | Status | new => resolved |
| 2008-08-30 13:11 | Wuischke | Resolution | open => fixed |
| 2008-08-30 13:11 | Wuischke | Assigned To | => Wuischke |
|
Notes |
|
|
|
|
It seems that the file known.met may be responsible for this problem - deleting this file will make amulegui connect correctly for a few hours (until amuled rebuilds it...). |
|
|
|
|
I've played around a bit with it and found:
- The remote gui protocol is very sensitive to dropped packets. If packets are lost, the whole connection goes out of sync and displays nothing useful anymore permanently (until you restart the remotegui).
- Remote packets are affected by the upload bandwidth throttler. That's why deleting known.met helps. It breaks your upload for a while, because aMule has to rehash all shared files. And during this time, the remotegui works better because there is more UL bandwidth available.
- Even with UL bandwidth = 0 (unlimited) it works sometimes, sometimes not (though better than with limit).
- with lots of files it works worse than with few, because more data has to be transferred.
Looks like the protocol needs some rework... |
|
|
|
|
|
|
|
|
|