[2006/08/04 20:51:35, 0] smbd/server.c:main(847) smbd version 3.0.23a started. Copyright Andrew Tridgell and the Samba Team 1992-2006 [2006/08/04 20:51:35, 0] passdb/pdb_interface.c:make_pdb_method_name(174) No builtin nor plugin backend for tdbsam guest found [2006/08/04 20:51:35, 0] lib/util.c:smb_panic(1592) PANIC (pid 14410): pdb_get_methods_reload: failed to get pdb methods for backend tdbsam guest [2006/08/04 20:51:35, 0] lib/util.c:log_stack_trace(1699) BACKTRACE: 7 stack frames: #0 /usr/sbin/smbd(log_stack_trace+0x23) [0x822cc13] #1 /usr/sbin/smbd(smb_panic+0x48) [0x822ca98] #2 /usr/sbin/smbd [0x81eadd6] #3 /usr/sbin/smbd(initialize_password_db+0x11) [0x81ecd61] #4 /usr/sbin/smbd(main+0x36a) [0x82c174a] #5 /lib/libc.so.6(__libc_start_main+0xc6) [0x4019de36] #6 /usr/sbin/smbd [0x8082d31] [2006/08/04 20:51:35, 0] lib/util.c:smb_panic(1600) smb_panic(): calling panic action [/usr/share/samba/panic-action 14410] [2006/08/04 20:51:36, 0] lib/util.c:smb_panic(1608) smb_panic(): action returned status 0 [2006/08/04 20:51:36, 0] lib/fault.c:dump_core(173) dumping core in /var/log/samba/cores/smbd what is that ? help in there please! regards
Please read the release notes. multiple passdb backends are no longer supported. In addition, the guest backend was never documented to be included in smb.conf. Just set passdb backend = tdbsam
(In reply to comment #1) > Please read the release notes. multiple passdb backends > are no longer supported. In addition, the guest backend > was never documented to be included in smb.conf. Just set > > passdb backend = tdbsam > he is still giving me the same message i supos to add that in smb.conf rigth?
yes.
(In reply to comment #3) > yes. > well i did all ready and is doing the same i had to downgrade to the samba version i had before
Please attach (not inline) the gzipped output from smbd -d 10 -i
I'd like to add that a segmentation fault is probably a suboptimal way to react to an invalid configuration file setting. It should just terminate normally after "failed to get pdb methods" or whatever.
(In reply to comment #6) > I'd like to add that a segmentation fault is probably a > suboptimal way to react to an invalid configuration file > setting. It should just terminate normally after "failed > to get pdb methods" or whatever. It's not a seg fault. It's a forced panic (similar to as assert() firing).
no response. Pretty sure this is just a config error.
>multiple passdb backends are no longer supported. so why doesn't the panic say that rather than a cryptic "failed to get pdb methods for backend tdbsam guest"