Re: Panic!

[Aarno Syvänen]

Did you configure with debug ? This would result an error message like that, because memery for debugging allocation is very small. Aarno On 5.7.2005, at 10.47, Saad Al-Khalfan wrote: Hi,   Has anyone seen something like this:   2005-07-02 12:00:44 [10] DEBUG: boxc_receiver: sms received 2005-07-02 12:00:44 [10] PANIC: Too many concurrent allocations. 2005-07-02 12:00:44 [3] DEBUG: HTTP: Resetting HTTPClient for `192.168.200.3'. 2005-07-02 12:00:44 [1] DEBUG: HTTP: Destroying HTTPClient area 0x81aec58. 2005-07-02 12:00:44 [1] DEBUG: HTTP: Destroying HTTPClient for `192.168.200.3'. 2005-07-02 12:00:44 [0] INFO: Connection closed by the bearerbox 2005-07-02 12:00:44 [0] INFO: Received (and handled?) 148 requests in 349287 seconds (0.00 per second) 2005-07-02 12:00:44 [0] INFO: Kannel smsbox terminating. 2005-07-02 12:00:44 [6] DEBUG: Thread 6 (gw/heartbeat.c:heartbeat_thread) terminates. 2005-07-02 12:00:44 [0] DEBUG: Waiting for 2 (gwlib/http.c:server_thread) to terminate 2005-07-02 12:00:44 [3] DEBUG: HTTP: No clients with requests, quitting. 2005-07-02 12:00:44 [3] DEBUG: Thread 3 (gw/smsbox.c:sendsms_thread) terminates. 2005-07-02 12:00:45 [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) terminates. 2005-07-02 12:00:45 [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) terminates. 2005-07-02 12:00:45 [0] DEBUG: Waiting for 4 (gw/smsbox.c:obey_request_thread) to terminate 2005-07-02 12:00:45 [4] DEBUG: Thread 4 (gw/smsbox.c:obey_request_thread) terminates. 2005-07-02 12:00:45 [0] DEBUG: Waiting for 5 (gw/smsbox.c:url_result_thread) to terminate 2005-07-02 12:00:45 [5] DEBUG: Thread 5 (gw/smsbox.c:url_result_thread) terminates. 2005-07-02 12:00:45 [0] DEBUG: Waiting for 8 (gwlib/http.c:write_request_thread) to terminate 2005-07-02 12:00:45 [8] DEBUG: Thread 8 (gwlib/http.c:write_request_thread) terminates. 2005-07-02 12:00:45 [7] DEBUG: Thread 7 (gwlib/fdset.c:poller) terminates. 2005-07-02 12:00:45 [0] DEBUG: Immutable octet strings: 158. 2005-07-02 12:00:45 [0] DEBUG: Current allocations: 151 areas, 2416 bytes 2005-07-02 12:00:45 [0] DEBUG: Highest number of allocations: 1687 areas 2005-07-02 12:00:45 [0] DEBUG: Highest memory usage: 74517 bytes 2005-07-02 12:00:45 [0] DEBUG: Area 0x43c0a338, size 16, max_size 16 2005-07-02 12:00:45 [0] DEBUG: Allocated by octstr_create_from_data_real at gwlib/octstr.c:170 2005-07-02 12:00:45 [0] DEBUG: Claimed by smsbox_req_handle at gw/smsbox.c:992 2005-07-02 12:00:45 [0] DEBUG: Contents of area (first 16 bytes): 2005-07-02 12:00:45 [0] DEBUG:   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2005-07-02 12:00:45 [0] DEBUG: Area 0x43c07f58, size 16, max_size 16 2005-07-02 12:00:45 [0] DEBUG: Allocated by octstr_create_from_data_real at gwlib/octstr.c:170 2005-07-02 12:00:45 [0] DEBUG: Claimed by smsbox_req_handle at gw/smsbox.c:992 2005-07-02 12:00:45 [0] DEBUG: Contents of area (first 16 bytes): 2005-07-02 12:00:45 [0] DEBUG:   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2005-07-02 12:00:45 [0] DEBUG: Area 0x43c04d60, size 16, max_size 16 2005-07-02 12:00:45 [0] DEBUG: Allocated by octstr_create_from_data_real at gwlib/octstr.c:170 2005-07-02 12:00:45 [0] DEBUG: Claimed by smsbox_req_handle at gw/smsbox.c:992 2005-07-02 12:00:45 [0] DEBUG: Contents of area (first 16 bytes): 2005-07-02 12:00:45 [0] DEBUG:   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00       Everything was working fine til I got this in the log and then nothing could be send through the kannel.   Regards, Saad ------------------------------Disclaimer------------------------------ This communication is intended for the above named person and is confidential and / or legally privileged. Any opinion(s) expressed in this communication are not necessarily those of the MTC. If it has come to you in error you must take no action based upon it, nor must you print it, copy it, forward it, or show it to anyone. Please delete and destroy the e-mail and any attachments and inform the sender immediately. Thank you. MTC is not responsible for the political, religious, racial or partisan opinion in any correspondence conducted by its domain users. Therefore, any such opinion expressed, whether explicitly or implicitly, in any said correspondence is not to be interpreted as that of MTC. MTC may monitor all incoming and outgoing e-mails in line with MTC business practice. Although MTC has taken steps to ensure that e-mails and attachments are free from any virus, we advise that, in keeping with best business practice, the recipient must ensure they are actually virus free. ----------------------------------------------------------------------