Print

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

[prilmeie]

Hi!

I don't know whether this is a bug or not. My amule (CVS version from sunday 03.April) can succesfully connect, but is not up- or downloading anything.

I am using amuled

Code: [Select]

aMulecmd$ Stats
 > Connected to Razorback 2 [195.245.244.243:4661] with HighID
 > Download:    0 Bytes/sec
 > Upload:      0 Bytes/sec
 > Clients in queue:    0
 > Total sources:       0
output on stdout:

Code: [Select]

amule@vl02s32:~$ amuled -o
Logging to stdout enabled
Initialising aMule
Checking if there is an instance already running...
2005-04-05 17:46:47: Creditfile loaded, 5050 clients are known
2005-04-05 17:46:47: Loaded ipfilter with 0 new IP addresses.
2005-04-05 17:46:47: Loading server.met file: /home/amule/.aMule/server.met
2005-04-05 17:46:48: 1233 servers in server.met found
Loading temp files from /home/amule/.aMule/Temp.
Loading PartFile 17 of 17
All PartFiles Loaded.
2005-04-05 17:46:48: Found 17 part files
2005-04-05 17:46:48: *** TCP socket (ECServer) listening on 0.0.0.0:4712
ListenSocket: Ok.

*** TCP socket (ECServer) listening on 0.0.0.0:4712
*** Server UDP socket (TCP+3) at 0.0.0.0:4665
*** TCP socket (TCP) listening on 0.0.0.0:4662
*** Client UDP socket (extended eMule) disabled on preferences
Adding file /home/amule/.aMule/Temp/042.part.met to shares
Adding file /home/amule/.aMule/Temp/037.part.met to shares
Adding file /home/amule/.aMule/Temp/036.part.met to shares
Adding file /home/amule/.aMule/Temp/034.part.met to shares
Adding file /home/amule/.aMule/Temp/027.part.met to shares
Adding file /home/amule/.aMule/Temp/017.part.met to shares
Adding file /home/amule/.aMule/Temp/013.part.met to shares
Adding file /home/amule/.aMule/Temp/012.part.met to shares
Adding file /home/amule/.aMule/Temp/011.part.met to shares
Adding file /home/amule/.aMule/Temp/010.part.met to shares
Adding file /home/amule/.aMule/Temp/007.part.met to shares
Adding file /home/amule/.aMule/Temp/006.part.met to shares
Adding file /home/amule/.aMule/Temp/005.part.met to shares
Adding file /home/amule/.aMule/Temp/004.part.met to shares
Adding file /home/amule/.aMule/Temp/002.part.met to shares
Adding file /home/amule/.aMule/Temp/001.part.met to shares
Empty dir /home/amule/.aMule/Incoming/ shared
2005-04-05 17:46:48: Found 16 known shared files
2005-04-05 17:46:48: Connecting
2005-04-05 17:46:48: Connecting to
2005-04-05 17:46:48: Connecting to ### SauGeileGirls ### (81.23.250.167 - 81.23.
250.167:4242)
aMuleweb is running on pid 23812
2005-04-05 17:46:51: Connecting to Razorback 2 (195.245.244.243 - 195.245.244.24
3:4661)
2005-04-05 17:46:51: AICH Thread: Syncronization thread started.
2005-04-05 17:46:51: Connecting client: aMuleweb CVS
2005-04-05 17:46:51: Access granted.
2005-04-05 17:46:51: AICH Thread: Masterhashes of known files have been loaded.
2005-04-05 17:46:51: AICH Thread: No new files found.
2005-04-05 17:46:51: AICH Thread: Terminated.
2005-04-05 17:46:51: Connected to Razorback 2 (195.245.244.243:4661)
CServerSocket: connection refused or timed out
CServerSocket: destroying socket 0x869c858
Netstat -an output (own IP address replaced by XXX.XXX.XXX.XXX):

Code: [Select]

tcp        0      0 XXX.XXX.XXX.XXX:993        0.0.0.0:*               LISTEN
tcp        0      0 XXX.XXX.XXX.XXX:389        0.0.0.0:*               LISTEN
tcp        0      0 XXX.XXX.XXX.XXX:4712       0.0.0.0:*               LISTEN
tcp        0      0 XXX.XXX.XXX.XXX:10024      0.0.0.0:*               LISTEN
tcp        0      0 XXX.XXX.XXX.XXX:10025      0.0.0.0:*               LISTEN
tcp        0      0 XXX.XXX.XXX.XXX:3306       0.0.0.0:*               LISTEN
tcp        0      0 XXX.XXX.XXX.XXX:143        0.0.0.0:*               LISTEN
tcp        0      0 XXX.XXX.XXX.XXX:783        0.0.0.0:*               LISTEN
tcp        0      0 XXX.XXX.XXX.XXX:80         0.0.0.0:*               LISTEN
tcp        0      0 XXX.XXX.XXX.XXX:4662       0.0.0.0:*               LISTEN
tcp        0      0 XXX.XXX.XXX.XXX:22         0.0.0.0:*               LISTEN
tcp        0      0 XXX.XXX.XXX.XXX:7000       0.0.0.0:*               LISTEN
tcp        0      0 XXX.XXX.XXX.XXX:25         0.0.0.0:*               LISTEN
tcp        0      0 XXX.XXX.XXX.XXX:443        0.0.0.0:*               LISTEN
tcp        0      0 XXX.XXX.XXX.XXX:636        0.0.0.0:*               LISTEN
tcp        0      0 XXX.XXX.XXX.XXX:43091      195.245.244.243:4661    CONNECTED
tcp        1      0 XXX.XXX.XXX.XXX:4662       195.245.244.241:56982   CLOSE_WAIT
tcp        0   1824 XXX.XXX.XXX.XXX:22         195.27.163.196:56069    CONNECTED
tcp        0      0 127.0.0.1:43089         XXX.XXX.XXX.XXX:4712       CONNECTED
tcp        0      0 XXX.XXX.XXX.XXX:4712       127.0.0.1:43089         CONNECTED
tcp        0      0 XXX.XXX.XXX.XXX:22         195.27.163.196:45508    CONNECTED
udp        0      0 XXX.XXX.XXX.XXX:4665       0.0.0.0:*
What is wrong here? - Do you need additional informations?

Best regards,
prilmeie

[wardevil]

I guess u are not the only one with that problem....but i find out a curious thing....amuled stop responding after it connects to a server with wxGTK-2.6.0 ....but with wxGTK-2.5.5 amuled runs fine until 5 minutes or so....when it crashes with a backtrace.....
So...is this an amuled bug or wx bug?  ?(

[lfroen]

I guess, it's amuled bug, BUT:
amuled socket code has been reworked. Please, take cvs snapshot version and test it. Feel welcomed to report any issues

[wardevil]

Well....I am posting the results of the amuled cvs today.....guess what?
Now it works....very well until now.....
Thanks lfroen for catching the stupid bug.... :baby:

Now i have to find a way to make HDDs from sand.....

Excelent work....

Cheers.....