Prev: getent behavior since 3.5.x
Next: samba winbind is not showing full list
From: Jelle de Jong on 28 Jun 2010 04:20
On 22-06-10 14:54, Jelle de Jong wrote:
> I configured a running samba server that seems to work, except that
> the logs are full with failures, errors and warnings. They seem to be
> related to winbindd idmap and smbd endpoints.

I did some testing and purged winbindd from the system I thought it was
needed for my setup with "net sam provision" but it seems not needed for
normal runtime.

However I still get a lot of smbd warnings and errors. Could somebody
help me explaining these errors and possibly make suggestions how to fix
the issues causing them.

See the attached file for my configuration errors and samba version.

Thanks in advance,

With kind regards,

Jelle de Jong
From: Andrew Masterson on 28 Jun 2010 14:30
-----Original Message-----
From: samba-bounces(a)lists.samba.org
[mailto:samba-bounces(a)lists.samba.org] On Behalf Of Jelle de Jong
Sent: Monday, June 28, 2010 2:12 AM
To: samba(a)lists.samba.org
Subject: Re: [Samba] smbd errors failures and warnings in logs

On 22-06-10 14:54, Jelle de Jong wrote:
> I configured a running samba server that seems to work, except that
> the logs are full with failures, errors and warnings. They seem to be
> related to winbindd idmap and smbd endpoints.

I did some testing and purged winbindd from the system I thought it was
needed for my setup with "net sam provision" but it seems not needed for
normal runtime.

However I still get a lot of smbd warnings and errors. Could somebody
help me explaining these errors and possibly make suggestions how to fix
the issues causing them.

See the attached file for my configuration errors and samba version.

Thanks in advance,

With kind regards,

Jelle de Jong

----------

I have been getting similar errors (call_nt_transact_ioctl and
get_peer_addr_internal) for months/years now. After much searching many
other people have the same problems.

When there are no users connected to the systems the
get_peer_addr_internal errors seem to diminish in frequency (it seems
like a DNS issue), and disabling oplocks seems to have removed most of
the call_nt_transact_ioctl errors.

-=Andrew
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
 | 
Pages: 1
Prev: getent behavior since 3.5.x
Next: samba winbind is not showing full list