Server crashed Named.run "too many open file descriptors"
 

I've been having lot of server crashes lately and the cause is because named.run is eating up space of errors from i think caused by shoutcast. It consume the hard disk until there is no space and the server becomes unstable.

I had to delete named.run files regularly to free up space and make the server run again. Checking named.run file I got this full or errors

"accept: too many open file descriptors
accept: too many open file descriptors
accept: too many open file descriptors
accept: too many open file descriptors
accept: too many open file descriptors
accept: too many open file descriptors
accept: too many open file descriptors"


--------------------

I already increased ulimit and file-max as stated on other threads.

**MY u-limit

root@server [/var/log/mysql]# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 256435
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 65535
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 65535
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited

**MY /etc/security/limits.conf
* soft nproc 65535
* hard nproc 65535
* soft nofile 65535
* hard nofile 65535


**MY /etc/sysctl.conf
net.ipv4.ip_forward = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
kernel.sysrq = 0

kernel.core_uses_pid = 1

net.ipv4.tcp_syncookies = 1

net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0

kernel.msgmnb = 65536
kernel.msgmax = 65536
kernel.shmmax = 68719476736
kernel.shmall = 4294967296
fs.file-max = 65536


Any ideas? Please help. Thanks in advance.

do you know where you are?

What do you mean? I'm seeking help on why im getting this errors.

DNAS version? and what do you mean by "named run files" ?

How is that a problem with shoutcast ...

named is a domain name server - a fast growing named.run file indicates

a) you have named running in debug mode (why?)
b) something is hitting the local named DNS server, and having problems

which all points to misconfigured named service, and f**k all to do with shoutcast


edit: I see where you went completely wrong

shoutcast = DNAS

named = DNS

they are not related one bit :rolleyes:

if you *think* it's caused by shoutcast, why did you not supply ANY configuration information for said product?

well, it could be caused by Shoutcast service(sc_serv or sc_trans). Why? Because i got so many concurrent listeners which could mean i have many open file streams or open files that would cause that error logs in named-run files. Researching this forum said to increase the ulimit and other values (sysctl.conf) to increase allowed open files which I did.

It "could" be caused by shoutcast that's why im trying to seek help in this forum. I would appreciate it if you can actually help me and not to get bashed instead.

I'm using SHOUTcast Server v2.0.0.29/posix(linux x64)

Thanks in advance.

that version of the DNAS is not supported. update to the current release (as per the sticky threads).

10's of thousands - yeah

I WAS trying to help the second post ...

let me help you betterer then

http://lmgtfy.com/?q=big+named.run+file