[Samba] Anybody got any ideas as to how to fix this problem? -- on both 3.0.5 and 3.0.6 PDC

[William Jojo]

I'm seeing this a great deal on AIX 5.2 as well....i thought i had a
problem with my 3-Gb link aggregation, so i destroyed it and went back to
a single gig link, but....i still have some problems:

[2004/09/09 10:54:12, 0] lib/util_file.c:do_file_lock(67)
  do_file_lock: failed to lock file.
[2004/09/09 10:54:12, 0] passdb/pdb_smbpasswd.c:mod_smbfilepwd_entry(712)
  mod_smbfilepwd_entry: unable to lock file /samba/3.0.6/private/smbpasswd
[2004/09/09 10:54:12, 0]
passdb/pdb_smbpasswd.c:smbpasswd_update_sam_account(1436)
  smbpasswd_update_sam_account: mod_smbfilepwd_entry failed!


happens a *LOT* - people can't change passwords and sometimes machines
can't join the domain and get access denied because the password file
can't be locked. This happened in 3.0.4 as well, but I seriously thought
it was me....i don't think it's me any more.

I had to write a wrapper around smbpasswd to retry on rc=1 for 10 times
until it successfully gets a lock and sometimes even that fails.

I'm also seeing a lot of:

[2004/09/09 10:54:16, 0] lib/access.c:check_access(328)
[2004/09/09 10:54:16, 0] lib/util_sock.c:get_peer_addr(1000)
  getpeername failed. Error was Socket is not connected
  Denied connection from  (0.0.0.0)
[2004/09/09 10:54:16, 0] lib/util_sock.c:write_socket_data(430)
  write_socket_data: write failure. Error = Broken pipe
[2004/09/09 10:54:16, 0] lib/util_sock.c:write_socket(455)
  write_socket: Error writing 5 bytes to socket 22: ERRNO = Broken pipe
[2004/09/09 10:54:16, 0] lib/util_sock.c:send_smb(647)
  Error writing 5 bytes to client. -1. (Broken pipe)
[2004/09/09 10:54:16, 0] lib/util_sock.c:get_peer_addr(1000)
  getpeername failed. Error was Socket is not connected
[2004/09/09 10:54:16, 0] lib/access.c:check_access(328)
[2004/09/09 10:54:16, 0] lib/util_sock.c:get_peer_addr(1000)
  getpeername failed. Error was Socket is not connected
  Denied connection from  (0.0.0.0)
[2004/09/09 10:54:16, 0] lib/util_sock.c:write_socket_data(430)
  write_socket_data: write failure. Error = Broken pipe
[2004/09/09 10:54:16, 0] lib/util_sock.c:write_socket(455)
  write_socket: Error writing 5 bytes to socket 22: ERRNO = Broken pipe
[2004/09/09 10:54:16, 0] lib/util_sock.c:send_smb(647)
  Error writing 5 bytes to client. -1. (Broken pipe)


I can't imagine having a great deal of network problems suddenly since
moving from 2.2.8a.

is there anyone that can shed some serious light on this issue because it
did not happen until we moved to version 3 and I've really exhausted my
searches on the AIX side and patched everything i can find to the latest
levels.

going back to 2.2.x is obviously not an option for me since it will no
longer be supported on 10/1 and i really want to move to our LDAP
implementation within the next two weeks, but I must admit i'm becoming
concerned.

thanks a bunch!


Bill



On Wed, 8 Sep 2004, M. D. Parker wrote:

> I previously reported a problem where I was seeing all sorts of Interrupted
> system call errors for the /etc/samba/smbpasswd file.  This caused some
> significant temporary problems at our site in user validations.
>
> Seems upon analysis of the various log material, and coding.....that the
> Interrupted system call is legit.  It is simply indicating a timeout for the
> lock request on the /etc/samba/smbpasswd file which really should not happen
> but it does.
>
> OK, in checking the system further, we find one system basically constantly
> holding open / or using the passwd file for authentication for some reason
> thus causing the other clients to become basically locked out.
>
> This client has the following log entries:
>
> [2004/09/07 18:32:52, 2] smbd/server.c:exit_server(568)
>   Closing connections
> [2004/09/07 18:45:32, 2] smbd/sesssetup.c:setup_new_vc_session(602)
>   setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all
> old resources.
> [2004/09/07 18:45:32, 2] smbd/sesssetup.c:setup_new_vc_session(602)
>   setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all
> old resources.
> [2004/09/07 18:45:32, 2] lib/access.c:check_access(324)
>   Allowed connection from  (141.248.152.163)
> [2004/09/07 18:45:32, 2] lib/access.c:check_access(324)
>   Allowed connection from  (141.248.152.163)
> [2004/09/07 18:45:32, 0] passdb/pdb_smbpasswd.c:mod_smbfilepwd_entry(899)
>   mod_smbfilepwd_entry:  Using old smbpasswd format.  This is no longer
> supported.!
> [2004/09/07 18:45:32, 0] passdb/pdb_smbpasswd.c:mod_smbfilepwd_entry(900)
>   mod_smbfilepwd_entry:  No changes made, failing.!
> [2004/09/07 18:45:32, 0]
> passdb/pdb_smbpasswd.c:smbpasswd_update_sam_account(1436)
>   smbpasswd_update_sam_account: mod_smbfilepwd_entry failed!
> [2004/09/07 18:45:32, 0] passdb/pdb_smbpasswd.c:mod_smbfilepwd_entry(899)
>   mod_smbfilepwd_entry:  Using old smbpasswd format.  This is no longer
> supported.!
> [2004/09/07 18:45:32, 0] passdb/pdb_smbpasswd.c:mod_smbfilepwd_entry(900)
>   mod_smbfilepwd_entry:  No changes made, failing.!
> [2004/09/07 18:45:32, 0]
> passdb/pdb_smbpasswd.c:smbpasswd_update_sam_account(1436)
>   smbpasswd_update_sam_account: mod_smbfilepwd_entry failed!
> [2004/09/07 18:47:40, 2] smbd/process.c:timeout_processing(1138)
>   Closing idle connection
> [2004/09/07 18:47:40, 2] smbd/server.c:exit_server(568)
>   Closing connections
>
> ====================
>
> NOTE: Both the machine and client smbpasswd entries are of the "NEW" type as
> noted by the number of fields in each entry:
>
> client$:753:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:BDCCBA58CAE2136EE5F68206ADC748E
> A:[W         ]:LCT-40F2BF93:
>
> username:962:A8AD058EA120084B1486235A2333E4D2:11D4C351D6C291170C2D6192EB8E99
> FC:[U          ]:LCT-41360DED:
>
> Further entries in the /etc/passwd and /etc/shadow file track correctly to
> the information in the samba passwd file.
> I'm not sure any changes are being made here as our site (by directive
> unfortunately) so I do not understand what would be changing either.
>
> What problem are we seeing?  Any ideas what to do to fix this?
>
>
>
>
> ==========================================
>
> M. D. Parker
> Systems Administrator
> General Atomics / Electromagnetic Systems
> +1 858 455 2877
> mike.parker at ga.com
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
>