samba - Mar 2010 - smb panic when trying to use printer (samba 3.3.11/CentOS5.4)

Hi everyone,

I recently wanted to try Samba 3.3.11 for CentOS 5.4. At first, I
tried the Sernet packages then I compiled my own packages but in both
cases, I get the same error messages (SMB?PANIC) when I try to
install/delete/use printers in Samba. At first, I thought this was a
right issue on filesystem (due to messages "Permission denied" in
logs), so I change many rights at many places but this always leads to
the same result :

[2010/03/04 18:30:49,  0] lib/debug.c:reopen_logs(663)
  Unable to open new log file /var/log/samba/po-7678.log: Permission denied
[2010/03/04 18:30:49,  0] lib/debug.c:reopen_logs(663)
  Unable to open new log file /var/log/samba/po-7678.log: Permission denied
[2010/03/04 18:34:28,  1] smbd/service.c:close_cnum(1344)
  po-7678 (10.92.20.198) closed connection to service print$
[2010/03/04 18:34:38,  0] lib/debug.c:reopen_logs(663)
  Unable to open new log file /var/log/samba/po-7678.log: Permission denied
[2010/03/04 18:34:38,  0] lib/util_tdb.c:tdb_wrap_log(886)
  tdb(/var/lib/samba/share_info.tdb): tdb_reopen: open failed
(Permission denied)
[2010/03/04 18:34:38,  0] lib/util.c:reinit_after_fork(1054)
  tdb_reopen_all failed.
[2010/03/04 18:34:38,  0] printing/print_cups.c:cups_pcap_load_async(432)
  cups_pcap_load_async: reinit_after_fork() failed
[2010/03/04 18:34:38,  0] lib/util.c:smb_panic(1673)
  PANIC (pid 3720): cups_pcap_load_async: reinit_after_fork() failed
[2010/03/04 18:34:38,  0] lib/util.c:log_stack_trace(1777)
  BACKTRACE: 21 stack frames:
[2010/03/04 18:34:38,  0] lib/debug.c:reopen_logs(663)
   #0 smbd(log_stack_trace+0x1c) [0x2b808cb0883c]
  Unable to open new log file /var/log/samba/po-7678.log: Permission denied
   #1 smbd(smb_panic+0x2b) [0x2b808cb0891b]
[2010/03/04 18:34:38,  0] lib/debug.c:reopen_logs(663)
   #2 smbd(cups_cache_reload+0x1b1) [0x2b808cad9211]
  Unable to open new log file /var/log/samba/po-7678.log: Permission denied
   #3 smbd(pcap_cache_reload+0xb8) [0x2b808cad5bf8]
[2010/03/04 18:34:38,  0] lib/debug.c:reopen_logs(663)
   #4 smbd(reload_printers+0x25) [0x2b808cd12ba5]
  Unable to open new log file /var/log/samba/po-7678.log: Permission denied
   #5 smbd(reload_services+0x68) [0x2b808cd12ce8]
[2010/03/04 18:34:38,  0] lib/debug.c:reopen_logs(663)
   #6 smbd(delete_printer_hook+0x14c) [0x2b808ca5d8fc]
  Unable to open new log file /var/log/samba/po-7678.log: Permission denied
   #7 smbd(_spoolss_deleteprinter+0x258) [0x2b808ca64418]
[2010/03/04 18:34:38,  0] lib/debug.c:reopen_logs(663)
   #8 smbd [0x2b808ca4b420]
  Unable to open new log file /var/log/samba/po-7678.log: Permission denied
   #9 smbd(api_pipe_request+0x2dc) [0x2b808ca8670c]
   #10 smbd [0x2b808ca82465]
   #11 smbd(write_to_internal_pipe+0x474) [0x2b808ca82904]
   #12 smbd [0x2b808c8f3b2e]
   #13 smbd [0x2b808c8f417b]
   #14 smbd(reply_trans+0x621) [0x2b808c8f4ed1]
   #15 smbd [0x2b808c94e2b4]
   #16 smbd [0x2b808c94f46c]
   #17 smbd(smbd_process+0x892) [0x2b808c94feb2]
   #18 smbd(main+0x1ce8) [0x2b808cd14f88]
   #19 /lib64/libc.so.6(__libc_start_main+0xf4) [0x2b8090199994]
   #20 smbd [0x2b808c8d8889]
[2010/03/04 18:34:38,  0] lib/fault.c:dump_core(231)
  dumping core in /var/log/samba/cores/smbd

Then, I thought this might be a problem with cups (version 1.3.7
bundled with CentOS?5.4), but using a working configuration on samba
3.0.33 with lprng, I got the same results on samba 3.3.11 :

2010/03/04 09:18:35,  1] smbd/service.c:make_connection_snum(1115)
  po-7678 (10.92.20.198) connect to service print$ initially as user
root (uid=0, gid=0) (pid 22666)
[2010/03/04 09:18:45,  1] smbd/service.c:close_cnum(1327)
  po-7678 (10.92.20.198) closed connection to service print$
[2010/03/04 09:18:52,  0] lib/fault.c:fault_report(40)
  ==============================================================[2010/03/04
09:18:52,  0] lib/fault.c:fault_report(41)
  INTERNAL ERROR: Signal 11 in pid 22666 (3.3.7)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2010/03/04 09:18:52,  0] lib/fault.c:fault_report(43)

  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2010/03/04 09:18:52,  0] lib/fault.c:fault_report(44)
  ==============================================================[2010/03/04
09:18:52,  0] lib/util.c:smb_panic(1673)
  PANIC (pid 22666): internal error
[2010/03/04 09:18:52,  0] lib/util.c:log_stack_trace(1777)
  BACKTRACE: 19 stack frames:
   #0 smbd(log_stack_trace+0x1c) [0x2b7088c1005c]
   #1 smbd(smb_panic+0x2b) [0x2b7088c1013b]
   #2 smbd [0x2b7088bfb49e]
   #3 /lib64/libpthread.so.0 [0x2b708a541930]
   #4 smbd(print_access_check+0x28) [0x2b7088c34fb8]
   #5 smbd(_spoolss_addprinterex+0x2b8) [0x2b7088b69aa8]
   #6 smbd [0x2b7088b54d60]
   #7 smbd(api_pipe_request+0x2dc) [0x2b7088b8da7c]
   #8 smbd [0x2b7088b897d5]
   #9 smbd(write_to_internal_pipe+0x474) [0x2b7088b89c74]
   #10 smbd [0x2b70889fb86e]
   #11 smbd [0x2b70889fbebb]
   #12 smbd(reply_trans+0x621) [0x2b70889fcc11]
   #13 smbd [0x2b7088a55ce4]
   #14 smbd [0x2b7088a56eac]
   #15 smbd(smbd_process+0xc79) [0x2b7088a57cb9]
   #16 smbd(main+0x1c31) [0x2b7088e1c251]
   #17 /lib64/libc.so.6(__libc_start_main+0xf4) [0x2b708c2a0994]
   #18 smbd [0x2b70889e0709]
[2010/03/04 09:18:52,  0] lib/fault.c:dump_core(231)
  dumping core in /var/log/samba/cores/smbd

So I'm really confused by now : I don't know if the problem comes from
Samba on CentOS5.4 (this seems weird?), CUPS, the printing system on
CentOS5.4 or even glibc on CentOS5.4. And I found no documentation
about a none compatibility of Samba 3.3.x with RHEL/CentOS.

As many of readers and writers to this list are using CentOS5.4 with
Sernet Samba packages (or with home-made packages), I highly doubt
none of you have encountered this type of issue, so if someone have a
clue or a trick to get it work, I will accept any help :).

Thanks.
--
Cl?ment V?ret