Summary:	ASTERISK-16708: Strange Message in 1.6.2 (64 Bits) only
Reporter:	Private Name (falves11)	Labels:
Date Opened:	2010-09-21 10:19:12	Date Closed:	2010-10-04 10:48:18
Priority:	Trivial	Regression?	No
Status:	Closed/Complete	Components:	Channels/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	Every time I start Asterisk or do a simple reload I see this message: "Cannot open maximum file descriptor 32767 at boot? No such file or directory" The people in the Asterisk users list think it is a bug.
Comments:	By: Private Name (falves11) 2010-09-21 11:13:27 Before you ask sysctl fs.file-max fs.file-max = 149346 core file size          (blocks, -c) unlimited data seg size           (kbytes, -d) unlimited scheduling priority             (-e) 0 file size               (blocks, -f) unlimited pending signals                 (-i) 400000 max locked memory       (kbytes, -l) 32 max memory size         (kbytes, -m) unlimited open files                      (-n) 400000 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) 12095 virtual memory          (kbytes, -v) unlimited file locks                      (-x) unlimited By: Private Name (falves11) 2010-09-21 11:14:12 It gives me this error in all my 1.6.2 boxes, regarding if they are virtual or physical. By: Private Name (falves11) 2010-09-21 11:21:08 The message only disappears if I set maxfiles=1024 in asterisk.conf By: Leif Madsen (lmadsen) 2010-09-21 14:22:38 I believe this issue has to deal with the system configuration and not Asterisk. I dealt with this same type of issue when doing load testing for Asterisk and I ran into an issue where I couldn't actually increase the file descriptor limit as I thought I could. This article helped me configure my system so that I could increase 'maxfiles' in asterisk.conf correctly: http://www.xenoclast.org/doc/benchmark/HTTP-benchmarking-HOWTO/node7.html By: Private Name (falves11) 2010-09-21 14:29:43 I read the document and it is inapplicable since my ulimit is already much higher than 1024, as you may see above, and my fs.file-max is way over 1024. There is something else lurking here. By: Private Name (falves11) 2010-09-21 14:32:04 I don't think this a trivial matter. Without access to more than 1024 file descriptors, Asterisk will become trivial itself. Kindly change it back to "minor" By: Private Name (falves11) 2010-09-21 15:35:13 I believe the explanation is in this section http://www.mail-archive.com/svn-commits@lists.digium.com/msg51758.html Can somebody please tell me what is Asterisk reading from or comparing to when the error is generated? By: Leif Madsen (lmadsen) 2010-09-21 15:35:40 What is the output of ulimit -aS? By: Private Name (falves11) 2010-09-21 15:38:03 ulimit -aS core file size          (blocks, -c) unlimited data seg size           (kbytes, -d) unlimited scheduling priority             (-e) 0 file size               (blocks, -f) unlimited pending signals                 (-i) 400000 max locked memory       (kbytes, -l) 32 max memory size         (kbytes, -m) unlimited open files                      (-n) 400000 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) 12095 virtual memory          (kbytes, -v) unlimited file locks                      (-x) unlimited I can give you access to the box if you prefer. Just email me. By: Leif Madsen (lmadsen) 2010-09-21 15:52:00 Sorry, I don't have time to debug your system. A developer will request information as time permits. By: Stefan Schmidt (schmidts) 2010-09-21 16:52:39 could you please try to update on the latest revision. on this row of asterisk.c where you see this error, there was a change on rev 287934. maybe this is allready fixed. By: Private Name (falves11) 2010-09-21 17:23:35 Yes, the error does not pop up anymore. Thanks for your help. Now, what is the ideal amount for maxfiles there? with 300 open calls, no media, mostly signaling? And let's reflect on the "dismissive" behavior of whoever lowered this BUG to "trivial" from "minor". Before I filed the bug I obviously spent some hours checking all the usual suspects, and then filed the bug. There is an attitude problem, pretty consistent, against us "business" users, from the developers. We are not capable of developing a single line of C, but we certainly keep the industry working. Guess who pays Digium bills? We do. Thank you. By: Stefan Schmidt (schmidts) 2010-09-21 17:32:26 i dont know the best value for maxfiles. the severity does not tell how important a issue is (except crash), it shows how many users could have this issue. I understand that you are not happy about such issue handling but at least 7 hours from opening to resolve is not that bad ;) By: Private Name (falves11) 2010-09-21 17:36:48 I am very happy about the resolution, but my ego was battered a bit. Nevertheless, reason prevailed. Thanks again and I apologize for the rant.