serverless: Deploy stops at "Installing dependencies for custom CloudFormation resources"

I´m using this template https://github.com/msfidelis/serverless-architecture-boilerplate and the issue has only occured with this template so far.

Creating new projects from scratch with the sls assistent and deploying works fine.

When running sls deploy it processes these 3 steps and then stops

Serverless: Packaging service...
Serverless: Excluding development dependencies...
Serverless: Installing dependencies for custom CloudFormation resources...

Running deploy with –verbose --force does not change anything and there are literally no additional exceptions or log messages thrown which makes it very hard to find the source of this issue.

Serverless v: 1.50.0 OS: Windows 10

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 6
  • Comments: 43 (16 by maintainers)

Most upvoted comments

I can confirm that it is resolved in 1.53.0…!

Thanks!

For me also the same issue but the what caused that seems to be different. When I use the property existing: true for S3 event this issue happens. Otherwise it works fine.

Chiming in, same story, 1.50.0 too many files, 1.48.4 deploys just fine.

     Operating System:          win32
     Node Version:              10.16.3
     Framework Version:         1.50.0
     Plugin Version:            1.3.8
     SDK Version:               2.1.0```

I also experienced the same problem, but with the error message:

EMFILE: too many open files, open 'C: \ Users \ marda \ AppData \ Local \ Temp \ tmpdirs-serverless \ 330d \ b435695edb9e63a1 \ resources \ node_modules \ tokopedia-api \ api node_modules \ caniuse-lite \ data \ regions \ GL.js'

 Your Environment Information ---------------------------
     Operating System:          win32
     Node Version:              12.8.1
     Framework Version:         1.50.0
     Plugin Version:            1.3.8
     SDK Version:               2.1.0

Serverless v: 1.50.0 OS: Windows 10

Update: After I tried to downgrade to the previous version (v1.49.0) it turns out that this message disappears and serverless runs normally. I think this is a bug for version v1.50.0

My bad, actually I hadn’t updated the serverless framework version globally. npm uninstall -g serverless and then npm install -g serverless updated the framework to 1.53.0. The issue got resolved in this build

Hey everyone, thanks for reporting and confirming this issue. I just created https://github.com/serverless/serverless/issues/6557 to explore different solutions for this issue.

Unfortunately I don’t have a Windows machine handy, so it would be super awesome if someone can checkout this PR and report back if this fixes the problem.

This issue seems to be related to https://github.com/serverless/serverless/issues/3249.


EDIT: apparently the current fix doesn’t do anything at all. I took another deep dive into this and it seems like the zipping is the issue here (see: https://github.com/serverless/serverless/pull/6636#issuecomment-528360012). I’ll work on an update on that front and post another comment when I have something to test.

1.51.0 still has the same error. Did they even try to fix the bug before the 1.51 release?