I was wondering if anyone could help me with this problem. I am running
samba 2.2.1a on a Sun Solaris 5.8 server. I have a bunch of windows 2000
machines connecting to this server to reference a small configuration file
(but I might have 30 or 100 machines logging in with this id at about the
same time). Anyway, it will work fine for weeks, but then five times now
samba "breaks" as seen below with the oplock errors...many per second.
These continue until the machine runs out of swap space and samba has to be
killed or the server rebooted to recover. Has anyone seen this or have any
ideas what could be causing it? It is not sufficient? Are there parameters
that I could use to help this? My smb.conf file and some of log.smbd is
included:
[global]
workgroup = EHPLANT
security = SERVER
password server = ehdc1
name resolve order = wins host bcast
deadtime = 5
lm announce = False
wins server = 191.29.78.41
lock dir = /pw/export/prod/svr4/samba/locks
log level = 1
[export]
path = /pw/export
read list = nobody
writeable = Yes
create mask = 0644
{log.smbd extract}:
[2001/09/20 13:35:15, 1] smbd/service.c:(646)
c0087976 (191.29.248.151) closed connection to service export
[2001/09/20 13:35:16, 1] smbd/service.c:(646)
bpc99103 (191.29.99.103) closed connection to service export
[2001/09/20 13:35:21, 0] smbd/oplock.c:(997)
request_oplock_break: no response received to oplock break request to pid
13400 on port 35754 for dev = 2a861b0, inode = 30739
for dev = 2a861b0, inode = 30739, tv_sec = 3baa2897, tv_usec = b8c54
[2001/09/20 13:35:21, 0] smbd/oplock.c:(997)
request_oplock_break: no response received to oplock break request to pid
13400 on port 35754 for dev = 2a861b0, inode = 30739
for dev = 2a861b0, inode = 30739, tv_sec = 3baa2897, tv_usec = b8c54
[2001/09/20 13:35:21, 0] smbd/oplock.c:(997)
request_oplock_break: no response received to oplock break request to pid
13400 on port 35754 for dev = 2a861b0, inode = 30739
for dev = 2a861b0, inode = 30739, tv_sec = 3baa2897, tv_usec = b8c54
etc, etc, etc...many per second until the server crashes due to lack of swap
space or samba is killed and restarted.
----------------------------------------------------------------------------
--------------------------------------------------
Evan Milewski
CSC System Administrator
Pratt & Whitney campus
milewse@pweh.com