Gammu 1.37.4 / smsd hangs on CentOS 7?

[Karl Pielorz]

Hi,

We've been running Gammu under CentOS 7 recently - but the sms daemon keeps
'hanging'.

Symptoms are - it'll start, in the logs you can 'see' it chatting to our
Huawei USB modem, and running 'gammu-smsd-inject' can be used to send
messages.

After a 'random' amount of time (20 minutes? - maybe an hour or few) - the
daemon stops 'noticing' there are SMS's to be sent.

In the logs - we can still see it conversing with the modem (getting signal
strength info, network info etc.) 'dmesg' etc. confirm the modem isn't
hanging, or disappearing (i.e. off the USB bus).

At this point 'kill' won't kill the daemon - you can 'kill -9' it - if you
restart it, it fires up - chats to the modem, see's there's a message to
send - and sends it. But then randomly 'hangs' again later.

We're running 'CentOS Linux release 7.2.1511' - and I compiled Gammu 1.37.4
from source.

We're using a very simple conifg - with 'files' queues for in/out SMS'd etc
(config is below).

Any suggestions? - It doesn't seem to 'crash' - it just stops noticing
there's stuff to send (and at that point a regular SIGTERM won't quit it -
only a SIGKILL.

I've found a few posts / articles about this - but nothing with any
concrete fixes / relevant to the versions I'm running.

Thanks,

-Karl


gammu.cfg:

[gammu]
port = /dev/ttyUSB2
connection = at115200
synchronizetime = yes
logfile = /var/log/gammu-three.log
logformat = textall
debuglevel = 255

StatusFrequency = 0

[smsd]
Service = files
logfile = /var/log/gammu-three.log
debuglevel = 255
InboxPath = /var/spool/sms/inbox-three/
OutboxPath = /var/spool/sms/outbox-three/
SentSMSPath = /var/spool/sms/sent-three/
ErrorSMSPath = /var/spool/sms/error-three/
PhoneID = three
ReceiveFrequency = 15
Receive = true

[Emiliano Vazquez]

Hi, i have some modems with a crazy leak and change ramdon from one port to
another without any notice in dmesg or some place.

The modem works using /dev/ttyUSB0 and when it gets working for a while
then change to the other port /dev/ttyUSB1.

/dev/ttyUSB0 works with a AT comand and you can get signal and other checks
commands but at+cusd= not work anymore.

Maybe you are in another workarround. If i kill and start again this still
persist.

Post your logs and maybe we can help you!

Best regards.

Emiliano.

Post by Karl Pielorz
Hi,
We've been running Gammu under CentOS 7 recently - but the sms daemon keeps
'hanging'.
Symptoms are - it'll start, in the logs you can 'see' it chatting to our
Huawei USB modem, and running 'gammu-smsd-inject' can be used to send
messages.
After a 'random' amount of time (20 minutes? - maybe an hour or few) - the
daemon stops 'noticing' there are SMS's to be sent.
In the logs - we can still see it conversing with the modem (getting signal
strength info, network info etc.) 'dmesg' etc. confirm the modem isn't
hanging, or disappearing (i.e. off the USB bus).
At this point 'kill' won't kill the daemon - you can 'kill -9' it - if you
restart it, it fires up - chats to the modem, see's there's a message to
send - and sends it. But then randomly 'hangs' again later.
We're running 'CentOS Linux release 7.2.1511' - and I compiled Gammu 1.37.4
from source.
We're using a very simple conifg - with 'files' queues for in/out SMS'd etc
(config is below).
Any suggestions? - It doesn't seem to 'crash' - it just stops noticing
there's stuff to send (and at that point a regular SIGTERM won't quit it -
only a SIGKILL.
I've found a few posts / articles about this - but nothing with any
concrete fixes / relevant to the versions I'm running.
Thanks,
-Karl
[gammu]
port = /dev/ttyUSB2
connection = at115200
synchronizetime = yes
logfile = /var/log/gammu-three.log
logformat = textall
debuglevel = 255
StatusFrequency = 0
[smsd]
Service = files
logfile = /var/log/gammu-three.log
debuglevel = 255
InboxPath = /var/spool/sms/inbox-three/
OutboxPath = /var/spool/sms/outbox-three/
SentSMSPath = /var/spool/sms/sent-three/
ErrorSMSPath = /var/spool/sms/error-three/
PhoneID = three
ReceiveFrequency = 15
Receive = true
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Gammu-users mailing list - https://lists.sourceforge.net/
lists/listinfo/gammu-users

