search

JoeDog / siege

Siege is an http load tester and benchmarking utility
GNU General Public License v3.0
5.91k stars 386 forks source link

No route to host / connection timed out #188

Closed Davincible closed 3 years ago

Davincible commented 3 years ago

With siege -c 100 -t 60s "https://example.com" I get:

[error] socket: unable to connect sock.c:282: No route to host
[alert] socket: select and discovered it's not ready sock.c:384: Connection timed out
[alert] socket: read check timed out(30) sock.c:273: Connection timed out

But it does work through the browser or curl

SIEGE 4.0.7
Linux unavailable 5.11.6-1-MANJARO #1 SMP PREEMPT Thu Mar 11 19:05:51 UTC 2021 x86_64 GNU/Linux
JoeDog commented 3 years ago

Can you traceroute to the host?

What happens if you run it with 1 user? How about 5 users?

On Sun, Mar 21, 2021 at 12:14 PM David Brouwer @.***> wrote:

With siege -c 100 -t 60s "https://example.com" I get:

[error] socket: unable to connect sock.c:282: No route to host [alert] socket: select and discovered it's not ready sock.c:384: Connection timed out [alert] socket: read check timed out(30) sock.c:273: Connection timed out

SIEGE 4.0.7 Linux unavailable 5.11.6-1-MANJARO #1 SMP PREEMPT Thu Mar 11 19:05:51 UTC 2021 x86_64 GNU/Linux

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/JoeDog/siege/issues/188, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJRHZVEV7ACLJXQXSGMO4LTEYLNZANCNFSM4ZRWMSNQ .

-- Jeff Fulmer 1-717-799-8226 https://www.joedog.org/ He codes

Davincible commented 3 years ago

I used https://mysite.com/webpage btw, not the empty domain, not sure if that makes a difference.

Traceroute with https gives Name or service not known, just bare domain does work.

I also tried wrk2 -t10 -c100 -d60s -R100 --latency "https://mysite.com/webpage" and that did work

siege -c 1 -t 20s "https://mysite.com/webpage"                                                                        
[error] socket: unable to connect sock.c:282: No route to host
[error] socket: unable to connect sock.c:282: No route to host

{       "transactions":                            0,
        "availability":                         0.00,
        "elapsed_time":                        19.20,
        "data_transferred":                     0.00,
        "response_time":                        0.00,
        "transaction_rate":                     0.00,
        "throughput":                           0.00,
        "concurrency":                          0.00,
        "successful_transactions":                 0,
        "failed_transactions":                     2,
        "longest_transaction":                  0.00,
        "shortest_transaction":                 0.00
}

It looks like some dependency is missing, but I'm not sure what. Just installed it with pacman

JoeDog commented 3 years ago

add --debug to your command line switches.

https won't work if you don't have openssl devel installed

On Sun, Mar 21, 2021 at 12:55 PM David Brouwer @.***> wrote:

I used https://mysite.com/webpage btw, not the empty domain, not sure if that makes a difference.

Traceroute with https gives Name or service not known, just bare domain does work.

I also tried wrk2 -t10 -c100 -d60s -R100 --latency " https://mysite.com/webpage" and that did work

siege -c 1 -t 20s "https://mysite.com/webpage" [error] socket: unable to connect sock.c:282: No route to host [error] socket: unable to connect sock.c:282: No route to host

{ "transactions": 0, "availability": 0.00, "elapsed_time": 19.20, "data_transferred": 0.00, "response_time": 0.00, "transaction_rate": 0.00, "throughput": 0.00, "concurrency": 0.00, "successful_transactions": 0, "failed_transactions": 2, "longest_transaction": 0.00, "shortest_transaction": 0.00 }

It looks like some dependency is missing, but I'm not sure what. Just installed it with pacman

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JoeDog/siege/issues/188#issuecomment-803621615, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJRHZRBY2PB6GRLWI5K7X3TEYQJFANCNFSM4ZRWMSNQ .

-- Jeff Fulmer 1-717-799-8226 https://www.joedog.org/ He codes

Davincible commented 3 years ago

siege --debug -c1 -t20s doesn't show anything extra compared to the regular one, also doesn't show up in the man page.

Hm that could be it, there doesn't seem to be an openssl-devel package on Arch, only a regular openssl

JoeDog commented 3 years ago

--debug was really just added for me.

Try -c2 -r2 http://www.google.com/ -c2 -r2 https://www.google.com/

See if one works and the other doesn't

On Sun, Mar 21, 2021 at 2:02 PM David Brouwer @.***> wrote:

siege --debug -c1 -t20s doesn't show anything extra compared to the regular one, also doesn't show up in the man page.

Hm that could be it, there doesn't seem to be an openssl-devel package on Arch, only a regular openssl

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JoeDog/siege/issues/188#issuecomment-803632969, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJRHZQ3G36R7C43AD6EZA3TEYYCFANCNFSM4ZRWMSNQ .

-- Jeff Fulmer 1-717-799-8226 https://www.joedog.org/ He codes

Davincible commented 3 years ago

They both seem to work, also tried some other sites which also seem to work. Which then would suggest it's actually something with my site, but then I don't understand why browser/curl/wrk2 do work with my site, but siege doesn't

JoeDog commented 3 years ago

It's especially curious because to reach that point in the code, the socket has to check out.

What happens if you use the IP address instead of the name in the url?

On Mon, Mar 22, 2021 at 8:13 AM David Brouwer @.***> wrote:

They both seem to work, also tried some other sites which also seem to work. Which then would suggest it's actually something with my site, but then I don't understand why browser/curl/wrk2 do work with my site, but siege doesn't

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JoeDog/siege/issues/188#issuecomment-804015831, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJRHZWN5RPAG2ORDPS6XJDTE4X5JANCNFSM4ZRWMSNQ .

-- Jeff Fulmer 1-717-799-8226 https://www.joedog.org/ He codes

Davincible commented 3 years ago

Still get nothing, maybe you can see if you get anything. Website I'm trying to test is https://lookwhosstreaming.com - 37.97.131.71

JoeDog commented 3 years ago

It's weird. My initial transaction took over 3 seconds, each ensuing one was fast. That might be a matter of distance.

Can you try compiling it?

wget http://download.joedog.org/siege/siege-4.0.8.tar.gz gunzip -9cd siege-4.0.8.tar.gz | tar -xvf - cd siege-4.0.8 ./configure make make install

That will put it in /usr/local/bin

You can change the install dir with --prefix, i.e., ./configure --prefix=/home/jdfulmer

On Mon, Mar 22, 2021 at 11:02 AM David Brouwer @.***> wrote:

Still get nothing, maybe you can see if you get anything. Website I'm trying to test is https://lookwhosstreaming.com - 37.97.131.71

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JoeDog/siege/issues/188#issuecomment-804131775, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJRHZXEXTTTRI5PURAMBADTE5LW3ANCNFSM4ZRWMSNQ .

-- Jeff Fulmer 1-717-799-8226 https://www.joedog.org/ He codes

Davincible commented 3 years ago

Still same results :/, other sites work, my site doesn't. Super strange. Are there any other logs I can provide?