Skip to content
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

Failure to start #11

Open
bigangryrobot opened this issue Nov 15, 2017 · 6 comments
Open

Failure to start #11

bigangryrobot opened this issue Nov 15, 2017 · 6 comments

Comments

@bigangryrobot
Copy link

Hey there, like where you are heading with this as others have mentioned as well. I installed istio via the docs and have prometheus and grafana in the same namespace using the simple config you provided within the "promviz-promviz-config" configmap. On first request to the promvis front end, I get the following. All attempts to grab more logs out of this have failed so far.

**
> [email protected] start /usr/src/app
> npm run dist && node server.js


> [email protected] dist /usr/src/app
> webpack

Killed
npm ERR! code ELIFECYCLE
npm ERR! errno 137
npm ERR! [email protected] dist: `webpack`
npm ERR! Exit status 137
npm ERR! 
npm ERR! Failed at the [email protected] dist 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!     /root/.npm/_logs/2017-11-15T01_23_46_147Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 137
npm ERR! [email protected] start: `npm run dist && node server.js`
npm ERR! Exit status 137
npm ERR! 
npm ERR! Failed at the [email protected] start 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!     /root/.npm/_logs/2017-11-15T01_23_46_159Z-debug.log
@bigangryrobot
Copy link
Author

I gave it a shot of running the front end locally while using kubectl to proxy the remote promviz server to my local 8000 port using this

kubectl port-forward promviz-promviz-0  8000:9091 -n istio-system

and that at least confirmed its not the server
image

@jensneuse
Copy link

npm ERR! errno 137 means you're out of memory. This is because on "runtime" the container builds itself via webpack which consumes much more memory than the default limits allow.

@nmnellis
Copy link

@bigangryrobot were you able to get this working with istio? if so what did your config look like?

@cmarquezrusso
Copy link

Same error, using the helm charts

 > [email protected] start /usr/src/app
> npm run dist && node server.js
 > [email protected] dist /usr/src/app
> webpack
 Killed
npm ERR! code ELIFECYCLE
npm ERR! errno 137
npm ERR! [email protected] dist: `webpack`
npm ERR! Exit status 137
npm ERR! 
npm ERR! Failed at the [email protected] dist 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!     /root/.npm/_logs/2018-05-13T23_23_17_421Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 137
npm ERR! [email protected] start: `npm run dist && node server.js`
npm ERR! Exit status 137
npm ERR! 
npm ERR! Failed at the [email protected] start 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!     /root/.npm/_logs/2018-05-13T23_23_17_457Z-debug.log

@markmssd
Copy link

Had the same issue, it was indeed not enough memory. Changed it in helm/promviz-front/values.yaml as:

resources:
  limits:
    cpu: 200m
    memory: 1Gi
  requests:
    cpu: 100m
    memory: 1Gi

(512Mi wasn't enough for me, 1Gi got it working)

@MoJo2600
Copy link

MoJo2600 commented May 2, 2019

Same here, the memory limit is way too low

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants