Hi - is anyone else using this GPS modem - recommended by Netways! - for notifying Icinga2 users by phone for serious CRITICAL etc. situations?
Since the beginning of our using it several years ago, we have occasionally had “CMS error 111” cases noted in the log of the SMS (Linux) service - /var/log/smsd/smsd.log - but only recently realised that SMSs that are involved are then deleted, i.e. they never get sent.
Unfortunately the list of possible CMS errors for GPS modems says this error 111 is an “unspecified protocol” error… Not much useful info there!
So we discovered that the problem can be solved, we assumed, if the modem is reset, and then the smsd restarted. We even found a way to automate this into an event-handler called by Icinga2 when a “logfiles” check notices appearance of the above-mentioned error.
Usually this reset+restart works, but currently we have the problem that it no longer has an effect!! Any SMS sent now experiences this error, and is then deleted by the smsd without having been sent.
Any ideas? Could it be the 3-year-old modem is “kaputt” and needs to be replaced? If so, how does one diagnose the modem?
P.S.: Here the details of the Icinga2 system involved (incomplete in terms of config. etc. since this is an error that does not really have to do with Icinga, I feel)…
on CentOS 7.5.1804;
Output of smsd -V is…
Version 3.1.15, Copyright (c) Keijo Kasvi, firstname.lastname@example.org, http://smstools3.kekekasvi.com Support: http://smstools3.kekekasvi.com/index.php?p=support Based on SMS Server Tools 2 from Stefan Frings, email@example.com, http://www.meinemullemaus.de SMS Server Tools version 2 and below are Copyright (C) Stefan Frings.