Dear list I've found that kannel bearerbox panics if ANY of the configured smsc_at modems is not available...
i.e. If when kannel starts any of the modems if for example turned off or somehow blocked, the kannel's bearerbox panics. Is this behaviour the expected? If so I think this should be changed. Kannel should continue with the process of the startup of rest of smsc and just have the "offending" smsc_at marked as died, as when we shutdown an smsc. This is the bearerbox log. Note: I 've found that this happens with modems configured as raw tcp/ports. Don't know with serial/usb modems. 2008-11-24 17:59:23 [30863] [0] INFO: ---------------------------------------- 2008-11-24 17:59:23 [30863] [0] INFO: Kannel bearerbox II version cvs-20081115 starting 2008-11-24 17:59:23 [30863] [0] INFO: MAIN: Start-up done, entering mainloop 2008-11-24 17:59:23 [30863] [0] DEBUG: AT2[t1]: start called 2008-11-24 17:59:23 [30863] [0] DEBUG: AT2[t2]: start called 2008-11-24 17:59:23 [30863] [0] DEBUG: AT2[t3]: start called 2008-11-24 17:59:23 [30863] [0] DEBUG: AT2[t4]: start called 2008-11-24 17:59:23 [30863] [0] DEBUG: AT2[m1]: start called 2008-11-24 17:59:23 [30863] [0] DEBUG: AT2[m2]: start called 2008-11-24 17:59:23 [30863] [0] DEBUG: AT2[m3]: start called 2008-11-24 17:59:23 [30863] [0] DEBUG: AT2[m4]: start called 2008-11-24 17:59:23 [30863] [23] DEBUG: Thread 23 (gw/smsc/smsc_http.c:httpsmsc_receiver) maps to pid 30863. 2008-11-24 17:59:23 [30863] [23] INFO: Logging thread `23' to logfile `/var/log/kannel/n1.log' with level `0'. 2008-11-24 17:59:23 [30863] [29] DEBUG: Thread 29 (gw/bb_boxc.c:wapboxc_run) maps to pid 30863. 2008-11-24 17:59:23 [30863] [25] DEBUG: Thread 25 (gw/smsc/smsc_http.c:httpsmsc_receiver) maps to pid 30863. 2008-11-24 17:59:23 [30863] [25] INFO: Logging thread `25' to logfile `/var/log/kannel/n2.log' with level `0'. 2008-11-24 17:59:23 [30863] [30] DEBUG: Thread 30 (gw/bearerbox.c:wdp_router) maps to pid 30863. 2008-11-24 17:59:23 [30863] [26] DEBUG: Thread 26 (gw/smsc/smsc_http.c:httpsmsc_send_cb) maps to pid 30863. 2008-11-24 17:59:23 [30863] [26] INFO: Logging thread `26' to logfile `/var/log/kannel/n2.log' with level `0'. 2008-11-24 17:59:23 [30863] [27] DEBUG: Thread 27 (gw/bb_smscconn.c:sms_router) maps to pid 30863. 2008-11-24 17:59:23 [30863] [28] DEBUG: Thread 28 (gw/bb_boxc.c:wdp_to_wapboxes) maps to pid 30863. 2008-11-24 17:59:23 [30863] [28] DEBUG: wdp_to_wapboxes: destroying lists 2008-11-24 17:59:23 [30863] [28] DEBUG: Thread 28 (gw/bb_boxc.c:wdp_to_wapboxes) terminates. 2008-11-24 17:59:24 [30863] [10] PANIC: AT2[t4]: Cannot detect modem and generic not found 2008-11-24 17:59:24 [30863] [10] PANIC: /usr/local/sbin/bearerbox(gw_panic+0xc2) [0x80cdfe2] 2008-11-24 17:59:24 [30863] [10] PANIC: /usr/local/sbin/bearerbox [0x806dd22] 2008-11-24 17:59:24 [30863] [10] PANIC: /usr/local/sbin/bearerbox [0x806e8b1] 2008-11-24 17:59:24 [30863] [10] PANIC: /usr/local/sbin/bearerbox [0x80c4871] 2008-11-24 17:59:24 [30863] [10] PANIC: /lib/libpthread.so.0 [0x4c83db] 2008-11-24 17:59:24 [30863] [10] PANIC: /lib/libc.so.6(clone+0x5e) [0x5a726e] Modem config =========== group = smsc smsc = at smsc-id = t4 modemtype = auto speed = 115200 log-level = 0 log-file = "/var/log/kannel/x1p3_4.log" allowed-smsc-id = t1;t4;t2_3 sim-buffering = true keepalive = 60 max-error-count = 8 device = rawtcp host = 10.10.5.3 port = 2300 Modem LOG ========== 2008-11-24 16:18:54 [11361] [10] DEBUG: AT2[4]: <-- +CMS ERROR: failed to abort 2008-11-24 16:18:54 [11361] [10] ERROR: AT2[4]: CMS ERROR: +CMS ERROR: failed to abort 2008-11-24 16:18:54 [11361] [10] ERROR: AT2[4]: Initialization of device failed. 2008-11-24 16:18:54 [11361] [10] INFO: AT2[4]: Closing device 2008-11-24 16:18:54 [11361] [10] ERROR: AT2[4]: Couldn't connect (retrying in 10 seconds). 2008-11-24 18:01:40 [31111] [10] DEBUG: AT2[4]: detecting modem type 2008-11-24 18:01:40 [31111] [10] INFO: AT2[4]: opening device 2008-11-24 18:01:40 [31111] [10] DEBUG: AT2[4]: device opened. Telnet mode = 0 2008-11-24 18:01:40 [31111] [10] DEBUG: AT2[4]: --> ^M 2008-11-24 18:01:40 [31111] [10] DEBUG: AT2[4]: <-- +CMS ERROR: failed to abort 2008-11-24 18:01:40 [31111] [10] ERROR: AT2[4]: CMS ERROR: +CMS ERROR: failed to abort 2008-11-24 18:01:40 [31111] [10] DEBUG: AT2[4]: --> AT^M 2008-11-24 18:01:40 [31111] [10] DEBUG: AT2[4]: <-- +CMS ERROR: failed to abort 2008-11-24 18:01:40 [31111] [10] ERROR: AT2[4]: CMS ERROR: +CMS ERROR: failed to abort 2008-11-24 18:01:40 [31111] [10] DEBUG: AT2[4]: --> AT&F^M 2008-11-24 18:01:40 [31111] [10] DEBUG: AT2[4]: <-- +CMS ERROR: failed to abort 2008-11-24 18:01:40 [31111] [10] ERROR: AT2[4]: CMS ERROR: +CMS ERROR: failed to abort 2008-11-24 18:01:40 [31111] [10] DEBUG: AT2[4]: --> ATE0^M 2008-11-24 18:01:41 [31111] [10] DEBUG: AT2[4]: <-- +CMS ERROR: failed to abort 2008-11-24 18:01:41 [31111] [10] ERROR: AT2[4]: CMS ERROR: +CMS ERROR: failed to abort 2008-11-24 18:01:41 [31111] [10] DEBUG: AT2[4]: --> ATI^M 2008-11-24 18:01:41 [31111] [10] DEBUG: AT2[4]: <-- +CMS ERROR: failed to abort 2008-11-24 18:01:41 [31111] [10] ERROR: AT2[4]: CMS ERROR: +CMS ERROR: failed to abort 2008-11-24 18:01:41 [31111] [10] DEBUG: AT2[4]: Cannot detect modem, using generic 2008-11-24 18:01:41 [31111] [10] DEBUG: AT2[4]: Reading modem definitions from </etc/kannel/kannel.conf> 2008-11-24 18:01:41 [31111] [10] DEBUG: AT2[4]: Found <5> modems in config 2008-11-24 18:04:38 [31252] [10] DEBUG: AT2[4]: detecting modem type 2008-11-24 18:04:38 [31252] [10] INFO: AT2[4]: opening device 2008-11-24 18:04:38 [31252] [10] DEBUG: AT2[4]: device opened. Telnet mode = 0
