Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: "getaddrinfo() thread failed to start" under heavy load
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Matt Toschlog via curl-library <curl-library_at_lists.haxx.se>
Date: Tue, 17 Oct 2023 14:49:22 -0400
Yep, it was the limit on file descriptors. Thanks!
On 10/16/2023 18:24, Henrik Holst wrote:
> could be the limit of number of descriptors :
> https://linuxhint.com/increase-open-file-limit-ubuntu/
>
> looked briefly at the code and unfortunately there are no error stack
> so there is really no way of really knowing why the call failed, it
> can be from fails to do malloc but that rarely happens on Linux even
> if there is no memory, but it also creates two sockets per call so
> that made me think of the opel files / descriptors limit.
>
> /HH
>
> Den tis 17 okt. 2023 kl 00:17 skrev Matt Toschlog via curl-library
> <curl-library_at_lists.haxx.se>:
>
> I'm using libcurl in a voice server app running on Ubuntu 20.04 on an
> Amazon AWS EC2 instance. When I get around 500 users on the system I
> start getting the error "getaddrinfo() thread failed to start" in my
> curl_easy_perform() calls.
>
> Memory doesn't seem to be an issue -- I'm not going above 15%
> utilization. Perhaps there's a Linux limitation (number of
> threads, for
> example) that I'm running up against but I haven't found it.
>
> I'm building with curl 7.68.0, which as far as I can tell is the most
> recent version for the system I'm running on.
>
> Any ideas?
>
> Thanks.
>
> --
> Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
> Etiquette: https://curl.se/mail/etiquette.html
>
Date: Tue, 17 Oct 2023 14:49:22 -0400
Yep, it was the limit on file descriptors. Thanks!
On 10/16/2023 18:24, Henrik Holst wrote:
> could be the limit of number of descriptors :
> https://linuxhint.com/increase-open-file-limit-ubuntu/
>
> looked briefly at the code and unfortunately there are no error stack
> so there is really no way of really knowing why the call failed, it
> can be from fails to do malloc but that rarely happens on Linux even
> if there is no memory, but it also creates two sockets per call so
> that made me think of the opel files / descriptors limit.
>
> /HH
>
> Den tis 17 okt. 2023 kl 00:17 skrev Matt Toschlog via curl-library
> <curl-library_at_lists.haxx.se>:
>
> I'm using libcurl in a voice server app running on Ubuntu 20.04 on an
> Amazon AWS EC2 instance. When I get around 500 users on the system I
> start getting the error "getaddrinfo() thread failed to start" in my
> curl_easy_perform() calls.
>
> Memory doesn't seem to be an issue -- I'm not going above 15%
> utilization. Perhaps there's a Linux limitation (number of
> threads, for
> example) that I'm running up against but I haven't found it.
>
> I'm building with curl 7.68.0, which as far as I can tell is the most
> recent version for the system I'm running on.
>
> Any ideas?
>
> Thanks.
>
> --
> Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
> Etiquette: https://curl.se/mail/etiquette.html
>
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2023-10-17