Skip to content
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

Continued timeouts when trying to start project. #225

Open
not-original opened this issue Mar 19, 2024 · 9 comments
Open

Continued timeouts when trying to start project. #225

not-original opened this issue Mar 19, 2024 · 9 comments

Comments

@not-original
Copy link

image

Using Pantheon recipe with Wordpress. I will run Lando Start, and the system runs through and starts docker with no problem. Then it will cycle through the local urls 25 times, finally getting a 10000 MS Exceeded.

If I run lando start again, SOMETIMES, it will finally connect and then I can develop. What can I look at to change this and get it working on the first try?

@pirog pirog transferred this issue from lando/lando Mar 19, 2024
@reynoldsalec
Copy link
Sponsor Member

@not-original if you try navigating to the URL before the healthcheck succeeds, do you get to the site?

@not-original
Copy link
Author

@not-original if you try navigating to the URL before the healthcheck succeeds, do you get to the site?

No, the site doesn't load. After it goes through the checks (25 times), I will wait a sec, then run Lando Start again -- and it usually goes green by the second or third check.

@reynoldsalec
Copy link
Sponsor Member

@not-original do you get an error code back when trying to access the URL while the scanner is failing?

Also curious if you run lando start --debug if you get any further information that appears relevant.

@not-original
Copy link
Author

No error code, just that site cannot be reached and times out.

The --debug info, doesn't add much more: (I only copied for the first 3 attempts)

wpt2 17:40:15 INFO ==> [STARTED] APPSERVER NGINX URLS
wpt2 17:40:15 INFO ==> [STARTED] https://localhost:60281
wpt2 17:40:15 INFO ==> [STARTED] http://localhost:60282
wpt2 17:40:15 INFO ==> [STARTED] http://wpt2.lndo.site/
wpt2 17:40:15 INFO ==> [STARTED] https://wpt2.lndo.site/
wpt2 17:40:19 DEBUG ==> scan of 'https://wpt2.lndo.site//' failed with 500 'Internal Server Error'
wpt2 17:40:19 DEBUG ==> scan of 'https://localhost:60281/' failed with 500 'Internal Server Error'
wpt2 17:40:19 DEBUG ==> scan of 'http://localhost:60282/' failed with 500 'Internal Server Error'
wpt2 17:40:19 DEBUG ==> scan of 'http://wpt2.lndo.site//' failed with 500 'Internal Server Error'
wpt2 17:40:20 INFO ==> [RETRY] https://wpt2.lndo.site/ [500] [1]
wpt2 17:40:20 INFO ==> [FAILED] Request failed with status code 500
wpt2 17:40:20 INFO ==> [RETRY] https://localhost:60281 [500] [1]
wpt2 17:40:20 INFO ==> [FAILED] Request failed with status code 500
wpt2 17:40:20 INFO ==> [RETRY] http://localhost:60282 [500] [1]
wpt2 17:40:20 INFO ==> [FAILED] Request failed with status code 500
wpt2 17:40:20 INFO ==> [RETRY] http://wpt2.lndo.site/ [500] [1]
wpt2 17:40:20 INFO ==> [FAILED] Request failed with status code 500
wpt2 17:40:30 DEBUG ==> scan of 'http://localhost:60282/' failed with 'TIMEOUT' 'unknown'
wpt2 17:40:30 DEBUG ==> scan of 'http://wpt2.lndo.site//' failed with 'TIMEOUT' 'unknown'
wpt2 17:40:30 DEBUG ==> scan of 'https://localhost:60281/' failed with 'TIMEOUT' 'unknown'
wpt2 17:40:30 DEBUG ==> scan of 'https://wpt2.lndo.site//' failed with 'TIMEOUT' 'unknown'
wpt2 17:40:31 INFO ==> [RETRY] http://localhost:60282 1/25 [TIMEOUT] [2]
wpt2 17:40:31 INFO ==> [FAILED] timeout of 10000ms exceeded
wpt2 17:40:31 INFO ==> [RETRY] http://wpt2.lndo.site/ 1/25 [TIMEOUT] [2]
wpt2 17:40:31 INFO ==> [FAILED] timeout of 10000ms exceeded
wpt2 17:40:31 INFO ==> [RETRY] https://localhost:60281 1/25 [TIMEOUT] [2]
wpt2 17:40:31 INFO ==> [FAILED] timeout of 10000ms exceeded
wpt2 17:40:31 INFO ==> [RETRY] https://wpt2.lndo.site/ 1/25 [TIMEOUT] [2]
wpt2 17:40:31 INFO ==> [FAILED] timeout of 10000ms exceeded
wpt2 17:40:41 DEBUG ==> scan of 'http://localhost:60282/' failed with 'TIMEOUT' 'unknown'
wpt2 17:41:21 DEBUG ==> scan of 'http://wpt2.lndo.site//' failed with 'TIMEOUT' 'unknown'
wpt2 17:41:21 DEBUG ==> scan of 'https://localhost:60281/' failed with 'TIMEOUT' 'unknown'
wpt2 17:41:21 DEBUG ==> scan of 'https://wpt2.lndo.site//' failed with 'TIMEOUT' 'unknown'
wpt2 17:41:22 INFO ==> [RETRY] http://localhost:60282 2/25 [TIMEOUT] [3]
wpt2 17:41:22 INFO ==> [FAILED] timeout of 10000ms exceeded
wpt2 17:41:22 INFO ==> [RETRY] http://wpt2.lndo.site/ 2/25 [TIMEOUT] [3]
wpt2 17:41:22 INFO ==> [FAILED] timeout of 10000ms exceeded
wpt2 17:41:22 INFO ==> [RETRY] https://localhost:60281 2/25 [TIMEOUT] [3]
wpt2 17:41:22 INFO ==> [FAILED] timeout of 10000ms exceeded
wpt2 17:41:22 INFO ==> [RETRY] https://wpt2.lndo.site/ 2/25 [TIMEOUT] [3]
wpt2 17:41:22 INFO ==> [FAILED] timeout of 10000ms exceeded

@reynoldsalec
Copy link
Sponsor Member

If you run lando logs do you see any additional output that seems related? Sometimes I like to look at the logs via Docker Desktop as well.

This sounds a bit like it could be some sort of weird app fatal, but that should show up in lando logs -s appserver

Could help to see your .lando.yml as well just to make sure there isn't anything special.

@reynoldsalec
Copy link
Sponsor Member

And if you haven't tried it already, the tried-and-true lando rebuild is always a good first-stop in weird problems, and of course you can always do the nuclear option: https://docs.lando.dev/help/purging-containers.html

@not-original
Copy link
Author

Could help to see your .lando.yml as well just to make sure there isn't anything special.

YML is pretty straight forward:

name: wpt2
recipe: pantheon
config:
framework: wordpress
site: wpt2
id: dd9b8b45-35a0-4ed2-b5a1-332fd7b56eba
edge: true

@not-original
Copy link
Author

And if you haven't tried it already, the tried-and-true lando rebuild is always a good first-stop in weird problems, and of course you can always do the nuclear option: https://docs.lando.dev/help/purging-containers.html

Tried the rebuild, but still no joy. Still have to wait for the timeouts.

@reynoldsalec
Copy link
Sponsor Member

Might be worth disabling edge as well (edge: false) to see if that gives you any joy.

Did those other lando log suggestions I gave you yield anything interesting? #225 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants