[Samba] error messages

Rowland Penny rowlandpenny at googlemail.com
Sat Jul 12 06:42:38 MDT 2014


On 12/07/14 13:22, Martin Smith wrote:
> On 12/07/2014 09:11, Rowland Penny wrote:
>> On 12/07/14 08:48, Martin Smith wrote:
>>> On 11/07/2014 22:56, Jeremy Allison wrote:
>>>> On Fri, Jul 11, 2014 at 09:20:16PM +0100, Martin Smith wrote:
>>>>> I have a brand new in stall of samba4 on a FreeBSD 10 machine and I
>>>>> am getting these messages on the console practically all the time.
>>>>> I have actually disabled load printer list in globals but it does
>>>>> not seem to make any difference, I am not intending to use it as a
>>>>> printserver at all, just for files, it is to replace a system which
>>>>> is quite old and running out of space
>>>>>
>>>>> Jul 11 20:24:25 server smbd[2480]: [2014/07/11 20:24:25.107693, 0]
>>>>> ../lib/util/pidfile.c:153(pidfile_unlink)
>>>>> Jul 11 20:24:25 server smbd[2480]:   Failed to delete pidfile
>>>>> /var/run/samba4/smbd.pid. Error was No such file or directory
>>>>> Jul 11 20:25:18 server smbd[2485]: [2014/07/11 20:25:18.037739, 0]
>>>>> ../source3/printing/print_cups.c:151(cups_connect)
>>>>> Jul 11 20:25:18 server smbd[2485]:   Unable to connect to CUPS
>>>>> server localhost:631 - Bad file descriptor
>>>>> Jul 11 20:25:18 server smbd[2484]: [2014/07/11 20:25:18.317527, 0]
>>>>> ../source3/printing/print_cups.c:528(cups_async_callback)
>>>>> Jul 11 20:25:18 server smbd[2484]:   failed to retrieve printer
>>>>> list: NT_STATUS_UNSUCCESSFUL
>>>>> Jul 11 20:26:18 server smbd[2487]: [2014/07/11 20:26:18.108999, 0]
>>>>> ../source3/printing/print_cups.c:151(cups_connect)
>>>>> Jul 11 20:26:18 server smbd[2487]:   Unable to connect to CUPS
>>>>> server localhost:631 - Bad file descriptor
>>>>> Jul 11 20:26:18 server smbd[2484]: [2014/07/11 20:26:18.109458, 0]
>>>>> ../source3/printing/print_cups.c:528(cups_async_callback)
>>>>> Jul 11 20:26:18 server smbd[2484]:   failed to retrieve printer
>>>>> list: NT_STATUS_UNSUCCESSFUL
>>>>>
>>>>> could someone point me to a way to disable this
>>>>> cheers
>>>> If you set "printing = bsd" and have an
>>>> empty printcap file that should do the
>>>> trick I think.
>>> Thanks, that solved to cups error messages, now I am getting the 
>>> following
>>> Jul 12 08:35:39 server smbd[1376]: [2014/07/12 08:35:39.636168, 0] 
>>> ../lib/util/pidfile.c:153(pidfile_unlink)
>>> Jul 12 08:35:39 server smbd[1376]:   Failed to delete pidfile 
>>> /var/run/samba4/smbd.pid. Error was No such file or directory
>>> Jul 12 08:35:39 server smbd[1377]: [2014/07/12 08:35:39.888389, 0] 
>>> ../lib/util/pidfile.c:153(pidfile_unlink)
>>> Jul 12 08:35:39 server smbd[1377]:   Failed to delete pidfile 
>>> /var/run/samba4/smbd.pid. Error was No such file or directory
>>> Jul 12 08:37:52 server smbd[1394]: [2014/07/12 08:37:52.124528, 0] 
>>> ../lib/util/pidfile.c:153(pidfile_unlink)
>>> Jul 12 08:37:52 server smbd[1394]:   Failed to delete pidfile 
>>> /var/run/samba4/smbd.pid. Error was No such file or directory
>>> Jul 12 08:37:52 server smbd[1395]: [2014/07/12 08:37:52.201422, 0] 
>>> ../lib/util/pidfile.c:153(pidfile_unlink)
>>> Jul 12 08:37:52 server smbd[1395]:   Failed to delete pidfile 
>>> /var/run/samba4/smbd.pid. Error was No such file or directory
>>>
>>> now in /var/run/samba4 there is indeed no smbd.pid but there is an 
>>> nmbd.pid
>>> could this be related to another problem I have, I can access the 
>>> share from macosx 10.9
>>> and I am on the list of authorized users but I cannot copy anything 
>>> into the share
>>> osx tells me I cannot copy the item because I do not have permission 
>>> to read it!
>>> The same problem exists with trying to copy an item in from win7, I 
>>> do not seem to have
>>> the requisite permissions, yet the share is set to 0777
>>> this is samba 4.0.19 on freebs
>> Hi, can you please post your smb.conf
> # Samba config file created using SWAT
> # from UNKNOWN (192.168.0.90)
> # Date: 2014/07/12 07:13:50
>
> [global]
>         client max protocol = SMB2
>         client min protocol = SMB2
>         load printers = No
>         show add printer wizard = No
>         idmap config * : range =
>         idmap config * : backend = tdb
>         printing = bsd
>
> [documents]
>         path = /docs
>         create mask = 0777
>         directory mask = 0777
>         valid users = rebecca, martin
>
> and the directory itself
> drwxrwxrwx   3 root  wheel          512 Jul 11 21:51 docs/
>
>>
>> Rowland
>>

I take it that your workgroup is 'WORKGROUP' and that you are using the 
tdbsam backend. Have you added the required users to samba?

I think that this line may be your problem:

idmap config * : range =

It is usually used with the idmap backend and should have a range i.e. 
1000000-1999999, it is quite possible that samba is getting confused and 
stopping the smbd daemon. Try setting samba up correctly and see how you 
go on.

Rowland



More information about the samba mailing list