smsd resends queued messages after crash

[Thomas Adamcik]

Reported by Vidar Stokkenes on the nav-users mailing-list:

I hope the developers can add some kind of logics to supress queued SMS messages in the alert queue after restarting smsd after a crash. We've had situations where smsd has pushed out 100-200 SMS messages after a restart, often more than 20 messages to one mobile phone.

Are there any modifications planned to maybe supress queued up SMS messages after a crash?

[Thomas Adamcik (adamcik)]

Based on the information provided it is not clear if this is an alertengine or smsd issue, could you please clearify which of them crashed or if it was a general system crash.

[Vidar Stokkenes (vidarst)]

Its been a while since the last time this happened, but I can submit a log dump the next time it happens. But generally I wanted to address the "spam" issue as alertengine probably still queue messages to the smsd sendqueue database table although smsd is not running.

[Thomas Adamcik (adamcik)]

LP#258327 has been fixed for 3.6 allowing users to tell alertengine to ignore alerts that are closed when they normaly would have been dispatched. This might allow users to avoid the problem you are describing. However once they are handed over to smsd it is to late for such measures to be enforced.

[Morten Brekkevold (mbrekkevold)]

First off, I would really like to see the smsd log from such an episode - when smsd checks the sms queue and finds 20 messages to the same phone number at the same time, it will normally put as many of these as it can into one 160 character message and ignore the rest (adding a note to the SMS that the rest can be seen in the web interface).

Secondly, smsd will ignore messages that were posted to the queue more than 24 hours ago (this is a configurable option, IIRC).

Thirdly, you can manually ignore all queued SMS messages before restarting smsd. See "smsd.py -h" for help on its command line options.

[Morten Brekkevold (mbrekkevold)]

There's been no feedback for almost two years on this, closing it as invalid.