-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Address resolution failure: What's the URL that failed? #216
Comments
I'm surprised nobody's asked this before. As a quick fix, put this at
sock.c:159 and recompile:
NOTIFY(ERROR, "%s: %s", gai_strerror(res), hn);
NOTE: That's untested. Let me know how it goes and I can add it.
…On Thu, Dec 8, 2022 at 6:36 PM Karim Ratib ***@***.***> wrote:
During a run, I see a consistent number of errors of the form:
[error] Address resolution failed at sock.c:158 with the following error:
[error] Name or service not known
I would like to find out which URLs / domain names caused this error. How
can I do that?
—
Reply to this email directly, view it on GitHub
<#216>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJRHZQQOXKMMMP3SAQJFQLWMJWIZANCNFSM6AAAAAASYWUPH4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
Jeff Fulmer
1-717-799-8226
https://www.joedog.org/
He codes
|
Looks like I need to adjust my build tools for this codebase (Ubuntu 22.04 here) so it might take longer than I would like :-) |
This will make it easier:
https://download.joedog.org/siege/siege-4.1.5.tar.gz
It has the configure script already built
…On Thu, Dec 8, 2022 at 8:19 PM Karim Ratib ***@***.***> wrote:
Looks like I need to adjust my build tools for this codebase (Ubuntu 22.04
here) so it might take longer than I would like :-)
—
Reply to this email directly, view it on GitHub
<#216 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJRHZQIWCH5B4KXBVOGAJLWMKCJVANCNFSM6AAAAAASYWUPH4>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Jeff Fulmer
1-717-799-8226
https://www.joedog.org/
He codes
|
Thanks, I was able to compile this archive. The error is now much clearer:
|
Glad to hear it!
…On Thu, Dec 8, 2022 at 10:09 PM Karim Ratib ***@***.***> wrote:
Thanks, I was able to compile this archive. The error is now much clearer:
[error] Address resolution failed at sock.c:158 with the following error:: Invalid argument
[error] Name or service not known: dev-api-jobboard.workbc.ca: Invalid argument
—
Reply to this email directly, view it on GitHub
<#216 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJRHZX3O4MVATDCKOHANG3WMKPF7ANCNFSM6AAAAAASYWUPH4>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Jeff Fulmer
1-717-799-8226
https://www.joedog.org/
He codes
|
Checking here: are you planning to include this fix in an upcoming release? |
It's in 4.1.6
https://download.joedog.org/siege/
…On Tue, Jan 10, 2023 at 12:20 PM Karim Ratib ***@***.***> wrote:
Checking here: are you planning to include this fix in an upcoming release?
—
Reply to this email directly, view it on GitHub
<#216 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJRHZVGWTP5PC4QQ3UTNJ3WRWK4ZANCNFSM6AAAAAASYWUPH4>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Jeff Fulmer
1-717-799-8226
https://www.joedog.org/
He codes
|
Thanks!! I'll validate then we can close this 🙏 |
You can verify here:
https://github.com/JoeDog/siege/blob/master/src/sock.c
Line 159
…On Tue, Jan 10, 2023 at 12:23 PM Karim Ratib ***@***.***> wrote:
Thanks!! I'll validate then we can close this 🙏
—
Reply to this email directly, view it on GitHub
<#216 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJRHZTMN5NDQBNYX56ANUTWRWLJDANCNFSM6AAAAAASYWUPH4>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Jeff Fulmer
1-717-799-8226
https://www.joedog.org/
He codes
|
Thanks I ran |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
During runs, I see a consistent number of errors of the form:
I would like to find out which URLs / domain names caused this error. How can I do that?
The text was updated successfully, but these errors were encountered: