Same problem with Samba 3.3.6 and 3.3.5 :(
The backtrace is shorter but the result is still here : I cannot
properly install or print through my samba server. Could it be a
problem at compilation time (no error reported)?? I'm rebuilding from
source rpm provided by sernet.
Le 1 septembre 2009 12:20, Cl?ment VERET<clement.veret at gmail.com> a
?crit :> Hi everyone,
>
> Recently upgraded to 3.3.7 on a test server (can do everything on it
> if you need to test something like patch, configuration options,
> etc?), and got big problems with printing very similar to
> http://www.mail-archive.com/samba at lists.samba.org/msg97841.html
> signaled for version 3.2.6
>
> I'm on CentOS 5.3 recently updated (with sernet packages) and I
> checked that I have the correct patch (included in the 3.3.0 release
> if I'm right?) with the close_all_print_db(); (in file
> source/printing/print_cups.c).
>
> But it still doesn't work. On the official CentOS version 3.0.33, I
> installed my printers without any troubles, upgrade to 3.3.7 and then
> can't print anymore (losing configurations, etc?). Tried on a fresh
> install with 3.3.7 -> same result?
>
> Here is the panic part :
>
> $ cat po-7678.log
> [2009/09/01 12:12:38, ?0] smbd/service.c:make_connection(1288)
> ?po-7678 (10.92.20.115) couldn't find service
> ::{2227a280-3aea-1069-a2de-08002b30309d}
> [2009/09/01 12:12:48, ?1] smbd/service.c:make_connection_snum(1115)
> ?po-7678 (10.92.20.115) connect to service print$ initially as user
> nobody (uid=99, gid=99) (pid 1030)
> [2009/09/01 12:12:57, ?0] smbd/nttrans.c:call_nt_transact_ioctl(1989)
> ?call_nt_transact_ioctl(0x90100): Currently not implemented.
> [2009/09/01 12:12:59, ?1] smbd/service.c:make_connection_snum(1115)
> ?po-7678 (10.92.20.115) connect to service print$ initially as user
> nobody (uid=99, gid=99) (pid 1030)
> [2009/09/01 12:12:59, ?1] smbd/service.c:close_cnum(1327)
> ?po-7678 (10.92.20.115) closed connection to service print$
> [2009/09/01 12:12:59, ?1] smbd/service.c:make_connection_snum(1115)
> ?po-7678 (10.92.20.115) connect to service print$ initially as user
> nobody (uid=99, gid=99) (pid 1030)
> [2009/09/01 12:12:59, ?1] smbd/service.c:close_cnum(1327)
> ?po-7678 (10.92.20.115) closed connection to service print$
> [2009/09/01 12:12:59, ?0] lib/debug.c:reopen_logs(663)
> ?Unable to open new log file /var/log/samba/po-7678.log: Permission denied
> [2009/09/01 12:12:59, ?0] lib/util_tdb.c:tdb_wrap_log(886)
> ?tdb(/var/lib/samba/notify.tdb): tdb_reopen: open failed (Permission
denied)
> [2009/09/01 12:12:59, ?0] lib/util.c:reinit_after_fork(1054)
> ?tdb_reopen_all failed.
> [2009/09/01 12:12:59, ?0] printing/print_cups.c:cups_pcap_load_async(432)
> ?cups_pcap_load_async: reinit_after_fork() failed
> [2009/09/01 12:12:59, ?0] lib/util.c:smb_panic(1673)
> ?PANIC (pid 1117): cups_pcap_load_async: reinit_after_fork() failed
> [2009/09/01 12:12:59, ?0] lib/util.c:log_stack_trace(1777)
> [2009/09/01 12:12:59, ?0] lib/debug.c:reopen_logs(663)
> ?BACKTRACE: 22 stack frames:
> ?Unable to open new log file /var/log/samba/po-7678.log: Permission denied
> ? #0 smbd(log_stack_trace+0x1a) [0x2b8c7813d620]
> [2009/09/01 12:12:59, ?0] lib/debug.c:reopen_logs(663)
> ? #1 smbd(smb_panic+0x5b) [0x2b8c7813d730]
> ?Unable to open new log file /var/log/samba/po-7678.log: Permission denied
> [2009/09/01 12:12:59, ?0] lib/debug.c:reopen_logs(663)
> ? #2 smbd(cups_cache_reload+0x27c) [0x2b8c78103e14]
> ?Unable to open new log file /var/log/samba/po-7678.log: Permission denied
> ? #3 smbd(pcap_cache_reload+0x109) [0x2b8c781007b5]
> [2009/09/01 12:12:59, ?0] lib/debug.c:reopen_logs(663)
> ? #4 smbd(reload_printers+0x25) [0x2b8c78353dfc]
> ?Unable to open new log file /var/log/samba/po-7678.log: Permission denied
> ? #5 smbd(reload_services+0x154) [0x2b8c78354043]
> [2009/09/01 12:12:59, ?0] lib/debug.c:reopen_logs(663)
> ? #6 smbd(add_printer_hook+0x24d) [0x2b8c7807ed34]
> ?Unable to open new log file /var/log/samba/po-7678.log: Permission denied
> ? #7 smbd(_spoolss_addprinterex+0x205) [0x2b8c78088e2c]
> ? #8 smbd [0x2b8c78073c95]
> ? #9 smbd(api_pipe_request+0x42a) [0x2b8c780af529]
> ? #10 smbd [0x2b8c780aa9ac]
> ? #11 smbd(write_to_internal_pipe+0x7cc) [0x2b8c780ab7b6]
> ? #12 smbd(write_to_pipe+0x135) [0x2b8c780ab9fe]
> ? #13 smbd [0x2b8c77f13005]
> ? #14 smbd [0x2b8c77f13695]
> ? #15 smbd(reply_trans+0x72e) [0x2b8c77f14327]
> ? #16 smbd [0x2b8c77f6bff2]
> ? #17 smbd [0x2b8c77f6cfab]
> ? #18 smbd(smbd_process+0xc23) [0x2b8c77f6dc89]
> ? #19 smbd(main+0x2135) [0x2b8c78356679]
> ? #20 /lib64/libc.so.6(__libc_start_main+0xf4) [0x2b8c7b1c7974]
> ? #21 smbd [0x2b8c77ef8b59]
> [2009/09/01 12:13:00, ?0] lib/fault.c:dump_core(231)
> ?dumping core in /var/log/samba/cores/smbd
>
> Any ideas on what's wrong ?
>
> Regards.
> --
> Cl?ment V?ret
>
--
Cl?ment V?ret