Your message dated Mon, 14 Nov 2022 16:27:30 +0300
with message-id <[email protected]>
and subject line Re: Bug#822812: samba: NT_STATUS_TOO_MANY_OPENED_FILES after
latest upgrade
has caused the Debian Bug report #822812,
regarding samba: NT_STATUS_TOO_MANY_OPENED_FILES after latest upgrade
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
822812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822812
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: samba
Version: 2:4.2.10+dfsg-0+deb8u2
Severity: normal
Dear Maintainer,
since the samba version in jessie was updated to 4.2 we have an issue with our
server that renders shares unusable. After they've been accessed for a small
amount of time, the log constantly shows:
single_accept_connection: accept: NT_STATUS_TOO_MANY_OPENED_FILES
In fact each samba process' /proc/*/limits file shows:
Max open files 1024 4096 files
>From what I read on the Internet this limit seems to be quite low for a
>frequently used Samba server.
ulimit -n in ssh shows 65536. I tried to increase the limit for samba by adding
a nofile configuration to /etc/security/limits.conf as well as adding a max
open files configuration to /etc/samba/smb.conf but it did not have any effect.
I also added pam_limits.so to /etc/pam.d/samba as I found that on the Internet,
however I doubt that it makes any sense in my situation as it is not about
per-login (smbd) processes but the limit is set for the main samba process and
every child.
I'm puzzled how to change the limit and why this shows up after the upgrade.
The server worked fine before.
Regards
Christopher
-- System Information:
Debian Release: 8.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages samba depends on:
ii adduser 3.113+nmu3
ii dpkg 1.17.26
ii libbsd0 0.7.0-2
ii libc6 2.19-18+deb8u4
ii libhdb9-heimdal [heimdal-hdb-api-8] 1.6~rc2+dfsg-9
ii libldb1 2:1.1.20-0+deb8u1
ii libpam-modules 1.1.8-3.1+deb8u1+b1
ii libpam-runtime 1.1.8-3.1+deb8u1
ii libpopt0 1.16-10
ii libpython2.7 2.7.9-2
ii libtalloc2 2.1.2-0+deb8u1
ii libtdb1 1.3.6-0+deb8u1
ii libtevent0 0.9.25-0+deb8u1
ii lsb-base 4.1+Debian13+nmu1
ii multiarch-support 2.19-18+deb8u4
ii procps 2:3.3.9-9
ii python 2.7.9-1
ii python-dnspython 1.12.0-1
ii python-ntdb 1.0-5
ii python-samba 2:4.2.10+dfsg-0+deb8u2
pn python2.7:any <none>
ii samba-common 2:4.2.10+dfsg-0+deb8u2
ii samba-common-bin 2:4.2.10+dfsg-0+deb8u2
ii samba-dsdb-modules 2:4.2.10+dfsg-0+deb8u2
ii samba-libs 2:4.2.10+dfsg-0+deb8u2
ii tdb-tools 1.3.6-0+deb8u1
ii update-inetd 4.43
Versions of packages samba recommends:
ii attr 1:2.4.47-2
ii logrotate 3.8.7-1+b1
ii samba-vfs-modules 2:4.2.10+dfsg-0+deb8u2
Versions of packages samba suggests:
pn bind9 <none>
pn bind9utils <none>
pn ctdb <none>
pn ldb-tools <none>
ii ntp 1:4.2.6.p5+dfsg-7+deb8u1
pn smbldap-tools <none>
ii winbind 2:4.2.10+dfsg-0+deb8u2
-- no debconf information
--- End Message ---
--- Begin Message ---
There was no reply to my inquiry and no other activity, let's assume the issue
is fixed.
If you think this is incorrect and the bug is still relevant with current
version of
samba, feel free to reopen this bugreport and provide some more information.
Thank you!
/mjt
--- End Message ---
