Hi Nikos, I tried to explain it before (maybe my English knowledge...). We have an smsc which can only accept 10-15 SMs per sec but we have batch SMs which are sent in the morning. So We send 40k SMs in the morning to kannel. Kannel keeps them in its queue until it can send them to smsc. While kannel sending SMs to the smsc there is no reply. Once there is no SM in the queue DLRs flood us because at that time on smsc side there is more than 40k DLR is waiting to be sent. We are connected through the Internet so we have bandwidth to get not just 15 DLR/sec but about 10k. So that's why we get so many SMs at once. I've red again my initial message but there is a mistake in it sorry for that: the smsc which has this kind of behaviour is not emi type but cimd2. We do have emi type smsc too but on this kind of smsc there is no problem like I mentioned before because at this connection we always get delivery even the queue is full (not just at the end when every messages are sent to smsc).
Bye, Gabor Nikos Balkanas wrote: > > Why are you getting 10000 dlrs/sec when you onl;y have peak 25 SMS/sec? > Something seems wrong here. > > BR, > Nikos > ----- Original Message ----- > From: "Nikos Balkanas" <nbalka...@gmail.com> > To: "Gabor Maros" <gabor.ma...@erstebank.hu>; <users@kannel.org> > Sent: Thursday, April 01, 2010 8:00 PM > Subject: Re: Too many dlr at once > > > Hi, > > Most people here use lighttpd for dlr web receiver. It is very fast and > should have no problem with this kind of traffic. > > BR, > Nikos > ----- Original Message ----- > From: "Gabor Maros" <gabor.ma...@erstebank.hu> > To: <users@kannel.org> > Sent: Thursday, April 01, 2010 6:33 PM > Subject: Re: Too many dlr at once > > > > Thanks Nikos, > > it may help but there is another problem i haven't mentioned before. We > have > a webapplication that receives dlrs from kannel. If kannel gets 10k dlr in > one sec then kannel tries to send all of them in the same sec to the app. > This behaviour kills the app (and the database behind it) because it gets > 10000 http connections in one sec which is quite huge amount according to > our peaktime when there is 25 SMs/sec. > Unfortunately we are not the NASA with unimaginable computing capacity, so > the ideal solution for us would be a parameter that tells kannel how many > connections are allowed in one sec. > > Bye, > Gabor > > > > Nikos Balkanas wrote: >> >> Hi, >> >> Check if you havd /etc/hosts, and if you do you should have specified >> your >> gateway. >> >> Also check if named is running (Linux) >> >> BR, >> Nikos >> ----- Original Message ----- >> From: "Gabor Maros" <gabor.ma...@erstebank.hu> >> To: <users@kannel.org> >> Sent: Thursday, April 01, 2010 12:58 PM >> Subject: Too many dlr at once >> >> >> >> Hi, >> >> I've got a kannel install with emi smsc connection. >> When we send lots of sms to the smsc at once the delivery notifications >> only >> come at the end when kannel's queue is empty. Smsc only accepts 10-15 >> SM/sec >> but can send back horrible amount at once. This is a problem for us >> because >> kannel gets thousands of dlrs in one second and ERROR messages appear in >> smsbox.log: >> >> 2010-04-01 08:21:17 [4834] [4] INFO: Starting delivery report <sms> from >> <0036303444481> >> 2010-04-01 08:21:17 [4834] [4] INFO: Starting delivery report <sms> from >> <0036303444481> >> 2010-04-01 08:21:17 [4834] [4] INFO: Starting delivery report <sms> from >> <0036303444481> >> 2010-04-01 08:21:17 [4834] [4] INFO: Starting delivery report <sms> from >> <0036303444481> >> 2010-04-01 08:21:17 [4834] [4] INFO: Starting delivery report <sms> from >> <0036303444481> >> >> …after thousands of such normal logrecords we can see thousands of >> the >> following: >> >> 2010-04-01 08:21:18 [4834] [9] ERROR: Error while gw_gethostbyname >> occurs. >> 2010-04-01 08:21:18 [4834] [9] ERROR: System error 2: No such file or >> directory >> 2010-04-01 08:21:18 [4834] [9] ERROR: gethostbyname failed >> 2010-04-01 08:21:18 [4834] [9] ERROR: error connecting to server `xxxx' >> at >> port `yyy' >> 2010-04-01 08:21:18 [4834] [9] ERROR: Couldn't send request to >> <https://xyz> >> 2010-04-01 08:21:18 [4834] [9] ERROR: Error while gw_gethostbyname >> occurs. >> 2010-04-01 08:21:18 [4834] [9] ERROR: System error 2: No such file or >> directory >> 2010-04-01 08:21:18 [4834] [9] ERROR: gethostbyname failed >> 2010-04-01 08:21:18 [4834] [9] ERROR: error connecting to server `xxxx' >> at >> port `yyy' >> 2010-04-01 08:21:18 [4834] [9] ERROR: Couldn't send request to >> <https://xyz> >> 2010-04-01 08:21:18 [4834] [9] ERROR: Error while gw_gethostbyname >> occurs. >> 2010-04-01 08:21:18 [4834] [9] ERROR: System error 2: No such file or >> directory >> 2010-04-01 08:21:18 [4834] [9] ERROR: gethostbyname failed >> 2010-04-01 08:21:18 [4834] [9] ERROR: error connecting to server `xxxx' >> at >> port `yyy' >> 2010-04-01 08:21:18 [4834] [9] ERROR: Couldn't send request to >> <https://xyz> >> 2010-04-01 08:21:18 [4834] [9] ERROR: Error while gw_gethostbyname >> occurs. >> 2010-04-01 08:21:18 [4834] [9] ERROR: System error 2: No such file or >> directory >> 2010-04-01 08:21:18 [4834] [9] ERROR: gethostbyname failed >> 2010-04-01 08:21:18 [4834] [9] ERROR: error connecting to server `xxxx' >> at >> port `yyy' >> 2010-04-01 08:21:18 [4834] [9] ERROR: Couldn't send request to >> <https://xyz> >> 2010-04-01 08:21:18 [4834] [9] ERROR: Error while gw_gethostbyname >> occurs. >> 2010-04-01 08:21:18 [4834] [9] ERROR: System error 2: No such file or >> directory >> >> Is there a configuration parameter that change this behavior and we can >> slow it down? >> I don’t know why it is happen but there must be some kind of limit >> (I >> think >> it is not an open file issue but something similar). >> Maybe there is another side effect (but I’m not sure yet) in >> connection >> with >> DLR database because the number of SMs that are not in the end phase >> (delivered or can’t be delivered) are growing. >> >> Thanks, >> Gabor >> >> -- >> View this message in context: >> http://old.nabble.com/Too-many-dlr-at-once-tp28106589p28106589.html >> Sent from the Kannel - User mailing list archive at Nabble.com. >> >> >> >> >> > > -- > View this message in context: > http://old.nabble.com/Too-many-dlr-at-once-tp28106589p28107811.html > Sent from the Kannel - User mailing list archive at Nabble.com. > > > > > > -- View this message in context: http://old.nabble.com/Too-many-dlr-at-once-tp28106589p28111882.html Sent from the Kannel - User mailing list archive at Nabble.com.
