Re: [RFC] New 'box' Kannel Pluginbox

[Hanh Le Bich]

I wish i can use this box to filter SMS by content or even other polices,
it is a kind of SMS firewall. Many thanks.

Cheers,
Hanh.

On Oct 6, 2016 18:02, "Donald Jackson"  wrote:

Hi Rene,

OK. I am familiar with SMPPBox (have written plugins too ;)) which is why I
was wondering. The 'problem' with this would be that SMPPBox plugin
architecture functions on PDUs (submit_sm, deliver_sm, data_sm etc) and not
Msg * structures, so in order to make the plugins compatible it would need
to convert messages to and from PDU structs's which may not be an ideal
architecture at this layer. It also wouldn't be able to deal with
authentication (bind_* PDUs) as SMPPBox does at the plugin level.

Of course if someone else needs this they can write a plugin to do these
conversions and process :)

Thanks,
Donald



On 6 October 2016 at 12:50, Rene Kluwen  wrote:

> This is more Stipe’s area.
>
> But his smppbox uses a plugin structure as well.
>
> If you use the same structure, people can upgrade/downgrade between
> smppbox server and opensmppbox while maintaining plugin compatibility.
>
>
>
> == Rene
>
>
>
> *Van:* donaldjs...@gmail.com [mailto:donaldjs...@gmail.com] *Namens *Donald
> Jackson
> *Verzonden:* donderdag 6 oktober 2016 11:26
> *Aan:* Rene Kluwen 
> *CC:* kannel_dev_mailinglist 
> *Onderwerp:* Re: [RFC] New 'box' Kannel Pluginbox
>
>
>
> Hi Rene,
>
>
>
> Glad to have saved you some work :)
>
>
> Could you explain what you mean about making it compatible with SMPPBox
> plugin architecture?
>
>
>
> Thanks,
>
> Donald
>
>
>
> On 6 October 2016 at 10:55, Rene Kluwen  wrote:
>
> Yeah, I think it’s useful.
>
> Mainly to prevent having a chain of many boxes if you want some extra
> functionality.
>
> In fact, just now I was thinking of making such a box. So you saved me
> some work.
>
>
>
> Tip: Maybe you can make it source-code compatible with the smppbox server
> plugin architecture.
>
>
>
> == Rene
>
>
>
>
>
> *Van:* devel [mailto:devel-boun...@kannel.org] *Namens *Donald Jackson
> *Verzonden:* donderdag 6 oktober 2016 9:25
> *Aan:* kannel_dev_mailinglist 
> *Onderwerp:* [RFC] New 'box' Kannel Pluginbox
>
>
>
> Hi everyone,
>
>
>
> I have started laying the foundations for a new 'box' for Kannel which
> intends to allow users more flexibility in terms of the platform.
>
>
>
> At the moment there are many ways to get messages into the bearerbox,
> namely: smsbox, wapbox, opensmppbox, smppbox, ksmppd, sqlbox. Some rely on
> routing in their own process and others allow bearerbox to do the routing.
> What they all have in common is they don't allow external or third party
> applications help make decisions at processing time (with the exception of
> ksmppd/smppbox).
>
>
>
> My new planned box is called pluginbox which will basically be like SQLBox
> - but instead of using database callbacks, it will allow linking of dynamic
> libraries (.so|.dylib) which will allow custom
> interception/filtering/modification of message packages to and from
> various boxes.
>
>
>
> So a hypothetical scenario for this box could be something like
>
>
>
> SMSBox, SMPPBox/KSMPPD, WapBox <--> PluginBox <--> Bearerbox
>
>
>
> Or even
>
>
>
> SMSBox, SMPPBox/KSMPPD, WapBox <--> SQLBox <--> PluginBox <--> Bearerbox
>
>
>
> For those who want to still make use of SQLBox.
>
>
>
> My initial design is to use an asynchronous callback chain to allow slow
> plugins to not hold up the processing of faster messages. This would be
> especially useful in the context of people using HTTP and other external
> services to process routing decisions. The plugin would also be able to
> return a status to 'reject' a message packet which would in turn not submit
> to the target receiver.
>
>
>
> My plan is also to implement at least one example plugin (probably an HTTP
> plugin?) which can show the submission and manipulation of a message packet
> in both directions.
>
>
>
> So here I am looking for comments.
>
>
>
> 1) Is this something worthwhile doing, does anyone else have a need for
> this?
>
> 2) Are there any considerations you wish to add at this time?
>
> 3) Are there any features you would like to see added?
>
> 4) Would there be any problem including this in the Kannel repository?
>
>
>
> Here is the initial version : https://github.com/donald-ja
> ckson/kannel-pluginbox
>
>
>
> Thanks Alejandro for SQLBox, its largely based on your code.
>
>
>
> Regards,
>
> --
>
> Donald Jackson
> http://www.ddj.co.za
>
>
>
>
>
> --
>
> Donald Jackson
> http://www.ddj.co.za
>



-- 
Donald Jackson
http://www.ddj.co.za

Re: start up error with SQLbox

[Hanh Le Bich]

Ho Joy,
Cause you said When i included --with-mysql= , i got an error of
unexpected paramter --with-mysql=.
So have you compiled with it or not? Check kannel status, it shows that
info.

Regards,
Hanh.


