Skip to content


File Errors ElasticBeanstalk #4558

MeisterMichael opened this Issue · 2 comments

4 participants


The same deploy actions causes different file not existing errors every time. This only seems to happen when it is run automatically. I ran the same commands on the server and everything installed fine.

0 info it worked if it ends with ok
1 verbose cli [ '/opt/elasticbeanstalk/node-install/node-v0.10.21-linux-x64/bin/node',
1 verbose cli   '/opt/elasticbeanstalk/node-install/node-v0.10.21-linux-x64/bin/npm',
1 verbose cli   'install' ]
2 info using npm@1.3.11
3 info using node@v0.10.21
4 verbose readDependencies using package.json deps
5 verbose install where, deps [ '/tmp/deployment/application',
5 verbose install   [ 'express',
5 verbose install     'jade',
5 verbose install     'asset-rack',
5 verbose install     'node-uuid',
5 verbose install     'newrelic',
5 verbose install     'redis-node',
5 verbose install     'useragent',
5 verbose install     'any-db',
5 verbose install     'any-db-postgres',
5 verbose install     'generic-pool',
5 verbose install     'addr',
5 verbose install     'toobusy',
5 verbose install     'cluster2',
5 verbose install     'connect-redis' ] ]
6 info preinstall playswell-node-api@2.0.1
7 verbose readDependencies using package.json deps
8 verbose cache add [ 'jade@*', null ]
9 verbose cache add name=undefined spec="jade@*" args=["jade@*",null]


2198 info install mkdirp@0.3.5 into /tmp/deployment/application/node_modules/express
2199 info install cookie@0.1.0 into /tmp/deployment/application/node_modules/express
2200 info install buffer-crc32@0.2.1 into /tmp/deployment/application/node_modules/express
2201 info install merge-descriptors@0.0.1 into /tmp/deployment/application/node_modules/express
2202 info install connect@2.12.0 into /tmp/deployment/application/node_modules/express
2203 info installOne debug@0.7.4
2204 info installOne cookie-signature@1.0.1
2205 info installOne fresh@0.2.0
2206 info installOne send@0.1.4
2207 info installOne methods@0.1.0
2208 info installOne commander@1.3.2
2209 info installOne range-parser@0.0.4
2210 info installOne mkdirp@0.3.5
2211 info installOne cookie@0.1.0
2212 info installOne buffer-crc32@0.2.1
2213 info installOne merge-descriptors@0.0.1
2214 info installOne connect@2.12.0
2215 info /tmp/deployment/application/node_modules/express/node_modules/debug unbuild
2216 info /tmp/deployment/application/node_modules/express/node_modules/cookie-signature unbuild
2217 info /tmp/deployment/application/node_modules/express/node_modules/fresh unbuild
2218 info /tmp/deployment/application/node_modules/express/node_modules/send unbuild
2219 info /tmp/deployment/application/node_modules/express/node_modules/methods unbuild
2220 info /tmp/deployment/application/node_modules/express/node_modules/commander unbuild
2221 info /tmp/deployment/application/node_modules/express/node_modules/range-parser unbuild
2222 info /tmp/deployment/application/node_modules/express/node_modules/mkdirp unbuild
2223 info /tmp/deployment/application/node_modules/express/node_modules/cookie unbuild
2224 info /tmp/deployment/application/node_modules/express/node_modules/buffer-crc32 unbuild
2225 info /tmp/deployment/application/node_modules/express/node_modules/merge-descriptors unbuild
2226 info /tmp/deployment/application/node_modules/express/node_modules/connect unbuild
2227 error Error: ENOENT, chmod '/tmp/npm-23806-Ee6ZAEeP/1390861156538-0.8627162503544241/package/test'
2228 error If you need help, you may report this log at:
2228 error     <>
2228 error or email it to:
2228 error     <>
2229 error System Linux 3.4.62-53.42.amzn1.x86_64
2230 error command "/opt/elasticbeanstalk/node-install/node-v0.10.21-linux-x64/bin/node" "/opt/elasticbeanstalk/node-install/node-v0.10.21-linux-x64/bin/npm" "install"
2231 error cwd /tmp/deployment/application
2232 error node -v v0.10.21
2233 error npm -v 1.3.11
2234 error path /tmp/npm-23806-Ee6ZAEeP/1390861156538-0.8627162503544241/package/test
2235 error fstream_path /tmp/npm-23806-Ee6ZAEeP/1390861156538-0.8627162503544241/package/test/index.js
2236 error fstream_type File
2237 error fstream_class FileWriter
2238 error fstream_finish_call setupMadeDir
2239 error code ENOENT
2240 error errno 34
2241 error fstream_stack end (/opt/elasticbeanstalk/node-install/node-v0.10.21-linux-x64/lib/node_modules/npm/node_modules/fstream/lib/writer.js:319:21)
2241 error fstream_stack /opt/elasticbeanstalk/node-install/node-v0.10.21-linux-x64/lib/node_modules/npm/node_modules/fstream/lib/writer.js:336:20
2241 error fstream_stack next (/opt/elasticbeanstalk/node-install/node-v0.10.21-linux-x64/lib/node_modules/npm/node_modules/fstream/lib/writer.js:366:20)
2241 error fstream_stack Object.oncomplete (fs.js:107:15)
2242 verbose exit [ 34, true ]
@iarna iarna added the support label

Is this still a problem for you?

There have been a lot of improvements to npm -- especially around conflicts and race conditions during install -- since 1.3.11. Can you try updating your npm installation?

To update npm, run npm -g install npm@latest

For some Linux distributions (Debian/Ubuntu and RedHat/CentOS), the latest node version provided by the distribution may lag behind the stable version. Here are instructions from NodeSource on getting the latest node.

We are trying to clean up older npm issues, so if we don't hear back from you within a week, we will close this issue. (Don't worry -- you can always come back again and open a new issue!)



Closing as resolved. The race condition fixes in npm@2 almost certainly will make behavior on Elastic Beanstalk deterministic, so even if installs fail, they should fail in the same places every time.

@othiym23 othiym23 closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.