I have an issue when running gulp as it kills itself during the task. I'm not doing anything:
> gulp build
[11:25:34] Using gulpfile /app/app-base/frontend/gulpfile.js
[11:25:34] Starting 'css-clean'...
[11:25:34] Starting 'js-clean'...
[11:25:34] Finished 'css-clean' after 5.99 ms
[11:25:34] Starting 'css-build'...
[11:25:34] Finished 'js-clean' after 17 ms
[11:25:34] Starting 'js-build'...
[11:25:35] Finished 'css-build' after 888 ms
[11:25:35] Starting 'css'...
[11:25:35] Finished 'css' after 13 μs
Killed
npm ERR! app-frontend@0.0.1 build: `gulp build`
npm ERR! Exit status 137
npm ERR!
npm ERR! Failed at the app-frontend@0.0.1 build script.
npm ERR! This is most likely a problem with the app-frontend package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! gulp build
npm ERR! You can get their info via:
npm ERR! npm owner ls app-frontend
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 3.13.0-43-generic
npm ERR! command "/root/.nvm/v0.10.35/bin/node" "/root/.nvm/v0.10.35/bin/npm" "run" "build"
npm ERR! cwd /app/app-base/frontend
npm ERR! node -v v0.10.35
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /app/app-base/frontend/npm-debug.log
npm ERR! not ok code 0
This is my js-build task which seem to be the cause of it:
gulp.task('js-build', ['js-clean'], function() {
return gulp
.src(PATHS.js.input)
.pipe(plumber())
.pipe(browserify({
transform: [
'reactify',
'envify',
],
}))
.pipe(rename(PATHS.js.outputFile))
.pipe(uglify())
.pipe(gulp.dest(PATHS.js.output));
});
It will work more often if I remove uglify but it doesn't work 100%. Could it be related to the time it takes, seems to be correlated to that.
Here is the npm-debug.log:
1 0 info it worked if it ends with ok
2 1 verbose cli [ '/root/.nvm/v0.10.35/bin/node',
3 1 verbose cli '/root/.nvm/v0.10.35/bin/npm',
4 1 verbose cli 'start' ]
5 2 info using npm@1.4.28
6 3 info using node@v0.10.35
7 4 verbose run-script [ 'prestart', 'start', 'poststart' ]
8 5 info prestart app-base@
9 6 info start app-base@
10 7 verbose unsafe-perm in lifecycle true
11 8 info app-base@ Failed to exec start script
12 9 error app-base@ start: `./scripts/start.sh`
13 9 error Exit status 1
14 10 error Failed at the app-base@ start script.
15 10 error This is most likely a problem with the app-base package,
16 10 error not with npm itself.
17 10 error Tell the author that this fails on your system:
18 10 error ./scripts/start.sh
19 10 error You can get their info via:
20 10 error npm owner ls app-base
21 10 error There is likely additional logging output above.
22 11 error System Linux 3.13.0-43-generic
23 12 error command "/root/.nvm/v0.10.35/bin/node" "/root/.nvm/v0.10.35/bin/npm" "start"
24 13 error cwd /app/app-base
25 14 error node -v v0.10.35
26 15 error npm -v 1.4.28
27 16 error code ELIFECYCLE
28 17 verbose exit [ 1, true ]
Unfortunately, Killed is caused by the kernel and is due to the memory of the machine running out. This was done on a 512Mb Virtual Machine and the memory wasn't sufficient enough for doing gulp builds. I had to do the bundling on another machine and transfer that code to this machine as a work around instead of simply giving the machine more memory, that would work too. Hope that helped someone else...
I faced the same problem. I have a 1 GB ram server and the gulp process was getting killed. I disabled any linting tasks in production mode which reduced the memory consumption quite a bit.
来源：https://stackoverflow.com/questions/28304018/gulp-is-killed-irregularly