Hello,
we're running 2.2.1a on a production server. Lately, it's been giving
us troubles. Monday mordning, this moring, and 2 times more during
today, samba stopped responding to all requests from Windows (2000)
clients. This has happened once before a week ago, and once several
weeks ago. Today it seems to be getting much worse.
If left un-attended the system will eventually run out of file
descriptors, requiring a reboot because you can't even login. In fact,
a hard reset might even be required if the shutdown scripts can't even
run.
If detected in time, a simple /etc/init.d/samba restart will suffice.
The symptomes is essentially "nothing works" on the Windows clients.
smbd/nmnd are still running though.
The logs do have some interesting tidbits. Since the last 3 days,
messages like the following have began showing up in the smbd log:
[2001/12/11 09:06:02, 0] smbd/oplock.c:oplock_break(815)
oplock_break: unable to re-become user!Shutting down server
[2001/12/11 09:06:56, 0] lib/fault.c:fault_report(40)
==============================================================[2001/12/11
09:06:56, 0] lib/fault.c:fault_report(41)
INTERNAL ERROR: Signal 11 in pid 2576 (2.2.1a)
Please read the file BUGS.txt in the distribution
[2001/12/11 09:06:56, 0] lib/fault.c:fault_report(43)
==============================================================[2001/12/11
09:06:56, 0] lib/util.c:smb_panic(1101)
PANIC: internal error
[2001/12/11 09:06:56, 0] locking/locking.c:delete_fn(255)
locking : delete_fn. LOGIC ERROR ! Entry for pid 2576 and it no longer exists
!
A zcat smbd.log.1(2,3) | grep fault | wc -l tells me that we're
getting perhaps 5 or so a day for the last 3 days, except for today -
now we're getting aroung 10-25. So I definitely think it's related.
Has anyone got a clue what the problem might be? It's been a while
since we touched the server; and when we did we mostly just upgraded
the kernel and reconfigured some networking stuff. We didn't mess
around with samba, we didn't perform any system-wide upgrade, etc. The
problems just showed up out of thin air as far as I can tell.
FYI, although I don't think it's related, the logs are *always*
flooded with messages like:
[2001/12/11 15:07:03, 0] smbd/password.c:authorise_login(915)
authorise_login: rejected invalid user nobody
And every once in a while something like this:
[2001/12/11 15:02:05, 0] smbd/posix_acls.c:create_canon_ace_lists(747)
create_canon_ace_lists: unable to map SID
S-1-5-21-172541935-2503484222-526327227-3069 to uid or gid.
[2001/12/11 15:02:05, 0] smbd/posix_acls.c:create_canon_ace_lists(747)
create_canon_ace_lists: unable to map SID
S-1-5-21-172541935-2503484222-526327227-3069 to uid or gid.
[2001/12/11 15:02:05, 0] smbd/posix_acls.c:create_canon_ace_lists(747)
create_canon_ace_lists: unable to map SID
S-1-5-21-172541935-2503484222-526327227-3069 to uid or gid.
Any ideas? Thanks!
--
/ Peter Schuller, InfiDyne Technologies HB
PGP userID: 0xE9758B7D or 'Peter Schuller
<peter.schuller@infidyne.com>'
Key retrival: Send an E-Mail to getpgpkey@scode.org
E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org