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 [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
