Markus_: Operating system name and version: Debian 7 (wheezy)
Version of smsd: 3.1.16beta
Name and model of a modem / phone: 2N VoiceBlue Next
Interface: network
Hallo,
I have sometimes problems with freezing modems.
smsd_trouble.log:
2016-05-06 01:48:14,7, M1-GSM1: -> AT+CREG?
2016-05-06 01:48:14,7, M1-GSM1: Command is sent, waiting for the answer
2016-05-06 01:48:24,7, M1-GSM1: put_command expected (\+CREG:.*OK)|(ERROR), timeout occurred. 1.
2016-05-06 01:48:24,7, M1-GSM1: <-
2016-05-06 01:48:24,3, M1-GSM1: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying
2016-05-06 01:48:24,7, M1-GSM1: Running alarmhandler: /usr/local/bin/smsd_alarmevent.sh ALARM 2016-05-06 01:48:24 3 M1-GSM1 "Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying"
2016-05-06 01:48:24,7, M1-GSM1: Done: alarmhandler, execution time 0 sec., status: 0 (0)
2016-05-06 01:48:24,3, M1-GSM1: Exec: alarmhandler encountered errors:
2016-05-06 01:48:24,3, M1-GSM1: ! + LOG=/var/log/smsd_alarms.log
2016-05-06 01:48:24,3, M1-GSM1: ! + echo '2016-05-06 01:48:24,3, M1-GSM1: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying'
2016-05-06 01:48:24,3, M1-GSM1: ! + grep 'Modem is not ready to answer commands'
2016-05-06 01:48:24,3, M1-GSM1: ! + echo -n 'Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying'
[...]
2016-05-06 02:04:29,7, M1-GSM1: -> AT+CSQ
2016-05-06 02:04:29,7, M1-GSM1: Command is sent, waiting for the answer
2016-05-06 02:04:39,7, M1-GSM1: put_command expected (OK)|(ERROR), timeout occurred. 92.
2016-05-06 02:04:39,7, M1-GSM1: <-
2016-05-06 02:04:39,7, M1-GSM1: -> AT+CREG?
2016-05-06 02:04:39,7, M1-GSM1: Command is sent, waiting for the answer
2016-05-06 02:04:49,7, M1-GSM1: put_command expected (\+CREG:.*OK)|(ERROR), timeout occurred. 93.
2016-05-06 02:04:49,7, M1-GSM1: <-
2016-05-06 02:04:49,3, M1-GSM1: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying
2016-05-06 02:04:49,7, M1-GSM1: Running alarmhandler: /usr/local/bin/smsd_alarmevent.sh ALARM 2016-05-06 02:04:49 3 M1-GSM1 "Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying"
2016-05-06 02:04:49,7, M1-GSM1: Done: alarmhandler, execution time 0 sec., status: 0 (0)
2016-05-06 02:04:49,3, M1-GSM1: Exec: alarmhandler encountered errors:
2016-05-06 02:04:49,3, M1-GSM1: ! + LOG=/var/log/smsd_alarms.log
2016-05-06 02:04:49,3, M1-GSM1: ! + echo '2016-05-06 02:04:49,3, M1-GSM1: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying'
2016-05-06 02:04:49,3, M1-GSM1: ! + echo -n 'Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying'
2016-05-06 02:04:49,3, M1-GSM1: ! + grep 'Modem is not ready to answer commands'
smsd.log
2016-05-06 02:04:49,3, M1-GSM1: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying
2016-05-06 02:04:49,3, M1-GSM1: Exec: alarmhandler encountered errors:
2016-05-06 02:04:49,3, M1-GSM1: ! + LOG=/var/log/smsd_alarms.log
2016-05-06 02:04:49,3, M1-GSM1: ! + echo '2016-05-06 02:04:49,3, M1-GSM1: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying'
2016-05-06 02:04:49,3, M1-GSM1: ! + echo -n 'Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying'
2016-05-06 02:04:49,3, M1-GSM1: ! + grep 'Modem is not ready to answer commands'
2016-05-06 02:04:50,3, M1-GSM1: write_to_modem: error 110: Connection timed out
2016-05-06 02:04:50,3, M1-GSM1: Exec: alarmhandler encountered errors:
2016-05-06 02:04:50,3, M1-GSM1: ! + LOG=/var/log/smsd_alarms.log
2016-05-06 02:04:50,3, M1-GSM1: ! + echo '2016-05-06 02:04:50,3, M1-GSM1: write_to_modem: error 110: Connection timed out'
2016-05-06 02:04:50,3, M1-GSM1: ! + echo -n 'write_to_modem: error 110: Connection timed out'
2016-05-06 02:04:50,3, M1-GSM1: ! + grep 'Modem is not ready to answer commands'
After restarting smsd it works fine again. Somebody know what the problem is?
It would be nice to find a solution without manually smsd restart.
|