On Fri, Jun 13, 2014 at 3:45 PM, Joy Larnyoh jilarn...@nalosolutions.com
wrote:

 Dear Hanh,

 On the contrary, my kannel was compiled with mysql (--with-mysql) and
 working fine. Only sqlbox is facing this issue.

 Best Regards

 Joy Ivan Larnyoh

 On Fri, Jun 13, 2014 at 5:11 AM, Hanh Le Bich hanhmi...@gmail.com wrote:

 Seem you have not compiled kannel with mysql (--with-mysql) from the
 beginning.
 As i guest, you should install mysqlclient develop packet before
 compiling.
 In Debian the packet name is (just FYR): mysqlclient-dev
 In CentOS, it's something similar but i forgot, something like mysql-dev.
 Googling and you'll find the name.


 Regards,
 Hanh.


 On Fri, Jun 13, 2014 at 9:47 AM, Joy Larnyoh jilarn...@nalosolutions.com
  wrote:

 Dear WIlly,

 Thanks for your response.

 Below is a snapshot of my config file and the output i get when i run
 the sqlbox:
 [root@vps-1155147-20951 ~]# cat /usr/local/SMSGW/conf/sqlbox.conf
 group = mysql-connection
 host = localhost
 username = usrnalo
 password = pssnalo
 database = dlr

 group = sqlbox
 id = sqlbox-db
 smsbox-id = sqlbox
 #global-sender = 
 bearerbox-host = localhost
 bearerbox-port = 13001
 smsbox-port = 13005
 smsbox-port-ssl = false
 sql-log-table = send_sms_log
 sql-insert-table = send_sms
 log-file = /data/logs/access/sqlbox.log
 log-level = 0

 [root@vps-1155147-20951 ~]# /usr/local/SMSGW/sbin/sqlbox -v 0 --user
 root /usr/local/SMSGW/conf/sqlbox.conf
  2014-06-13 02:46:09 [12306] [0] INFO: Debug_lvl = 0, log_file = none,
 log_lvl = 0
 2014-06-13 02:46:09 [12306] [0] DEBUG: Kannel sqlbox version `1.5.0'.
 Build `Jun  6 2014 18:02:19', compiler `4.4.7 20120313 (Red Hat
 4.4.7-4)'.
 System Linux, release 2.6.32-042stab088.4, version #1 SMP Thu Apr 3
 17:41:05 MSK 2014, machine x86_64.

 Libxml version 2.7.6.
 Using OpenSSL 1.0.1e-fips 11 Feb 2013.
 Using native malloc.

 2014-06-13 02:46:09 [12306] [0] INFO: Starting to log to file
 /data/logs/access/sqlbox.log level 0
 2014-06-13 02:46:09 [12306] [0] INFO: Added logfile
 `/data/logs/access/sqlbox.log' with level `0'.
 2014-06-13 02:46:09 [12306] [0] PANIC: No proper SQL server defined.
 2014-06-13 02:46:09 [12306] [0] PANIC:
 /usr/local/SMSGW/sbin/sqlbox(gw_panic+0x147) [0x423387]
 2014-06-13 02:46:09 [12306] [0] PANIC:
 /usr/local/SMSGW/sbin/sqlbox(main+0x502) [0x40a7f2]
 2014-06-13 02:46:09 [12306] [0] PANIC:
 /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f5985681d1d]
 2014-06-13 02:46:09 [12306] [0] PANIC: /usr/local/SMSGW/sbin/sqlbox()
 [0x409559]
 [root@vps-1155147-20951 ~]#

 Best Regards

 Joy Ivan Larnyoh
 Chief Technical Officer
 NALO Solutions Limited
 House No. 1, Mahogany Close, Dansoman Last Stop

 M: +233  574928710, T: +233 289311489

 E: jilarn...@nalosolutions.com jilarn...@nalosolutions.com, W:
 www.nalosolutions.com http://www.nalosol.com/


 On Fri, Jun 13, 2014 at 2:20 AM, Willy Mularto sangpr...@gmail.com
 wrote:

 —with-mysql parameter is not exist for SQLBox

 No proper SQL server error means you have not set up a configuration
 file. Please refer to the user guide how to set it up


 Willy Mularto
 SMS Gateway, Content Provider, Mobile Solution Specialist
 M: +62811923464, +62818923464
 PIN BBM: 74924429



 On Jun 13, 2014, at 9:15 AM, Joy Larnyoh jilarn...@nalosolutions.com
 wrote:

 Hi Alvaro,

 While installing the sqlbox, I used below to configure
 ./configure --prefix=/usr/local/SMSGW/
 --with-kannel-dir=/usr/local/SMSGW/
 When i included --with-mysql= , i got an error of unexpected paramter
 --with-mysql=.

 Below is the error i get when I start SQLbox
 2014-06-12 14:56:04 [1593] [0] INFO: Starting to log to file
 /data/logs/access/sqlbox.log level 0
 2014-06-12 14:56:04 [1593] [0] INFO: Added logfile
 `/data/logs/access/sqlbox.log' with level `0'.
 *2014-06-12 14:56:04 [1593] [0] PANIC: No proper SQL server defined.*
 2014-06-12 14:56:04 [1593] [0] PANIC:
 /usr/local/SMSGW/sbin/sqlbox(gw_panic+0x147) [0x423387]
 2014-06-12 14:56:04 [1593] [0] PANIC:
 /usr/local/SMSGW/sbin/sqlbox(main+0x502) [0x40a7f2]
 2014-06-12 14:56:04 [1593] [0] PANIC:
 /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f1dad015d1d]
 2014-06-12 14:56:04 [1593] [0] PANIC: /usr/local/SMSGW/sbin/sqlbox()
 [0x409559]

 Best Regards

 Joy Ivan Larnyoh
 Chief Technical Officer
 NALO Solutions Limited
 House No. 1, Mahogany Close, Dansoman Last Stop

 M: +233  574928710, T: +233 289311489

 E: jilarn...@nalosolutions.com jilarn...@nalosolutions.com, W:
 www.nalosolutions.com http://www.nalosol.com/


 On Thu, Jun 12, 2014 at 6:48 PM, Alvaro Cornejo 
 cornejo.alv...@gmail.com wrote:

 Hi

 Seems you have not configured the database to use or compiled it
 without a database option.

 Check manual for details or post logs

 Regards

 Alvaro

Re: start up error with SQLbox

[Hanh Le Bich]

Seem you have not compiled kannel with mysql (--with-mysql) from the
beginning.
As i guest, you should install mysqlclient develop packet before compiling.
In Debian the packet name is (just FYR): mysqlclient-dev
In CentOS, it's something similar but i forgot, something like mysql-dev.
Googling and you'll find the name.


Regards,
Hanh.


On Fri, Jun 13, 2014 at 9:47 AM, Joy Larnyoh jilarn...@nalosolutions.com
wrote:

 Dear WIlly,

 Thanks for your response.

 Below is a snapshot of my config file and the output i get when i run the
 sqlbox:
 [root@vps-1155147-20951 ~]# cat /usr/local/SMSGW/conf/sqlbox.conf
 group = mysql-connection
 host = localhost
 username = usrnalo
 password = pssnalo
 database = dlr

 group = sqlbox
 id = sqlbox-db
 smsbox-id = sqlbox
 #global-sender = 
 bearerbox-host = localhost
 bearerbox-port = 13001
 smsbox-port = 13005
 smsbox-port-ssl = false
 sql-log-table = send_sms_log
 sql-insert-table = send_sms
 log-file = /data/logs/access/sqlbox.log
 log-level = 0

 [root@vps-1155147-20951 ~]# /usr/local/SMSGW/sbin/sqlbox -v 0 --user root
 /usr/local/SMSGW/conf/sqlbox.conf
 2014-06-13 02:46:09 [12306] [0] INFO: Debug_lvl = 0, log_file = none,
 log_lvl = 0
 2014-06-13 02:46:09 [12306] [0] DEBUG: Kannel sqlbox version `1.5.0'.
 Build `Jun  6 2014 18:02:19', compiler `4.4.7 20120313 (Red Hat 4.4.7-4)'.
 System Linux, release 2.6.32-042stab088.4, version #1 SMP Thu Apr 3
 17:41:05 MSK 2014, machine x86_64.

 Libxml version 2.7.6.
 Using OpenSSL 1.0.1e-fips 11 Feb 2013.
 Using native malloc.

 2014-06-13 02:46:09 [12306] [0] INFO: Starting to log to file
 /data/logs/access/sqlbox.log level 0
 2014-06-13 02:46:09 [12306] [0] INFO: Added logfile
 `/data/logs/access/sqlbox.log' with level `0'.
 2014-06-13 02:46:09 [12306] [0] PANIC: No proper SQL server defined.
 2014-06-13 02:46:09 [12306] [0] PANIC:
 /usr/local/SMSGW/sbin/sqlbox(gw_panic+0x147) [0x423387]
 2014-06-13 02:46:09 [12306] [0] PANIC:
 /usr/local/SMSGW/sbin/sqlbox(main+0x502) [0x40a7f2]
 2014-06-13 02:46:09 [12306] [0] PANIC:
 /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f5985681d1d]
 2014-06-13 02:46:09 [12306] [0] PANIC: /usr/local/SMSGW/sbin/sqlbox()
 [0x409559]
 [root@vps-1155147-20951 ~]#

 Best Regards

 Joy Ivan Larnyoh
 Chief Technical Officer
 NALO Solutions Limited
 House No. 1, Mahogany Close, Dansoman Last Stop

 M: +233  574928710, T: +233 289311489

 E: jilarn...@nalosolutions.com jilarn...@nalosolutions.com, W:
 www.nalosolutions.com http://www.nalosol.com/


 On Fri, Jun 13, 2014 at 2:20 AM, Willy Mularto sangpr...@gmail.com
 wrote:

 —with-mysql parameter is not exist for SQLBox

 No proper SQL server error means you have not set up a configuration
 file. Please refer to the user guide how to set it up


 Willy Mularto
 SMS Gateway, Content Provider, Mobile Solution Specialist
 M: +62811923464, +62818923464
 PIN BBM: 74924429



 On Jun 13, 2014, at 9:15 AM, Joy Larnyoh jilarn...@nalosolutions.com
 wrote:

 Hi Alvaro,

 While installing the sqlbox, I used below to configure
 ./configure --prefix=/usr/local/SMSGW/ --with-kannel-dir=/usr/local/SMSGW/
 When i included --with-mysql= , i got an error of unexpected paramter
 --with-mysql=.

 Below is the error i get when I start SQLbox
 2014-06-12 14:56:04 [1593] [0] INFO: Starting to log to file
 /data/logs/access/sqlbox.log level 0
 2014-06-12 14:56:04 [1593] [0] INFO: Added logfile
 `/data/logs/access/sqlbox.log' with level `0'.
 *2014-06-12 14:56:04 [1593] [0] PANIC: No proper SQL server defined.*
 2014-06-12 14:56:04 [1593] [0] PANIC:
 /usr/local/SMSGW/sbin/sqlbox(gw_panic+0x147) [0x423387]
 2014-06-12 14:56:04 [1593] [0] PANIC:
 /usr/local/SMSGW/sbin/sqlbox(main+0x502) [0x40a7f2]
 2014-06-12 14:56:04 [1593] [0] PANIC:
 /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f1dad015d1d]
 2014-06-12 14:56:04 [1593] [0] PANIC: /usr/local/SMSGW/sbin/sqlbox()
 [0x409559]

 Best Regards

 Joy Ivan Larnyoh
 Chief Technical Officer
 NALO Solutions Limited
 House No. 1, Mahogany Close, Dansoman Last Stop

 M: +233  574928710, T: +233 289311489

 E: jilarn...@nalosolutions.com jilarn...@nalosolutions.com, W:
 www.nalosolutions.com http://www.nalosol.com/


 On Thu, Jun 12, 2014 at 6:48 PM, Alvaro Cornejo cornejo.alv...@gmail.com
  wrote:

 Hi

 Seems you have not configured the database to use or compiled it
 without a database option.

 Check manual for details or post logs

 Regards

 Alvaro

 |-|
 Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
 celular y Nextel
 en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via
 SMS y GPRS online
   Visitenos en www.perusms.com


 On Thu, Jun 12, 2014 at 11:36 AM, Joy Larnyoh
 jilarn...@nalosolutions.com wrote:
  Hi ,
 
  I have SQLbox verson 1.5 installed on CEntos 6 OS.
 
  I however have below error when i start the SQlbox:
   No proper SQL server defined.
 
  I would be 

