Bug 3199 - seemingly random smbd SIGSEGVs on RH Linux 3 print server
Summary: seemingly random smbd SIGSEGVs on RH Linux 3 print server
Status: RESOLVED FIXED
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: Printing (show other bugs)
Version: 3.0.9
Hardware: x86 Linux
: P3 normal
Target Milestone: none
Assignee: Gerald (Jerry) Carter (dead mail address)
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-20 08:25 UTC by Chris Tengi
Modified: 2005-10-24 07:19 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Tengi 2005-10-20 08:25:46 UTC
At seemingly random times, one of the smbd processes on our print server system
dies with a SIGSEGV.  Unfortunately, there are no core files left around so we
have no idea why this occurs.  The log entry from the latest crash is different
from the last 3, which all had something like:

[2005/09/29 11:40:55, 0, pid=23540] smbd/connection.c:register_message_flags(220)
  register_message_flags: tdb_fetch failed

as the last message before the failure.

The system is running Red Hat Enterprise Linux 3, with Samba installed from RPM.
 The Red Hat version number for the currently installed package is 3.0.9-1.3E.3.

Here is the (hopefully) relevant portion of the log file from the latest failure:

-+-+-+-+-
[2005/10/18 14:22:47, 1, pid=23507] smbd/service.c:make_connection_snum(648)
  dell-aslp (128.112.95.121) connect to service xrx_331c initially as user aslp
(uid=113, gid=920) (pid 23507)
[2005/10/18 14:22:47, 0, pid=23507] lib/fault.c:fault_report(36)
  ===============================================================
[2005/10/18 14:22:47, 0, pid=23507] lib/fault.c:fault_report(37)
  INTERNAL ERROR: Signal 11 in pid 23507 (3.0.9-1.3E.3)
  Please read the appendix Bugs of the Samba HOWTO collection
[2005/10/18 14:22:47, 0, pid=23507] lib/fault.c:fault_report(39)
  ===============================================================
[2005/10/18 14:22:47, 0, pid=23507] lib/util.c:smb_panic2(1504)
  PANIC: internal error
[2005/10/18 14:22:47, 0, pid=23507] lib/util.c:smb_panic2(1512)
  BACKTRACE: 24 stack frames:
   #0 smbd(smb_panic2+0x14f) [0x52854f]
   #1 smbd(smb_panic+0x27) [0x5283f7]
   #2 smbd [0x513248]
   #3 /lib/tls/libc.so.6 [0xa2aeb8]
   #4 smbd(smb_io_notify_info_data_strings+0x1e8) [0x4ca2c8]
   #5 smbd [0x4ca4b6]
   #6 smbd(spoolss_io_r_rfnpcnex+0xa3) [0x4cde73]
   #7 smbd [0x45f46b]
   #8 smbd(api_rpcTNP+0x189) [0x497719]
   #9 smbd(api_pipe_request+0xc8) [0x497498]
   #10 smbd [0x4907ed]
   #11 smbd [0x490b79]
   #12 smbd [0x490df9]
   #13 smbd [0x491038]
   #14 smbd(write_to_pipe+0x115) [0x490f75]
   #15 smbd [0x3bb981]
   #16 smbd(reply_trans+0x59b) [0x3bc3ab]
   #17 smbd [0x407243]
   #18 smbd [0x407473]
   #19 smbd(process_smb+0xa6) [0x4076c6]
   #20 smbd(smbd_process+0x192) [0x408512]
   #21 smbd(main+0x52b) [0x5a97cb]
   #22 /lib/tls/libc.so.6(__libc_start_main+0xda) [0xa1878a]
   #23 smbd [0x3a51f2]
[2005/10/18 14:32:10, 0, pid=27669] smbd/connection.c:register_message_flags(220)
  register_message_flags: tdb_fetch failed
-+-+-+-+-

The password servers are running MS-Windows 2000 and the WINS server is the
first password server (bart/128.112.137.3).  Here is our smb.conf file:

-+-+-+-+-
[global]
        workgroup = PUCS
        security = server
        server string = CS Print Server - Samba %v
        password server = bart lisa
        encrypt passwords = yes
        lanman auth = no
        wins server = 128.112.137.3
        name resolve order = host lmhosts bcast
        netbios name = lpdrelay
        domain master = no
        local master = no
        preferred master = no
        os level = 0
        load printers = yes
        printcap name = cups
        printing = cups
        cups options = raw
        ;
        allow hosts =
192.168.0.0/255.255.0.0,128.112.0.0/255.255.0.0,140.180.0.0/255.255.0.0,172.16.0.0/255.240.0.0
        remote announce = 128.112.5.255 128.112.93.255 128.112.94.255
128.112.95.255 128.112.107.255 128.112.139.191
        ;
        dead time = 30
        debug level = 1
        debug pid = yes
        socket options = TCP_NODELAY
        syslog = 0
        dns proxy = yes
        ;
        message command = /usr/local/bin/zwrite -q -c PRINTER -i samba:%f@%m <
%s ; rm %s
        ;
        ; members of the ntadmin group should be able
        ; to add drivers and set printer properties
        ; root is implicitly a 'printer admin'
        ;
        printer admin = cmmiller,cmsanche,elgersma,jonesy,jrc,pel,scott,tengi
        lpq cache time = 10
        ;
        case sensitive = no

[printers]
        comment = All Printers
        path = /var/spool/samba
        public = yes
        browseable = yes
        printable = yes 
        default case = lower
        preserve case = yes
        short preserve case = yes
        create mask = 0700
        map archive = no
        writable = no
        ; since this share is configured as read only, then we need
        ; sure this account can copy files to the share.  If this
        ; is setup to a non-root account, then it should also exist
        ; as a 'printer admin'
        write list = @ntadmin,root,tengi


[PRINT$]
        comment = Printer Drivers
        path = /etc/samba/printers
        public = yes
        browseable = yes
        ; since this share is configured as read only, then we need
        ; sure this account can copy files to the share.  If this
        ; is setup to a non-root account, then it should also exist
        ; as a 'printer admin'
        read only = yes
        write list = @ntadmin,root,tengi
        create mask = 0644
        directory mask = 0755

-+-+-+-+-

Please let me know if there is any additional information I can provide that
will assist in finding and fixing this problem.

Thanks,
    /Chris
Comment 1 Gerald (Jerry) Carter (dead mail address) 2005-10-24 07:19:28 UTC
You have 2 choices I think.  Either get read hat to send you some 
patches or upgrade to a newer version of Samba (3.0.20b) which should 
resolve this.  Wish I had better news for you.