samba - Jun 2013 - Samba4 errors

Hello,
We've been using samba v4 for a while, but recently we faced two problems
for which we cannot determine the source - nor the solution:
- every day samba4 stops authenticating new users and sharing folders.
While previous logged users can access resources and services, users that
weren't logged can't log in. It happens either from kerberos or directly
from LDAP.
- We are forwarding all DNS requests to the internal DNS server in samba.
When samba it's restarted, our main DNS server must be restarted too as it
cannot forward new queries to the samba server - howerver, both reply to
requests if queried individually.

We have tried to update from 4.0.5 to 4.0.6, and to downgrade it as it
wasn't working either.

Logs don't show anything that we can identify as an error/misconfiguration
- and samba main log file remains with extension %m, it does not get
expanded; while client's log file end with the IP/hostname of the machine.

What steps can we perform to identify the root of the problem?
Is there a particular string in the log files that can help?

PS: if necessary, we can upload a log file sample and the samba
configuration.

Thanks in advance.

We found out that samba is performing connections on the RPC port (TCP 445)
against itself, and it scales until the memory is gone completely and
crashes.

Any hint?


On Mon, Jun 10, 2013 at 3:08 PM, Andreas Calvo <flipy.bcn at gmail.com>
wrote:
> Hello,
> We've been using samba v4 for a while, but recently we faced two
problems
> for which we cannot determine the source - nor the solution:
> - every day samba4 stops authenticating new users and sharing folders.
> While previous logged users can access resources and services, users that
> weren't logged can't log in. It happens either from kerberos or
directly
> from LDAP.
> - We are forwarding all DNS requests to the internal DNS server in samba.
> When samba it's restarted, our main DNS server must be restarted too as
it
> cannot forward new queries to the samba server - howerver, both reply to
> requests if queried individually.
>
> We have tried to update from 4.0.5 to 4.0.6, and to downgrade it as it
> wasn't working either.
>
> Logs don't show anything that we can identify as an
error/misconfiguration
> - and samba main log file remains with extension %m, it does not get
> expanded; while client's log file end with the IP/hostname of the
machine.
>
> What steps can we perform to identify the root of the problem?
> Is there a particular string in the log files that can help?
>
> PS: if necessary, we can upload a log file sample and the samba
> configuration.
>
> Thanks in advance.
>


-- 
Atentamente,
Andreas Calvo