[Karl Pielorz]

--On 24 October 2016 at 11:39:54 -0300 Emiliano Vazquez

Post by Emiliano Vazquez
Hi, i have some modems with a crazy leak and change ramdon from one port
to another without any notice in dmesg or some place.
The modem works using /dev/ttyUSB0 and when it gets working for a while
then change to the other port /dev/ttyUSB1.
/dev/ttyUSB0 works with a AT comand and you can get signal and other
checks commands but at+cusd= not work anymore.

The software isn't even attempting to send the message - it's like the part
that scans the outbox directories has hung.

When I 'inject' an SMS the first time - I can see the daemon pick it up -
and start sending commands to the modem.

Once it's in the 'hung' state - I can't see any evidence that the SMS
daemon picks up the message, or even attempts to send it :(

Post by Emiliano Vazquez
Maybe you are in another workarround. If i kill and start again this still
persist.
Post your logs and maybe we can help you!

I'd gladly post some logs - which ones do you want? - I can't see any
errors logged in any of the log files - everything is just "fine" - except
the daemon doesn't notice new files in the outbox directory (and so makes
no attempt to send them).

I've just seen 1.37.91 is now - I'll update to that and see if it makes any
difference...

-Karl

[gilberto dos santos alves]

[1] https://wammu.eu/docs/manual/smsd/config.html#message-filtering
[2]
https://en.wikipedia.org/wiki/Short_Message_Service_technical_realisation_(GSM)
Hi. Please look at your smsc number points. see [1] and find smsc number.
Many telecom operators have special handles for some receiving or sending
controls (like areas, other carriers, etc) be sure that is handling or left
over. if necessary use set smsc number for what you want. see [2].

--
gilberto dos santos alves
[phone]
sao paulo - sp - brasil

Post by Karl Pielorz
Hi,
We've been running Gammu under CentOS 7 recently - but the sms daemon keeps
'hanging'.
Symptoms are - it'll start, in the logs you can 'see' it chatting to our
Huawei USB modem, and running 'gammu-smsd-inject' can be used to send
messages.
After a 'random' amount of time (20 minutes? - maybe an hour or few) - the
daemon stops 'noticing' there are SMS's to be sent.
In the logs - we can still see it conversing with the modem (getting signal
strength info, network info etc.) 'dmesg' etc. confirm the modem isn't
hanging, or disappearing (i.e. off the USB bus).
At this point 'kill' won't kill the daemon - you can 'kill -9' it - if you
restart it, it fires up - chats to the modem, see's there's a message to
send - and sends it. But then randomly 'hangs' again later.
We're running 'CentOS Linux release 7.2.1511' - and I compiled Gammu 1.37.4
from source.
We're using a very simple conifg - with 'files' queues for in/out SMS'd etc
(config is below).
Any suggestions? - It doesn't seem to 'crash' - it just stops noticing
there's stuff to send (and at that point a regular SIGTERM won't quit it -
only a SIGKILL.
I've found a few posts / articles about this - but nothing with any
concrete fixes / relevant to the versions I'm running.
Thanks,
-Karl
[gammu]
port = /dev/ttyUSB2
connection = at115200
synchronizetime = yes
logfile = /var/log/gammu-three.log
logformat = textall
debuglevel = 255
StatusFrequency = 0
[smsd]
Service = files
logfile = /var/log/gammu-three.log
debuglevel = 255
InboxPath = /var/spool/sms/inbox-three/
OutboxPath = /var/spool/sms/outbox-three/
SentSMSPath = /var/spool/sms/sent-three/
ErrorSMSPath = /var/spool/sms/error-three/
PhoneID = three
ReceiveFrequency = 15
Receive = true
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Gammu-users mailing list - https://lists.sourceforge.net/
lists/listinfo/gammu-users