Hi, I've also had similar problem some time ago when I was sending some bulk of 5.000 msgs. There was sometimes "Broken pipe" error and several problems with some DLRs (PDU unpacking failed). I tried to reproduce this problem but I was not able to get those errors anymore, it was happening one time when there was a huge traffic.
Tomasz. W Twoim liście datowanym 17 sierpnia 2010 (17:09:57) można przeczytać: > Hi, > I kept playing around with the configuration files but still no > luck. Today I tried to send 20 sms to smppbox but my smppbox or kannel kept > stalling again. > My system receives some 6 sms from my client and than it stalls for > 1 minute or so before it continues receiving the rest. Moreover, my client > does not > receive all the deliveries back. It gets some 12 out of 20. I > checked my log files and I noticed several error and warning messages. In my > smppbox.log I > get the following error and warning messages periodically. > DEBUG: SMPP[ESME]: Sending PDU: > DEBUG: SMPP PDU 0x910c7b0 dump: > DEBUG: type_name: bind_receiver_resp > DEBUG: command_id: 2147483649 = 0x80000001 > DEBUG: command_status: 0 = 0x00000000 > DEBUG: sequence_number: 1 = 0x00000001 > DEBUG: system_id: "VMA" > DEBUG: SMPP PDU dump ends. > WARNING: SMPP: PDU NULL terminated string (service_type) has no NULL. > DEBUG: Octet string at 0x910ae28: > DEBUG: len: 12 > DEBUG: size: 13 > DEBUG: immutable: 0 > DEBUG: data: 00 00 00 05 00 00 00 00 00 00 00 02 ............ > DEBUG: Octet string dump ends. > ERROR: smppbox[ESME]: PDU unpacking failed. > DEBUG: smppbox[ESME]: Failed PDU omitted. > ERROR: Invalid SMPP PDU received. > DEBUG: Thread 2 (smppbox.c:smpp_to_bearerbox) terminates. > DEBUG: Started thread 3 (smppbox.c:function) > ERROR: SMPP: Unknown TLV `dlr_err', don't send. > INFO: We received an SMS message. > DEBUG: DLR[internal]: Looking for DLR smsc=ESME, ts=a4517482, > dst=+37494086408, type=1 > WARNING: DLR[internal]: DLR from SMSC<ESME> for DST<+37494086408> not found. > and in my kannel.log I get this message periodically > DEBUG: boxc_sender: sent message to <127.0.0.1> > DEBUG: send_msg: sending msg to boxc: <ESME> > DEBUG: boxc_sender: sent message to <127.0.0.1> > ERROR: Connection to box <127.0.0.1> broke. > EBUG: send_msg: sending msg to boxc: <ESME> > ERROR: Error writing 16 octets to fd 29: > ERROR: System error 32: Broken pipe > ERROR: Couldn't write Msg to box <127.0.0.1>, disconnecting > DEBUG: Thread 19 (gw/bb_boxc.c:boxc_sender) terminates. > ERROR: Error writing 16 octets to fd 29: > ERROR: System error 32: Broken pipe > DEBUG: Thread 18 (gw/bb_boxc.c:function) terminates. > DEBUG: send_msg: sending msg to boxc: <ESME> > DEBUG: boxc_sender: sent message to <127.0.0.1> > DEBUG: send_msg: sending msg to boxc: <ESME> > DEBUG: boxc_sender: sent message to <127.0.0.1> > INFO: Connection closed by the box <127.0.0.1> > DEBUG: send_msg: sending msg to boxc: <ESME> > DEBUG: Thread 17 (gw/bb_boxc.c:boxc_sender) terminates. > WARNING: smsbox_list empty! > Most of all the error about the "Broken pipe" alerts me, I don't > know what that means but it seems to be serious. > I don't know if that can be the reason. > My current configuration is as follows: > **** smskannel.conf ****** > group = core > admin-port = 13000 > smsbox-port = 13001 > admin-password = bar > log-file = "/tmp/kannel.log" > log-level = 0 > box-deny-ip = "*.*.*.*" > box-allow-ip = "127.0.0.1" > include = > "/home/davit/workspace/kannel/gateway-revision-4837/gw/smsbox.conf" > include = > "/home/davit/workspace/kannel/gateway-revision-4837/gw/smsc.conf" > ****************************************** > ******** smsc.conf ************* > group=smsc > smsc=smpp > smsc-id=17 > interface-version=34 > host=*********** > port=***** > system-id=***** > smsc-password=****** > system-type=default > transceiver-mode=1 > ****************************************** > ********* smsbox.conf *************** > group = smsbox > bearerbox-host = 127.0.0.1 > sendsms-port = 13013 > log-level = 0 > group = smsbox-route > smsbox-id = VMA > smsc-id = 17 > ******************************************* > ******** smppbox.conf ******************** > group = core > group = smppbox > # our boxc type > smppbox-id = box1 > # the port to listen on for smpp connections > smppbox-port = 16000 > # we connect to the following host as a box > bearerbox-host = 127.0.0.1 > bearerbox-port = 13001 > log-level = 0 > log-file = smppbox.log > our-system-id = VMA > route-to-smsc = 17 > # see sample smpplogins.txt > smpp-logins = > "/home/davit/workspace/kannel/smppbox-revision-41/gw/smpplogins.txt" > *************************************************** > and my smpplogins.txt > foo bar VMA 245.127.0.0.1 > client-02 password-02 vma 127.0.0.1 > I would really appreciate any help and ideas. I don't know how to tackle this > problem ;) > Cheers, > Davit >> Date: Sat, 14 Aug 2010 21:14:04 +0200 >> Subject: Re: smppbox bulk sms: slow reception from a client >> From: rene.klu...@chimit.nl >> To: davit.mirzo...@hotmail.com >> CC: users@kannel.org >> >> Onlly 10 sms is nothing of course. I wouldn't even call it bulk sms. >> >> Is there anyone else with the same problems? Because if so, it seems a >> serious enough issue to look into. >> >> -- Rene >> >> >> >> >> >> > Dear users, >> > >> > Has anybody tried to send bulk sms from a client via smpp to smppbox? It >> > seems that smppbox or bearerbox accepts bulk sms extremely slowly. My >> > client is not able to inject bulk sms to my smppbox (10 sms or so). Kannel >> > keeps stalling while receiving the messages. I am using a smppbox revision >> > 43 that is connected to a gateway revision 4837. Has anybody come up with >> > such a problem? Any help is appreciated ;). >> > >> > Many thanks, >> > >> > Cheers, >> > Davit >> >