> I posted an question about something that might be the same problem in > ServerFault: > > http://serverfault.com/questions/527214/samba-4-file-server-will-not-allow-any-additional-users-to-log-on > > Den 10.07.13 16:43, skrev Andrew Martin: >> Hello, >> >> I am using Samba 4.0.6 on Ubuntu 12.04 with the internal DNS and dns >> forwarder set to forward to an upstream dnsmasq server as follows: >> [global] >> workgroup = EXAMPLE >> realm = EXAMPLE.COM >> netbios name = DC0 >> server role = active directory domain controller >> dns forwarder = 192.168.010 >> idmap_ldb:use rfc2307 = Yes >> >> # disable printing since we're not using it and to get rid of >> printcap errors in log >> printcap name = /dev/null >> load printers = no >> printing = bsd >> >> [netlogon] >> path = /var/lib/samba/sysvol/example.com/scripts >> read only = No >> >> [sysvol] >> path = /var/lib/samba/sysvol >> read only = No >> >> >> Samba 4 has been working well so far as an AD DC, however I have seen >> this message appear in the samba log: >> [2013/07/10 08:52:35, 0] >> ../source4/smbd/process_single.c:57(single_accept_connection) >> single_accept_connection: accept: NT_STATUS_TOO_MANY_OPENED_FILES >> >> I found this bug report and thread regarding this issue, and stating >> that it had been fixed in 4.0.0 rc3: >> https://bugzilla.samba.org/show_bug.cgi?id=8878 >> http://samba.2283325.n4.nabble.com/Samba3-gt-samba-4-td4638214.html >> >> I confirmed that the attached patch is indeed applied in my copy of >> 4.0.6. What else can I do to debug this problem? >> >> Thanks, >> >> Andrew >>
It happened to me too last weekend, with almost no users connected. but I'm using samba4 with bind_dlz. my samba4 last update was 2 weeks ago. Felix. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba