Unexplained queuing of messages
I have had Kannel running for a couple of months without a hitch. For no apparent reason, a couple of weeks ago it suddenly quit sending messages but started queuing them. I am using a Multitech modem. When I looked at Kannel's status page it showed my SMSC connection name in red and the SMS: sent (in the middle of the status page) said (98 queued). I tried to to restart Kannel and bearer box would not shut down. I assume it was waiting to process the queued messages. I finally kill -9'd it and restarted Kannel. It would not connect to my modem. So I shut Kannel back down. I left it down for a couple of days until I had some time to look at it. When I started kannel up again, everything was working fine. I never like problems that fix themselves because I know they will be back. Two days ago it stopped sending messages again, after only 3 days of functioning. This time the SMS connection does not show in red but, everything is being queued. I have tried to shutdown just the SMSC connection to my modem. The response I get is Denied. Can this only be done if I have included a password in the smsc group in the config file? I also tried to place kannel in the suspend mode using the status password but also received the Denied response. Below I have included the current response page. Can anyone tell me why Kannel would simply start queuing instead of sending messages? Could this be a full memory problem in my modem? If it could, what are the best settings for equipment/memory/SIM usage using a GSM modem to manage the memories of this equipment? I asked this question earlier without any response here: http://www.kannel.org/pipermail/users/2008-September/005616.html Thanks for any help you can give. I really appreciate it. -Tony Kannel bearerbox version `cvs-20080613'. Build `Jun 24 2008 23:13:52', compiler `4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)'. System Linux, release 2.6.22-14-generic, version #1 SMP Tue Feb 12 02:46:46 UTC 2008, machine x86_64. Hostname message1, IP 127.0.1.1. Libxml version 2.6.30. Using native malloc. Status: running, uptime 5d 0h 32m 37s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 0 (0 queued), sent 22 (0 queued), store size -1 SMS: inbound 0.00 msg/sec, outbound 0.00 msg/sec DLR: 0 queued, using internal storage Box connections: smsbox:(none), IP 127.0.0.1 (0 queued), (on-line 5d 0h 32m 36s) SMSC connections: *vzn00*AT2[vzn00] (online 433944s, rcvd 0, sent 22, failed 0, queued 1522 msgs)
Re: Unexplained queuing of messages
Hmm, the store size -1 looks pretty suspicious for me. Try setting log-level to 0, restart kannel and see if you find something of interest on kannel.log. Regards, Alejandro On Mon, Oct 6, 2008 at 1:45 PM, Tony Kirkham [EMAIL PROTECTED] wrote: I have had Kannel running for a couple of months without a hitch. For no apparent reason, a couple of weeks ago it suddenly quit sending messages but started queuing them. I am using a Multitech modem. When I looked at Kannel's status page it showed my SMSC connection name in red and the SMS: sent (in the middle of the status page) said (98 queued). I tried to to restart Kannel and bearer box would not shut down. I assume it was waiting to process the queued messages. I finally kill -9'd it and restarted Kannel. It would not connect to my modem. So I shut Kannel back down. I left it down for a couple of days until I had some time to look at it. When I started kannel up again, everything was working fine. I never like problems that fix themselves because I know they will be back. Two days ago it stopped sending messages again, after only 3 days of functioning. This time the SMS connection does not show in red but, everything is being queued. I have tried to shutdown just the SMSC connection to my modem. The response I get is Denied. Can this only be done if I have included a password in the smsc group in the config file? I also tried to place kannel in the suspend mode using the status password but also received the Denied response. Below I have included the current response page. Can anyone tell me why Kannel would simply start queuing instead of sending messages? Could this be a full memory problem in my modem? If it could, what are the best settings for equipment/memory/SIM usage using a GSM modem to manage the memories of this equipment? I asked this question earlier without any response here: http://www.kannel.org/pipermail/users/2008-September/005616.html Thanks for any help you can give. I really appreciate it. -Tony Kannel bearerbox version `cvs-20080613'. Build `Jun 24 2008 23:13:52', compiler `4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)'. System Linux, release 2.6.22-14-generic, version #1 SMP Tue Feb 12 02:46:46 UTC 2008, machine x86_64. Hostname message1, IP 127.0.1.1. Libxml version 2.6.30. Using native malloc. Status: running, uptime 5d 0h 32m 37s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 0 (0 queued), sent 22 (0 queued), store size -1 SMS: inbound 0.00 msg/sec, outbound 0.00 msg/sec DLR: 0 queued, using internal storage Box connections: smsbox:(none), IP 127.0.0.1 (0 queued), (on-line 5d 0h 32m 36s) SMSC connections: *vzn00*AT2[vzn00] (online 433944s, rcvd 0, sent 22, failed 0, queued 1522 msgs)
Re: Unexplained queuing of messages
Store Size reflects the number of messages on the filesystem store. A value of 0 is expected if no messages are currently on the store. -1 suggests me that something's probably wrong somewhere, because it means that the Dict (if store is file) or Counter (if it's spool) variable that holds the messages (or the number of) is not defined. This is definitely not normal, should be = 0. Your log file may be showing something for what matters. Try enqueueing a new message and see what shows in there. Regarding memory problems, try emptying the sim messages and see if that solves the problem, maybe you're not deleting the messages from the SIM after sending? You can shutdown kannel fromt the web interface with the shutdown command. Look for the details on the userguide. Regards, Alejandro Guerrieri On Mon, Oct 6, 2008 at 6:10 PM, Tony Kirkham [EMAIL PROTECTED] wrote: I have been running with log-level 0 and I haven't noticed anything, although I do not know what to expect. What should I be looking for? I believe I have always seen a store size -1 even when things were working. What does this mean? If messages are queued but not being processed, is there a way to shut Kannel down other than kill -9? I would like to do this so I can restart Kannel and watch the log on start up as you have suggested. Thanks, -Tony On Mon, Oct 6, 2008 at 11:57 AM, Alejandro Guerrieri [EMAIL PROTECTED] wrote: Hmm, the store size -1 looks pretty suspicious for me. Try setting log-level to 0, restart kannel and see if you find something of interest on kannel.log. Regards, Alejandro On Mon, Oct 6, 2008 at 1:45 PM, Tony Kirkham [EMAIL PROTECTED]wrote: I have had Kannel running for a couple of months without a hitch. For no apparent reason, a couple of weeks ago it suddenly quit sending messages but started queuing them. I am using a Multitech modem. When I looked at Kannel's status page it showed my SMSC connection name in red and the SMS: sent (in the middle of the status page) said (98 queued). I tried to to restart Kannel and bearer box would not shut down. I assume it was waiting to process the queued messages. I finally kill -9'd it and restarted Kannel. It would not connect to my modem. So I shut Kannel back down. I left it down for a couple of days until I had some time to look at it. When I started kannel up again, everything was working fine. I never like problems that fix themselves because I know they will be back. Two days ago it stopped sending messages again, after only 3 days of functioning. This time the SMS connection does not show in red but, everything is being queued. I have tried to shutdown just the SMSC connection to my modem. The response I get is Denied. Can this only be done if I have included a password in the smsc group in the config file? I also tried to place kannel in the suspend mode using the status password but also received the Denied response. Below I have included the current response page. Can anyone tell me why Kannel would simply start queuing instead of sending messages? Could this be a full memory problem in my modem? If it could, what are the best settings for equipment/memory/SIM usage using a GSM modem to manage the memories of this equipment? I asked this question earlier without any response here: http://www.kannel.org/pipermail/users/2008-September/005616.html Thanks for any help you can give. I really appreciate it. -Tony Kannel bearerbox version `cvs-20080613'. Build `Jun 24 2008 23:13:52', compiler `4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)'. System Linux, release 2.6.22-14-generic, version #1 SMP Tue Feb 12 02:46:46 UTC 2008, machine x86_64. Hostname message1, IP 127.0.1.1. Libxml version 2.6.30. Using native malloc. Status: running, uptime 5d 0h 32m 37s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 0 (0 queued), sent 22 (0 queued), store size -1 SMS: inbound 0.00 msg/sec, outbound 0.00 msg/sec DLR: 0 queued, using internal storage Box connections: smsbox:(none), IP 127.0.0.1 (0 queued), (on-line 5d 0h 32m 36s) SMSC connections: *vzn00*AT2[vzn00] (online 433944s, rcvd 0, sent 22, failed 0, queued 1522 msgs)
Re: Unexplained queuing of messages
Alejandro Guerrieri schrieb: Store Size reflects the number of messages on the filesystem store. A value of 0 is expected if no messages are currently on the store. -1 suggests me that something's probably wrong somewhere, because it means that the Dict (if store is file) or Counter (if it's spool) variable that holds the messages (or the number of) is not defined. This is definitely not normal, should be = 0. [...] Look for the details on the userguide. Looking at the userguide is always a good idea. Under core-configuration you find that for example: Set maximum size of incoming message queue. After number of messages has hit this value, Kannel began to discard them. Value 0 means giving strict priority to outgoing messages. -1, default, means that the queue of infinite length is accepted. (This works with any normal input, use this variable only when Kannel message queues grow very long). So -1 is not only normal but even default. Sorry that I can't state anything productive to the problem, but this is it surely not.
Re: Unexplained queuing of messages
Falko, You're getting confused with the queue-limit setting. Store Size displays the number of messages currently on the store, and that should be 0 or greater. Regards, Alejandro Guerrieri No, that's not the meaning of the Store Size indicator on the status page. On Mon, Oct 6, 2008 at 7:42 PM, Falko Ziemann [EMAIL PROTECTED] wrote: Alejandro Guerrieri schrieb: Store Size reflects the number of messages on the filesystem store. A value of 0 is expected if no messages are currently on the store. -1 suggests me that something's probably wrong somewhere, because it means that the Dict (if store is file) or Counter (if it's spool) variable that holds the messages (or the number of) is not defined. This is definitely not normal, should be = 0. [...] Look for the details on the userguide. Looking at the userguide is always a good idea. Under core-configuration you find that for example: Set maximum size of incoming message queue. After number of messages has hit this value, Kannel began to discard them. Value 0 means giving strict priority to outgoing messages. -1, default, means that the queue of infinite length is accepted. (This works with any normal input, use this variable only when Kannel message queues grow very long). So -1 is not only normal but even default. Sorry that I can't state anything productive to the problem, but this is it surely not.
