SMSTools3 Help and support

#1 Tue Jul 12, 2016 00:40, 105 months ago.

Member

Registered:
Oct 2010

Location: New Caledonia

Operating system name and version: Ubuntu 12.04.5 x64 3.2.0-105-generic
Version of smsd: Smsd v3.1.14
Smsd installed from: sources
Name and model of a modem / phone: FALCOM TANGO 55
Interface: serial to USB

Well, after nearly 8 years of good services, sms3 has failed once today.
Despite to have setup a lot of automatic failure detection that restarts sms3 when needed, it wasn't enough today.
Here is the log when sms3 wasn't running correctly (better tell the modem wasn't answreing correctly):

2016-07-12 09:43:06,7, GSM1: -> AT
2016-07-12 09:43:06,7, GSM1: Command is sent, waiting for the answer
2016-07-12 09:43:06,7, GSM1: <- OK
2016-07-12 09:43:06,6, GSM1: Pre-initializing modem
2016-07-12 09:43:06,7, GSM1: -> ATE0+CMEE=1
2016-07-12 09:43:06,7, GSM1: Command is sent, waiting for the answer
2016-07-12 09:43:07,7, GSM1: <- OK
2016-07-12 09:43:07,6, GSM1: Checking if modem needs PIN
2016-07-12 09:43:07,7, GSM1: -> AT+CPIN?
2016-07-12 09:43:07,7, GSM1: Command is sent, waiting for the answer
2016-07-12 09:43:07,7, GSM1: <- +CPIN: READY OK
2016-07-12 09:43:07,7, GSM1: -> AT+CSQ
2016-07-12 09:43:07,7, GSM1: Command is sent, waiting for the answer
2016-07-12 09:43:17,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 1.
2016-07-12 09:43:17,7, GSM1: <-
2016-07-12 09:43:17,7, GSM1: -> AT+CSQ
2016-07-12 09:43:17,7, GSM1: Command is sent, waiting for the answer
2016-07-12 09:43:27,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 2.
2016-07-12 09:43:27,7, GSM1: <-

[ Select ]

Then after a sms3 stop and start, everything is back OK:

2016-07-12 10:03:17,5, smsd: Outgoing file checker has started. PID: 30027.
2016-07-12 10:03:17,5, smsd: Everything ok now.
2016-07-12 10:03:18,3, GSM1: Unexpected input: +CSQ: 16,99 OK +CSQ: 16,99 OK +CREG: 0,1 OK
2016-07-12 10:03:18,7, GSM1: -> AT
2016-07-12 10:03:18,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:18,7, GSM1: <- OK
2016-07-12 10:03:18,6, GSM1: Pre-initializing modem
2016-07-12 10:03:18,7, GSM1: -> ATE0+CMEE=1
2016-07-12 10:03:18,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:18,7, GSM1: <- OK
2016-07-12 10:03:18,6, GSM1: Checking if modem needs PIN
2016-07-12 10:03:19,7, GSM1: -> AT+CPIN?
2016-07-12 10:03:19,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:19,7, GSM1: <- +CPIN: READY OK
2016-07-12 10:03:19,7, GSM1: -> AT+CSQ
2016-07-12 10:03:19,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:19,7, GSM1: <- +CSQ: 16,99 OK
2016-07-12 10:03:19,6, GSM1: Signal Strength Indicator: (16,99) -81 dBm (Good)
2016-07-12 10:03:19,6, GSM1: Checking if Modem is registered to the network
2016-07-12 10:03:20,7, GSM1: -> AT+CREG?
2016-07-12 10:03:20,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:20,7, GSM1: <- +CREG: 0,1 OK
2016-07-12 10:03:20,6, GSM1: Modem is registered to the network
2016-07-12 10:03:20,6, GSM1: Selecting PDU mode
2016-07-12 10:03:20,7, GSM1: -> AT+CMGF=0
2016-07-12 10:03:20,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:20,7, GSM1: <- OK
2016-07-12 10:03:20,6, GSM1: Changing SMSC
2016-07-12 10:03:21,7, GSM1: -> AT+CSCA="+687770009"
2016-07-12 10:03:21,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:21,7, GSM1: <- OK
2016-07-12 10:03:21,7, GSM1: -> AT+CIMI
2016-07-12 10:03:21,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:21,7, GSM1: <- 546010100209020 OK
2016-07-12 10:03:22,7, GSM1: -> AT+CGSN
2016-07-12 10:03:22,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:22,7, GSM1: <- 357248015960598 OK
2016-07-12 10:03:22,5, GSM1: CGSN: 357248015960598
2016-07-12 10:03:22,5, GSM1: IMSI: 546010100209020
2016-07-12 10:03:22,6, GSM1: Checking if reading of messages is supported
2016-07-12 10:03:22,7, GSM1: -> AT+CPMS?
2016-07-12 10:03:22,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:22,7, GSM1: <- +CPMS: "MT",1,49,"MT",1,49,"MT",1,49 OK
2016-07-12 10:03:22,6, GSM1: Checking memory size
2016-07-12 10:03:23,7, GSM1: -> AT+CPMS?
2016-07-12 10:03:23,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:23,7, GSM1: <- +CPMS: "MT",1,49,"MT",1,49,"MT",1,49 OK
2016-07-12 10:03:23,6, GSM1: Used memory is 1 of 49
2016-07-12 10:03:23,6, GSM1: Trying to get stored message 1
2016-07-12 10:03:23,7, GSM1: -> AT+CMGR=1
2016-07-12 10:03:23,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:24,7, GSM1: <- +CMGR: 0,,22 069186770700F924099186772869F400006170219065904404D4F29C0E OK

