search

cloudfoundry-attic / bosh-lite

A lite development env for BOSH
Apache License 2.0
319 stars 245 forks source link

Blobstore error: Failed to fetch object, underlying error: #<HTTPClient::ReceiveTimeoutError: execution expired> #428

Closed ivandavidov closed 7 years ago

ivandavidov commented 7 years ago

I've been following the official instructions about deploying Cloud Foundry on my local bosh-lite VM. I am currently stuck with HTTP timeout while bosh was trying to fetch dotnet-core-buildpack from the blobstore:

Building dotnet-core-buildpack...
  Using final version '1e561dd9d5e980c690759e37a711b0f03488608d'
  Downloading from blobstore (id=78751dff-018f-4339-b702-1437c5a5b921)...
Blobstore error: Failed to fetch object, underlying error: #<HTTPClient::ReceiveTimeoutError: execution expired>

You can find the full output, including the ruby/gem stacktrace here.

I suspect this error is due to the weak CPU on my local machine (N3700 CPU, 8GB RAM, Ubuntu 16.04 LTS). This is in line with the other issues of similar type which I opened recently.

My question: is there a way to explicitly set/increase the timeout which is causing me troubles?

Regards, Ivan Davidov

ivandavidov commented 7 years ago

Yet another question: I assume the dotnet-core-buildpack is too big and my CPU is too weak which causes the issue. Apart from increasing the timeout, is it possible to exclude this buildpack from the release? That said, should I look in the YAML manifest file in the relase (cf-258) or I should try to remove this pack from somewhere else?

Thank you!

ivandavidov commented 7 years ago

Even though I managed to workaround my issue by using nothing but a terminal window on my Ubuntu OS (no browser, no other running apps), the issue is still there - the default timeouts may work fine in cloud environment but they are causing troubles on not-so-great entry level laptops like mine.

dpb587-pivotal commented 7 years ago

While Cloud Foundry does utilize a fair bit of CPU and memory, this seems more like an internet connectivity issue and retrying the download may fix it. I don't think a weak CPU should have much to do with this error since HTTP downloads are cheap.

I do recommend trying CF on a cloud somewhere if you're not having luck with your local machine - it may save you some time and hassle in the long-run. Feel free to follow up if you encounter other errors, or join the #bosh channel in https://slack.cloudfoundry.org.