Package: samba
Version: 3.0.23b

Since shifting to the unstable version of samba, I now get a seg fault
every time I run it.  The following text is from the log file:

[2006/08/23 14:03:23, 0] smbd/server.c:main(847)
  smbd version 3.0.23b started.
  Copyright Andrew Tridgell and the Samba Team 1992-2006
[2006/08/23 14:03:23, 0] passdb/pdb_interface.c:make_pdb_method_name(174)
  No builtin nor plugin backend for tdbsam, found
[2006/08/23 14:03:23, 0] lib/util.c:smb_panic(1592)
  PANIC (pid 13597): pdb_get_methods_reload: failed to get pdb methods
for backend tdbsam,

[2006/08/23 14:03:23, 0] lib/util.c:log_stack_trace(1699)
  BACKTRACE: 7 stack frames:
   #0 /usr/sbin/smbd(log_stack_trace+0x23) [0x822b923]
   #1 /usr/sbin/smbd(smb_panic+0x46) [0x822ba16]
   #2 /usr/sbin/smbd [0x81ea8d1]
   #3 /usr/sbin/smbd(initialize_password_db+0xe) [0x81ea91e]
   #4 /usr/sbin/smbd(main+0x591) [0x82c1bf1]
   #5 /lib/tls/libc.so.6(__libc_start_main+0xc8) [0xb7c21ea8]
   #6 /usr/sbin/smbd [0x8082a01]
[2006/08/23 14:03:23, 0] lib/util.c:smb_panic(1600)
  smb_panic(): calling panic action [/usr/share/samba/panic-action 13597]
[2006/08/23 14:03:26, 0] lib/util.c:smb_panic(1608)
  smb_panic(): action returned status 0
[2006/08/23 14:03:26, 0] lib/fault.c:dump_core(173)
  dumping core in /var/log/samba/cores/smbd

And the email root gets:

The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for pid 13597 (/usr/sbin/smbd).

Below is a backtrace for this process generated with gdb, which shows
the state of the program at the time the error occurred. 

If the problem persists, you are encouraged to first install the 
samba-dbg package which contains the debugging symbols for samba 
binaries. Then submit the provided information as a bug report to Debian.
For information about the procedure for submitting bug reports , please see
http://www.debian.org/Bugs/Reporting or the reportbug(1) manpage.

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1212623168 (LWP 13597)]
0xb7c9a7be in waitpid () from /lib/tls/libc.so.6
#0  0xb7c9a7be in waitpid () from /lib/tls/libc.so.6
#1  0xb7c42699 in strtold_l () from /lib/tls/libc.so.6
#2  0xb7dd24fd in system () from /lib/tls/libpthread.so.0
#3  0x0822ba7a in smb_panic (
    why=0xbf97e904 "pdb_get_methods_reload: failed to get pdb methods for 
backend tdbsam,\n") at lib/util.c:1601
#4  0x081ea8d1 in pdb_get_methods_reload (reload=<value optimized out>)
    at passdb/pdb_interface.c:218
#5  0x081ea91e in initialize_password_db (reload=0)
    at passdb/pdb_interface.c:1116
#6  0x082c1bf1 in main (argc=-1211882153, argv=0xb7dd5ff4) at smbd/server.c:922


My smb.conf:

# Samba config file created using SWAT
# from 192.168.42.5 (192.168.42.5)
# Date: 2006/08/23 14:04:47

[global]
        workgroup = XANIA
        server string = %h server (Samba %v)
        obey pam restrictions = Yes
        passdb backend = tdbsam,
        passwd program = /usr/bin/smbpasswd %u
        passwd chat = *New\sSMB\spassword:* %n\n *Retype\snew\sSMB\spassword:* 
%n\n .
        syslog = 0
        log file = /var/log/samba/log.%m
        max log size = 1000
        smb ports = 139
        logon path = 
        logon home = 
        domain logons = Yes
        preferred master = Yes
        domain master = Yes
        dns proxy = No
        ldap ssl = no
        panic action = /usr/share/samba/panic-action %d
        admin users = root
        force create mode = 0744

[homes]
        comment = Home Directories
        read only = No
        create mask = 0700
        directory mask = 0700
        browseable = No

[printers]
        comment = All Printers
        path = /tmp
        create mask = 0700
        printable = Yes
        browseable = No

[websites]
        path = /home/websites
        force user = www-data
        force group = www-data
        read only = No

[music]
        path = /home/music
        read only = No

[video]
        path = /home/video


        read only = No


I'm very happy to help with any follow ups to this.  In the mean time
I'm going to attempt to fathom out what the tdbsam issue is and/or
revert to smbpasswd authentication.

Warm regards,

Matt


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to