Operating system name and version: OperatLinux OpenWrt 2.6.25.17 #16 Sun Feb 15 00:19:46 CET 2009 mips unknown - ASUS WL-500G Premium - Kamikaze 8.09, r14511
Version of smsd: 3.1.5
Smsd installed from: sources
Name and model of a modem / phone: Nokia 6210
Interface: serial


What are the typical causes for Modem handler to terminate abnormally? Below a log for a case where such a thing happened [last line in log]

How does people here recover from this i.e. any comments on how to detect abnormal termination and restart smsd?

2009-10-02 15:30:50,2, smsd: Smsd v3.1.5 started. 2009-10-02 15:30:50,2, smsd: Running as root:root. 2009-10-02 15:30:50,4, smsd: File mode creation mask: 022 (0644, rw-r--r--). 2009-10-02 15:30:50,5, paarsim: Modem handler 0 has started. PID: 1222. 2009-10-02 15:30:50,5, paarsim: Using check_memory_method 1: CPMS is used. 2009-10-02 15:30:50,5, smsd: Outgoing file checker has started. PID: 1221. 2009-10-02 15:31:05,5, paarsim: IMSI: 350xxxxxxxxxx 2009-10-03 10:39:22,5, paarsim: SMS received, From: 358xxxxxxxxx 2009-10-03 10:40:25,5, smsd: Moved file /mnt/usbdrive/sms/spool/outgoing/sms.park to /mnt/usbdrive/sms/spool/checked 2009-10-03 10:40:26,5, smsd: Moved file /mnt/usbdrive/sms/spool/outgoing/sms.park.NOTIFY to /mnt/usbdrive/sms/spool/checked 2009-10-03 10:40:31,5, paarsim: SMS sent, Message_id: 79, To: 358xxxxxxxxx, sending time 5 sec. 2009-10-03 10:40:37,5, paarsim: SMS sent, Message_id: 80, To: 358xxxxxxxxx, sending time 5 sec. 2009-10-03 15:00:07,5, smsd: Moved file /mnt/usbdrive/sms/spool/outgoing/SMS.temperature to /mnt/usbdrive/sms/spool/checked 2009-10-03 15:00:15,5, paarsim: SMS sent, Message_id: 81, To: 358xxxxxxxxx, sending time 7 sec. 2009-10-03 20:05:17,3, paarsim: Modem did not accept the pre-init string 2009-10-03 21:40:17,3, paarsim: Modem did not accept the pre-init string 2009-10-04 08:10:17,3, paarsim: Modem did not accept the pre-init string 2009-10-04 12:55:17,3, paarsim: Modem did not accept the pre-init string 2009-10-04 15:00:11,5, smsd: Moved file /mnt/usbdrive/sms/spool/outgoing/SMS.temperature to /mnt/usbdrive/sms/spool/checked 2009-10-04 15:11:06,3, paarsim: The modem did not answer (expected OK). 2009-10-04 15:11:06,5, paarsim: Waiting 10 sec. before retrying 2009-10-04 15:15:10,5, paarsim: SMS sent, Message_id: 83, To: 358xxxxxxxxx, sending time 603 sec. 2009-10-04 16:35:16,3, paarsim: Modem did not accept the pre-init string 2009-10-04 18:05:17,2, paarsim: PIN handling: expected READY, modem answered 2009-10-04 18:05:18,2, paarsim: Modem handler 0 terminated abnormally. PID: 1222.

smsd.conf

I think that there are no "typical" causes for termination.

In production systems the PIN could be disabled. It does not offer any additional security, and is just a thing which can go wrong.

Alarmhandler can be used to track problems with a modem. For example if there are "The modem did not answer" errors too many times, that script can create an alarm using some another system. It can also create a flag-file which can be detected by the script running by cron. That script can restart the daemon, if necessary.

I do not have any samples for alarmhandler, but the following script can detect if a daemon is not running:



However, that kind of script has been running on production almost two years continuously, and has never detected a missing daemon...

You have an interesting environment. Did you have to modify the sources to get smsd compiled?

ok. thanks for script, pointing to look for alarmhandler and ideas around it.

Didn't need to change the code at all - so big thanks for easy "portability".