samba - Oct 2019 - message error NT_STATUS_OBJECT_NAME_NOT_FOUND regulary in the log

Le 16/10/2019 ? 12:07, Rowland penny via samba a ?crit?:
> On 16/10/2019 10:59, nathalie ramat wrote:
>> ???????????? Checking file: /etc/samba/smb.conf
>>
>> # Global parameters
>> [global]
>> ?????? dns forwarder = 192.168.xx.230
> You cannot forward to the DC itself, it needs to be a dns server 
> outside the AD dns domain.
>> ?????? netbios name = BLUEYESTEST
>> ?????? realm = SAMBADOM.CALAIS.FR
>> ?????? server role = active directory domain controller
>> ?????? workgroup = SAMBADOM
>> ?????? idmap_ldb:use rfc2307 = yes
>> ?????? log level = 3
>> ?????? log file = /var/log/samba/log.%M
>>
>> [sysvol]
>> ?????? path = /var/lib/samba/sysvol
>> ?????? read only = No
>>
>> [netlogon]
>> ?????? path = /var/lib/samba/sysvol/sambadom.calais.fr/scripts
>> ?????? read only = No
>>
>> -----------
>>
>> *BIND_DLZ not detected in smb.conf --Why i have this message - I 
>> choose samba_internal with i used samba-tool domain *
>
> You get that message to confirm that smb.conf isn't set up to use 
> Bind9, it is nothing to worry about.
>
> The question has to be, why didn't your smb.conf show up the first time
?
>
I don't know. I restarted the script several times and each time the 
file smb.conf is present

I modified my dns forwarded in my? smb.conf but I have always errors 
with smbd

/usr/sbin/smbd: pid_to_procid: messaging_dgm_get_unique failed: Aucun 
fichier ou dossier de ce type
/usr/sbin/smbd: send_all_fn: messaging_send_buf to 20756 failed: 
NT_STATUS_OBJECT_NAME_NOT_FOUND
/usr/sbin/smbd: send_all_fn: messaging_send_buf to 20726 failed: 
NT_STATUS_OBJECT_NAME_NOT_FOUND
/usr/sbin/smbd: send_all_fn: messaging_send_buf to 20765 failed: 
NT_STATUS_OBJECT_NAME_NOT_FOUND
/usr/sbin/smbd: send_all_fn: messaging_send_buf to 20750 failed: 
NT_STATUS_OBJECT_NAME_NOT_FOUND
/usr/sbin/smbd: samba_tevent: EPOLL_CTL_DEL EBADF for 
fde[0x556f777743c0] mpx_fde[(nil)] fd[35] - disabling


I saw that this error is always after

/usr/sbin/smbd: reloading printcap cache
/usr/sbin/smbd: reload status: ok
/usr/sbin/smbd: pid_to_procid: messaging_dgm_get_unique failed: Aucun 
fichier ou dossier de ce type
/usr/sbin/smbd: send_all_fn: messaging_send_buf to 15718 failed: 
NT_STATUS_OBJECT_NAME_NOT_FOUND
/usr/sbin/smbd: samba_tevent: EPOLL_CTL_DEL EBADF for 
fde[0x55b6941c2c20] mpx_fde[(nil)] fd[35] - disabling


I have not configured printers -- Is it a problem ?
> Rowland
>
>
>
-- 
Nathalie RAMAT-LECLERCQ

Service Informatique

Universite du Littoral-C?te d'Opale
SCoSI - Service Commun du Syst?me d'Information
P?le Syst?mes et r?seaux

Centre de Gestion Universitaire de Calais
50 rue ferdinand Buisson
C.S 80699
62228 CALAIS CEDEX