Re: memory leaks in opensmppbox

[Hanh Le Bich]

:263)
==26926==by 0x4576C2: octstr_duplicate_real (octstr.c:377)
==26926==by 0x417074: msg_duplicate (msg-decl.h:80)
==26926==by 0x4103DF: catenate_msg (opensmppbox.c:525)
==26926==by 0x4106F9: check_multipart (opensmppbox.c:1481)
==26926==by 0x411878: smpp_to_bearerbox (opensmppbox.c:1639)
==26926==by 0x44C5F5: new_thread (gwthread-pthread.c:385)
==26926==by 0x6162B4F: start_thread (pthread_create.c:304)
==26926==by 0x6CF90EC: clone (clone.S:112)
==26926==
==26926== 4,032 bytes in 14 blocks are possibly lost in loss record 680 of
734
==26926==at 0x4C27013: calloc (vg_replace_malloc.c:618)
==26926==by 0x401128E: _dl_allocate_tls (dl-tls.c:300)
==26926==by 0x6163483: pthread_create@@GLIBC_2.2.5 (allocatestack.c:580)
==26926==by 0x44C1C8: gwthread_create_real (gwthread-pthread.c:475)
==26926==by 0x40D490: main (opensmppbox.c:2157)
==26926==
==26926== 4,135 (1,952 direct, 2,183 indirect) bytes in 61 blocks are
definitely lost in loss record 681 of 734
==26926==at 0x4C28D84: malloc (vg_replace_malloc.c:291)
==26926==by 0x44B4C0: gw_native_malloc (gwmem-native.c:87)
==26926==by 0x457164: octstr_create_from_data_real (octstr.c:263)
==26926==by 0x4576C2: octstr_duplicate_real (octstr.c:377)
==26926==by 0x416FE4: msg_duplicate (msg-decl.h:80)
==26926==by 0x4103DF: catenate_msg (opensmppbox.c:525)
==26926==by 0x4106F9: check_multipart (opensmppbox.c:1481)
==26926==by 0x411878: smpp_to_bearerbox (opensmppbox.c:1639)
==26926==by 0x44C5F5: new_thread (gwthread-pthread.c:385)
==26926==by 0x6162B4F: start_thread (pthread_create.c:304)
==26926==by 0x6CF90EC: clone (clone.S:112)
==26926==
==26926== 4,320 bytes in 15 blocks are possibly lost in loss record 682 of
734
==26926==at 0x4C27013: calloc (vg_replace_malloc.c:618)
==26926==by 0x401128E: _dl_allocate_tls (dl-tls.c:300)
==26926==by 0x6163483: pthread_create@@GLIBC_2.2.5 (allocatestack.c:580)
==26926==by 0x44C1C8: gwthread_create_real (gwthread-pthread.c:475)
==26926==by 0x40E9AA: run_smppbox (opensmppbox.c:2125)
==26926==by 0x44C5F5: new_thread (gwthread-pthread.c:385)
==26926==by 0x6162B4F: start_thread (pthread_create.c:304)
==26926==by 0x6CF90EC: clone (clone.S:112)
==26926==
==26926== LEAK SUMMARY:
==26926==definitely lost: 7,104 bytes in 207 blocks
==26926==indirectly lost: 3,652 bytes in 208 blocks
==26926==  possibly lost: 8,640 bytes in 30 blocks
==26926==still reachable: 7,516,113 bytes in 30,609 blocks
==26926== suppressed: 0 bytes in 0 blocks
==26926== Reachable blocks (those to which a pointer was found) are not
shown.
==26926== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==26926==
==26926== For counts of detected and suppressed errors, rerun with: -v
==26926== ERROR SUMMARY: 10 errors from 10 contexts (suppressed: 6 from 4)

Regards,
Hanh.


On Wed, Jun 11, 2014 at 1:58 AM, hbil...@ecommunicate.biz wrote:

 Hi Hanh,

 I can’t access the drop box contents.
 Please paste the details of the drop box into this email so we can all see
 your Valgrind results.
 Track origins should be the key.  valgrind --leak-check=full
 --track-origins=yes ./opensmppbox?

 thanks

 From: Hanh Le Bich [mailto:hanhmi...@gmail.com]
 Sent: Tuesday, June 10, 2014 4:44 PM
 To: hbil...@ecommunicate.biz
 Cc: devel@kannel.org; Rene Kluwen
 Subject: Re: memory leaks in opensmppbox

 Dear all,
 I've migrated my SMSC Gateway to another physical SUN server last week,
 using the lastest SVN 5090.
 I still keep the current kannel configuration except changed store-type =
 spool from file as trailing mail.
 And the memory leaking due to opensmppbox still persist:

 https://www.dropbox.com/s/dnvs20j3omo7ail/opensmppbox_memleakcheck_20140608.txt

 Hopefully you can find something helpful. Thank you and wish you healthy.
 Regards,
 Hanh.

 On Tue, Jun 10, 2014 at 2:44 AM, hbil...@ecommunicate.biz wrote:
 Hi Hanh,

 Now that you and Stipe have confirmed there is currently no memory leak in
 smsbox, let’s focus only on the memory leaks in opensmppbox with a new
 thread as you suggested.
 If anyone else has experience with memory leaks in opensmppbox please post
 to this thread, so that we can use others experience to find if there are
 memory leaks.

 Hanh as discussed, please check again using valgrind the latest svn for
 opensmppbox using your new virtual machine and the approach Rene suggested
 which is:
 valgrind --leak-check=full --track-origins=yes ./opensmppbox

 Without you re-running valgrind on your new virtual machine and sending us
 the results, we will not know if the previous memory leaks you reported
 were
 caused by your faulty memory on the other server or via memory leaks in
 opensmppbox.

 Here are the Kannel configurations that you posted before and I assume they
 are still valid.  If there are any changes to these please correct them.

 **kannel.conf

Re: memory leaks in opensmppbox

[Hanh Le Bich]

Dear all,
I've migrated my SMSC Gateway to another physical SUN server last week,
using the lastest SVN 5090.
I still keep the current kannel configuration except changed store-type =
spool from file as trailing mail.
And the memory leaking due to opensmppbox still persist:
https://www.dropbox.com/s/dnvs20j3omo7ail/opensmppbox_memleakcheck_20140608.txt

Hopefully you can find something helpful. Thank you and wish you healthy.

Regards,
Hanh.


On Tue, Jun 10, 2014 at 2:44 AM, hbil...@ecommunicate.biz wrote:

 Hi Hanh,

 Now that you and Stipe have confirmed there is currently no memory leak in
 smsbox, let’s focus only on the memory leaks in opensmppbox with a new
 thread as you suggested.
 If anyone else has experience with memory leaks in opensmppbox please post
 to this thread, so that we can use others experience to find if there are
 memory leaks.

 Hanh as discussed, please check again using valgrind the latest svn for
 opensmppbox using your new virtual machine and the approach Rene suggested
 which is:
 valgrind --leak-check=full --track-origins=yes ./opensmppbox

 Without you re-running valgrind on your new virtual machine and sending us
 the results, we will not know if the previous memory leaks you reported
 were
 caused by your faulty memory on the other server or via memory leaks in
 opensmppbox.

 Here are the Kannel configurations that you posted before and I assume they
 are still valid.  If there are any changes to these please correct them.

 **kannel.conf
 group = core
 admin-port = 13000
 smsbox-port = 13001
 admin-password = **
 status-password = **
 log-file = /var/log/kannel/bearerbox.log
 access-log = /var/log/kannel/bearerbox-access.log
 log-level = 1
 ssl-server-cert-file = /etc/kannel/cert.pem
 ssl-server-key-file = /etc/kannel/key.pem
 dlr-storage = mysql
 admin-allow-ip = *.*.*.*
 smsbox-max-pending = 100
 sms-incoming-queue-limit = -1
 store-type = file
 store-location = /var/log/kannel/kannel.store
 store-dump-freq = 10

 include = /etc/kannel/smsc.conf

 include = /etc/kannel/service_route.conf

 group = smsbox
 smsbox-id = Redundancy
 bearerbox-host = localhost
 sendsms-port = 13013
 sendsms-chars = 0123456789 +-
 log-file = /var/log/kannel/smsbox.log
 log-level = 2

 #For DLR
 group = mysql-connection
 id = bb_dlr_id
 host = localhost
 username = root
 password = *
 database = kannel
 max-connections = 10

 group = dlr-db
 id = bb_dlr_id
 table = kannel_bb_dlr
 field-smsc = smsc
 field-timestamp = ts
 field-destination = destination
 field-source = source
 field-service = service
 field-url = url
 field-mask = mask
 field-status = status
 field-boxc-id = boxc


 **sqlbox.conf
 group = sqlbox
 id = sqlbox-idd
 smsbox-id = sqlbox
 bearerbox-host = localhost
 bearerbox-port = 13001
 smsbox-port = 13005
 smsbox-port-ssl = false
 limit-per-cycle = 50
 save-dlr = 0
 sql-log-table = sent_sms
 sql-insert-table = send_sms
 log-file = /var/log/kannel/sqlbox.log
 log-level = 1

 group = mysql-connection
 id = sqlbox-idd
 host = localhost
 username = root
 password = **
 database = kannel
 max-connections = 10



 **opensmppbox.conf**
 **
 group = core
 dlr-storage = mysql

 group = opensmppbox
 opensmppbox-id = smppbox-idd
 opensmppbox-port = 2775
 bearerbox-host = 127.0.0.1
 bearerbox-port = 13005
 our-system-id = thefirstsmppbox
 smpp-logins = /etc/kannel/smpplogins.txt
 use-systemid-as-smsboxid = 1
 log-file = /var/log/kannel/smppbox.log
 log-level = 1

 group = smsc-route
 smsc-id = main_smsc
 smsbox-id = payment
 shortcode = 155

 group = smsc-route
 smsc-id = main_smsc
 smsbox-id = lumata
 shortcode = 146

 group = mysql-connection
 id = smppboxdlr-idd
 host = localhost
 username = root
 password = **
 database = kannel
 max-connections = 10

 group = dlr-db
 id = smppboxdlr-idd
 table = kannel_smppbox_dlr
 field-smsc = smsc
 field-timestamp = ts
 field-destination = destination
 field-source = source
 field-service = service
 field-url = url
 field-mask = mask
 field-status = status
 field-boxc-id = boxc



 **service_route.conf
 
 group = smsbox-route
 smsbox-id = payment
 shortcode = 155

 group = smsbox-route
 smsbox-id = lumata
 shortcode = 146


 **smsc.conf
 group = smsc
 smsc = smpp
 smsc-id = main_smsc
 allowed-smsc-id = main_smsc
 host = x.x.x.x
 port = 45289
 log-file=/var/log/kannel/smsc.log
 log-level = 1
 transceiver-mode = true
 smsc-username = SMSCGW
 smsc-password = **
 system-type = VMA
 reconnect-delay = 10
 enquire-link-interval = 300
 throughput = 150
 max-pending-submits = 200
 max-sms-octets = 140
 source-addr-ton = 0
 source-addr-npi = 1
 alt-charset = ASCII
 alt-addr-charset = GSM

 

Re: Does opensmppbox and smsbox have serious memory issues?

[Hanh Le Bich]

Hi,
Just a notice that my opensmppbox used to run on another server, not
related to SMS Broadcast server which has smsbox issue.
The server which run opensmppbox is a good one, but last week, i also
migrated it to another model server (still a physical one).
Here is the valgrind report for opensmppbox running on the new server, the
leaking is true:

https://www.dropbox.com/s/dnvs20j3omo7ail/opensmppbox_memleakcheck_20140608.txt

==26926== LEAK SUMMARY:
==26926==definitely lost: 7,104 bytes in 207 blocks
==26926==indirectly lost: 3,652 bytes in 208 blocks
==26926==  possibly lost: 8,640 bytes in 30 blocks
==26926==still reachable: 7,516,113 bytes in 30,609 blocks
==26926== suppressed: 0 bytes in 0 blocks
==26926== Reachable blocks (those to which a pointer was found) are not shown.
==26926== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==26926==
==26926== For counts of detected and suppressed errors, rerun with: -v
==26926== ERROR SUMMARY: 10 errors from 10 contexts (suppressed: 6 from 4)

Regards,

Hanh.





