samba - Feb 2006 - RE: problem with Too many open files(REASON FOUND)

Hi again,

 

For what it is worth, we found out that MS Outlook on Citrix

now and then opens thousands(17-18000) of references(filehandles)

 to the same PAB(Personal Address Book) files and then

give up these references again after a while !? This was what

made Samba chooke. We will now remove all PAB access

from Outlook.

 

Sorry for wasting Samba mailing list bandwidth ;-)

 

Kind regards, Hans.

 

________________________________

From: Hans B. Randgaard 
Sent: 12. februar 2006 22:10
To: 'samba@lists.samba.org'
Subject: problem with Too many open files

 

Hi Samba community,

 

Last year we upgraded from version 3.0.10 to 3.0.20b and at the same
time

switch from NT-domain controller membership to AD membership. After this

upgrade we began to experience that drives sometimes were not mapped.

We saw this both on our Citrix servers and on our XP PCs.

A couple of weeks back we then moved to 3.0.21b in the hope that this

misbehaviour would disappear, but in fact it didn't. I noticed that we
see

the error message:

"Too many open files"

each time drives are not mapped.

 

In the log files I can see that it has happened even when we ran version
3.0.10.

 

We run Samba on Solaris and have previously increased both
"rlim_fd_cur"
and

"rlim_fd_max" to 1024. Do we need to increase these values further ?

If I do "plimit <smbd process>" it says:

  resource                current         maximum

  time(seconds)        unlimited      unlimited

  file(blocks)             unlimited      unlimited

  data(kbytes)           unlimited      unlimited

  stack(kbytes)         8192            unlimited

  coredump(blocks)   unlimited      unlimited

  nofiles(descriptors) 10020           10020

  vmemory(kbytes)    unlimited      unlimited

 

I have tried increasing "nofiles" to 20040 without any success :-(

 

Here are some examples of the full error messages from the logs:

 

[2005/04/21 08:45:36, 0] passdb/pdb_smbpasswd.c:startsmbfilepwent(204)

  startsmbfilepwent_internal: unable to open file
/usr/local/samba/private/smbpasswd. Error was: Too many open files

[2005/04/21 08:45:36, 0]
passdb/pdb_smbpasswd.c:smbpasswd_getsampwnam(1326)

  Unable to open passdb database.

 

another example:

 

[2006/01/26 08:19:06, 0] lib/debug.c:reopen_logs(591)

  Unable to open new log file /usr/local/samba/var/log.pcped250: Too
many open files

 

Have any of you experienced the same and if yes what did you do to

get Samba to behave ?

It is as if files are not closed...

 

Any help would be appreciated !

 

Kind regards, Hans.

 

PS. below is an extract of smb.conf(testparm -v) parameters(excluding
all the shares: LOTS)

 


**********************************************************************
This e-mail and any files transmitted with it are confidential and 
intended solely for the use of the individual or entity to which they 
are addressed. If you have received this e-mail in error please notify 
the system manager at helpdesk@maerskoil.com.

This e-mail and its contents do not constitute and shall not be 
considered as a financial commitment of Maersk Olie og Gas AS 
and its affiliates. 
Maersk Olie og Gas AS expressly disclaims any responsibility
as to the accuracy and use of this e-mail and its contents.
**********************************************************************

Hans B. Randgaard wrote:
> Sorry for wasting Samba mailing list bandwidth ;-)
No no, thank YOU for coming back with what you found was the actual cause /
solution. I had been keeping an eye on your thread as it was a good puzzler
indeed. Good old uncle Billy Gates strikes again!

P.S. What about switching to aaahhh, what's that thing... Thunderbird?! ;-)

-- 
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/

Remove the upper case letters NOSPAM to contact me directly.