Hi Giovanni,
I'm glad it's fixed. The patch was pushed in 5.0 branch after the latest
release (5.0.4, Oct 25th 2017), so it should be available as soon as 5.0.5
will be released (I think soon).
Best Regards,
Giacomo
On 20 November 2017 at 15:12, gmele wrote:
> Hi,
>
>
Hi,
I recompiled the http_async_client instead of using the one provided in the
rpm repository: all is working fine!
I think we can close the topic!
Do do know where we can find rpm with the latest 5.0.4 release?
Regards
Giovanni
--
Sent from:
Hello Giacomo,
I installed latest rpm found on
http://download.opensuse.org/repositories/home:/kamailio:/v5.0.x-rpms/CentOS_7/x86_64/.
Build date is Nov 16.
I also installed curl version 7.52.1.
After the installation, I started to test the https connection and still get
the same problem with
Hi Giovanni,
This is what I've done, on the same CentOS 7.4.1708 (and libcurl
7.56.1-1.0.cf.rhel7) machine referred to in this thread.
- Checked out 071b85f66cabaa3a705a014b26b7c1eb31029b26 from branch 5.0
(which is the last one before Aug 18th).
- Used the latest http_async_client module
- make
Hello Giacomo,
any news on this topic? Are you waiting something from me?
Thx
Giovanni
--
Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
Hello,
I reduced the number of kamailio children to 1 and found something that may
be interesting:
all requests are processed by 1 principal thread, but time to time, another
thread handle them (why, I don't know as children=1). When this occurs, the
https request ALWAYS fails with error 77.
Hello Giacomo,
here are the requested info:
1) unfortunately, I cannot give you this information as we copied the source
from git branch 5.0, August 18th and put it in our own source control
(Perforce)
2)1-2 requests per seconds seems ok, but as soon rate increases, problem
appears
3) I cannot
OK Giovanni,
then I'd need some more information to try and get to the root cause, like:
- 5.0.2 git hash you've applied the patch on.
- Rate of requests that seem to trigger this behaviour.
- A sample .cfg file I can use to simulate your scenario (you posted one at
the beginning but please see if
Hello Giacomo,
I patched my branch 5.0.2 with your modifications, but the result is the
same: same problem occurs with heavy load and lot of http requests in
parallel. Same error code 77.
I didn't upgrade the version of curl. I will maybe give it a try. Can you
give me the link from where you
Hi Giovanni,
This commit attempts to fix the issue:
https://github.com/kamailio/kamailio/commit/574a11d8c0c20d3d0c058726609df8ed4e5b68dc
Would it be possible to try that branch or patch the module accordingly?
I've tested it on CentOS 7.4.1708 with libcurl 7.56.1-1.0.cf.rhel7 (but I
don't think
Ok, thx!
BTW, do you know if it is possible to build the http_async_client rpm on the
openSUSE download server?
The http_client is present, but not the http_async one
Regards
Giovanni
--
Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html
OK Giovanni,
this is likely to be an issue with the way CURLOPT_CAPATH is set. I'll
submit a fix as soon as possible.
Giacomo
On 3 November 2017 at 09:49, gmele wrote:
> Hello Giacomo,
>
> currently, I don't see these CURL warnings. Here are the logs I get using
> the
Hello Giacomo,
currently, I don't see these CURL warnings. Here are the logs I get using
the verbose mode of Curl.
When it works:
Nov 3 08:41:46 d-wn-sipregistrar-003 kamailio-registrar[18948]: INFO:
http_async_client [http_multi.c:238]: debug_cb(): [cURL] About to connect()
to pusher-service
Hi Giovanni,
what's the related OS and libcurl versions please?
Regards,
Giacomo
On 2 November 2017 at 09:54, gmele wrote:
> Hello,
>
> I'm having strange behavior with the http_async_client module and https
> connections. Our kamailio config use REST interfaces to
Hello,
I'm having strange behavior with the http_async_client module and https
connections. Our kamailio config use REST interfaces to send push to mobile
apps when calls are initiated. We also use a REST interface to register the
client in our push database (and then be able to use the info to
15 matches
Mail list logo