On Sun, Jun 8, 2014 at 3:35 AM, hbil...@ecommunicate.biz wrote:

 Hi Hanh,

 That's good news. As it seemed strange no one else would have picked up
 this
 issue for smsbox, which is so well used.

 However for opensmppbox, which is not as well used as smsbox, there may
 still be actual memory leaks.
 Please check again using your new virtual machine and send us your results
 using:
 valgrind --leak-check=full --track-origins=yes ./opensmppbox

 thanks

 --
 Date: Sat, 7 Jun 2014 10:31:18 +0700
 From: Hanh Le Bich hanhmi...@gmail.com
 To: Stipe Tolj st...@kannel.org
 Cc: devel@kannel.org
 Subject: Re: Does opensmppbox and smsbox have serious memory issues?
 Message-ID:
 
 ca+p4dgyjy-26_t0rhpkohrmtqebavk8gceqslkh6jvvbbpy...@mail.gmail.com
 Content-Type: text/plain; charset=utf-8

 Hi Stipe and list,
 I don't know how to say now. I had migrated my SMS Broadcast system to
 another server last week (an Virtual machine) and there is no mem leak of
 smsbox  any more.
 I've tested for every scenarios and it is clean:

 ==22709== Memcheck, a memory error detector ==22709== Copyright (C)
 2002-2013, and GNU GPL'd, by Julian Seward et al.
 ==22709== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info
 ==22709== Command: /usr/local/sbin/smsbox -v -d -- /etc/kannel/kannel.conf
 ==22709== Parent PID: 22707 ==22709== ==22709== ==22709== HEAP SUMMARY:
 ==22709== in use at exit: 2,184 bytes in 39 blocks
 ==22709==   total heap usage: 3,084,394 allocs, 3,084,355 frees,
 630,991,485 bytes allocated
 ==22709==
 ==22709== LEAK SUMMARY:
 ==22709==definitely lost: 0 bytes in 0 blocks
 ==22709==indirectly lost: 0 bytes in 0 blocks
 ==22709==  possibly lost: 0 bytes in 0 blocks
 ==22709==still reachable: 2,184 bytes in 39 blocks
 ==22709== suppressed: 0 bytes in 0 blocks
 ==22709== Reachable blocks (those to which a pointer was found) are not
 shown.
 ==22709== To see them, rerun with: --leak-check=full --show-leak-kinds=all
 ==22709== ==22709== For counts of detected and suppressed errors, rerun
 with: -v ==22709== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 6
 from 4)

 Suppose that i have physical mem issue in my old machine(!?), cause in
 migration progress, i found the old one has an alarm at its booting time:
 8601: All memory marked as fail. Forcing minimum back online. Then i have
 to press F1 to Resume.

 I apology and appreciate all of you to spending time on this issue. If have
 any request for testing in high loading, also  the opensmppbox mem leak,
 please let me know. Thank you.

 Regards,
 Hanh.


 On Mon, Jun 2, 2014 at 8:48 PM, Stipe Tolj st...@kannel.org wrote:

  Am 20.05.2014 04:54, schrieb Hanh Le Bich:
 
   Hello again,
  Sorry for late reply, i was stuck on field.
 
  1. I upload again the previous Valgrind report in below link also in
  attachment as usual:
  https://www.dropbox.com/s/wbnkewitosiwv5i/opensmppbox_
  memleakcheck_20140502.txt
 
  2. Here is my kannel configuration:
  https://www.dropbox.com/s/u90vs8srbubbmhn/kannel_configuration_file.t
  xt
 
 
  Hi list,
 
  I can't reproduce the memory leak that Hanh is reporting here, even
  with setting 'smsbox-id' in the 'group = smsbox' context I get clean
  memory deallocations.
 
  Here is my valgrind report:
 
  ==00:00:00:00.000 14193== Memcheck, a memory error detector.
  ==00:00:00:00.000 14193== Copyright (C) 2002-2007, and GNU GPL'd, by
  Julian Seward et al.
  ==00:00:00:00.000 14193== Using LibVEX rev 1854, a library for dynamic
  binary translation.
  ==00:00:00:00.000 14193== Copyright (C) 2004-2007, and GNU GPL'd, by
  OpenWorks LLP.
  ==00:00:00:00.000 14193== Using valgrind-3.3.1-Debian, a dynamic
  binary instrumentation framework.
  ==00:00:00:00.000 14193== Copyright (C) 2000-2007, and GNU GPL'd, by
  Julian Seward et al.
  ==00:00:00:00.000 14193== For more

Re: Does opensmppbox and smsbox have serious memory issues?

[Hanh Le Bich]

Hi Stipe and list,
I don't know how to say now. I had migrated my SMS Broadcast system to
another server last week (an Virtual machine) and there is no mem leak of
smsbox  any more.
I've tested for every scenarios and it is clean:

==22709== Memcheck, a memory error detector
==22709== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==22709== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info
==22709== Command: /usr/local/sbin/smsbox -v -d -- /etc/kannel/kannel.conf
==22709== Parent PID: 22707
==22709==
==22709==
==22709== HEAP SUMMARY:
==22709== in use at exit: 2,184 bytes in 39 blocks
==22709==   total heap usage: 3,084,394 allocs, 3,084,355 frees,
630,991,485 bytes allocated
==22709==
==22709== LEAK SUMMARY:
==22709==definitely lost: 0 bytes in 0 blocks
==22709==indirectly lost: 0 bytes in 0 blocks
==22709==  possibly lost: 0 bytes in 0 blocks
==22709==still reachable: 2,184 bytes in 39 blocks
==22709== suppressed: 0 bytes in 0 blocks
==22709== Reachable blocks (those to which a pointer was found) are not
shown.
==22709== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==22709==
==22709== For counts of detected and suppressed errors, rerun with: -v
==22709== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 6 from 4)

Suppose that i have physical mem issue in my old machine(!?), cause in
migration progress, i found the old one has an alarm at its booting time:
8601: All memory marked as fail. Forcing minimum back online. Then i have
to press F1 to Resume.

I apology and appreciate all of you to spending time on this issue. If have
any request for testing in high loading, also  the opensmppbox mem leak,
please let me know. Thank you.

Regards,
Hanh.


On Mon, Jun 2, 2014 at 8:48 PM, Stipe Tolj st...@kannel.org wrote:

 Am 20.05.2014 04:54, schrieb Hanh Le Bich:

  Hello again,
 Sorry for late reply, i was stuck on field.

 1. I upload again the previous Valgrind report in below link also in
 attachment as usual:
 https://www.dropbox.com/s/wbnkewitosiwv5i/opensmppbox_
 memleakcheck_20140502.txt

 2. Here is my kannel configuration:
 https://www.dropbox.com/s/u90vs8srbubbmhn/kannel_configuration_file.txt


 Hi list,

 I can't reproduce the memory leak that Hanh is reporting here, even with
 setting 'smsbox-id' in the 'group = smsbox' context I get clean memory
 deallocations.

 Here is my valgrind report:

 ==00:00:00:00.000 14193== Memcheck, a memory error detector.
 ==00:00:00:00.000 14193== Copyright (C) 2002-2007, and GNU GPL'd, by
 Julian Seward et al.
 ==00:00:00:00.000 14193== Using LibVEX rev 1854, a library for dynamic
 binary translation.
 ==00:00:00:00.000 14193== Copyright (C) 2004-2007, and GNU GPL'd, by
 OpenWorks LLP.
 ==00:00:00:00.000 14193== Using valgrind-3.3.1-Debian, a dynamic binary
 instrumentation framework.
 ==00:00:00:00.000 14193== Copyright (C) 2000-2007, and GNU GPL'd, by
 Julian Seward et al.
 ==00:00:00:00.000 14193== For more details, rerun with: -v
 ==00:00:00:00.000 14193==
 ==00:00:00:00.000 14193== My PID = 14193, parent PID = 1.  Prog and args
 are:
 ==00:00:00:00.000 14193== /home/tolj/src/kannel/devel/
 gateway-redis/gw/smsbox
 ==00:00:00:00.000 14193==-v
 ==00:00:00:00.000 14193==4
 ==00:00:00:00.000 14193==-p
 ==00:00:00:00.000 14193==/opt/kannel/var/run/smsbox_client.pid
 ==00:00:00:00.000 14193==/opt/kannel/etc/kannel_client.conf
 ==00:00:00:00.000 14193==
 ==00:00:05:18.814 14193==
 ==00:00:05:18.814 14193== FILE DESCRIPTORS: 6 open at exit.
 ==00:00:05:18.814 14193== Open file descriptor 6:
 ==00:00:05:18.814 14193==at 0x71E2377: pipe (in /usr/lib/debug/
 libc-2.7.so)
 ==00:00:05:18.814 14193==by 0x437A2E: fill_threadinfo
 (gwthread-pthread.c:186)
 ==00:00:05:18.814 14193==by 0x437D0D: gwthread_init
 (gwthread-pthread.c:281)
 ==00:00:05:18.814 14193==by 0x4371D9: gwlib_init (gwlib.c:85)
 ==00:00:05:18.814 14193==by 0x40FC5C: main (smsbox.c:3543)
 ==00:00:05:18.814 14193==
 ==00:00:05:18.814 14193== Open file descriptor 5:
 ==00:00:05:18.814 14193==at 0x71E2377: pipe (in /usr/lib/debug/
 libc-2.7.so)
 ==00:00:05:18.814 14193==by 0x437A2E: fill_threadinfo
 (gwthread-pthread.c:186)
 ==00:00:05:18.814 14193==by 0x437D0D: gwthread_init
 (gwthread-pthread.c:281)
 ==00:00:05:18.814 14193==by 0x4371D9: gwlib_init (gwlib.c:85)
 ==00:00:05:18.814 14193==by 0x40FC5C: main (smsbox.c:3543)
 ==00:00:05:18.814 14193==
 ==00:00:05:18.814 14193== Open file descriptor 3:
 /opt/kannel-1.5.0-svn/log.valgrind
 ==00:00:05:18.814 14193==inherited from parent
 ==00:00:05:18.814 14193==
 ==00:00:05:18.814 14193== Open file descriptor 2: /dev/null
 ==00:00:05:18.814 14193==inherited from parent
 ==00:00:05:18.814 14193==
 ==00:00:05:18.814 14193== Open file descriptor 1: /dev/null
 ==00:00:05:18.814 14193==inherited from parent
 ==00:00:05:18.814 14193==
 ==00:00:05:18.814 14193== Open file descriptor 0: /dev/null
 ==00:00:05:18.814 14193

