Kalle Marjola wrote: >On 24 May 2002, Abd Rahman Johari wrote: > > >>I'm trying to send out SMS Broadcast and after a while kannel just die >>because of PANIC: Too many concurrent allocations >> >> > >You need to compile Kannel with non-checking malloc, i.e. use native >malloc. ./configure --with-defaults=speed or --with-malloc=native should >help. >
Further question: In general situation, does this really correct problems or just hide them? I though that the checking malloc spots errors and making error messages to go away by just not checking anymore sounds quite hazard.. Or is it so, that this "Too many concurrent allocations" checking failing does not always mean there is an error? I have got the smsbox to panic this way when put under too heavy load and bearerbox when restoring big enough store file (1000+ messages), and these sound like this message would occur more often when Kannel is put under high pressure (and possibly making much concurrent allocations for some good reason?). Example of bearerbox log when latter happens: 2002-05-31 14:17:28 [0] INFO: Loading store file /var/log/kannel/kannel.store 2002-05-31 14:17:28 [0] INFO: Store-file size 386359, starting to unpack (may take awhile) 2002-05-31 14:17:28 [17] DEBUG: sms_router: time to sleep 2002-05-31 14:17:28 [17] DEBUG: sms_router: list_len = 0 2002-05-31 14:17:28 [0] INFO: Retrieved 1012 messages, non-acknowledged messages: 1001 2002-05-31 14:17:28 [0] PANIC: Too many concurrent allocations.
