Closed jmank88 closed 6 years ago
This happens often. Perhaps we are retaining too much history.
Sometimes it's more severe, and requires service docker restart
.
Logs:
#
# Fatal error in , line 0
# API fatal error handler returned after process out of memory
#
Illegal instruction (core dumped)
npm ERR! code ELIFECYCLE
npm ERR! errno 132
npm ERR! gochain-netstats@0.0.17 start: `node ./bin/www`
npm ERR! Exit status 132
npm ERR!
npm ERR! Failed at the gochain-netstats@0.0.17 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-03-19T00_42_57_974Z-debug.log
Attempting to stop/rm/kill the containers results in something like:
Error response from daemon: cannot stop container: netstats: Cannot kill container b7ce6fe3a5cb3f5374e70c35440688ddf836bc831350711e6c53ddcc551765bb: connection error: desc = "transport: dial unix /var/run/docker/containerd/docker-containerd.sock: connect: connection refused": unknown
all good
Error while monitoring a high volume load test: