[Mldonkey-bugs] [Bug #985] NetBSD: Too many open files

[nobody]

=================== BUG #985: LATEST MODIFICATIONS ==================
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=985&group_id=1409

Changes by: mldonkey admin <address@hidden>
Date: 2002-Sep-22 13:52 (GMT)

            What     | Removed                   | Added
---------------------------------------------------------------------------
     Reproducibility | How long does it take to get the "too many open files" 
message ? 

Before it happens, set the "net_debug" and "verbose" options to true (with CVS 
version), and keeps a log of mldonkey output (pipe it to a file).
Keep also a telnet session to mldonkey opened, so that you are sure to be able 
to send commands when no fd will be available.

 When it happens:
* In mldonkey telnet, call the "debug_socks" command, verify that mldonkey has 
placed some debug information on sockets in the log.
* In the shell, do a "netstat -nap", check mldonkey pid, go in /proc/<pid>/fd 
(if you have it), and "ls -l", use the "lsof" program on mldonkey (if you have 
it). Take as much information as you can (downloads.ini for example too), put 
them in a tar file, compress it (bzip2 or gzip) and upload it here in a bug 
report. 

Do you have special behavior of your connection between the time you start 
mldonkey and the error (ppp connection reseted, IP changed, etc ?).
 | 


------------------ Additional Follow-up Comments ----------------------------
How long does it take to get the "too many open files" message ? 

Before it happens, set the "net_debug" and "verbose" options to true (with CVS 
version), and keeps a log of mldonkey output (pipe it to a file).
Keep also a telnet session to mldonkey opened, so that you are sure to be able 
to send commands when no fd will be available.

 When it happens:
* In mldonkey telnet, call the "debug_socks" command, verify that mldonkey has 
placed some debug information on sockets in the log.
* In the shell, do a "netstat -nap", check mldonkey pid, go in /proc/<pid>/fd 
(if you have it), and "ls -l", use the "lsof" program on mldonkey (if you have 
it). Take as much information as you can (downloads.ini for example too), put 
them in a tar file, compress it (bzip2 or gzip) and upload it here in a bug 
report. 

Do you have special behavior of your connection between the time you start 
mldonkey and the error (ppp connection reseted, IP changed, etc ?).



=================== BUG #985: FULL BUG SNAPSHOT ===================


Submitted by: None                      Project: mldonkey, a free e-Donkey 
client
Submitted on: 2002-Aug-13 12:59
Category:  Core                         Severity:  5 - Major                    
Bug Group:  None                        Resolution:  Remind                     
Assigned to:  mldonkey                  Status:  Open                           
Release:  None                          Release:                                
Platform Version:  None                 Binaries Origin:  None                  
Reproducibility:                        

Summary:  NetBSD: Too many open files

Original Submission:  Hi,

my logfile is filled with endless repetitions of:

+++ Exception BEFORE CONNECT socket failed: Too many open files
Exception socket failed: Too many open files in client connection

What does it mean - how can I solve this problem?

Thanks,
 Andreas

mldonkey is great! I'd be happy to provide some code for it,
but why the heck did you use ocaml and not something less
exotic? :)

Follow-up Comments
*******************

-------------------------------------------------------
Date: 2002-Sep-22 13:52             By: mldonkey
How long does it take to get the "too many open files" message ? 

Before it happens, set the "net_debug" and "verbose" options to true (with CVS 
version), and keeps a log of mldonkey output (pipe it to a file).
Keep also a telnet session to mldonkey opened, so that you are sure to be able 
to send commands when no fd will be available.

 When it happens:
* In mldonkey telnet, call the "debug_socks" command, verify that mldonkey has 
placed some debug information on sockets in the log.
* In the shell, do a "netstat -nap", check mldonkey pid, go in /proc/<pid>/fd 
(if you have it), and "ls -l", use the "lsof" program on mldonkey (if you have 
it). Take as much information as you can (downloads.ini for example too), put 
them in a tar file, compress it (bzip2 or gzip) and upload it here in a bug 
report. 

Do you have special behavior of your connection between the time you start 
mldonkey and the error (ppp connection reseted, IP changed, etc ?).

-------------------------------------------------------
Date: 2002-Sep-22 13:34             By: None
I've now got two systems running the CVS version, one has this problem and the 
other doesn't.  I've had a look at the setup and the only difference I can see 
is that one is linked against libz (the working one) and the other isn't.

I've now recompiled the broken one with libz-devel installed (but it's also 
with a newer CVS version) so I'll see whether this makes a difference.

If anyone else suffering this problem has their mldonkey executable linked 
against libz, can they say so?  Or can any of the developers suggest whether 
this would/would not lead to these (or any other) problems?

Cheers,
Robin

-------------------------------------------------------
Date: 2002-Sep-22 09:33             By: None
I've got OpenBSD and this error is solved (on my system) by reducing 
max_open_connections to 37 (when i put there 38, error occures).

Please help us because such small number means small downloads (at least for 
me)!

Regards
BusteR

-------------------------------------------------------
Date: 2002-Sep-17 13:09             By: mldonkey
Not enough information to solve this bug. An important bug, though


-------------------------------------------------------
Date: 2002-Sep-16 08:26             By: None
Not just NetBSD, I have this problem on Linux as well:

After running mldonkey for under 12 hours it has 995 file descriptors allocated 
to sockets (from /proc/mldonkey_PID/fd) and only 13 client and 2 server sockets 
in use (from netstat).  There are 27 file descriptors allocated to shared & 
config files (of which 11 are marked deleted). This is with 
max_opened_connections set to only 200, and mainly downloading.

-------------------------------------------------------
Date: 2002-Sep-15 16:13             By: None
I've got the same.. I don't know what's wrong. Since it prints out a handled 
error msg someone of the developers should be able to take a look on it. 
Hopefully ;)

-------------------------------------------------------
Date: 2002-Sep-15 16:11             By: None
I've got the same.. I don't know what's wrong. Since it prints out a handled 
error msg someone of the developers should be able to take a look on it. 
Hopefully ;)

-------------------------------------------------------
Date: 2002-Sep-10 13:19             By: None
I agree with you....
I have compiled mldonkey for OpenBSD-i386 and the same problem happens.
Just try to reduce your maximum connections...
But this will not solve your problem permanently.

-------------------------------------------------------
Date: 2002-Sep-10 13:18             By: None
I agree with you....
I have compiled mldonkey for OpenBSD-i386 and the same problem happens.
Just try to reduce your maximum connections...
But this will not solve your problem permanently.

-------------------------------------------------------
Date: 2002-Sep-10 13:17             By: None
I agree with you....
I have compiled mldonkey for OpenBSD-i386 and the same problem happens.
Just try to reduce your maximum connections...
But this will not solve your problem permanently.


CC list is empty


No files currently attached


For detailed info, follow this link:
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=985&group_id=1409