Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[training failure] Backend response timeout (30s)

See original GitHub issue

First, training with web app:


Then training with cacli:

$ cacli train

Bucket panels-01

⠏ Starting training run... error Backend response timeout (30s)
$ cacli list
 name                                          model id         status          submitted 
 panels-01                                  model-1qn1nzc4      error         an hour ago 
 panels-01                                  model-mno1p33h      error         an hour ago 
 panels-01                                  model-y7lg8gi8      error         an hour ago 
 panels-01                                  model-z9od9ow4      error      36 minutes ago 
 panels-01                                  model-2iwj18c1      error      30 minutes ago 
$ cacli logs model-1qn1nzc4
error NoSuchKey: The specified key does not exist.
	status code: 404, request id: 70e8fc34-d48d-4055-9eaf-a2ea61703910, host id:

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:8 (5 by maintainers)

github_iconTop GitHub Comments

playrobotics-alexcommented, Mar 1, 2020

I think I found the problem. The machine learning service is set to London location by default, while the storage is in the US. I deleted the ML service and created a new one in Dallas location, I am no longer getting the error , the message now says “Waiting for an available GPU (this may take a while)…” which seems to be normal.

bourdakos1commented, Mar 5, 2020

The issue with London has been resolved, training should work now 😃

Read more comments on GitHub >

github_iconTop Results From Across the Web

Queries failing after 30s despite changing dataproxy.timeout ...
Long running queries to Azure Log Analytics are failed after 30 seconds with a 504 Gateway timeout issue despite dataproxy.timeout set above 30s...
Read more >
Troubleshoot Azure Front Door common issues | Microsoft Learn
Your origin is taking longer than the timeout configured to receive the request from Azure Front Door. The default is 30 seconds. The...
Read more >
Common Timeouts effecting Web Services, HTTP and SOAP ...
The default value is 5 seconds. Increase the value to 30 seconds or greater. Set the value using the administrative console. If the...
Read more >
Better performance: the case for timeouts - Alessandro Nadalin
the backend service will wait 100ms (this is to simulate real-world use cases) before returning a response; I'm using the unirest HTTP client:...
Read more >
Setting a Request Timeout for a Spring REST API - Baeldung
Explore a few possible ways to implement request timeouts for a ... 500 HTTP error, which we can transform into a more meaningful...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found