question-mark
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.

amplify push timeout: An error occured during the push operation: Your socket connection to the server was not read from or written to within the timeout period

See original GitHub issue

Describe the bug

For the past few days, as the schema started growing it has been almost impossible to reliably push any changes via amplify push --yes

The “Updating resources in the cloud. This may take a few minutes…” message only appears for one in several push attempts.

Some more logs/status updates relating to what it does at every step between compiling the schema and updating the resources in the cloud would be helpful.

I’m not sure if it’s some sort of intermittent outage related to S3 or other resources amplify push might be using. This is not an internet problem on my end.

Running amplify api push results in a stack trace that mentions S3 as the reson for the timeout.

I have attached a screenshot below.

Error is: Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. An error occured during the push operation: Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.

Amplify CLI Version

4.18.0

Expected behavior

Pushing should not timeout.

Screenshots

image

Desktop (please complete the following information):

node -v: 13.7.0 Win10 with WSL2 (Ubuntu)

Additional context

This started happening yesterday, presumably related to schema changes but I’m not sure. The processing step before it starts “Updating resources in the cloud. This may take a few minutes…” has been taking longer and longer.

Has been reported several times but the issues are closed:

https://github.com/aws-amplify/amplify-cli/issues/462 https://github.com/aws-amplify/amplify-cli/issues/501 https://github.com/aws-amplify/amplify-cli/issues/2121

Issue Analytics

  • State:open
  • Created 3 years ago
  • Reactions:5
  • Comments:44 (13 by maintainers)

github_iconTop GitHub Comments

6reactions
amcdnlcommented, Jun 16, 2021

This is a pretty big issue since you are not able to deploy any complex app that has large set of changes.

3reactions
amcdnlcommented, Jun 10, 2021

So I was able to figure out what the issue was …

  • Amplify Push
  • Connections Opened ( S3/etc )
  • Amplify Build + Your Build
  • Build > S3 Socket Timeout time = Failure
Read more comments on GitHub >

github_iconTop Results From Across the Web

Amplify socket connection error while executing push or publish
An error occurred during the push operation: Your socket connection to the server was not read from or written to within the timeout...
Read more >
Troubleshooting a failed canary - Amazon CloudWatch
Error : No datapoint - Canary Shows timeout error. This means that your canary run exceeded the timeout. The canary execution stopped before...
Read more >
Subscriptions - Apollo GraphQL Docs
When Apollo Client executes the OnCommentAdded subscription, it establishes a connection to your GraphQL server and listens for response data. Unlike with a ......
Read more >
Troubleshoot Dataflow errors - Google Cloud
Some Cloud APIs need to be enabled; Bad request; Cannot read and write in ... This issue occurs because some required APIs are...
Read more >
All configuration options - Quarkus
AWS Lambda Type Default AWS Lambda Common Type Default AWS Lambda Gateway REST API Type Default Agroal ‑ Database connection pool Type Default
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 Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found