Re: memory leaks in opensmppbox
str.c: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, 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, 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 configu
RE: memory leaks in opensmppbox
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, 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
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, 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 > > > >
Re: memory leaks in opensmppbox
please don send this mail to me. On Tue, Jun 10, 2014 at 1:14 AM, 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 = &quo
memory leaks in opensmppbox
Hi Hanh, Now that you and Stipe have confirmed there is currently no memory leak in smsbox, lets 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" -- Regards, Hanh 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
