aMule Forum
English => aMule Help => Topic started by: steinex on November 13, 2008, 03:48:25 PM
-
Hi, I'm running amuled 2.2.2 on Debian. On my laptop, latest aMule Remote GUI is installed. I configured amuled properly, and I have no problems connecting from the laptop. All works as aspected. However, after some time when I restart aMule Remote GUI, it won't connect to amuled properly anymore. Connection seems to get established, but my downloading-queue-list won't show up anymore and stuff like that. If I connect to amuled via amuleweb, all seems fine though, so I guess this is some problem with the Remote GUI stuff.
I understand that this is experimental code, but want to ask anyway if someone has a hint how to solve or at least workaround this problem.
BTW, I wanted to give amuled from CVS (or SVN?) a shot to try if it's fixed there, but I can't find a working repository anywhere?
Clues are *very* welcome.
TIA,
Frank
-
Latest snapshot is here (http://forum.amule.org/index.php?topic=16043).
Please check amuled's logfile after the failed connect.
-
I have similar problems. After long time run, amuled is hard to get connected from amule remote gui.This is easy to reproduce. Run 10+ tasks and wait a few days, then try to use the remote gui connect to amuled. You will find it is hard to connect. ??? ??? ???
-
Please check amuled's logfile after the failed connect.
-
Beside supporting us with the log of aMule after the unsucessfull conect attem, could you please check out with top how many CPU the amuled process is using, if you have this problem?
-
I attached the wireshark sniff image.
You can see 200 seconds delay after amule gui send "amule-remote.....0x0001..........v(.+.9..S-6......."...".
I checked the top for cpu usage.The average amuled cpu usage was below 15%.