[Samba] log errors - worry or don't worry?

Craig White craigwhite at azapple.com
Fri Jan 30 05:52:43 GMT 2004

Red Hat AS 3
Samba 3.0.0 (from distro)
PDC and LDAP Master / BDC and LDAP slave
errors in client logs - should I worry? something I can fix?

client log A - Worry? Don't Worry?
[2004/01/29 08:08:59, 0] groupdb/mapping.c:init_group_mapping(139)
  Failed to open group mapping database
[2004/01/29 08:08:59, 0]

client log B - Worry? Don't Worry?
[2004/01/29 10:49:19, 0]
  failed to decode PDU
[2004/01/29 10:49:19, 0]
  process_request_pdu: failed to do schannel processing.
[2004/01/29 12:24:47, 0] lib/util_sock.c:read_socket_data(342)
  read_socket_data: recv failure for 4. Error = Connection reset by peer
[2004/01/29 13:56:07, 0] lib/util_sock.c:read_socket_data(342)
  read_socket_data: recv failure for 4. Error = No route to host

client log C - same client as log B but this log resides on BDC
(profiles and most shares) where as A and B are for client activities on
PDC. Worry? Don't Worry?
[2004/01/29 12:44:44, 0] smbd/connection.c:register_message_flags(220)
  register_message_flags: tdb_fetch failed

client log D - This is more unique...it's the NAS from Dell (running
Windows 2000 Server/some special version. Machine does have domain
account but I am presently using SFU 2.2 and NFS mounts on samba server
to attach but these errors occur every time I 'touch' a file on the NFS
mount via a cron script running on the samba server on each mount from
the NAS...
[2004/01/29 20:18:00, 0] auth/auth_sam.c:smb_pwd_check_ntlmv2(107)
  smb_pwd_check_ntlmv2: incorrect password length (9)
[2004/01/29 20:18:00, 0] auth/auth_sam.c:smb_pwd_check_ntlmv1(52)
  smb_pwd_check_ntlmv1: incorrect password length (9)

seems to want to map root to Administrator in SFU user mapping - mount
is by root, file is touched (updated) and mounts seem to work just fine.
Worry or not worry?

I am now fully in production usage - things seem to work ok with one
exception...I have about 5 different samba 'shares' which are available
to the domain users which are nfs mounts from the Win2k NAS server to
the samba server(s) which are available to the clients only via the
samba server (gigabit ethernet LAN that clients aren't connected to but
servers are) and if the connection hasn't been used recently (don't
exactly know what the time period of recently is but at least 10
minutes), there is a delay of up to 45 seconds to access files, then all
is fine.


More information about the samba mailing list