I've been testing both T400P and TE405P boards and I'm running into some kind of hard limit on the number of simultaneous calls. This is on x86 with 2 Athlon MP 2800+ CPUs running Fedora Core 1. Everything is fine up to 190 channels, but the 191st call fails every time with errors like: Dec 14 15:44:00 WARNING[1215]: Unable to start PBX on Zap/201-1 Dec 14 15:44:00 WARNING[1215]: Failed to create update thread! Dec 14 15:44:00 WARNING[1215]: Unable to start PBX on channel 0/9, span 9 Dec 14 15:44:00 WARNING[1215]: Call specified, but not found? Dec 14 15:44:00 WARNING[1215]: Hangup on bad channel 0/9 on span 9 It's not tied to which channel the call comes in on. It's some resource that's exhausted after 190 calls. A limit on threads? I thought it might be per-process file descriptors even though we were only going up to 529 on that PID and I used 'ulimit -n' to increase it before starting asterisk, but that didn't make a difference. # cat /proc/sys/kernel/threads-max 14336 I would think that's enough, but perhaps the per-process limit is much lower. Any clues? Thanks...
Hello, Have you analized quality of the calls ? what was quality of 190 call ? :) On Thu, 16 Dec 2004 19:51:28 -0800, Jim Gottlieb <jimmy@nccom.com> wrote:> I've been testing both T400P and TE405P boards and I'm running into > some kind of hard limit on the number of simultaneous calls. This is > on x86 with 2 Athlon MP 2800+ CPUs running Fedora Core 1. > > Everything is fine up to 190 channels, but the 191st call fails every > time with errors like: > > Dec 14 15:44:00 WARNING[1215]: Unable to start PBX on Zap/201-1 > Dec 14 15:44:00 WARNING[1215]: Failed to create update thread! > Dec 14 15:44:00 WARNING[1215]: Unable to start PBX on channel 0/9, span 9 > Dec 14 15:44:00 WARNING[1215]: Call specified, but not found? > Dec 14 15:44:00 WARNING[1215]: Hangup on bad channel 0/9 on span 9 > > It's not tied to which channel the call comes in on. It's some > resource that's exhausted after 190 calls. A limit on threads? > > I thought it might be per-process file descriptors even though we were > only going up to 529 on that PID and I used 'ulimit -n' to increase it > before starting asterisk, but that didn't make a difference. > > # cat /proc/sys/kernel/threads-max > 14336 > > I would think that's enough, but perhaps the per-process limit is much > lower. > > Any clues? > > Thanks... > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-- Vitaly Nikolaev
On 2004-12-17 at 12:13, Vitaly Nikolaev (nvitaly@gmail.com) wrote:> Have you analized quality of the calls ? what was quality of 190 call ? :)Quality was perfect and a load average of only about 2.
Jim Gottlieb wrote:>I've been testing both T400P and TE405P boards and I'm running into >some kind of hard limit on the number of simultaneous calls. This is >on x86 with 2 Athlon MP 2800+ CPUs running Fedora Core 1. > >Everything is fine up to 190 channels, but the 191st call fails every >time with errors like: > >Dec 14 15:44:00 WARNING[1215]: Unable to start PBX on Zap/201-1 >Dec 14 15:44:00 WARNING[1215]: Failed to create update thread! >Dec 14 15:44:00 WARNING[1215]: Unable to start PBX on channel 0/9, span 9 >Dec 14 15:44:00 WARNING[1215]: Call specified, but not found? >Dec 14 15:44:00 WARNING[1215]: Hangup on bad channel 0/9 on span 9 > >It's not tied to which channel the call comes in on. It's some >resource that's exhausted after 190 calls. A limit on threads? > >Try http://people.redhat.com/alikins/tuning_utils/thread-limit.c and see what happens. Nick
Hi!> >Everything is fine up to 190 channels, but the 191st call fails every > >time with errors like: > > > >Dec 14 15:44:00 WARNING[1215]: Unable to start PBX on Zap/201-1 > >Dec 14 15:44:00 WARNING[1215]: Failed to create update thread! > >Dec 14 15:44:00 WARNING[1215]: Unable to start PBX on channel 0/9, span 9 > >Dec 14 15:44:00 WARNING[1215]: Call specified, but not found? > >Dec 14 15:44:00 WARNING[1215]: Hangup on bad channel 0/9 on span 9 > > > >It's not tied to which channel the call comes in on. It's some > >resource that's exhausted after 190 calls. A limit on threads?>From what I know there is an asterisk-inherent limit of 250 (255?) Zapchannels that you won't be able to surpass. I know that this doesn't explain your 191st call problem, but since you asked... :-) Cheers, Philipp