[Samba] smb panic when adding printer with apw

[Dermot]

On 24 June 2011 10:38, Thorsten Leiser <t.leiser at synchron-is.de> wrote:
 10:08, schrieb Dermot:
>>>>
>>>> On 24 June 2011 07:13, Thorsten Leiser<t.leiser at synchron-is.de>
>>>>  wrote:
>>>>>
>>>>> Hi,
>>>>> [2011/06/24 07:47:56,  0] lib/debug.c:reopen_logs(663)
>>>>>  Unable to open new log file /var/log/samba/log.smbd: Permission denied
>>>>> [2011/06/24 07:47:56,  0] lib/debug.c:reopen_logs(663)
>>>>>  Unable to open new log file /var/log/samba/log.smbd: Permission denied
>>>>> [2011/06/24 07:47:56,  0] lib/debug.c:reopen_logs(663)
>>>>>  Unable to open new log file /var/log/samba/log.smbd: Permission denied
>>>>> [2011/06/24 07:47:56,  0] lib/fault.c:fault_report(40)
>>
>> Can you determine what the user process is? smbstatus perhaps? This
>> error says that it wants to create a new log file. What does your
>> smb.conf say about max log size? I am not very savy with smb printing
>> but that message suggests that something wants to have write access
>> either to the /var/log/samab directory or the log.smbd file and
>> doesn't have it. There are a few tests you can do to see where the
>> error lies. I would chmod the log.smbd file and see it that gets you
>> round the error.
>> Dp.
>
> Hi Dermot,
>
>> Can you determine what the user process is? smbstatus perhaps?
>
> as long as the apw is opened, smbstatus says user "administrator". I
> controlled the pid with ps -ef and it said uid 1001. Also, smbd seems to run
> with normal user priviliges.
>
>> I would chmod the log.smbd file and see it that gets you
>> round the error.
>
> I did so, but the smb panic occured again, but the error messages "Unable to
> open new log file /var/log/samba/log.smbd: Permission denied
> " disappeared.
> For a test i set the permissions for all files and subdirectories in
> /var/lib/samba to 777, but this didn't solve the error.
> When the panic occurs, samba was still able to create the queue in cups, but
> the smbd died before associating the queue with the uploaded printer driver.

I'm afraid I'm out of ideas. You might want to turn up the debug for
printdrivers, loglevel = 3 printdrivers:9 Hopefully that will give you
a few more details.
Dp.