Failure to start

[bigangryrobot]

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]

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

[jensneuse]

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]

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

[cmarquezrusso]

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]

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]

Same here, the memory limit is way too low