Re: sqlbox MySQL error
it is kannel 1.5.0, not from the trunk but the tar.gz file available on site and yes sqlbox is from the same kannel source code from addons folder On Thu, Dec 6, 2012 at 1:05 AM, spameden spame...@gmail.com wrote: SQLBox as well from there. 2012/12/6 spameden spame...@gmail.com Did you install kannel from the latest SVN trunk? 2012/12/5 moz...@gmail.com I have installed kannel 1.5.0 with sqlbox. It works fine but sometime I see following error in the sqlbox log 2012-12-05 15:33:16 [25488] [4] ERROR: MYSQL: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''' at line 1 2012-12-05 16:33:16 [25488] [4] ERROR: MYSQL: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''' at line 1 2012-12-05 20:33:16 [25488] [4] ERROR: MYSQL: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''' at line 1 2012-12-05 20:33:16 [25488] [4] ERROR: MYSQL: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''' at line 1 Most of my messages contains Latin or Arabic characters like 5 15:33:16 [25497] [4] INFO: Starting to service أنا علي سالم الحداد من الابيار ليبيا ابعث سلامي لجدي عقوب البرعصي و from x to 55051 Its happening randomly not with every message. Could it be due to unsupported char? please help
accesslog_parser.pl
anybody knows how to use accesslog_parser.pl from utils folder?
throttling error and dlr
is it possible to have dlr from SMSC if some messages are facing throttling error?
Re: throttling error and dlr
true, but my question was is it possible to get some kind of dlr if a message failed with throttling error. For example if we see the kannel logs, SMSC only send dlr for error 0x0045 (submit failed) but not for 0x0058 (throttling error) so i want to have the dlr also for error 58 On 07/04/2012 11:00 PM, spameden wrote: kannel is an asynchronous sender, pretty sure 'throttling error' limits only sending functionality not DLR receiving 2012/7/4 Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com is it possible to have dlr from SMSC if some messages are facing throttling error?
Re: throttling error and dlr
exactly, i want to have dlr report with an error in case of throttling. OK, it is not supported by SMPP? On 07/04/2012 11:09 PM, spameden wrote: You mean SMSC should send a DLR report with an error? I don't think it's by SMPP standard. You can always grep kannel's log on this error. 2012/7/4 Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com true, but my question was is it possible to get some kind of dlr if a message failed with throttling error. For example if we see the kannel logs, SMSC only send dlr for error 0x0045 (submit failed) but not for 0x0058 (throttling error) so i want to have the dlr also for error 58 On 07/04/2012 11:00 PM, spameden wrote: kannel is an asynchronous sender, pretty sure 'throttling error' limits only sending functionality not DLR receiving 2012/7/4 Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com is it possible to have dlr from SMSC if some messages are facing throttling error?
Re: R: Kannel MySQL problem
Thanks, i got it working. It was MySQL, you were right. I increased the wait_timeout to 24 hours and the error has gone //moazzam On 06/23/2012 9:09 PM, spameden wrote: What about sqlbox ? Is it from latest SVN as well? You need to compile it after you've installed kannel from trunk. Also try dropping kannel's database tables, sqlbox should re-create them upon startup. 'MySQL server has gone away' generally means something wrong with your MySQL setup, not with kannel. 2012/6/23 Julien Buratto julien.bura...@linkas.it mailto:julien.bura...@linkas.it Why don't you try to measure how long that happens from start of connection ? Ie: start kannel and see what happens after x seconds until it goes to error.. Maybe is a timeout.. 120 secs is short if kannel is not keepaliving the connection.. Also check your my.cnf file as the compiled mysql libs us such conf file And check that libs are same version of server.. Test another mysql server instance and see if it happens again Julien Buratto Linkas SRL Tel.02 30321419 *From: * Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com *Date: *Sat, 23 Jun 2012 18:41:13 +0500 *To: *spamedenspame...@gmail.com mailto:spame...@gmail.com *Cc: *julien.bura...@linkas.it mailto:julien.bura...@linkas.it; users-boun...@kannel.org mailto:users-boun...@kannel.org; users@kannel.org mailto:users@kannel.org *Subject: *Re: R: Kannel MySQL problem already upgraded to latest snapshot but error still persists 2012-06-23 13:29:59 [14633] [6] ERROR: MYSQL: database check failed! 2012-06-23 13:29:59 [14633] [6] ERROR: MYSQL: MySQL server has gone away On 06/23/2012 4:43 PM, spameden wrote: Why don't you use latest from the trunk? There were lots of fixes since 1.4.3. 2012/6/23 Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com complied kannel 1.4.3 stable with mysql support from source on CentOS 6 64-bit //moazzam On 06/23/2012 4:40 PM, spameden wrote: How did you install kannel? Is it from debian's packages? Try to install latest from SVN. 2012/6/23 Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com wait_timeout is set to 120, is it the case? there is no firewall between mysql and kannel as they are both on localhost //moazzam On 06/23/2012 2:38 AM, Julien Buratto wrote: Ali, Check also timeouts values in mysql.. Are you using a custom configured mysql ? Do you have any firewall/proxy/etc in between ? Julien Buratto Linkas SRL Tel.02 30321419 -Original Message- From: Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com Sender: users-bounces@kannel.orgDate mailto:users-bounces@kannel.orgDate: Fri, 22 Jun 2012 23:33:00 To: users@kannel.org mailto:users@kannel.org Subject: Kannel MySQL problem I am facing one issue with the kannel 1.4.3 and MySQL, due to some unknown reason sometime kannel throw following error in the log 2012-06-22 17:14:50 [18671] [6] ERROR: MYSQL: database check failed! 2012-06-22 17:14:50 [18671] [6] ERROR: MYSQL: MySQL server has gone away 2012-06-22 17:14:50 [18671] [6] DEBUG: DBPool has too few connections, reconnecting up to maximum... 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: Connected to server at localhost. 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: server version 5.1.61-log, client version 5.1.61. 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: Connected to server at localhost. 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: server version 5.1.61-log, client version 5.1.61. i have already tried increasing the max_connection both in kannel db connection setting and in my.cnf but still same
Re: release queued messages one by one
anybody, please help //moazzam On Thu, Jun 21, 2012 at 12:40 AM, Moazzam Ali moz...@gmail.com wrote: is it possible to define delay interval between the queued messages? For example if there are 100 SMS queued then after every second one SMS should be submitted to SMSC? //moazzam
Re: release queued messages one by one
throughout controls the overall bind capacity not something to control the delay between the queued messages //moazzam On Sun, Jun 24, 2012 at 4:16 PM, Willy Mularto sangpr...@gmail.com wrote: Set the throughput On Jun 21, 2012 2:42 AM, Moazzam Ali moz...@gmail.com wrote: is it possible to define delay interval between the queued messages? For example if there are 100 SMS queued then after every second one SMS should be submitted to SMSC? //moazzam
Re: release queued messages one by one
out smsapp is already doing this we submit each message to kannel with 3 sec delay from the smsapp but sometime it happen that due to connectivity issue or due to some reason like throttling error, kannel can not submit messages so it starts queues all the messages and when the link become alive it tries to submit all of the queued messages at once or in single burst so lets say you have 200 SMS already in our queue and the total throughput of the link is 50 then again we will hit with the throttling error. Therefore, I am looking for a solution how to create delay between the queued messages so kannel process the queued messages in effective way without hitting the throughput limit. On 06/24/2012 8:10 PM, spameden wrote: What do you mean under 'delay'? Well, you can insert the messages into send_sms with a delay inside your program, i.e (on bash): for i in $(seq 1 10); do mysql -e INSERT INTO send_sms set receiver=... ; sleep 1; done 2012/6/24 Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com throughout controls the overall bind capacity not something to control the delay between the queued messages //moazzam On Sun, Jun 24, 2012 at 4:16 PM, Willy Mularto sangpr...@gmail.com mailto:sangpr...@gmail.com wrote: Set the throughput On Jun 21, 2012 2:42 AM, Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com wrote: is it possible to define delay interval between the queued messages? For example if there are 100 SMS queued then after every second one SMS should be submitted to SMSC? //moazzam
Re: release queued messages one by one
this is not desired because my bind limit is 50, actually however some countries like US/Canada there's a limitation of 1sms/sec/number (sender) so i am trying to find out how to handle this on kannel level. On 06/24/2012 10:25 PM, spameden wrote: did you specify throughput = 1 in your smsc config? 2012/6/24 Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com out smsapp is already doing this we submit each message to kannel with 3 sec delay from the smsapp but sometime it happen that due to connectivity issue or due to some reason like throttling error, kannel can not submit messages so it starts queues all the messages and when the link become alive it tries to submit all of the queued messages at once or in single burst so lets say you have 200 SMS already in our queue and the total throughput of the link is 50 then again we will hit with the throttling error. Therefore, I am looking for a solution how to create delay between the queued messages so kannel process the queued messages in effective way without hitting the throughput limit. On 06/24/2012 8:10 PM, spameden wrote: What do you mean under 'delay'? Well, you can insert the messages into send_sms with a delay inside your program, i.e (on bash): for i in $(seq 1 10); do mysql -e INSERT INTO send_sms set receiver=... ; sleep 1; done 2012/6/24 Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com throughout controls the overall bind capacity not something to control the delay between the queued messages //moazzam On Sun, Jun 24, 2012 at 4:16 PM, Willy Mularto sangpr...@gmail.com mailto:sangpr...@gmail.com wrote: Set the throughput On Jun 21, 2012 2:42 AM, Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com wrote: is it possible to define delay interval between the queued messages? For example if there are 100 SMS queued then after every second one SMS should be submitted to SMSC? //moazzam
Re: release queued messages one by one
Setting throughout to 1 is out of question. OK, i found that this is due to the concatenation. if we keep this disabled then no throttling error appear and if we enable it, we get this error when message length is more than 160. maybe we need to add some delay in each chunk of a mupli-part message on application level On 06/24/2012 11:32 PM, spameden wrote: It might be either kannel bug or SMSC itself, you can try limiting throughput to 1 and testing it out. don't think there is a limit for number/sec, you should handle this limit at your application level before you inserting message into kannel's queue 2012/6/24 Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com this is not desired because my bind limit is 50, actually however some countries like US/Canada there's a limitation of 1sms/sec/number (sender) so i am trying to find out how to handle this on kannel level. On 06/24/2012 10:25 PM, spameden wrote: did you specify throughput = 1 in your smsc config? 2012/6/24 Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com out smsapp is already doing this we submit each message to kannel with 3 sec delay from the smsapp but sometime it happen that due to connectivity issue or due to some reason like throttling error, kannel can not submit messages so it starts queues all the messages and when the link become alive it tries to submit all of the queued messages at once or in single burst so lets say you have 200 SMS already in our queue and the total throughput of the link is 50 then again we will hit with the throttling error. Therefore, I am looking for a solution how to create delay between the queued messages so kannel process the queued messages in effective way without hitting the throughput limit. On 06/24/2012 8:10 PM, spameden wrote: What do you mean under 'delay'? Well, you can insert the messages into send_sms with a delay inside your program, i.e (on bash): for i in $(seq 1 10); do mysql -e INSERT INTO send_sms set receiver=... ; sleep 1; done 2012/6/24 Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com throughout controls the overall bind capacity not something to control the delay between the queued messages //moazzam On Sun, Jun 24, 2012 at 4:16 PM, Willy Mularto sangpr...@gmail.com mailto:sangpr...@gmail.com wrote: Set the throughput On Jun 21, 2012 2:42 AM, Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com wrote: is it possible to define delay interval between the queued messages? For example if there are 100 SMS queued then after every second one SMS should be submitted to SMSC? //moazzam
Re: R: Kannel MySQL problem
wait_timeout is set to 120, is it the case? there is no firewall between mysql and kannel as they are both on localhost //moazzam On 06/23/2012 2:38 AM, Julien Buratto wrote: Ali, Check also timeouts values in mysql.. Are you using a custom configured mysql ? Do you have any firewall/proxy/etc in between ? Julien Buratto Linkas SRL Tel.02 30321419 -Original Message- From: Moazzam Ali moz...@gmail.com Sender: users-bounces@kannel.orgDate: Fri, 22 Jun 2012 23:33:00 To: users@kannel.org Subject: Kannel MySQL problem I am facing one issue with the kannel 1.4.3 and MySQL, due to some unknown reason sometime kannel throw following error in the log 2012-06-22 17:14:50 [18671] [6] ERROR: MYSQL: database check failed! 2012-06-22 17:14:50 [18671] [6] ERROR: MYSQL: MySQL server has gone away 2012-06-22 17:14:50 [18671] [6] DEBUG: DBPool has too few connections, reconnecting up to maximum... 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: Connected to server at localhost. 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: server version 5.1.61-log, client version 5.1.61. 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: Connected to server at localhost. 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: server version 5.1.61-log, client version 5.1.61. i have already tried increasing the max_connection both in kannel db connection setting and in my.cnf but still same
Re: R: Kannel MySQL problem
complied kannel 1.4.3 stable with mysql support from source on CentOS 6 64-bit //moazzam On 06/23/2012 4:40 PM, spameden wrote: How did you install kannel? Is it from debian's packages? Try to install latest from SVN. 2012/6/23 Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com wait_timeout is set to 120, is it the case? there is no firewall between mysql and kannel as they are both on localhost //moazzam On 06/23/2012 2:38 AM, Julien Buratto wrote: Ali, Check also timeouts values in mysql.. Are you using a custom configured mysql ? Do you have any firewall/proxy/etc in between ? Julien Buratto Linkas SRL Tel.02 30321419 -Original Message- From: Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com Sender: users-bounces@kannel.orgDate: Fri, 22 Jun 2012 23:33:00 To: users@kannel.org mailto:users@kannel.org Subject: Kannel MySQL problem I am facing one issue with the kannel 1.4.3 and MySQL, due to some unknown reason sometime kannel throw following error in the log 2012-06-22 17:14:50 [18671] [6] ERROR: MYSQL: database check failed! 2012-06-22 17:14:50 [18671] [6] ERROR: MYSQL: MySQL server has gone away 2012-06-22 17:14:50 [18671] [6] DEBUG: DBPool has too few connections, reconnecting up to maximum... 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: Connected to server at localhost. 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: server version 5.1.61-log, client version 5.1.61. 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: Connected to server at localhost. 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: server version 5.1.61-log, client version 5.1.61. i have already tried increasing the max_connection both in kannel db connection setting and in my.cnf but still same
Re: R: Kannel MySQL problem
already upgraded to latest snapshot but error still persists 2012-06-23 13:29:59 [14633] [6] ERROR: MYSQL: database check failed! 2012-06-23 13:29:59 [14633] [6] ERROR: MYSQL: MySQL server has gone away On 06/23/2012 4:43 PM, spameden wrote: Why don't you use latest from the trunk? There were lots of fixes since 1.4.3. 2012/6/23 Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com complied kannel 1.4.3 stable with mysql support from source on CentOS 6 64-bit //moazzam On 06/23/2012 4:40 PM, spameden wrote: How did you install kannel? Is it from debian's packages? Try to install latest from SVN. 2012/6/23 Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com wait_timeout is set to 120, is it the case? there is no firewall between mysql and kannel as they are both on localhost //moazzam On 06/23/2012 2:38 AM, Julien Buratto wrote: Ali, Check also timeouts values in mysql.. Are you using a custom configured mysql ? Do you have any firewall/proxy/etc in between ? Julien Buratto Linkas SRL Tel.02 30321419 -Original Message- From: Moazzam Ali moz...@gmail.com mailto:moz...@gmail.com Sender: users-bounces@kannel.orgDate mailto:users-bounces@kannel.orgDate: Fri, 22 Jun 2012 23:33:00 To: users@kannel.org mailto:users@kannel.org Subject: Kannel MySQL problem I am facing one issue with the kannel 1.4.3 and MySQL, due to some unknown reason sometime kannel throw following error in the log 2012-06-22 17:14:50 [18671] [6] ERROR: MYSQL: database check failed! 2012-06-22 17:14:50 [18671] [6] ERROR: MYSQL: MySQL server has gone away 2012-06-22 17:14:50 [18671] [6] DEBUG: DBPool has too few connections, reconnecting up to maximum... 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: Connected to server at localhost. 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: server version 5.1.61-log, client version 5.1.61. 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: Connected to server at localhost. 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: server version 5.1.61-log, client version 5.1.61. i have already tried increasing the max_connection both in kannel db connection setting and in my.cnf but still same
Kannel MySQL problem
I am facing one issue with the kannel 1.4.3 and MySQL, due to some unknown reason sometime kannel throw following error in the log 2012-06-22 17:14:50 [18671] [6] ERROR: MYSQL: database check failed! 2012-06-22 17:14:50 [18671] [6] ERROR: MYSQL: MySQL server has gone away 2012-06-22 17:14:50 [18671] [6] DEBUG: DBPool has too few connections, reconnecting up to maximum... 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: Connected to server at localhost. 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: server version 5.1.61-log, client version 5.1.61. 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: Connected to server at localhost. 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: server version 5.1.61-log, client version 5.1.61. i have already tried increasing the max_connection both in kannel db connection setting and in my.cnf but still same
Re: outgoing SMS limit per MSISDN
Throughput variable controls the overall SMSC bind transaction per second not per destination_add. What I am looking for is to control number of allowed SMS per unique receiver basis in a given second so if there are 10 messages in the kannel queue then it should not send all of them at once and should release the queue one by one //moazzam On 06/20/2012 2:28 PM, Amin Mukhaimer wrote: You may want to try using a the variable throughput in SMSC configurations, I hope that works... Also, kindly reply to all so others can read the message, to get help or maybe comment on the issue :) Good luck. -Original Message- From: Moazzam Ali [mailto:moz...@gmail.com] Sent: Wednesday, June 20, 2012 12:21 PM To: Amin Mukhaimer Subject: Re: outgoing SMS limit per MSISDN We already doing this, we store messages in the MySQL database and send one SMS to unique MSISDN per second. However, sometime when we need to restart MySQL or Kannel or sms handler, Kannel starts storing and queuing the messages and Kannel do not release the queued one by one It tries to process all queued messages at once hence SMSC return throttling error in submit response because SMSC only allows one SMS per MSISDN per second. OK if kannel does not support such limit, is there any way if i can limit the queue releasing one message per second? On 06/20/2012 11:59 AM, Amin Mukhaimer wrote: Hi, I would suggest saving that information on your database and having your server check before sending new SMSs whether the number received a SMS already, or maybe having the service that sends the messages run once a day... I don't know if kannel itself has such feature, good luck. -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Moazzam Ali Sent: Wednesday, June 20, 2012 3:29 AM To: users@kannel.org Subject: outgoing SMS limit per MSISDN Hi, is there any way to limit the outgoing SMS per destination MSISDN? For example xxx is a mobile nr and i want to let kannel send only one SMS to this MSISDN per second? //moazzam
release queued messages one by one
is it possible to define delay interval between the queued messages? For example if there are 100 SMS queued then after every second one SMS should be submitted to SMSC? //moazzam
outgoing SMS limit per MSISDN
Hi, is there any way to limit the outgoing SMS per destination MSISDN? For example xxx is a mobile nr and i want to let kannel send only one SMS to this MSISDN per second? //moazzam
kannel session receiving but not sending
Dear all, 5 connections are configured on kannel with TATA and all of them are active but surprisingly the most 1rst connection is only receiving messages not sending. other 4 connection are sending and receiving properly. what can be the problem? any idea SMSC connections: TATASMPP:xx.xx.xx.xx/2775:etopup: (online 11303s, rcvd 20546, sent 325, failed 0, queued 0 msgs) TATASMPP:xx.xx.xx.xx/775:etopup: (online 11288s, rcvd 20527, sent 74564, failed 1, queued 0 msgs) TATASMPP:xx.xx.xx.xx/2775:etopup: (online 11337s, rcvd 20527, sent 37437, failed 2, queued 0 msgs) TATASMPP:xx.xx.xx.xx/2775:etopup: (online 11349s, rcvd 20495, sent 37099, failed 1, queued 0 msgs) TATASMPP:xx.xx.xx.xx2775:etopup: (online 11313s, rcvd 20444, sent 36813, failed 2, queued 0 msgs)
