Home
Support Forums

Failed during stage 'building site': Failed to execute deploy: timed out while waiting to enter states [prepared, ready]

Because you’re removing support for the Ubuntu Trusty Image, I’m trying to update my various sites and deploy using Ubuntu Focal.

While several of my very small sites upgraded and deployed without issue, 4 my larger sites are failing to deploy.

I’ve removed details I would prefer to remain private, but here’s a recent failed deploy log for one of the sites in question:

4:07:19 PM: Build ready to start
4:07:21 PM: build-image version: 081db65c3e4ce8423fedb40e7689a87de6f84667
4:07:21 PM: build-image tag: v4.3.1
4:07:21 PM: buildbot version: a7ed393d7802bf453be684c29d76700ec4b7cbba
4:07:21 PM: Fetching cached dependencies
4:07:21 PM: Failed to fetch cache, continuing with build
4:07:21 PM: Starting to prepare the repo for build
4:07:22 PM: No cached dependencies found. Cloning fresh repo
4:07:22 PM: git clone git@bitbucket.org:xxx/xxx
4:07:33 PM: Preparing Git Reference refs/heads/master
4:07:34 PM: Parsing package.json dependencies
4:07:35 PM: No build steps found, continuing to publishing
4:07:35 PM: Starting to deploy site from ‘/’
4:07:36 PM: Creating deploy tree asynchronously
4:07:36 PM: Creating deploy upload records
4:08:00 PM: Starting post processing
4:08:00 PM: Post processing - HTML
4:12:37 PM: Creating deploy upload records
4:12:37 PM: Failing build: Failed to build site
4:12:37 PM: Failed during stage ‘building site’: Failed to execute deploy: timed out while waiting to enter states [prepared, ready]
4:12:37 PM: Finished processing build request in 5m16.192242471s

Any assissance is greatly appreciated.

BTW, dennis@netlify assisted me back in February 01, 2019 the last time one of these sites had a similar problem deploying.

This is actually unrelated to the upgrade, but we can adjust some timeouts on your sites to fix it. Could you let me know the name of the sites or API ID’s (from the top config card, on each site settings page - these are ok to share publicly!), so I can make the adjustment?

Thank you so much, here are the API IDs:

b1b31fcf-0373-4e3f-ab36-1428cacd6973
cf951426-7be3-44d5-ab1f-7945b1a062cc
9900ddb1-0f43-4745-b003-ab4077ff08a4
36d952e6-7ab0-4168-8262-0c8a8bd2d78b

great, just got those all adjusted. While you cannot “retry” a failed deploy (it will use the old setting), new deploys either from git or from using the trigger deploy button should work better. Please let me know if not!

Shucks, only 1 of the 4 deployed successfully; these 3 didn’t make it past the 10 minute cutoff:

36d952e6-7ab0-4168-8262-0c8a8bd2d78b
b1b31fcf-0373-4e3f-ab36-1428cacd6973
cf951426-7be3-44d5-ab1f-7945b1a062cc

wow - how many files are in those sites? I bumped you up to 20 min but let’s hope it only takes 10:01!

Well… 1 of the last 3 sites deployed, but 2 did not.

The remaining 2 sites:

b1b31fcf-0373-4e3f-ab36-1428cacd6973
cf951426-7be3-44d5-ab1f-7945b1a062cc

The last time they were deployed (2-3 years ago) each one took almost 80 minutes (about 28k pages each) :

I’ve bumped the timeout even more - but these are the numbers we never really end up going to, so it’s strange that it’s happening.

On a side note, if you are not using Netlify Forms, you could disable form detection from the site’s settings in the UI. That might change some stuff. I’d advise to try this before triggering another deploy.

After disabling Netlify Forms… each site took 45 SECONDS to deploy!

Case closed.

Thank you!
:peace_symbol:

1 Like