Re: Does opensmppbox and smsbox have serious memory issues?

[Hanh Le Bich]

Hi team,
Here they are, both last time report and the one i have produced few
minutes ago. Thank you.
I captured in 10  12 minutes, interested that they have same size.

Upload again on dropbox cause my friend has deleted it:

https://www.dropbox.com/s/yjrc6wmdm0rwonz/smsbox_memleakcheck_20140503.txt

https://www.dropbox.com/s/f8zgfc5ji84a0n8/smsbox_memleakcheck_20140510.txt

Regards, Hanh.


On Fri, May 9, 2014 at 9:07 PM, hbil...@ecommunicate.biz wrote:

 Hi Hanh,



 Please you email us the file smsbox_memleakcheck_20140503.txt with your
 results from Valgrind, as it’s no longer available on drop box.



 Thanks





 *From:* Alexander Malysh [mailto:malys...@gmail.com] *On Behalf Of *Alexander
 Malysh
 *Sent:* Friday, May 9, 2014 12:58 PM
 *To:* hbil...@ecommunicate.biz
 *Cc:* Hanh Le Bich; devel@kannel.org; Stipe Tolj; af...@list.fink.org

 *Subject:* Re: Does opensmppbox and smsbox have serious memory issues?



 Hi,



 unfortunately this file is not there anymore. Could you please new file
 please?



 Alex



 Am 07.05.2014 um 13:15 schrieb hbil...@ecommunicate.biz:



 HI Hanh and Kannel developers,



 The memory leaks in the latest svn for smsbox, as mentioned in your post
 Date: Sat, 3 May 2014 10:06:54 +0700 and  shown in
 https://www.dropbox.com/s/yjrc6wmdm0rwonz/smsbox_memleakcheck_20140503.txt

 are also contributing to the increase in the total memory leak.  Each
 SMSs needs to also go through smsbox.  There are memory leaks both smsbox
 and also in opensmppbox.



 Thanks for bringing this to the attention of the Kannel devel group and
 producing these Valgrinds. It’s useful to see what happens to Kannel with a
 high throughput.

 This is currently not my area of expertise.



 We need the help of the top Kannel developers to fix this, so the latest
 svn will be free of memory leaks.



 You mention in the post on Sat, 3 May 2014 10:06:54 +0700: “Hello again,
 Here is valgrind report for the smsbox memory leaking. This is also the
 latest kannel revision 5089.

 For me, it still happen, i submit (broadcast) million SMS(s) per day
 within few hours at 1000 TPS of throughput. Thus each day, smsbox swallow ~
 400MB RAM and not release until server memory exhaust after few days. At
 this time, the box is auto restarted and i have my memory back, so on,
 again and again.



 I not sure, but in very low throughput system, i am not aware this issue.



 ==5730== LEAK SUMMARY:

 ==5730==definitely lost: 231,680 bytes in 14,480 blocks

 ==5730==indirectly lost: 144,790 bytes in 14,479 blocks

 ==5730==  possibly lost: 0 bytes in 0 blocks

 ==5730==still reachable: 1,250 bytes in 40 blocks

 ==5730== suppressed: 0 bytes in 0 blocks

 ==5730== Reachable blocks (those to which a pointer was found) are not
 shown.

 ==5730== To see them, rerun with: --leak-check=full --show-leak-kinds=all
 ==5730== ==5730== For counts of detected and suppressed errors, rerun with:

 -v ==5730== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 45 from
 10)”



 rgds



 *From:* Hanh Le Bich [mailto:hanhmi...@gmail.com hanhmi...@gmail.com]
 *Sent:* Wednesday, May 7, 2014 10:32 AM
 *To:* Rene Kluwen
 *Cc:* hbil...@ecommunicate.biz; af...@list.fink.org; devel@kannel.org
 *Subject:* Re: Does opensmppbox and smsbox have serious memory issues?



 No Rene, i just monitor by some mem check tool. For example, htop tell me
 in the fist day, opensmppbox occupied 0.1% of RAM, the next 2 day is was
 0.2%, and the 5th day, it is 0.3% now. Slowly increase.



 Regards, Hanh.



 On Wed, May 7, 2014 at 3:09 PM, Rene Kluwen rene.klu...@chimit.nl wrote:

 Would you happen to have a valgrind output for this?



 == Rene



 *From:* Hanh Le Bich [mailto:hanhmi...@gmail.com]
 *Sent:* woensdag 7 mei 2014 9:20
 *To:* hbil...@ecommunicate.biz
 *Cc:* Rene Kluwen; af...@list.fink.org; devel@kannel.org


 *Subject:* Re: Does opensmppbox and smsbox have serious memory issues?



 Hello again,

 Hope you are doing great.
 After close monitoring opensmppbox after  4 days continuous running, I
 just want to inform the mem leak still happen, the box is eating few tens
 (or nearly hundred) byte per day at throughput 100TPS (at max) and keep
 increasing.

 Regards, Hanh.



==5730== Memcheck, a memory error detector
==5730== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==5730== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info
==5730== Command: /usr/local/sbin/smsbox -v -d -- /etc/kannel/kannel.conf
==5730== Parent PID: 5728
==5730== 
==5730== 
==5730== HEAP SUMMARY:
==5730== in use at exit: 377,720 bytes in 28,999 blocks
==5730==   total heap usage: 2,999,707 allocs, 2,970,708 frees, 399,074,706 
bytes allocated
==5730== 
==5730== 376,470 (231,680 direct, 144,790 indirect) bytes in 14,480 blocks are 
definitely lost in loss record 42 of 42
==5730==at 0x4027434: malloc (vg_replace_malloc.c:291)
==5730==by 0x8081BD3: gw_native_malloc (gwmem-native.c:87)
==5730

Re: Does opensmppbox and smsbox have serious memory issues?

[Hanh Le Bich]

Hello again,
Hope you are doing great.
After close monitoring opensmppbox after  4 days continuous running, I
just want to inform the mem leak still happen, the box is eating few tens
(or nearly hundred) byte per day at throughput 100TPS (at max) and keep
increasing.

Regards, Hanh.

Re: Does opensmppbox and smsbox have serious memory issues?

[Hanh Le Bich]

No Rene, i just monitor by some mem check tool. For example, htop tell me
in the fist day, opensmppbox occupied 0.1% of RAM, the next 2 day is was
0.2%, and the 5th day, it is 0.3% now. Slowly increase.

Regards, Hanh.

On Wed, May 7, 2014 at 3:09 PM, Rene Kluwen rene.klu...@chimit.nl wrote:

 Would you happen to have a valgrind output for this?



 == Rene



 *From:* Hanh Le Bich [mailto:hanhmi...@gmail.com]
 *Sent:* woensdag 7 mei 2014 9:20
 *To:* hbil...@ecommunicate.biz
 *Cc:* Rene Kluwen; af...@list.fink.org; devel@kannel.org

 *Subject:* Re: Does opensmppbox and smsbox have serious memory issues?



 Hello again,

 Hope you are doing great.
 After close monitoring opensmppbox after  4 days continuous running, I
 just want to inform the mem leak still happen, the box is eating few tens
 (or nearly hundred) byte per day at throughput 100TPS (at max) and keep
 increasing.

 Regards, Hanh.

Re: Does opensmppbox and smsbox have serious memory issues?

[Hanh Le Bich]

Hello again,
Here is valgrind report for the smsbox memory leaking. This is also the
latest kannel revision 5089.
For me, it still happen, i submit (broadcast) million SMS(s) per day within
few hours at 1000 TPS of throughput. Thus each day, smsbox swallow ~ 400MB
RAM and not release until server memory exhaust after few days. At this
time, the box is auto restarted and i have my memory back, so on, again and
again.

