aMule Bug Tracker - aMule
View Issue Details
0000130aMuleMessagespublic2004-08-27 20:582004-08-30 18:55
PythonZuul 
 
normalmajoralways
closedopen 
 
 
0000130: client "xxx" caused an error 0, 107, 115,11 happening for most clients
In the window view of amule journal
I always get the error 0,107,115 for most of clients amule is connecting with.

Because I didn't find anywhere an explanation of errors 0,107,11 or 115. I'm reporting this as a bug

Most are error 0 (+-90%)
then 115, 107
and sometimes 11

I checked automatic drop of full queue, not needed sources,..

Perhaps it matters

More generaly it could be very usefull to have a short explanation of the errors, the possible causes, and ways to fix it.

I search the faq and the web, but i found no info.


Since i have an error message every 2 sec
It Take a lot of time (minutes!)for every amule screen to refresh.
I have a dozen files in the download queue
And a very small upload queue
30 in standby (nearly sure it's abnormal)

It can still upload and download.
I have mandrake 9.10 installed
No other process consumming important ressources
I did not installed the SUI
I have a relatively fast connection (1024/128)
No proxy, the default ports are open.

No tags attached.
Issue History
2004-08-27 20:58PythonZuulNew Issue
2004-08-28 11:56PythonZuulNote Added: 0000216
2004-08-30 18:55XaignarStatusnew => closed
2004-08-30 18:55XaignarNote Added: 0000221

Notes
(0000216)
PythonZuul   
2004-08-28 11:56   
As a result of this problem the upload client list become empty after few hours.

So every client amule is connecting with are disconnected time after time
(0000221)
Xaignar   
2004-08-30 18:55   
These "errors"* are only meant for developers or people doing specific debugging. I'd suggest that you just disable verbose messages and ignore this. Enabling verbose is also known to cause much greater cpu-usage, so disabling it might help.

* They are not really errers as such. 0 for instance means "No Error".