Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[rbox]

I've got the following problems:

2004-02-08 16:07:06: aMule 1.2.4
2004-02-08 16:07:06: Found 1 known shared files
2004-02-08 16:07:13: Connecting to ...
2004-02-08 16:07:13: Fatal Error while trying to connect. Internet connection might be down
2004-02-08 16:07:13: Disconnected
2004-02-08 16:07:13: Disconnected

[ Connecting - Fatal error - Disconnected are repeated many times while connecting to server ]

2004-02-08 16:07:24: Connection established on:
2004-02-08 16:07:24: New clientid is
2004-02-08 16:07:26: Client '(null)' (IP:) caused an error: 107. Disconnecting client!
2004-02-08 16:07:28: Client '(null)' (IP:) caused an error: 107. Disconnecting client!
2004-02-08 16:07:30: Disconnected
2004-02-08 16:07:30: Client '(null)' (IP:) caused an error: 107. Disconnecting client!
2004-02-08 16:07:30: Client '(null)' (IP:) caused an error: 107. Disconnecting client!
2004-02-08 16:07:30: Client '(null)' (IP:) caused an error: 107. Disconnecting client!

So, the problems are:

1. Connection to server is established after a lot of insuccessfull attempts (while eMule (win) works fine, connection is established almost immediately).

2. After connecting to server, while source exchange is going on, all the clients are disconnected.


I use Slackware 9.1, kernel 2.4.24 (build from source), aMule 1.2.4. It seems the only client that works fine for me in linux is xMule 1.6.1, while xMule >1.6.1 and recent versions of aMule have the same problems. I tried prebuilt versions of amule/wxgtk from linuxpackages.net, tried to build everything from sources but it doensn't help.

Tried everything without any iptable filtering rules, result was the same.
It seems that something wrong with my networking or kernel, because all the *mule linux clients have similar behaviour.

Help, please.

[deltaHF]

set your upload limit a bit smaller plz ..
 
we had an ugly upload bug =< 1.2.4 and it's fixed now in cvs .. means 1.2.5 will not have it anymore

u could compile cvs right now -> http://www.amule.org/amule/thread.php?threadid=617&sid=

greets

[Kry]

1.2.5 will be out tomorrow.

[rbox]

I use a 56k modem so limits are rather small: 6 for down and 2 up kb/s.
3/1 doesn't help so I'll try the updated version.


BTW, there's a typo - Bandwith instead of Bandwidth Limits at Preferences-Connection tab.

Thank you.

[rbox]

I have compiled the current version from cvs, and now I see errors 0, 2, 84, 107 in verbose mode in log area. Result is the same - "Disconnecting client!". 107 and 0 are the most frequent.


The output of get-info.sh is as follows:

I.   Development Environment

     A. Compiler Info
        Reading specs from /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/specs Configured with: ../gcc-3.2.3/configure --prefix=/usr --enable-shared --enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose --target=i486-slackware-linux --host=i486-slackware-linux Thread model: posix gcc version 3.2.3

     B. wxWindows Info
        Version: 2.4.2
        -L/usr/local/wxBase-2.4.2/lib -pthread -lwx_base-2.4

     C. GTK Info
        GTK 1: 1.2.10
        GTK 2: 2.2.4

II.  System Environment
      ...

     B. Memory Info
        Total:   515488 kB
        Unused:  149080 kB

     C. Kernel Info
        Version: 2.4.24

     D. Library Info
        wxWindows library: libwx_gtk-2.4.so (libc6) => /usr/local/wxGTK-2.4.2/lib/libwx_gtk-2.4.so libwx_base-2.4.so (libc6) => /usr/local/wxBase-2.4.2/lib/libwx_base-2.4.so

[Kry]

those aerrors are not strange - eMule gives the same. Just disable verbose to get rid of them.

About server connection, hope new version helps you.