Npm ошибка установки при развертывании в elasti c beanstalk - PullRequest
0 голосов
/ 28 апреля 2020

Я хочу развернуть свое приложение nodejs на elasti c beanstalk. Я использую стандартный бесплатный экземпляр уровня t2.micro.

Но когда я пытаюсь развернуть приложение, я получаю сообщение об ошибке

"не удается найти приложение npm журнал отладки в / tmp / deploy / application / npm -debug.log ".

Следуя другим вопросам, связанным с SO, я добавил подкачку памяти, так как нехватка памяти могла вызвать эту проблему. Но я все еще получаю ту же ошибку. Как правильно развернуть приложение nodejs?

Полный журнал ошибок выглядит следующим образом:

  Running npm install:  /opt/elasticbeanstalk/node-install/node-v12.16.1-linux-x64/bin/npm
  Setting npm config jobs to 1
  npm config jobs set to 1
  Running npm with --production flag
  Failed to run npm install. Snapshot logs for more details.
  UTC 2020/04/28 02:30:39 cannot find application npm debug log at /tmp/deployment/application/npm-debug.log 

  Traceback (most recent call last):
    File "/opt/elasticbeanstalk/containerfiles/ebnode.py", line 695, in <module>
      main()
    File "/opt/elasticbeanstalk/containerfiles/ebnode.py", line 677, in main
      node_version_manager.run_npm_install(options.app_path)
    File "/opt/elasticbeanstalk/containerfiles/ebnode.py", line 136, in run_npm_install
      self.npm_install(bin_path, self.config_manager.get_container_config('app_staging_dir'))
    File "/opt/elasticbeanstalk/containerfiles/ebnode.py", line 180, in npm_install
      raise e
  subprocess.CalledProcessError: Command '['/opt/elasticbeanstalk/node-install/node-v12.16.1-linux-x64/bin/npm', '--production', 'install']' returned non-zero exit status 1 (ElasticBeanstalk::ExternalInvocationError)
caused by: + /opt/elasticbeanstalk/containerfiles/ebnode.py --action npm-install
  npm WARN deprecated babel-preset-es2015@6.24.1: ?  Thanks for using Babel: we recommend using babel-preset-env now: please read https://babeljs.io/env to update!
  npm WARN deprecated material-ui@0.20.2: You can now upgrade to @material-ui/core
  npm WARN deprecated popper.js@1.16.1: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
  npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
  npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart()
  npm WARN deprecated core-js@1.2.7: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
  npm WARN deprecated fsevents@1.2.12: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.

  > node-sass@4.12.0 install /tmp/deployment/application/node_modules/material-kit-react/node_modules/node-sass
  > node scripts/install.js


  Running npm install:  /opt/elasticbeanstalk/node-install/node-v12.16.1-linux-x64/bin/npm
  Setting npm config jobs to 1
  npm config jobs set to 1
  Running npm with --production flag
  Failed to run npm install. Snapshot logs for more details.
  UTC 2020/04/28 02:30:39 cannot find application npm debug log at /tmp/deployment/application/npm-debug.log 

  Traceback (most recent call last):
    File "/opt/elasticbeanstalk/containerfiles/ebnode.py", line 695, in <module>
      main()
    File "/opt/elasticbeanstalk/containerfiles/ebnode.py", line 677, in main
      node_version_manager.run_npm_install(options.app_path)
    File "/opt/elasticbeanstalk/containerfiles/ebnode.py", line 136, in run_npm_install
      self.npm_install(bin_path, self.config_manager.get_container_config('app_staging_dir'))
    File "/opt/elasticbeanstalk/containerfiles/ebnode.py", line 180, in npm_install
      raise e
  subprocess.CalledProcessError: Command '['/opt/elasticbeanstalk/node-install/node-v12.16.1-linux-x64/bin/npm', '--production', 'install']' returned non-zero exit status 1 (Executor::NonZeroExitStatus)


[2020-04-28T02:30:39.737Z] INFO  [5113]  - [Application update influencertiktok-source-1@3/AppDeployStage0/AppDeployPreHook/50npm.sh] : Activity failed.
[2020-04-28T02:30:39.737Z] INFO  [5113]  - [Application update influencertiktok-source-1@3/AppDeployStage0/AppDeployPreHook] : Activity failed.
[2020-04-28T02:30:39.737Z] INFO  [5113]  - [Application update influencertiktok-source-1@3/AppDeployStage0] : Activity failed.
[2020-04-28T02:30:39.738Z] INFO  [5113]  - [Application update influencertiktok-source-1@3] : Completed activity. Result:
  Application update - Command CMD-AppDeploy failed
[2020-04-28T02:31:36.601Z] INFO  [5427]  - [CMD-BundleLogs] : Starting activity...
[2020-04-28T02:31:36.601Z] INFO  [5427]  - [CMD-BundleLogs/AddonsBefore] : Starting activity...
[2020-04-28T02:31:36.601Z] INFO  [5427]  - [CMD-BundleLogs/AddonsBefore] : Completed activity.
[2020-04-28T02:31:36.601Z] INFO  [5427]  - [CMD-BundleLogs/BundleLogs] : Starting activity...
[2020-04-28T02:31:36.601Z] INFO  [5427]  - [CMD-BundleLogs/BundleLogs/BundleLogs] : Starting activity...

1 Ответ

0 голосов
/ 08 мая 2020

Я исправил это путем обновления до ec2.medium. Похоже, моему приложению потребовалось больше ресурсов для сборки, и тогда эта ошибка может возникнуть, даже иногда недетерминированной.

Добро пожаловать на сайт PullRequest, где вы можете задавать вопросы и получать ответы от других членов сообщества.
...