-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
octopus$ npm run build fails #10
Comments
Hi @shotelco! Could you provide me the details of the machine that you are using to run the install? Are you trying to run this on a server/VPS or on your local machine? |
Thanks for the response msypko: Node: v8.9.2 (Latest LTS: Carbon) I wanted to compile octopus here, and deploy the build/ on AWS, Netlify & Fastly. Let me know if you need anything else. |
@shotelco do you compile Octopus on your local machine or directly on your EC2 instance? |
Compiled on EC2 directly. |
@shotelco please try to compile Octopus on your local machine and then upload |
Will give that a try. Due to time constraints, it may be a while. Thanks! |
@shotelco sure :-) Let me know if you spot the issue again! Merry Christmas from LiveChat team :D |
@bolchowka feel free to close this issue |
Hello- Not an expert here at all. Walked through the installation and npm install seemed to run ok (skipped some options). Build killed itself. Please review below. Thanks
ubuntu@ip-172-31-13-93:~/octopus$ npm install
[grpc] Success: "/home/ubuntu/octopus/node_modules/grpc/src/node/extension_binary/node-v57-linux-x64-glibc/grpc_node.node" is installed via remote
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.1.3 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
added 1441 packages in 17776.575s
ubuntu@ip-172-31-13-93:/octopus$
ubuntu@ip-172-31-13-93:/octopus$ ls
config npm-debug.log public _redirects yarn.lock
LICENSE package.json readme-assets scripts
node_modules package-lock.json README.md src
ubuntu@ip-172-31-13-93:*/octopus$ npm run build
Creating an optimized production build...
Killed
npm ERR! code ELIFECYCLE
npm ERR! errno 137
npm ERR! octopus@0.1.0 build:
node scripts/build.js && cp _redirects build/_redirects && cp .htaccess build/.htaccess
npm ERR! Exit status 137
npm ERR!
npm ERR! Failed at the octopus@0.1.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/ubuntu/.npm/_logs/2017-12-08T17_27_01_029Z-debug.log
!
!
!
ubuntu@ip-172-31-13-93:/octopus$ ls
build node_modules package-lock.json README.md src
config npm-debug.log public _redirects yarn.lock
LICENSE package.json readme-assets scripts
ubuntu@ip-172-31-13-93:/octopus$ cd build/
ubuntu@ip-172-31-13-93:/octopus/build$ ls
manifest.json static
ubuntu@ip-172-31-13-93:/octopus/build$ nano manifest.json
ubuntu@ip-172-31-13-93:/octopus/build$ cd static/
ubuntu@ip-172-31-13-93:/octopus/build/static$ ls
livechat.png octopus.png
---->more 2017-12-08T17_27_01_029Z-debug.log<------
ubuntu@ip-172-31-13-93:/.npm/_logs$ more 2017-12-08T17_27_01_029Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/home/ubuntu/.nvm/versions/node/v8.9.2/bin/node',
1 verbose cli '/home/ubuntu/.nvm/versions/node/v8.9.2/bin/npm',
1 verbose cli 'run',
1 verbose cli 'build' ]
2 info using npm@5.5.1
3 info using node@v8.9.2
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle octopus@0.1.0prebuild: octopus@0.1.0
6 info lifecycle octopus@0.1.0build: octopus@0.1.0
7 verbose lifecycle octopus@0.1.0build: unsafe-perm in lifecycle true
8 verbose lifecycle octopus@0.1.0build: PATH: /home/ubuntu/.nvm/versions/node/v
8.9.2/lib/node_modules/npm/bin/node-gyp-bin:/home/ubuntu/octopus/node_modules/.b
in:/home/ubuntu/.nvm/versions/node/v8.9.2/bin:/home/ubuntu/bin:/home/ubuntu/.loc
al/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/
usr/local/games:/snap/bin
9 verbose lifecycle octopus@0.1.0~build: CWD: /home/ubuntu/octopus
10 silly lifecycle octopus@0.1.0build: Args: [ '-c',
10 silly lifecycle 'node scripts/build.js && cp _redirects build/_redirects &&
cp .htaccess build/.htaccess' ]
11 silly lifecycle octopus@0.1.0build: Returned: code: 137 signal: null
12 info lifecycle octopus@0.1.0build: Failed to exec build script
13 verbose stack Error: octopus@0.1.0 build:
node scripts/build.js && cp _redir ects build/_redirects && cp .htaccess build/.htaccess
13 verbose stack Exit status 137
13 verbose stack at EventEmitter. (/home/ubuntu/.nvm/versions/nod
e/v8.9.2/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:280:16)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at EventEmitter.emit (events.js:214:7)
13 verbose stack at ChildProcess. (/home/ubuntu/.nvm/versions/nod
e/v8.9.2/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at ChildProcess.emit (events.js:214:7)
13 verbose stack at maybeClose (internal/child_process.js:925:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_proc
ess.js:209:5)
14 verbose pkgid octopus@0.1.0
15 verbose cwd /home/ubuntu/octopus
16 verbose Linux 4.4.0-1028-aws
17 verbose argv "/home/ubuntu/.nvm/versions/node/v8.9.2/bin/node" "/home/ubuntu/
.nvm/versions/node/v8.9.2/bin/npm" "run" "build"
18 verbose node v8.9.2
19 verbose npm v5.5.1
20 error code ELIFECYCLE
21 error errno 137
22 error octopus@0.1.0 build:
node scripts/build.js && cp _redirects build/_red irects && cp .htaccess build/.htaccess
22 error Exit status 137
23 error Failed at the octopus@0.1.0 build script.
23 error This is probably not a problem with npm. There is likely additional log
ging output above.
24 verbose exit [ 137, true ]
ubuntu@ip-172-31-13-93:*/.npm/_logs$
(* = ~)
The text was updated successfully, but these errors were encountered: