search

Graphcool / graphcool-framework

Apache License 2.0
1.77k stars 131 forks source link

"Code storage limit exceeded" on some deployments #517

Closed marktani closed 6 years ago

marktani commented 6 years ago

Current behavior

Sometimes, a deployment can lead to this error:

Global × software.amazon.awssdk.services.lambda.model.CodeStorageExceededException: Code storage limit exceeded. (Service: null; Status Code: 400; Error Code: CodeStorageExceededException; Request ID: d49eb523-47ba-11e8-b52a-25f53c86282e)

Workaround

Deploy multiple times, until the error doesn't appear.

Expected behavior?

No deployment returns this error.

senorcodecat commented 6 years ago

Thanks, Nilan!

stefanoTron commented 6 years ago

The workaround works. But this is still pretty annoying, is this being actively worked on? And should the graphcool status page not be updated?

senorcodecat commented 6 years ago

Agreed. It's adding 5 - 20 minutes per deploy to get this to work. Can the status page be updated so we know when this is resolved?

stefanoTron commented 6 years ago

Sometimes, I'm also getting this:

'ECONNRESET': request to https://api.graph.cool/system failed, reason: socket hang up

and this:

'EPROTO': request to
 ▸    https://graphcool-lambda-3-deploy-eu-west-1.s3-eu-west-1.amazonaws.com/cjgkm99bt68ym0161v3zo2g7f?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20180429T093222Z&X-Amz-SignedHeaders=host&X-Amz-Expires=3599&X-Amz-Credential=AKIAIWGVI2G6RGAWGJPQ%2F20180429%2Feu-west-1%2Fs3%2Faws4_request&X-Amz-Signature=d294db20e1ef1b88a50f7989c8f9ee482153657f954ca59a44ea879d045eda84
 ▸    failed, reason: write EPROTO 140736184116160:error:1409E0E5:SSL routines:ssl3_write_bytes:ssl handshake failure:../deps/openssl/openssl/ssl/s3_pkt.c:659:
ahsanwtc commented 6 years ago

having same issue

philippbosch commented 6 years ago

It feels like it takes more attempts every day until successful deployment. Have not been able to deploy today at all. 😢

senorcodecat commented 6 years ago

Yeah, this is completely unacceptable for production environments. Can we get an update on this? Otherwise I'm going to need to find a different host.

marktani commented 6 years ago

Thanks all, we're planning to release a fix for this soon.

stefanoTron commented 6 years ago

@philippbosch I confirm, workaround does not work anymore. I've been trying to deploy for 30mins every 5secs.

dpetrick commented 6 years ago

Looking into it right now, it might take a bit of time to fix the underlying issue.

usulpro commented 6 years ago

Tried to deploy about fifty times and no success at all :( Are there other ideas about workaround?

stefanoTron commented 6 years ago

@UsulPro @dpetrick yeah, in the meantime, some kind of workaround would be great :)

marktani commented 6 years ago

Hey all, we expect this to work for all deployments again, can you confirm?

@senorcodecat @littletower @ahsanwtc @philippbosch @UsulPro? :slightly_smiling_face:

usulpro commented 6 years ago

Everything works well. Just deployed on the first attempt :+1: Thanks a lot!!!

stefanoTron commented 6 years ago

@marktani successfully deployed this morning. Thanks!

marktani commented 6 years ago

Thanks for the confirmation :pray:

ahsanwtc commented 6 years ago

yep, seems to be working perfectly :+1:

usulpro commented 6 years ago

Not sure is it related but after I deployed I start to receive this from server: Whoops. Looks like an internal server error. Please contact us from the Console (https://console.graph.cool) or via email (support@graph.cool) and include your Request ID: eu-west-1:simple:cjgnq1wtg2j2p0102ayvkgbh0

tsdexter commented 6 years ago

works for me. thx

marktani commented 6 years ago

@UsulPro, that's not related. Please reach out to support@graph.cool 🙂

nmajozi1 commented 5 years ago

Seems like this issue is back. Please re-open this ticket. I have tried to deploy multiple times without any luck.