[Samba] 3.0.24 weird errors, harmless?
Schaefer Jr, Thomas R.
tom at umsl.edu
Wed Mar 7 15:00:10 GMT 2007
A couple weeks ago I upgraded my servers from 3.0.14a to 3.0.24. My
main server generally has about 800 to 1200 people connected to it at
any given time. Its a Solaris 8/Sparc system, samba is configured as
security = domain . Everything seems to be functioning fine, I haven't
noticed any odd behavior, haven't had any complaints.
But, a few weird errors have got me concerned.
1) I often run smbstatus, about once every dozen or so times of running
smbstatus I'll get an error like this..
tdb(/usr/local/samba/var/locks/locking.tdb): rec_read bad magic
0xd9fee666 at offset=250092, I run smbstatus again, literally 1 second
later and its fine.
2) Every several seconds to every several minutes depending, I guess
depending on how heavy the server's being worked I'm getting log.smbd
[2007/03/07 08:16:57, 0] passdb/pdb_smbpasswd.c:startsmbfilepwent(204)
startsmbfilepwent_internal: unable to open file
/usr/local/samba/private/smbpasswd. Error was
: Too many open files
[2007/03/07 08:16:57, 0]
Unable to open passdb database.
3) Again in log.smbd, I'm frequently seeing.
Failed to set socket option SO_KEEPALIVE (Error Invalid argument)
[2007/03/07 08:44:15, 0] lib/util_sock.c:set_socket_options(261)
Failed to set socket option TCP_NODELAY (Error Invalid argument)
[2007/03/07 08:44:15, 0] lib/util_sock.c:get_peer_addr(1229)
getpeername failed. Error was Transport endpoint is not connected
[2007/03/07 08:44:15, 0] lib/util_sock.c:write_data(562)
write_data: write failure in writing to client 18.104.22.168. Error
I went back and looked at my old 3.0.14a logs, I wasn't getting any of
this stuff logged before the upgrade, wasn't having the smbstatus issue
I've got another Samba server, using the identical compilation of Samba,
configured almost identically, it generally has 300 - 400 users
connected to it and I am not seeing any of these issues with it.
University of Missouri Saint Louis
More information about the samba