RE: PANIC: Too many concurrent allocations
yep i have seen this problem with 1.1.5 I have a simulator that the best i get is about 20 msgs per second before getting the same errors ... this was with 4 different connections sendinging a request to an application not just a nop -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of ml Sent: Thursday, 25 October 2001 5:55 p.m. To: [EMAIL PROTECTED] Subject: PANIC: Too many concurrent allocations hi, Jörg we met the problem too. but if we compile kannel with native malloc mode , the following PANIC occur, 2001-10-08 17:57:50 [8] PANIC: mutex_unlock: Mutex failure! 2001-10-08 17:57:50 [8] PANIC: System error 22: Invalid argument thanks best regards ml - Original Message - From: Jörg Pommnitz [EMAIL PROTECTED] To: 'Tim Hammonds' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, October 25, 2001 12:12 AM Subject: AW: PANIC: Too many concurrent allocations It's either a bug in Kannel (memory leak) or a heavily stressed system running in debug limits. If it's not a memory leak, you can prevent the emergency shutdown by disabling debug malloc while calling configure. Regards Jörg -Ursprüngliche Nachricht- Von: Tim Hammonds [mailto:[EMAIL PROTECTED]] Gesendet am: Mittwoch, 24. Oktober 2001 17:58 An: [EMAIL PROTECTED] Betreff: PANIC: Too many concurrent allocations I am using a cvs version of Kannel as an SMS Gateway to a UCP/EMI SMSC. I was originally having throughput problems with Kannel V1.1.5, as the SMSC was ignoring messages sent if they received more than 5 a second. My earlier posting to this list resulted in the suggestion that I use the CVS version as it has flow control built in and the stop-and-wait protocol would sort things out. By setting flow-control to 1 in the config, Kannel now waits for the ACK from the SMSC and the maximum throughput is achieved. Great stuff. My next problems is that after submitting batches of (over 2000) messages to Kannel (using the http interface) I invariably get the message PANIC: Too many concurrent allocations in the log file followed by the Kannel processes dying and the remainder of the messages in the batch being lost. Is this a Kannel issue, Linux/Kernel issue, hardware issue, network issue or SMSC issue? Have any of you kind people got a suggestion as to what causes this problem and how I can overcome it, as I need to use Kannel in a live system! Regards, Tim.
RE: Kannel 1.1.5 and bug with SMPP protocol and @-character?
I had this problem a long time ago with 1.0.3 :) Richard Braakman suggested : In smsc_smpp.h, the line that has '@', change 0x64 to just 64. Hope this helps... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Andreas Fink Sent: Friday, 26 October 2001 4:32 a.m. To: Jim Walsh Cc: [EMAIL PROTECTED] Subject: RE: Kannel 1.1.5 and bug with SMPP protocol and @-character? It's my understaning that kannel uses latin-1 character set, shouldn't @ be replaced with 0x40, as 0x00 relates to ^@ symbol? -Original Message- Hi and thanx for your answer! I used Logica's 2700 SMSC with SMPP v3.4 (kannel only supports v3.3, so I used 3.3). I also looked at the packages sent out (with tcpdump) and noticed that @ was converted to 0x00. So, can it really be SMSC bug or does it just need different encoding? yours, Veljo In latin-1 @ is 0x40 but in GSM default character set it is 0x00. Kannel converts between iso-latin-1 and GSM default character set before sending it to the SMSC. Check your documentation on what the SMSC would expect. by the way, Kannel very well supports SMPP v3.4 and v3.3. -- Andreas Fink Fink-Consulting -- Tel: +41-61-6932730 Fax: +41-61-6932729 Mobile: +41-79-2457333 Address: A. Fink, Schwarzwaldallee 16, 4058 Basel, Switzerland E-Mail: [EMAIL PROTECTED] Homepage: http://www.finkconsulting.com -- Something urgent? Try http://www.smsrelay.com/ Nickname afink
Number portability
Has anyone asked this question ? How does one handle number portability ? I have kannel with multiple SMSC connections from different countries. if Country A has 4 providers all connected to kannel so far I have only seen prefix routing ? Now number portability means that these numbers can be from any provider and the prefix won't route correctly ? How does kannel plan to get around this or has this been fixed/added in a later release ? Regards, Neville MacAlister
RE: Number portability
Thanks for the response also Stephen Rothwell... not what I was hoping to hear as number portability is an issue for me and no doubt many others. Obviously kannel knows which network a message is supplied from due to the fact that it comes in from SMSC-1 or SMSC-2 So maybe an attribute could be sent through with each message. This would enable an app to be able to respond to a correct gateway rather than flooding availble gateways with requests. My main concern is routing traffic over GSM internationally when not needed. Just my 5 cents worth ... Thanks again. -Original Message- From: Andreas Fink [mailto:[EMAIL PROTECTED]] Sent: Thursday, 25 October 2001 12:37 p.m. To: Nev Cc: [EMAIL PROTECTED] Subject: Re: Number portability Has anyone asked this question ? How does one handle number portability ? I have kannel with multiple SMSC connections from different countries. if Country A has 4 providers all connected to kannel so far I have only seen prefix routing ? Now number portability means that these numbers can be from any provider and the prefix won't route correctly ? How does kannel plan to get around this or has this been fixed/added in a later release ? there's no way around this as this involves SS7 database lookups to find out where the user currently is subscribed. Kannel doesnt have any way of knowing this.
