[Samba] smbd doesn't start anymore

Rowland Penny rowlandpenny at googlemail.com
Tue Sep 23 10:13:16 MDT 2014 

On 23/09/14 16:56, Bruno MACADRÉ wrote:
> Rowland, can you pointing me on your man 'cause the man located at 
> (https://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html#SOCKETOPTIONS) 
> doesn't mention this warning.
>
> I'll disable my socket options now.
>
> Apparmor is started but don't deny anything related to smbd (or other 
> pieces of SAMBA)
>
> Like I said before, my smbd hangs on creating 'messaging pointer' I 
> think I've ran out of ressources 'cause I've just rebooted the server 
> and all start fine....
>
> I will monitor this server more precisely to see what happens exactly 
> (and when it happens). I hope there's no memory leaks
>
> Thanks again for your answers, I'll cross my fingers and keep an eye 
> on this server for some days
>
> Best regards,
> Bruno
>
> Le 23/09/2014 17:05, Rowland Penny a écrit :
>> On 23/09/14 15:42, Bruno MACADRÉ wrote:
>>> Thanks for your answer Rowland but when I read again smb.conf man 
>>> (https://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html#SOCKETOPTIONS) 
>>> I don't see any line mentionning that socket options mustn't be 
>>> used.....
>>
>> You mean that you missed this:
>>
>>        socket options (G)
>>
>>                Warning
>>                Modern server operating systems are tuned for high 
>> network performance in the majority of situations; when you set 
>> socket options
>>                you are overriding those settings. Linux in particular 
>> has an auto-tuning mechanism for buffer sizes that will be disabled 
>> if you specify
>>                a socket buffer size. This can potentially cripple 
>> your TCP/IP stack.
>>
>>>
>>> I'm really sorry to have made some mistakes (i'm just a human ... 
>>> me), schema instead of schema_mode is a typo and some options 
>>> reverted to default are used for tuning (and not deleted .... sorry 
>>> again)
>>>
>>> Thanks again for your answer pointing some of my mistakes that have 
>>> nothing to do with my problem.... but my smb.conf is clean now (i 
>>> keep socket options for the moment).
>>
>> We are all human, Well I hope we are ;-)  but people seem to post on 
>> here without giving enough information, haven't read anything and 
>> expect somebody to magically fix their problem. All people like 
>> myself can do is guess, point out anything obvious (when we get more 
>> info) and then take it from there.
>>
>> Having said all that and I know that you were asked about Selinux, 
>> but what about apparmor, is this installed and has it somehow been 
>> changed/started ?
>>
>> Rowland
>>
>>>
>>> Regards
>>> Bruno
>>>
>>> Le 23/09/2014 15:59, Rowland Penny a écrit :
>>>> On 23/09/14 14:36, Bruno MACADRÉ wrote:
>>>>> No system reboot, crash or update at all
>>>>>
>>>>> My server runs on ubuntu server 14.04 x64 without SELinux enabled.
>>>>>
>>>>> This server has run many days without problem and the main smbd 
>>>>> process disappear without any explication today (during lunch 
>>>>> time....)
>>>>>
>>>>> Here my smb.conf :
>>>>>
>>>>> [global]
>>>>>    netbios name = filzen
>>>>>    workgroup = SAMDOM
>>>>>    security = ADS
>>>>>    realm = SAMDOM.FR
>>>>>    encrypt passwords = yes
>>>>>
>>>>>    log level = 9
>>>>>    log file = /var/log/samba/log.%M
>>>>>
>>>>>    idmap config *:backend = tdb
>>>>>    idmap config *:range = 70000-80000
>>>>>    idmap config SAMDOM:backend = ad
>>>>>    idmap config SAMDOM:schema = rfc2307
>>>>>    idmap config SAMDOM:range = 10000-60000
>>>>>
>>>>>    winbind nss info = rfc2307
>>>>>    winbind trusted domains only = no
>>>>>    winbind use default domain = yes
>>>>>    winbind enum users  = yes
>>>>>    winbind enum groups = yes
>>>>>
>>>>>
>>>>>    interfaces = lo bond0
>>>>>    bind interfaces only = yes
>>>>>
>>>>>
>>>>>    # Tunning
>>>>>    strict locking = No
>>>>>    strict sync = No
>>>>>    sync always = No
>>>>>    socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE 
>>>>> SO_RCVBUF=8192 SO_SNDBUF=8192
>>>>>    lanman auth = No
>>>>>    lm announce = No
>>>>>    ea support = No
>>>>>
>>>>>    kernel oplocks = yes
>>>>>    read raw = yes
>>>>>    write raw = yes
>>>>>
>>>>>    max xmit = 65535
>>>>>    dead time = 15
>>>>>    getwd cache = yes
>>>>>
>>>>>    invalid users = root morpheus
>>>>>
>>>>>    case sensitive = yes
>>>>>
>>>>>    registry shares = Yes
>>>>>
>>>>>
>>>>>
>>>>> I hope it would be usefull
>>>>>
>>>>> Le 23/09/2014 15:08, Gaiseric Vandal a écrit :
>>>>>> Was this after any system reboot, system crash, system update?
>>>>>>
>>>>>> What OS?  If this is linux, is SELinux enabled?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 09/23/14 09:03, Bruno MACADRÉ wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>>     I've a really big problem with my SAMBA 4.1.11 production 
>>>>>>> server.... it doesn't want to start smbd anymore.... nmbd starts 
>>>>>>> fine but not smbd.
>>>>>>>
>>>>>>>     I've tried to start smbd in interactive mode to see what's 
>>>>>>> happened :
>>>>>>>
>>>>>>>     # /srv/progs/samba4/sbin/smbd -i -d9
>>>>>>>
>>>>>>>     produce a lot of lines about configuration (all fine), some 
>>>>>>> last lines are :
>>>>>>>
>>>>>>> added interface lo ip=::1 bcast= 
>>>>>>> netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
>>>>>>> added interface lo ip=127.0.0.1 bcast=127.255.255.255 
>>>>>>> netmask=255.0.0.0
>>>>>>> added interface bond0 ip=10.130.162.20 bcast=10.130.162.255 
>>>>>>> netmask=255.255.255.0
>>>>>>> loaded services
>>>>>>> Netbios name list:-
>>>>>>> my_netbios_names[0]="FILZEN"
>>>>>>> fcntl_lock 9 6 0 1 1
>>>>>>> fcntl_lock: Lock call successful
>>>>>>> Attempting to register passdb backend smbpasswd
>>>>>>> Successfully added passdb backend 'smbpasswd'
>>>>>>> Attempting to register passdb backend tdbsam
>>>>>>> Successfully added passdb backend 'tdbsam'
>>>>>>> Attempting to register passdb backend wbc_sam
>>>>>>> Successfully added passdb backend 'wbc_sam'
>>>>>>> Attempting to register passdb backend ldapsam
>>>>>>> Successfully added passdb backend 'ldapsam'
>>>>>>> Attempting to register passdb backend NDS_ldapsam
>>>>>>> Successfully added passdb backend 'NDS_ldapsam'
>>>>>>> Attempting to register passdb backend IPA_ldapsam
>>>>>>> Successfully added passdb backend 'IPA_ldapsam'
>>>>>>> Attempting to find a passdb backend to match tdbsam (tdbsam)
>>>>>>> Found pdb backend tdbsam
>>>>>>> pdb backend tdbsam has a valid init
>>>>>>> check lock order 1 for 
>>>>>>> /srv/progs/samba4/var/lock/smbXsrv_version_global.tdb
>>>>>>> release lock order 1 for 
>>>>>>> /srv/progs/samba4/var/lock/smbXsrv_version_global.tdb
>>>>>>>
>>>>>>> After this last line, it stop writing anything and wait 
>>>>>>> indefinitely...... but there's no listenning socket opened so 
>>>>>>> the daemon never listen and never be used....
>>>>>>>
>>>>>>>
>>>>>>> Is there a way to get more informations about why my smbd 
>>>>>>> doesn't work at all magically ?
>>>>>>>
>>>>>>> Thanks
>>>>>>> Regards,
>>>>>>> Bruno
>>>>>>>
>>>>>>
>>>>>
>>>> <SIGH> doesn't anybody read the smb.conf manpage ??
>>>>
>>>> Quite a lot of what you have in your global section should only be 
>>>> in a share and quite a lot of these are the defaults anyway!
>>>> Please don't use the  'socket options' line, the reason why is in 
>>>> the manpage.
>>>>
>>>> There is also one mistake (unless it is a typo), 'idmap config 
>>>> SAMDOM:schema = rfc2307' should be 'idmap config SAMDOM:schema_mode 
>>>> = rfc2307'
>>>>
>>>> Rowland
>>>
>>
>
Hi, when you first posted, you said that you were using samba 4.1.11 and 
as Ubuntu 14.04 comes with 4.1.6, I take it you compiled it yourself. 
Unless you add the required packages, shown here: 
https://wiki.samba.org/index.php/OS_Requirements#Debian_.2F_Ubuntu
Plus xsltproc and inkscape, you will not get the manpages built.

The manpage that you refer to, is for version 3 of samba, the manpage I 
referred to, is from the samba 4.1.11 packages install from backports on 
Debian wheezy that I use.

Rowland

More information about the samba mailing list