Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

A problem: too many open files

Status
Not open for further replies.

tg2003

IS-IT--Management
Joined
Feb 6, 2003
Messages
270
Location
IL
Hello, I'm using Samba v2.2.8a on Solaris 8 machine which connecting to winXP/Win2000 machines.
The Windows users complain about slow performance. I think it may caused by the samba.
I see on many of the hosts' logs such message: "Unable to open log files log.<hostname> . too many open files".

What's that mean? the filesystem of the logs is not full. Is the problem related to the OS or to the samba? how to solve it?

thanx!
 
This is a rather vague post.

You really need to gather more information, not only for us, but to help yourself as well.

When did this start? What recent changes?

Did samba run cleanly ever?

When they are slow, is that when you get these errors, or are these errors always around?

Also, define slow performance? The workstations are always slow, or just opening files, editing files, saving files?

Does everybody have this problem?

What type of data do they access? What database types?

Also, seeing your smb.conf might be helpful.


Matt J.

Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.
 
HI,
thanx for answering.
I add here more details:
The problem is for a month approx.
The main purpose of the samba is for sharing files (unix-windows) for ClearCase ( a Software Configuration Managment tool). The users are getting to specific files resides on the unix server.
Everybody has that problem, and the above message ("Unable to open log files log.<hostname> . too many open files") is written into every log's host. the problem that users fill is quite slow response time and slow machine when reading/writing files which resides on the unix machine.
When I'm using the smbstatus, I see many of locked files.

Here's the smb.conf:
workgroup = xxxxxxxx
security = DOMAIN
encrypted Passwords = Yes
password serer = xxxxxxxx
log file = /var/samba/log.%m
max log size = 50
max open files = 32768
socket options = TCP_NODELAY
local master = no
kernel oplocks = No
case sensitive = No
preserve case = Yes
create mask = 0775
directory mask = 0775
wins server = xxxxxxxxxxxx
keepalive = 0

( I use the xxxxxxxxxxx since this information is confidential and irelevant)

Thanks !!
 
Try changing :
log file = /var/samba/log.%m
To
log file = /var/samba/log.access

Add :
socket options = TCP_NODELAY SO_RCVBUF=8192 IPTOS_LOWDELAY SO_RCVBUF=8192 SO_SNDBUF=8192

wins server = XXX.XXX.XXX.XXX
wins proxy = yes

It MAY also help to add the IP address of the Domain Controller to the hosts file.


&quot;If you always do what you've always done, you will always be where you've always been.&quot;
 
thanx! I try it asap
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top