Ich habe kürzlich eine neue Anwendung "node.js" auf Beanstalk bereitgestellt und führe den folgenden Fehler aus?Fehler beim Bereitstellen der Anwendung "node.js" in Amazon Elastic-Bohnenstange
[Instanz: i-cce89e4a] Der Befehl ist in der Instanz fehlgeschlagen. Rückgabecode: 1 Ausgabe: (TRUNCATED) ... opt/elasticbeanstalk/containerfiles/ebnode.py ", Zeile 180, in npm_install raise e subprocess.CalledProcessError: Befehl '['/opt/elasticbeanstalk/node-install/node-v4 .4.6-linux-x64/bin/npm ',' --production ',' rebuild ']' hat den Nicht-Null-Exit-Status 254 zurückgegeben. Hook /opt/elasticbeanstalk/hooks/configploy/pre/50npm.sh ist fehlgeschlagen Detail, überprüfen /var/log/eb-activity.log mit Konsole oder EB CLI
Meine Version des Knotens ist. 4.4.7
der Einsatz scheint in der letzten Zeile unten zu andernfalls:
except Exception, e:
npm_debug_log = '/var/log/nodejs/npm-debug.log'
app_npm_debug_log = os.path.join(app_path, "npm-debug.log")
write_event('Failed to run npm install. Snapshot logs for more details.', 'ERROR')
if not os.path.exists(app_npm_debug_log):
utc_time_str = datetime.datetime.utcnow().strftime("UTC %Y/%m/%d %H:%M:%S")
err_msg = str.format("{0} cannot find application npm debug log at {1} \n", utc_time_str, app_npm_debug_log)
print(err_msg)
with open(npm_debug_log, 'a') as f:
f.write(err_msg)
else:
shutil.copyfile(app_npm_debug_log, npm_debug_log)
raise e
Ich kann nicht scheinen, irgendwelche zu finden feste Lösung da draußen?
Ich manuell die Dateien gezippt und uplaoded.
Die App funktioniert perfekt lokal.
Kann jemand helfen?
Application deployment failed at 2016-07-09T18:47:38Z with exit status 1 and error: Hook /opt/elasticbeanstalk/hooks/appdeploy/pre/50npm.sh failed.
+ /opt/elasticbeanstalk/containerfiles/ebnode.py --action npm-install
npm WARN package.json [email protected] No repository field.
> [email protected] postinstall /tmp/deployment/application/node_modules/history
> node ./npm-scripts/postinstall.js
npm ERR! Linux 4.4.14-24.50.amzn1.x86_64
npm ERR! argv "/opt/elasticbeanstalk/node-install/node-v4.4.6-linux-x64/bin/node" "/opt/elasticbeanstalk/node-install/node-v4.4.6-linux-x64/bin/npm" "--production" "rebuild"
npm ERR! node v4.4.6
npm ERR! npm v2.15.5
npm ERR! path /tmp/deployment/application/node_modules/gulp-main-bower-files/node_modules/main-bower-files/node_modules/vinyl-fs/node_modules/duplexify/node_modules/readable-stream/node_modules/unreachable-branch-transform/node_modules/recast/node_modules/esprima/bin/esvalidate.js
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod '/tmp/deployment/application/node_modules/gulp-main-bower-files/node_modules/main-bower-files/node_modules/vinyl-fs/node_modules/duplexify/node_modules/readable-stream/node_modules/unreachable-branch-transform/node_modules/recast/node_modules/esprima/bin/esvalidate.js'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! Please include the following file with any support request:
npm ERR! /tmp/deployment/application/npm-debug.log
Running npm install: /opt/elasticbeanstalk/node-install/node-v4.4.6-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.
Traceback (most recent call last):
File "/opt/elasticbeanstalk/containerfiles/ebnode.py", line 695, in
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-v4.4.6-linux-x64/bin/npm', '--production', 'rebuild']' returned non-zero exit status 254.
Ich aktualisierte zu einer mittleren Instanz. – user1526912
actualy ich sprach zu bald - stil Begegnung mit dem gleichen Fehler – user1526912
Hatte das gleiche Problem und Upgrade auf höhere Speicher Instanz behoben. – aravindaM