I not sure, but in very low throughput system, i am not aware this issue.

==5730== LEAK SUMMARY:
==5730==definitely lost: 231,680 bytes in 14,480 blocks
==5730==indirectly lost: 144,790 bytes in 14,479 blocks
==5730==  possibly lost: 0 bytes in 0 blocks
==5730==still reachable: 1,250 bytes in 40 blocks
==5730== suppressed: 0 bytes in 0 blocks
==5730== Reachable blocks (those to which a pointer was found) are not shown.
==5730== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==5730==
==5730== For counts of detected and suppressed errors, rerun with: -v
==5730== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 45 from 10)


Please find the report in the attached also this link:
https://www.dropbox.com/s/yjrc6wmdm0rwonz/smsbox_memleakcheck_20140503.txt

Regards, Hanh.

On Fri, May 2, 2014 at 9:33 PM, hbil...@ecommunicate.biz wrote:

 Hi Hand,



 Did you see the latest change by Rene committed to SVN  (
 http://www.kannel.org/pipermail/devel/2014-April/005612.html)

 Does it fix the memory issue you reported?



 rgds




 

 Kind Regards



 Hillel Bilman

 Manager eCommunicate

 mailto: hbil...@ecommunicate.co.za

 Cell: 083-232

 Landline: 011-443-6164

 Fax: 088-011-443-6164



 Social Media marketing campaigns (Facebook, Google+, Twitter, LinkedIn
 etc)  –  Interactive Websites - .mobi Sites – Mobile Apps(Android, iPhone,
 Blackberry, Nokia) -  Premium Rated SMSs and short codes - SMS competitions
 and campaigns – Lead Generation - opt-in subscription Billing – MMS
 campaigns - USSD campaigns - WAP - Outlook SMS – Bulk SMS and Bulk Email –
 Email 2 SMS 2 Email - Developer Kit for Mobile Services integration - Voice
 Over IP services



 *From:* Hanh Le Bich [mailto:hanhmi...@gmail.com]
 *Sent:* 29 April 2014 12:25 PM
 *To:* Alexander Malysh
 *Cc:* hbil...@ecommunicate.biz; devel@kannel.org
 *Subject:* Re: Does opensmppbox and smsbox have serious memory issues?



 It's happy to get it now. Thank a lot.

 Regards,
 Tuan.



 On Tue, Apr 29, 2014 at 4:02 PM, Alexander Malysh amal...@kannel.org
 wrote:

 Hi,



 just checked daily snapshot, yes you can use it, this is uptodate.



 Alex



 Am 29.04.2014 um 04:44 schrieb Hanh Le Bich hanhmi...@gmail.com:



 Dear hbilman  development team,

 I'm willing to help to provide more evident but i have no background to
 work in IT fields.

 Cause my server has no internet connection thus i cannot get the lastest
 SVN trunk. Normally i download source files via the daily snapshot, is it
 ok?

 Regards, Hanh.



 On Mon, Apr 28, 2014 at 12:25 AM, hbil...@ecommunicate.biz wrote:

 Hi Kannel developers,

 Hanh posted his Valgrind research to the user group for smsbox and
 opensmppbox.  His results seem interesting and so I'm copying them to this
 thread so the Kannel developers can view them.
 These results can be viewed by following the thread on Wed, Apr 23, 2014 at
 3:41 AM, by Hanh Le Bich hanhmi...@gmail.com with the Subject: Re: 2
 Questions re Redis/Debian. (The email subject is not related to this
 issue.)

 His research shows that opensmppbox and smsbox may have serious memory
 issues.
 I use the word may as until others have confirmed his results, there
 could
 be a mistake somewhere.
 Is there anyone who has a test environment that can follow his approach and
 confirm for the Kannel community if opensmppbox and smsbox have serious
 memory issues or if his testing approach has flaws?

 His approach is:
  Let me describe a little bit for my application back end. It's  pretty
  simple: i make a loop that for each second, it push an sms via kannel
  CGI for 1K mobile numbers, that mean throughput is 1000 msg/sec.
  My kannel configuration is simple too, it's only smsbox - bearerbox
  - SMSC (via smpp), no file storage, no SQL, no dlr (actually
 dlr-mask=8).
   I even don't expect the sms can deliver  to all end users and the app
 run some hours per day only. That why i
  can play with the lasted SVN which don't care so much for the
 reliability.

 For smsbox:
 In the pass when using ver 1.4.3, it was fine for years. After
  upgrade to 1.5.0, after each few days, i realized smsbox is reset,
  then i found it exhaust my memory. It's funny that smsbox consume the
  mem and doesn't release. Example, if it occupies 50% your mem and you
  stop sms pushing, it will 50% forever except the box restarting.
  That's all, same server with no other tasks, same back end

Re: Does opensmppbox and smsbox have serious memory issues?

[Hanh Le Bich]

It's happy to get it now. Thank a lot.

Regards,
Tuan.


On Tue, Apr 29, 2014 at 4:02 PM, Alexander Malysh amal...@kannel.orgwrote:

 Hi,

 just checked daily snapshot, yes you can use it, this is uptodate.

 Alex

 Am 29.04.2014 um 04:44 schrieb Hanh Le Bich hanhmi...@gmail.com:

 Dear hbilman  development team,
 I'm willing to help to provide more evident but i have no background to
 work in IT fields.
 Cause my server has no internet connection thus i cannot get the lastest
 SVN trunk. Normally i download source files via the daily snapshot, is it
 ok?

 Regards, Hanh.


 On Mon, Apr 28, 2014 at 12:25 AM, hbil...@ecommunicate.biz wrote:

 Hi Kannel developers,

 Hanh posted his Valgrind research to the user group for smsbox and
 opensmppbox.  His results seem interesting and so I'm copying them to this
 thread so the Kannel developers can view them.
 These results can be viewed by following the thread on Wed, Apr 23, 2014
 at
 3:41 AM, by Hanh Le Bich hanhmi...@gmail.com with the Subject: Re: 2
 Questions re Redis/Debian. (The email subject is not related to this
 issue.)

 His research shows that opensmppbox and smsbox may have serious memory
 issues.
 I use the word may as until others have confirmed his results, there
 could
 be a mistake somewhere.
 Is there anyone who has a test environment that can follow his approach
 and
 confirm for the Kannel community if opensmppbox and smsbox have serious
 memory issues or if his testing approach has flaws?

 His approach is:
  Let me describe a little bit for my application back end. It's  pretty
  simple: i make a loop that for each second, it push an sms via kannel
  CGI for 1K mobile numbers, that mean throughput is 1000 msg/sec.
  My kannel configuration is simple too, it's only smsbox - bearerbox
  - SMSC (via smpp), no file storage, no SQL, no dlr (actually
 dlr-mask=8).
   I even don't expect the sms can deliver  to all end users and the app
 run some hours per day only. That why i
  can play with the lasted SVN which don't care so much for the
 reliability.

 For smsbox:
 In the pass when using ver 1.4.3, it was fine for years. After
  upgrade to 1.5.0, after each few days, i realized smsbox is reset,
  then i found it exhaust my memory. It's funny that smsbox consume the
  mem and doesn't release. Example, if it occupies 50% your mem and you
  stop sms pushing, it will 50% forever except the box restarting.
  That's all, same server with no other tasks, same back end, just
  different kannel version.
 
  Just paste the valgrind sum in here:
 
  ==27581== LEAK SUMMARY:
  ==27581==definitely lost: 1,077,904 bytes in 67,369 blocks
  ==27581==indirectly lost: 673,660 bytes in 67,366 blocks
  ==27581==  possibly lost: 160 bytes in 13 blocks
  ==27581==still reachable: 1,240 bytes in 39 blocks
  ==27581== suppressed: 0 bytes in 0 blocks
  ==27581== Reachable blocks (those to which a pointer was found) are
  not shown.
  ==27581== To see them, rerun with: --leak-check=full
  --show-leak-kinds=all ==27581== ==27581== For counts of detected and
  suppressed errors, rerun with: -v ==27581== ERROR SUMMARY: 3 errors
  from 3 contexts (suppressed: 45 from 10)

 For opensmppbox
 opensmppbox  drains your memory 10 times faster than smsbox
 ==31087== Memcheck, a memory error detector ==31087== Copyright (C)
 2002-2013, and GNU GPL'd, by Julian Seward et al.
 ==31087== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright
 info
 ==31087== Command: /usr/local/sbin/opensmppbox -v -d --
 /etc/kannel/opensmppbox.conf ==31087== Parent PID: 31085 ==31087==
 ==31087==
 ==31087== HEAP SUMMARY:
 ==31087== in use at exit: 8,163,073 bytes in 36,550 blocks
 ==31087==   total heap usage: 893,827 allocs, 857,277 frees, 295,662,079
 bytes allocated
 ==31087==
 ==31087== 49 (32 direct, 17 indirect) bytes in 2 blocks are definitely
 lost
 in loss record 485 of 813
 ==31087==at 0x4027434: malloc (vg_replace_malloc.c:291)
 ==31087==by 0x80970B3: gw_native_malloc (gwmem-native.c:87)
 ==31087==by 0x80A37A1: octstr_create_from_data_real (octstr.c:263)
 ==31087==by 0x80A3D81: octstr_duplicate_real (octstr.c:377)
 ==31087==by 0x808B106: cfg_get_real (cfg.c:670)
 ==31087==by 0x8052769: main (opensmppbox.c:2291)
 ==31087==
 ==31087== 79 (64 direct, 15 indirect) bytes in 4 blocks are definitely
 lost
 in loss record 529 of 813
 ==31087==at 0x4027434: malloc (vg_replace_malloc.c:291)
 ==31087==by 0x80970B3: gw_native_malloc (gwmem-native.c:87)
 ==31087==by 0x80A37A1: octstr_create_from_data_real (octstr.c:263)
 ==31087==by 0x80A3D81: octstr_duplicate_real (octstr.c:377)
 ==31087==by 0x805D52F: msg_duplicate (msg-decl.h:80)
 ==31087==by 0x805651D: catenate_msg (opensmppbox.c:525)
 ==31087==by 0x805686B: check_multipart (opensmppbox.c:1481)
 ==31087==by 0x8057AD8: smpp_to_bearerbox (opensmppbox.c:1639)
 ==31087==by 0x80983AE: new_thread (gwthread-pthread.c:385)
 ==31087==by 0x46F9C38

Re: Does opensmppbox and smsbox have serious memory issues?

[Hanh Le Bich]

Dear hbilman  development team,
I'm willing to help to provide more evident but i have no background to
work in IT fields.
Cause my server has no internet connection thus i cannot get the lastest
SVN trunk. Normally i download source files via the daily snapshot, is it
ok?

Regards, Hanh.


On Mon, Apr 28, 2014 at 12:25 AM, hbil...@ecommunicate.biz wrote:

 Hi Kannel developers,

 Hanh posted his Valgrind research to the user group for smsbox and
 opensmppbox.  His results seem interesting and so I'm copying them to this
 thread so the Kannel developers can view them.
 These results can be viewed by following the thread on Wed, Apr 23, 2014 at
 3:41 AM, by Hanh Le Bich hanhmi...@gmail.com with the Subject: Re: 2
 Questions re Redis/Debian. (The email subject is not related to this
 issue.)

 His research shows that opensmppbox and smsbox may have serious memory
 issues.
 I use the word may as until others have confirmed his results, there
 could
 be a mistake somewhere.
 Is there anyone who has a test environment that can follow his approach and
 confirm for the Kannel community if opensmppbox and smsbox have serious
 memory issues or if his testing approach has flaws?

 His approach is:
  Let me describe a little bit for my application back end. It's  pretty
  simple: i make a loop that for each second, it push an sms via kannel
  CGI for 1K mobile numbers, that mean throughput is 1000 msg/sec.
  My kannel configuration is simple too, it's only smsbox - bearerbox
  - SMSC (via smpp), no file storage, no SQL, no dlr (actually
 dlr-mask=8).
   I even don't expect the sms can deliver  to all end users and the app
 run some hours per day only. That why i
  can play with the lasted SVN which don't care so much for the
 reliability.

 For smsbox:
 In the pass when using ver 1.4.3, it was fine for years. After
  upgrade to 1.5.0, after each few days, i realized smsbox is reset,
  then i found it exhaust my memory. It's funny that smsbox consume the
  mem and doesn't release. Example, if it occupies 50% your mem and you
  stop sms pushing, it will 50% forever except the box restarting.
  That's all, same server with no other tasks, same back end, just
  different kannel version.
 
  Just paste the valgrind sum in here:
 
  ==27581== LEAK SUMMARY:
  ==27581==definitely lost: 1,077,904 bytes in 67,369 blocks
  ==27581==indirectly lost: 673,660 bytes in 67,366 blocks
  ==27581==  possibly lost: 160 bytes in 13 blocks
  ==27581==still reachable: 1,240 bytes in 39 blocks
  ==27581== suppressed: 0 bytes in 0 blocks
  ==27581== Reachable blocks (those to which a pointer was found) are
  not shown.
  ==27581== To see them, rerun with: --leak-check=full
  --show-leak-kinds=all ==27581== ==27581== For counts of detected and
  suppressed errors, rerun with: -v ==27581== ERROR SUMMARY: 3 errors
  from 3 contexts (suppressed: 45 from 10)

 For opensmppbox
 opensmppbox  drains your memory 10 times faster than smsbox
 ==31087== Memcheck, a memory error detector ==31087== Copyright (C)
 2002-2013, and GNU GPL'd, by Julian Seward et al.
 ==31087== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info
 ==31087== Command: /usr/local/sbin/opensmppbox -v -d --
 /etc/kannel/opensmppbox.conf ==31087== Parent PID: 31085 ==31087==
 ==31087==
 ==31087== HEAP SUMMARY:
 ==31087== in use at exit: 8,163,073 bytes in 36,550 blocks
 ==31087==   total heap usage: 893,827 allocs, 857,277 frees, 295,662,079
 bytes allocated
 ==31087==
 ==31087== 49 (32 direct, 17 indirect) bytes in 2 blocks are definitely lost
 in loss record 485 of 813
 ==31087==at 0x4027434: malloc (vg_replace_malloc.c:291)
 ==31087==by 0x80970B3: gw_native_malloc (gwmem-native.c:87)
 ==31087==by 0x80A37A1: octstr_create_from_data_real (octstr.c:263)
 ==31087==by 0x80A3D81: octstr_duplicate_real (octstr.c:377)
 ==31087==by 0x808B106: cfg_get_real (cfg.c:670)
 ==31087==by 0x8052769: main (opensmppbox.c:2291)
 ==31087==
 ==31087== 79 (64 direct, 15 indirect) bytes in 4 blocks are definitely lost
 in loss record 529 of 813
 ==31087==at 0x4027434: malloc (vg_replace_malloc.c:291)
 ==31087==by 0x80970B3: gw_native_malloc (gwmem-native.c:87)
 ==31087==by 0x80A37A1: octstr_create_from_data_real (octstr.c:263)
 ==31087==by 0x80A3D81: octstr_duplicate_real (octstr.c:377)
 ==31087==by 0x805D52F: msg_duplicate (msg-decl.h:80)
 ==31087==by 0x805651D: catenate_msg (opensmppbox.c:525)
 ==31087==by 0x805686B: check_multipart (opensmppbox.c:1481)
 ==31087==by 0x8057AD8: smpp_to_bearerbox (opensmppbox.c:1639)
 ==31087==by 0x80983AE: new_thread (gwthread-pthread.c:385)
 ==31087==by 0x46F9C38: start_thread (pthread_create.c:304)
 ==31087==by 0x482F78D: clone (clone.S:130)
 ==31087==
 ==31087== 100 (80 direct, 20 indirect) bytes in 5 blocks are definitely
 lost
 in loss record 577 of 813
 ==31087==at 0x4027434: malloc (vg_replace_malloc.c:291)
 ==31087==by 0x80970B3: gw_native_malloc