[Samba] Signal 11 in Samba adding Windows XP printer driver

[David Simpson]

Volker Lendecke wrote:
> On Tue, Mar 11, 2008 at 10:58:05PM +1100, David Simpson wrote:
>   
>> The error messages in the log file are :
>>
>> [2008/03/09 17:19:48, 1] smbd/service.c:make_connection_snum(1033)
>>  xxxxxxxx (192.168.0.99) connect to service print$ initially as user
>> xxxxxx (uid=10000, gid=513)
>> (pid 29631)
>> [2008/03/09 17:19:48, 0] lib/fault.c:fault_report(41)
>>  ===============================================================
>> [2008/03/09 17:19:48, 0] lib/fault.c:fault_report(42)
>>  INTERNAL ERROR: Signal 11 in pid 29631 (3.0.25b-1.el5_1.4)
>>  Please read the Trouble-Shooting section of the Samba3-HOWTO
>> [2008/03/09 17:19:48, 0] lib/fault.c:fault_report(44)
>>
>>  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
>> [2008/03/09 17:19:48, 0] lib/fault.c:fault_report(45)
>>  ===============================================================
>> [2008/03/09 17:19:48, 0] lib/util.c:smb_panic(1654)
>>  PANIC (pid 29631): internal error
>> [2008/03/09 17:19:48, 0] lib/util.c:log_stack_trace(1758)
>>  BACKTRACE: 24 stack frames:
>>   #0 smbd(log_stack_trace+0x2d) [0xb36b9d]
>>   #1 smbd(smb_panic+0x5d) [0xb36ccd]
>>   #2 smbd [0xb216ba]
>>   #3 [0x110420]
>>   #4 smbd [0x9a53fc]
>>   #5 smbd(close_file+0x417) [0x9a58e7]
>>     
>
> Would it be possible that you recompile Samba without
> optimization and with -g, so that we get a better stack
> trace?
>
> Thanks,
>
>   
Hi Volker,

The Samba server was a straight yum install for Centos 5.1 on a i386 
system, with the latest updates. I was setting this system up for a 
local church,  using some of our superseded  server  hardware, and don't 
easily have access to change things around now, as it is pretty much 
working they way the want, and most admin is done remotely, so I don't 
want to break it, as they have a lot of files being shared etc, which is 
working well. It was just the final step of setting them up with printer 
sharing that failed.

I did however change the log level to 10, and found the following in the 
messages log file :
....
Mar 12 21:33:52 jonah smbd[25838]: [2008/03/12 21:33:52, 0] 
librpc/ndr/ndr.c:ndr_print_debug_helper(203)
Mar 12 21:33:52 jonah smbd[25838]:               
result                   : WERR_OK
Mar 12 21:34:32 jonah smbd[25838]: [2008/03/12 21:34:32, 0] 
smbd/nttrans.c:call_nt_transact_ioctl(2481)
Mar 12 21:34:32 jonah smbd[25838]:   call_nt_transact_ioctl(0x90100): 
Currently not implemented.
Mar 12 21:34:38 jonah smbd[25838]: [2008/03/12 21:34:38, 0] 
printing/nt_printing.c:move_driver_to_download_area(1829)
Mar 12 21:34:38 jonah smbd[25838]:   move_driver_to_download_area: 
Unable to rename [W32X86/PSCRIPT5.DLL] to [W32X86/3/PSCRIPT5.DLL]
....

Note that when it did crash with the signal 11, there were strange 
directories left in the print$ share, under the W32X86 directory, with 
names like __SKIP_034B.

Acting on the "unable to rename" error message, and comparing to our new 
servers which are based on the same distro,(but X86_64) and work fine 
for printer driver sharing and uploading, I added the following lines to 
smb.conf (in the general section) and that seemed to solve the problem, 
and I could then upload the printer drivers, and connect the printers to 
the workstations.

directory mask = 3770
create mask = 770
force create mode = 770

Hopefully this will help you sort out the issue.

If it would be of help, I could try to replicate the error on a virtual 
server and then recompile with changed flags.

Thanks very much for you help, and the fantastic product Samba is, and 
all the effort your team put in.

Regards
David