Hi forum,
Here are the symptoms:
Periodically, and especially when our dual-quad-core file servers are under load, the Windows Server 2003 systems report:
Quote:
"Insufficient system resources exist to complete the requested service"
|
With log level turned up to 6 in smb.conf, the only thing logged at the exact moment of failure is:
Quote:
@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^ @^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^ @^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^v
|
(no exaggeration, it's all At's and Carat's and an arbitrary seeming number of 'em. A Google search for even the phonetic 'at'+'carat' doesn't return a thing...)
...which leads me to many various docs, including a KB which indicates NTBackup has such and such an issue with the blob of data that certain apps send instead of chunking it out, and to assuage the issue one can simply increase PagedPoolSize etc, and at this point I'm near to insane with the babysitting and restarting samba when my monitors report they can't get the directory listing any longer.
Configuration is fairly simple. Here's my smb.conf sans anything that might get me in trouble:
Code:
[global]
log file = /var/log/samba/%m.log
log level = 3
socket options = TCP_NODELAY SO_RCVBUF=8162 SO_SNDBUF=8162 IPTOS_LOWDELAY
smb ports = 445
oplocks = no
dns proxy = yes
disable netbios = yes
server string = SATA04
workgroup = TPV
security = SHARE
max log size = 50
unix extensions = no
local master = no
os level = 0
load printers = no
map to guest = bad user
deadtime = 1
...plus some share definitions which basically look like:
Code:
path = /some/path
force directory mode = 777
force create mode = 777
comment = This is a comment
create mode = 777
directory mode = 777
write list = @writers
guest ok = yes
DNS is functional, CentOS is up to date on one system, but the same issue occurs on a RHEL4 system with a completely different version of samba, so I guess the fact that CentOS is current is immaterial.
I've done tcpdump's and captured the packets that are being transmitted at the time of the failure between the linux and windows systems and there are no errors (like invalid checksums, or otherwise transport issues).
Thanks in advance...
A