When 'bench start' I have a problem - node error while rebuilding js with yarn script

Install / Update Deployment
1

Execute the command ‘bench start’ ,Program stopped, It’s shown in the information.

18:00:04 watch.1          | Rebuilding marketplace.css
18:00:04 watch.1          | Rebuilding erpnext-web.min.js
18:00:04 watch.1          | Rebuilding erpnext-web.css
18:00:04 watch.1          | Rebuilding marketplace.min.js
18:01:15 watch.1          | /tmp/yarn--1544349570636-0.5825234237514014/node: li
ne 3: 11766 Killed                  "/usr/local/node-v6/bin/node" "$@"
18:01:15 watch.1          | error Command failed with exit code 137.
18:01:15 watch.1          | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
18:01:17 system           | watch.1 stopped (rc=0)
18:01:17 system           | sending SIGTERM to redis_socketio.1 (pid 11557)
18:01:17 system           | sending SIGTERM to worker_long.1 (pid 11550)
18:01:17 system           | sending SIGTERM to redis_queue.1 (pid 11552)
18:01:17 system           | sending SIGTERM to web.1 (pid 11556)
18:01:17 system           | sending SIGTERM to schedule.1 (pid 11548)
18:01:17 system           | sending SIGTERM to worker_default.1 (pid 11549)'
2

Not sure what your trying to do from the small info provided, But try:
Updating to the latest stable version of node. I find using NVM helpful. Install and update to the latest stable version of Yarn. I find using NPM helpful.
HTH

3

from here…possibly… a low memory problem.

The application hit an OOM (out of memory) condition. With regards to OOM condition handling, review the node’s kernel logs to validate whether this occurred. This would require knowing which node the failed container was running on, or proceed with checking all nodes. Run something like this on your node(s) to help you identify whether you’ve had a container hit an OOM condition:

journalctl -k | grep -i -e memory -e oom

2 Likes
5

Yes, I run journalctl -k | grep -i -e memory -e oom the results。Thank！

kernel: Out of memory: Kill process 11766 (node) score 442 or sacrifice child