Hello, I am running Debian/sarge and upgraded samba to 3.0 some time ago Since the upgrade I am having an issue with one user connecting to samba. When they try to access the samba file server from any machine (2K/XP) the smbd has a panic and crashes after they put in the login details. Samba continues to operate so I guess the daemon is automatically re-started. This samba box is part of an ADS domain (aprox 50,000 users). I have a dozen other users accessing this machine with no problem. The only difference I can see in the username's which are working and the one that is not is are userone and the one that is failing is user2. Any suggestions for fixing or diagnosing this issue further would be helpful. Best Regards, Lee Sanders ==============================================================smbd[16028]: [2003/08/27 16:05:56, 0] lib/fault.c:fault_report(37) Aug 27 16:05:56 squidjr smbd[16028]: INTERNAL ERROR: Signal 11 in pid 16028 (3.0.0beta2-1 for Debian) smbd[16028]: Please read the appendix Bugs of the Samba HOWTO collection smbd[16028]: [2003/08/27 16:05:56, 0] lib/fault.c:fault_report(39) smbd[16028]: ====================================================smbd[16028]: [2003/08/27 16:05:56, 0] lib/util.c:smb_panic(1452) smbd[16028]: smb_panic(): calling panic action [/usr/share/samba/panic-action 16028] smbd[16028]: [2003/08/27 16:05:56, 0] lib/util.c:smb_panic(1460) smbd[16028]: smb_panic(): action returned status 0 smbd[16028]: [2003/08/27 16:05:56, 0] lib/util.c:smb_panic(1462) smbd[16028]: PANIC: internal error smbd[16028]: [2003/08/27 16:05:56, 0] lib/util.c:smb_panic(1469) smbd[16028]: BACKTRACE: 26 stack frames: smbd[16028]: #0 /usr/sbin/smbd(smb_panic+0xc9) [0x817eb3d] smbd[16028]: #1 /usr/sbin/smbd [0x81700e2] smbd[16028]: #2 /lib/libc.so.6 [0x401ca9d8] smbd[16028]: #3 /lib/libc.so.6(malloc+0xa1) [0x4020d145] smbd[16028]: #4 /lib/libc.so.6(__libc_realloc+0x53) [0x4020d345] smbd[16028]: #5 /lib/libc.so.6 [0x401cc3f1] smbd[16028]: #6 /lib/libc.so.6(setenv+0x23) [0x401cc670] smbd[16028]: #7 /usr/sbin/smbd(sys_getgrouplist+0x54) [0x81c7a84] smbd[16028]: #8 /usr/sbin/smbd [0x81aa1d5] smbd[16028]: #9 /usr/sbin/smbd(make_server_info_info3+0x4e7) [0x81aaefb] smbd[16028]: #10 /usr/sbin/smbd [0x81a7445] smbd[16028]: #11 /usr/sbin/smbd [0x81a4550] smbd[16028]: #12 /usr/sbin/smbd [0x81abcf4] smbd[16028]: #13 /usr/sbin/smbd [0x80dbdf8] smbd[16028]: #14 /usr/sbin/smbd(ntlmssp_server_update+0xe7) [0x80dc0fb] smbd[16028]: #15 /usr/sbin/smbd(auth_ntlmssp_update+0x25) [0x81abec5] smbd[16028]: #16 /usr/sbin/smbd [0x809db79] smbd[16028]: #17 /usr/sbin/smbd [0x809dd4b] smbd[16028]: #18 /usr/sbin/smbd(reply_sesssetup_and_X+0x9d0) [0x809e828] smbd[16028]: #19 /usr/sbin/smbd [0x80b670d] smbd[16028]: #20 /usr/sbin/smbd [0x80b6903] smbd[16028]: #21 /usr/sbin/smbd(process_smb+0x74) [0x80b6ab0] smbd[16028]: #22 /usr/sbin/smbd(smbd_process+0x198) [0x80b7578] smbd[16028]: #23 /usr/sbin/smbd(main+0x440) [0x81d5140] smbd[16028]: #24 /lib/libc.so.6(__libc_start_main+0xdd) [0x401b9a51] smbd[16028]: #25 /usr/sbin/smbd(chroot+0x31) [0x8075fa5] smbd[16028]: smbd[16038]: [2003/08/27 16:05:56, 0] lib/fault.c:fault_report(36) smbd[16038]: ===============================================================
Gerald (Jerry) Carter
2003-Sep-02 15:07 UTC
[Samba] One user's logon crashing Samba 3.0.0beta2-1
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 2 Sep 2003, Lee Sanders wrote:> Hello, > > I am running Debian/sarge and upgraded samba to 3.0 some time agoFixed in either rc1 I'm pretty sure. This is actually a glibc bug in getgrouplist() cheers, jerry ---------------------------------------------------------------------- Hewlett-Packard ------------------------- http://www.hp.com SAMBA Team ---------------------- http://www.samba.org GnuPG Key ---- http://www.plainjoe.org/gpg_public.asc "You can never go home again, Oatman, but I guess you can shop there." --John Cusack - "Grosse Point Blank" (1997) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE/VLIyIR7qMdg1EfYRAi5ZAJ9ePtoy+03i2giH3ZG8GjNKwcMH1gCaAyPC yB5w6v64U//VfiOe2fgaHAQ=r8kK -----END PGP SIGNATURE-----