Operating system name and version: Oracle Linux 6.2
Version of smsd: 3.1.15
Smsd installed from: package repository
Name and model of a modem / phone: 2 x MCTBA-G2-EN2-ED-EN
Interface: socket/Ethernet

Hi.

I was wondering if there is a possibility to monitor/react on socket timeouts like
2012-11-22 11:19:34,7, GSM_Net1: put_command expected (OK)|(ERROR), timeout occurred. 1.

or
2012-11-22 11:22:09,3, GSM_Net1: Couldn't connect socket @10.74.3.10:5000, error: Connection timed out, waiting 5 sec.

?

I guess alarmhandler won't do the job right?

Thanks

I'm still stuck on this one. Any ideas anyone?

Regards,
Daniel

I did not understand the problem, sorry .

When you get those messages, alarmhandler is also called if it's defined in the smsd.conf.

What alarmhandler does, depends on the handler itself. Smstools just calls it, and does nothing more.

I don't see that alarmhandler is called at all though it is defined in smsd.conf...

Here is my smsd.conf:


Let's say the modems become unresponsive and regular run cmd produce this output:
2013-02-19 13:03:47,7, GSM_Net2: -> AT+CSQ 2013-02-19 13:03:47,7, GSM_Net2: Command is sent, waiting for the answer 2013-02-19 13:03:48,7, GSM_Net1: -> AT+CSQ 2013-02-19 13:03:48,7, GSM_Net1: Command is sent, waiting for the answer 2013-02-19 13:03:52,7, GSM_Net2: put_command expected (OK)|(ERROR), timeout occurred. 1. 2013-02-19 13:03:52,7, GSM_Net2: <- 2013-02-19 13:03:52,7, GSM_Net2: -> AT+CREG? 2013-02-19 13:03:53,7, GSM_Net1: put_command expected (OK)|(ERROR), timeout occurred. 1. 2013-02-19 13:03:53,7, GSM_Net1: <- 2013-02-19 13:03:53,7, GSM_Net1: -> AT+CREG? 2013-02-19 13:04:01,5, smsd: Moved file /smspool/smsd/sms/outgoing/send_jyCfK7 to /smspool/smsd/sms/checked

I don't see that alarmhandler is called. SMS are checked but nothing else happens. Is there any misconfiguration in my config file?

The alrmhandler script is world-executable and based on your example alarmhandler script, simply pasting the output to a log file which is world-writeable.

Hi Keke,

Have you found the time to have a closer look at the config?
I can't get alarmhandler to work with my configuration.

Kind regards,
Daniel

Sorry for the delay.

You are right, "put_command expected" messages are not given to alarmhandler. This is because those errors are not usually permanent and therefore fatal. If the modem gets broken, or needs hardware reset or anything, you could track the message "Modem is not ready to answer commands" and do something when it exists.

For example, in some system I run this kind of alarmhandler:



When any modem stops answering, power-off is needed. Smstools itself does not do that. An external watchdog process monitors if that CONTROLFILE exists, and when it exists with correct content, smsd is stopped by the watchdog. After stopping, USB I/O is used to remove the mains from the modems. After couple of seconds mains is switched back, and smsd is restarted. Notification SMS is created, and administrator will receive it.

Perhaps in your case something like this can do the job.

About the socket error, it is called once, but not all errors are given to the alarmhandler. This is because there was no need to repeat those calls. When the socket is permanently unavailable, modem process should stop after trying for some time. External watchdog or Nagios can be used to monitor the process list, and do the actions which are necessary when one or more modem processes are not running. I have some code for the monitoring, please let me know if samples are required.

Hi Keke,

can we have a sample script watcgdog which will reset the modem or do USB i/o to recycle the mains.

Thanks