Self rebooting

Self rebooting SearchSearch
Author Message
Alexandre
Frequent Contributor
Username: Alexd

Post Number: 145
Registered: 01-2008
Posted on Saturday, December 11, 2010 - 11:28 am:   

Hi!

NowSMS have any mechanism for self restarting ?Sometimes I see, NowSMS self restarts service. Because of what this might be?
ashot shahbazian
Frequent Contributor
Username: Animatele

Post Number: 93
Registered: 06-2004
Posted on Wednesday, December 15, 2010 - 02:22 am:   

Hi Alex,

This may happen if a corrupt message (could be a DLR I think too) hit NowSMS. For example, if there is a mismatch between the message size in the message header and the actual number of bytes. To trace it, you first check the NowSMS event log for the timestamp of "NowSMS started" and then check the logs for messages/DLR just preceding the crash for anything unusual.

If the pattern is NowSMS stopping-starting at near equal/interleaving intervals, then it is most definitely a crooked message/messages timing out and resubmitting - it'd be easy to identify by B-numbers in SMPPDEBUG log (I don't recommend enabling debugging for extended time as it may cause other problems.)

If you look in the except.log in your NowSMS folder (it records regardless if the debugging is on or not) you'd notice "Exception in Thread xxx ...." messages their timestamps (the actual times of the events) almost equal to those of the crashes. Also, the thread # in except.log corresponds to that in SMSdebug.log, if debugging is on - so if the trouble is related to a specific message you'll have a chance of finding it. Note though the thread numbers are rotating, so when searching in SMSDEBUG log make sure you look for entries around the time of those in Except.log.

You may also have this problem if you have too many files in your filsystem, such as unsubmitted messages or DLR in the queues. When this happens, the times of servuce start/stop are pretty much random. We've had one such case recently and also noticed NowSMS leaking memory. Deleting unneded files and rebooting the server fixed both service restarts and the leak.


Kind regards,
Ashot