Hi Alexander, Thank you for the tip!
I've found the following errors: 2020-05-20 23:28:50 [52975] [10] ERROR: Couldn't create new socket. 2020-05-20 23:28:50 [52975] [10] ERROR: System error 24: Too many open files 2020-05-20 23:28:50 [52975] [10] ERROR: error connecting to server `dlrreceiver_ip' at port `dlrreceiver_port' 2020-05-20 23:28:50 [52975] [10] ERROR: Couldn't send request to <http://dlrreceiver_ip:dlrreceiver_port/receive-dlr?type=8&mtMsgId=XXXXXXXXX&reply=ACK%2F&error=&dispatchId=XXXXXXX&meta=×tamp=XXXXXXX&sendMtUsername=aUsername> I'll check what's needed to increase the limit of open files. Kind regards, Paulo Correia Head of Development telephone:+351210337760 fax: +351210337761 email: paulo.corr...@go4mobility.com<mailto:paulo.corr...@go4mobility.com> skype: pcorreia.g4m [cid:41dd4998-4570-4e42-b57d-85b304fa79e0]<https://go4mobility.com/en> [assinatura_email_go4mobility_followus]<https://www.linkedin.com/company/go4mobility/> _____________________________________________________________________________________________ CONFIDENTIALITY This message, as well as existing attached files, may be confidential and privileged. Use or disclosure by anyone other than an intended recipient is not authorised. If you have received this message by error, you are kindly requested to delete it and notify the sender. Thank you for your cooperation. ________________________________ From: Alexander Malysh <malys...@gmail.com> on behalf of Alexander Malysh <amal...@kannel.org> Sent: 22 May 2020 15:38 To: Paulo Correia <paulo.corr...@go4mobility.com> Cc: users@kannel.org <users@kannel.org> Subject: Re: Unable to deliver DLRs: "Couldn't fetch..." Hi, do you have any errors except couldn’t fetch? mostly it’s because either kannel ran out of filedexfriptors or because receiving server is unable to accept that much connections from kannel (or both). Check you kannel log file for other errors. Thanks, Alex Am 21.05.2020 um 14:35 schrieb Paulo Correia <paulo.corr...@go4mobility.com<mailto:paulo.corr...@go4mobility.com>>: Hi fellow kannel users, We've been using kannel for quite some years and on the latest months we've seen an issue when processing DLRs on high traffic. We send the messages to kannel using HTTP with the /cgi-bin/sendsms adding the dlr-url and dlr-mask values as always have been sending. When kannel receives a DLR, it'll then send us an HTTP notification using the previously defined dlr-url for that message, assuming the dlr-mask matches the status. When the traffic is high, we normally get the following on our smsbox logs: 2020-05-21 00:02:58 [47847] [9] ERROR: Couldn't fetch <http://dlrreceiver_ip:dlrreceiver_port/receive-dlr?type=8&mtMsgId=XXXXXXXXX&reply=ACK%2F&error=&dispatchId=XXXXXXX&meta=×tamp=XXXXXXX&sendMtUsername=aUsername> We then have to parse the logs to obtain these "lost" DLRs and reprocess them. My questions: * Has anyone seen this behaviour? * Any hints how to solve it? * What can cause this issue? * Failure of processing on the dlrreceiver_ip:dlrreceiver_port ? * Timeout on dlrreceiver_ip:dlrreceiver_port ? * Could there be another way to send the DLRs instead of HTTP? * Could they be stored in SQL? * We even created a HAProxy to receive the requests and route them to the server, and in case of an issue, reroute them to an application that stores the "missed dlr" into the DB, but still doesn't cut it. Thanks in advance! Kind regards, Paulo Correia Head of Development telephone:+351210337760 fax: +351210337761 email: paulo.corr...@go4mobility.com<mailto:paulo.corr...@go4mobility.com> skype: pcorreia.g4m <Outlook-ef2t2cv0.png><https://go4mobility.com/en> [assinatura_email_go4mobility_followus]<https://www.linkedin.com/company/go4mobility/> _____________________________________________________________________________________________ CONFIDENTIALITY This message, as well as existing attached files, may be confidential and privileged. Use or disclosure by anyone other than an intended recipient is not authorised. If you have received this message by error, you are kindly requested to delete it and notify the sender. Thank you for your cooperation.
