After a little more digging around it seems like theres a bigger issue with my system.
Ive noticed for a while that when people logon they get errors such as chdir (/home/ACADEMIC/test) failed chdir (/home/ACADEMIC/test) failed And at the time when things went a bit weird this morning there were lots of these messages. Im not sure if this was a cause or an effect of the problem. However, futher investigation shows... 172.16.1.11 (172.16.1.11) connect to service test initially as user ACADEMIC+helpdesk-1$ (uid=11458, gid=10515) (pid 7036) chdir (/home/ACADEMIC/test) failed chdir (/home/ACADEMIC/test) failed chdir (/home/ACADEMIC/test) failed chdir (/home/ACADEMIC/test) failed chdir (/home/ACADEMIC/test) failed chdir (/home/ACADEMIC/test) failed chdir (/home/ACADEMIC/test) failed chdir (/home/ACADEMIC/test) failed chdir (/home/ACADEMIC/test) failed chdir (/home/ACADEMIC/test) failed helpdesk-1 (172.16.1.11) connect to service test initially as user ACADEMIC+test (uid=13576, gid=10513) (pid 7037) So it tries to access the home directory of test as the user helpdesk-1$ (the machine account) obviously fails, then tries again as test. What was odd was when it was falling over it would try repeatadly to do this for a user, eventually (possibly) locking out the system. Should it actually be doing this? Or is there another special switch/winxp tweak I need to perform? Ross -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ross McInnes Sent: 20 March 2006 11:00 To: [email protected] Subject: [Samba] Samba 3.0.21c with RH ES3 - Winbind issues? Hi the list. I have couple of issues that may or maynot be related to winbind. All of our servers except 1 are running on rh 3.0.20a without problem. But the main FileStore which was recently upgrade/replace has on it the latest 3.0.21c We use winbind/pam to authenticate against the 2003sp1 AD, but have had a few issues with winbind dying (previously an issue for us pre 3.0.20a, stable in 3.0.20a) This morning, the entire server locked up, eventually it died of its own free will with me being unable to get to the home space etc. Restarted smb and things are fine again. Have a look at the log files and I am presented with... [2006/03/20 10:23:51, 0] lib/util_sock.c:get_peer_addr(1225) getpeername failed. Error was Transport endpoint is not connected [2006/03/20 10:23:52, 1] smbd/service.c:close_cnum(885) 172.16.148.150 (172.16.148.150) closed connection to service shared [2006/03/20 10:23:52, 1] smbd/service.c:close_cnum(885) 172.16.148.150 (172.16.148.150) closed connection to service winfiles [2006/03/20 10:23:52, 1] smbd/service.c:close_cnum(885) 172.16.148.150 (172.16.148.150) closed connection to service tib04 [2006/03/20 10:23:52, 1] smbd/sesssetup.c:reply_spnego_kerberos(303) Username ACADEMIC+USERNAME is invalid on this system [2006/03/20 10:23:52, 0] lib/util_sock.c:get_peer_addr(1225) getpeername failed. Error was Transport endpoint is not connected [2006/03/20 10:23:52, 0] lib/util_sock.c:write_data(557) write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer [2006/03/20 10:23:52, 0] lib/util_sock.c:send_smb(765) Error writing 4 bytes to client. -1. (Connection reset by peer) [2006/03/20 10:23:54, 1] smbd/sesssetup.c:reply_spnego_kerberos(303) Username ACADEMIC+USERNAME is invalid on this system [2006/03/20 10:23:54, 1] smbd/sesssetup.c:reply_spnego_kerberos(303) Username ACADEMIC+E6-1$ is invalid on this system [2006/03/20 10:23:55, 1] smbd/sesssetup.c:reply_spnego_kerberos(303) Username ACADEMIC+HELPDESK-3$ is invalid on this system [2006/03/20 10:23:57, 1] smbd/sesssetup.c:reply_spnego_kerberos(303) Username ACADEMIC+USERNAME is invalid on this system [2006/03/20 10:23:57, 0] auth/auth_util.c:make_server_info_info3(1297) make_server_info_info3: pdb_init_sam failed! [2006/03/20 10:23:57, 0] auth/auth_util.c:make_server_info_info3(1297) make_server_info_info3: pdb_init_sam failed! [2006/03/20 10:23:58, 1] smbd/sesssetup.c:reply_spnego_kerberos(303) Username ACADEMIC+USERNAME is invalid on this system [2006/03/20 10:24:10, 0] sam/idmap.c:idmap_init(137) idmap_init: idmap backend uses deprecated 'idmap_' prefix. Please replace 'idmap_rid' by 'rid' in /usr/local/samba/lib/smb.conf I know the last line is a bit of a issue, but one assumes that it still works? Else getent passwd would return incorrect names/uids etc? >From looking above it kind of smacks of it losing the rid backend. >During this time, the system was almost totally unresponsive. Eventually smb died and when restarted all was well again. Im kinda worried about this as im acutally due to leave my current employ in a few weeks. My clear choice at the moment is to revert back to the stable 3.0.20a. Any ideas / thoughts on this? Cheers Ross -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
