SMS Server Tools 3
This site is hosted by
Basic information:
Additional information:
Get SMS Server Tools 3:
Additional Options

 Sponsored links

Custom Search

 Visitor locations
 SMS Server Tools 3 Community
Welcome, Guest. Please login or register. Mon Jun 24, 2024 13:58
SMSTools3 Community » Help and support Bottom

[solved] Strange behaviour with incoming messages

Login and Post Reply

Page:  1

Author Post
Feb 2016
Location: Teramo, Italy
Operating system name and version: RHEL 6.8
Version of smsd: 3.1.16
Smsd installed from: sources
Name and model of a modem / phone: Telit GT863-PY GSM Modem
Interface: Digi Portserver II TCP to Serial

This happend quite frequently with incoming messages. It happend now with the current version as well as with previous ones (at least with 3.1.15).

Here it is the line logged by the deamon. The message file contains chunks from a couple of incoming messages, so it seems that the same file was overwritten by the newer incoming messages. However, looking at the entire log, i cannot find any other occurrence with the same file name.

GSM7.bQGNwd incoming SMS from + file /data/sms/var/spool/incoming/GSM7.bQGNwd matches on Thu Feb 16 07:38:34 CET 2017

That "matches" is the point.

Furthermore, you maybe had noticed that the phone number wasn't correctly logged, while inside the file i can regulary find it.

Any help is appreciated.


May 2009
Location: Jyväskylä, Finland
Sorry to say, but I do not understand what is going on now. :shock:

What is the daemon which logs that kind of a line?

At the moment, the only thing I can imagine is that the file system is badly broken. But there likely is something else strange.

Feb 2016
Location: Teramo, Italy
Topic owner
Nevermind, just a problem with a bash script handling incoming SMS, when they were written in binary.



Login and Post Reply

Page:  1

SMSTools3 Community » Help and support Top

Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.