[ Select ]

[ Expand ]

When modem wasn't answering to AT+CSQ , tests about sms3 state where running without problem:

/bin/ps ax | grep -v grep | grep 'smsd -n MAINPROCESS'
28447 ?        Ss     0:34 /usr/local/bin/smsd -n MAINPROCESS -p/var/run/smsd.pid -i/var/run/smsd.working -uroot -gdialout -l/var/log/smsd.log

[ Select ]

/bin/ps ax | grep -v grep | grep 'GSM1_'
28448 ?        S     65:32 /usr/local/bin/smsd -n GSM1_______ -p/var/run/smsd.pid -i/var/run/smsd.working -uroot -gdialout -l/var/log/smsd.log

[ Select ]

/bin/ps ax | grep -v grep | grep '[smsd] <defunct>'

[ Select ]

What would be an option to detect this failure ?
Thanks in advance for your time.
(I think it is a sporadic failure, but I'd like to try to fix it)

keke

Top

#3 Tue Jul 12, 2016 07:09, 105 months ago.

Administrator

Registered:
May 2009

Posts: 2070

Location: Jyväskylä, Finland

Here is an option, taken from this post.

Alarmhandler:

#!/bin/bash

LOG="/var/log/smstools/alarmhandler.log"
CONTROLFILE="/var/lib/smsd/application/control"

# $1 the keyword ALARM
# $2 a date in the format yyyy-mm-dd
# $3 a time in the format hh:mm:ss
# $4 the alarm severity (1 digit number)
# $5 the modem name or SMSD
# $6 the alarm text

echo "$2 $3,$4, $5: $6" >> $LOG

if echo -n "$6" | grep "Modem is not ready to answer commands" >/dev/null; then

  if [ ! -f $CONTROLFILE ]
  then
    DATE=`date +"%Y-%m-%d %T"`
    echo "${DATE},1, $5: Alarmhandler created request for reset." >> $LOG
    echo "APPLICATION RESET 358401111111 $5 $DATE" > $CONTROLFILE
  fi
fi

[ Select ]

'bash' Syntax Highlight powered by GeSHi

Create a cron job which regularly checks the existence of CONTROLFILE, and deletes it and restarts the smsd when required.

sms3 failure once (seems modem wasn't aswering)