Hi Sean, Thanks for your reply, but that wasn't exactly what I was getting at.
I don't need to increase the system's imposed limit on the number of open files. I'm more concerned to see if anyone has run across a memory or fd leak in asterisk that sucks them all up. There should be no reason that I hit my limit of open files on this machine. Restarting asterisk immediately solved the problem, so I'm leaning towards a leak, however, I didn't have the opportunity, in the moment, to check and see how many files and what type were open. - Eric On Wed, 08 Dec 2004 16:48:19 +0000 Sean Cook <[EMAIL PROTECTED]> wrote: > Easiest thing (as long as filedescriptors are being closed properly) is > to increase the number of allowed open files: > > /proc/sys/fs/file-max > This file defines a system-wide limit on the number of open > files for all processes. (See also setrlimit(2), which can be > used by a process to set the per-process limit, RLIMIT_NOFILE, > on the number of files it may open.) If you get lots of error > messages about running out of file handles, try increasing this > value: > > echo 100000 > /proc/sys/fs/file-max > > The kernel constant NR_OPEN imposes an upper limit on the value > that may be placed in file-max. > > If you increase /proc/sys/fs/file-max, be sure to increase > /proc/sys/fs/inode-max to 3-4 times the new value of > /proc/sys/fs/file-max, or you will run out of inodes. > > > > > On Wed, 2004-12-08 at 16:26 -0500, Eric wrote: > > My asterisk process produced the following errors this morning: > > > > Dec 8 10:44:07 WARNING[50315282]: rtp.c:829 ast_rtp_new_with_bindaddr: > > Unable to allocate socket: Too many open files > > Dec 8 10:44:07 WARNING[50315282]: chan_sip.c:2352 sip_alloc: Unable to > > create RTP session: Too many open files > > Dec 8 10:44:07 WARNING[50315282]: chan_sip.c:8024 sip_request: Unable to > > build sip pvt data for '[EMAIL PROTECTED]' > > Dec 8 10:44:07 NOTICE[50315282]: app_dial.c:743 dial_exec: Unable to create > > channel of type 'SIP' > > > > I don't think it's related to the unreachable peer thing from last year, > > this machine only has one peer and a TE405p acting as a pure PSTN gateway. > > > > I restarted the process to fix the problem, however, I was wondering if > > anyone saw this problem with 1.0.1, and if so, any chance it was fixed > > for 1.0.2 or 1.0.3? > > > > Thanks. > > > > > > > > _______________________________________________ > > Asterisk-Users mailing list > > [EMAIL PROTECTED] > > http://lists.digium.com/mailman/listinfo/asterisk-users > > To UNSUBSCRIBE or update options visit: > > http://lists.digium.com/mailman/listinfo/asterisk-users > > _______________________________________________ > Asterisk-Users mailing list > [EMAIL PROTECTED] > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