On 16/10/2019 11:33, nathalie ramat wrote:
>
>
> Le 16/10/2019 ? 12:07, Rowland penny via samba a ?crit?:
>> On 16/10/2019 10:59, nathalie ramat wrote:
>>> ???????????? Checking file: /etc/samba/smb.conf
>>>
>>> # Global parameters
>>> [global]
>>> ?????? dns forwarder = 192.168.xx.230
>> You cannot forward to the DC itself, it needs to be a dns server 
>> outside the AD dns domain.
>>> ?????? netbios name = BLUEYESTEST
>>> ?????? realm = SAMBADOM.CALAIS.FR
>>> ?????? server role = active directory domain controller
>>> ?????? workgroup = SAMBADOM
>>> ?????? idmap_ldb:use rfc2307 = yes
>>> ?????? log level = 3
>>> ?????? log file = /var/log/samba/log.%M
>>>
>>> [sysvol]
>>> ?????? path = /var/lib/samba/sysvol
>>> ?????? read only = No
>>>
>>> [netlogon]
>>> ?????? path = /var/lib/samba/sysvol/sambadom.calais.fr/scripts
>>> ?????? read only = No
>>>
>>> -----------
>>>
>>> *BIND_DLZ not detected in smb.conf --Why i have this message - I 
>>> choose samba_internal with i used samba-tool domain *
>>
>> You get that message to confirm that smb.conf isn't set up to use 
>> Bind9, it is nothing to worry about.
>>
>> The question has to be, why didn't your smb.conf show up the first 
>> time ?
>>
>
> I don't know. I restarted the script several times and each time the 
> file smb.conf is present
>
> I modified my dns forwarded in my? smb.conf but I have always errors 
> with smbd
>
> /usr/sbin/smbd: pid_to_procid: messaging_dgm_get_unique failed: Aucun 
> fichier ou dossier de ce type
> /usr/sbin/smbd: send_all_fn: messaging_send_buf to 20756 failed: 
> NT_STATUS_OBJECT_NAME_NOT_FOUND
> /usr/sbin/smbd: send_all_fn: messaging_send_buf to 20726 failed: 
> NT_STATUS_OBJECT_NAME_NOT_FOUND
> /usr/sbin/smbd: send_all_fn: messaging_send_buf to 20765 failed: 
> NT_STATUS_OBJECT_NAME_NOT_FOUND
> /usr/sbin/smbd: send_all_fn: messaging_send_buf to 20750 failed: 
> NT_STATUS_OBJECT_NAME_NOT_FOUND
> /usr/sbin/smbd: samba_tevent: EPOLL_CTL_DEL EBADF for 
> fde[0x556f777743c0] mpx_fde[(nil)] fd[35] - disabling
>
>
> I saw that this error is always after
>
> /usr/sbin/smbd: reloading printcap cache
> /usr/sbin/smbd: reload status: ok
> /usr/sbin/smbd: pid_to_procid: messaging_dgm_get_unique failed: Aucun 
> fichier ou dossier de ce type
> /usr/sbin/smbd: send_all_fn: messaging_send_buf to 15718 failed: 
> NT_STATUS_OBJECT_NAME_NOT_FOUND
> /usr/sbin/smbd: samba_tevent: EPOLL_CTL_DEL EBADF for 
> fde[0x55b6941c2c20] mpx_fde[(nil)] fd[35] - disabling
>
>
> I have not configured printers -- Is it a problem ?
Could be, it defaults to 'printcap name = /etc/printcap' and that may 
not exist. if you are not going to use printers on the DC, try adding 
these lines to your DC smb.conf:

 ??????? load printers = no
 ??????? printing = bsd
 ??????? printcap name = /dev/null
 ??????? disable spoolss = yes

Rowland

Le 16/10/2019 ? 12:43, Rowland penny via samba a ?crit?:
> On 16/10/2019 11:33, nathalie ramat wrote:
>>
>>
>> Le 16/10/2019 ?? 12:07, Rowland penny via samba a ??crit??:
>>> On 16/10/2019 10:59, nathalie ramat wrote:
>>>> ???????????????????????? Checking file: /etc/samba/smb.conf
>>>>
>>>> # Global parameters
>>>> [global]
>>>> ???????????? dns forwarder = 192.168.xx.230
>>> You cannot forward to the DC itself, it needs to be a dns server 
>>> outside the AD dns domain.
>>>> ???????????? netbios name = BLUEYESTEST
>>>> ???????????? realm = SAMBADOM.CALAIS.FR
>>>> ???????????? server role = active directory domain controller
>>>> ???????????? workgroup = SAMBADOM
>>>> ???????????? idmap_ldb:use rfc2307 = yes
>>>> ???????????? log level = 3
>>>> ???????????? log file = /var/log/samba/log.%M
>>>>
>>>> [sysvol]
>>>> ???????????? path = /var/lib/samba/sysvol
>>>> ???????????? read only = No
>>>>
>>>> [netlogon]
>>>> ???????????? path =
/var/lib/samba/sysvol/sambadom.calais.fr/scripts
>>>> ???????????? read only = No
>>>>
>>>> -----------
>>>>
>>>> *BIND_DLZ not detected in smb.conf --Why i have this message -
I
>>>> choose samba_internal with i used samba-tool domain *
>>>
>>> You get that message to confirm that smb.conf isn't set up to
use
>>> Bind9, it is nothing to worry about.
>>>
>>> The question has to be, why didn't your smb.conf show up the
first
>>> time ?
>>>
>>
>> I don't know. I restarted the script several times and each time
the
>> file smb.conf is present
>>
>> I modified my dns forwarded in my?? smb.conf but I have always errors 
>> with smbd
>>
>> /usr/sbin/smbd: pid_to_procid: messaging_dgm_get_unique failed: Aucun 
>> fichier ou dossier de ce type
>> /usr/sbin/smbd: send_all_fn: messaging_send_buf to 20756 failed: 
>> NT_STATUS_OBJECT_NAME_NOT_FOUND
>> /usr/sbin/smbd: send_all_fn: messaging_send_buf to 20726 failed: 
>> NT_STATUS_OBJECT_NAME_NOT_FOUND
>> /usr/sbin/smbd: send_all_fn: messaging_send_buf to 20765 failed: 
>> NT_STATUS_OBJECT_NAME_NOT_FOUND
>> /usr/sbin/smbd: send_all_fn: messaging_send_buf to 20750 failed: 
>> NT_STATUS_OBJECT_NAME_NOT_FOUND
>> /usr/sbin/smbd: samba_tevent: EPOLL_CTL_DEL EBADF for 
>> fde[0x556f777743c0] mpx_fde[(nil)] fd[35] - disabling
>>
>>
>> I saw that this error is always after
>>
>> /usr/sbin/smbd: reloading printcap cache
>> /usr/sbin/smbd: reload status: ok
>> /usr/sbin/smbd: pid_to_procid: messaging_dgm_get_unique failed: Aucun 
>> fichier ou dossier de ce type
>> /usr/sbin/smbd: send_all_fn: messaging_send_buf to 15718 failed: 
>> NT_STATUS_OBJECT_NAME_NOT_FOUND
>> /usr/sbin/smbd: samba_tevent: EPOLL_CTL_DEL EBADF for 
>> fde[0x55b6941c2c20] mpx_fde[(nil)] fd[35] - disabling
>>
>>
>> I have not configured printers -- Is it a problem ?
>
> Could be, it defaults to 'printcap name = /etc/printcap' and that
may
> not exist. if you are not going to use printers on the DC, try adding 
> these lines to your DC smb.conf:
>
> ?????????????? load printers = no
> ?????????????? printing = bsd
> ?????????????? printcap name = /dev/null
> ?????????????? disable spoolss = yes
>
I modified my smb.conf and all errors messages disappeared.


Thank you for your help

> Rowland
>
>
>
-- 
Nathalie RAMAT-LECLERCQ

Service Informatique

Universite du Littoral-C?te d'Opale
SCoSI - Service Commun du Syst?me d'Information
P?le Syst?mes et r?seaux

Centre de Gestion Universitaire de Calais
50 rue ferdinand Buisson
C.S 80699
62228 CALAIS CEDEX