Error message on bench start? sh: 1: rollup: not found

I receive following error message on running bench start using erpnext-vm-develop after update to version 10.1.4

frappe@erpnext:~/frappe-bench$ bench start
22:31:20 system | web.1 started (pid=2450)
22:31:20 system | redis_socketio.1 started (pid=2446)
22:31:20 system | worker_long.1 started (pid=2448)
22:31:20 redis_socketio.1 | [2453] 26 Feb 22:31:20.918 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
22:31:20 redis_socketio.1 | [2453] 26 Feb 22:31:20.918 # Warning: 32 bit instance detected but no memory limit set. Setting 3 GB maxmemory limit with ‘noeviction’ policy now.
22:31:20 redis_socketio.1 | .
22:31:20 redis_socketio.1 | .-__ ''-._ 22:31:20 redis_socketio.1 | _.- . . ‘’-._ Redis 2.8.4 (00000000/0) 32 bit
22:31:20 redis_socketio.1 | .- .-```. ```\/ _.,_ ''-._ 22:31:20 redis_socketio.1 | ( ' , .-` | `, ) Running in stand alone mode 22:31:20 redis_socketio.1 | |`-._`-...-` __...-.-.|'_.-'| Port: 12000 22:31:20 redis_socketio.1 | | -. ._ / _.-' | PID: 2453 22:31:20 redis_socketio.1 | -._ -._ -./ .-’ .-’
22:31:20 redis_socketio.1 | |-._-.
-.__.-' _.-'_.-'| 22:31:20 redis_socketio.1 | | -.
-._ _.-'_.-' | http://redis.io 22:31:20 redis_socketio.1 | -._ -._-..-'.-’ .-’
22:31:20 redis_socketio.1 | |-._-.
-.__.-' _.-'_.-'| 22:31:20 redis_socketio.1 | | -.
-._ _.-'_.-' | 22:31:20 redis_socketio.1 | -._ -._-.
.-‘.-’ .-’
22:31:20 redis_socketio.1 | -._ -..-’ _.-’
22:31:20 redis_socketio.1 | -._ _.-' 22:31:20 redis_socketio.1 | -.
.-’
22:31:20 redis_socketio.1 |
22:31:20 redis_socketio.1 | [2453] 26 Feb 22:31:20.926 # Server started, Redis version 2.8.4
22:31:20 redis_socketio.1 | [2453] 26 Feb 22:31:20.926 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add ‘vm.overcommit_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit_memory=1’ for this to take effect.
22:31:20 redis_socketio.1 | [2453] 26 Feb 22:31:20.927 * The server is now ready to accept connections on port 12000
22:31:20 system | watch.1 started (pid=2447)
22:31:20 system | schedule.1 started (pid=2449)
22:31:20 system | worker_default.1 started (pid=2451)
22:31:20 system | socketio.1 started (pid=2452)
22:31:20 system | redis_queue.1 started (pid=2456)
22:31:20 redis_queue.1 | [2480] 26 Feb 22:31:20.931 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
22:31:20 redis_queue.1 | [2480] 26 Feb 22:31:20.931 # Warning: 32 bit instance detected but no memory limit set. Setting 3 GB maxmemory limit with ‘noeviction’ policy now.
22:31:20 redis_queue.1 | .
22:31:20 redis_queue.1 | .-__ ''-._ 22:31:20 redis_queue.1 | _.- . . ‘’-.
Redis 2.8.4 (00000000/0) 32 bit
22:31:20 redis_queue.1 | .- .-```. ```\/ _.,_ ''-._ 22:31:20 redis_queue.1 | ( ' , .-` | `, ) Running in stand alone mode 22:31:20 redis_queue.1 | |`-._`-...-` __...-.-.
|’_.-'| Port: 11000 22:31:20 redis_queue.1 | | -._ ._ / _.-' | PID: 2480 22:31:20 redis_queue.1 | -._ -._ -./ .-’ .-’
22:31:20 redis_queue.1 | |-._-.
-.__.-' _.-'_.-'| 22:31:20 redis_queue.1 | | -.
-._ _.-'_.-' | http://redis.io 22:31:20 redis_queue.1 | -._ -._-..-'.-’ .-’
22:31:20 redis_queue.1 | |-._-.
-.__.-' _.-'_.-'| 22:31:20 redis_queue.1 | | -.
-._ _.-'_.-' | 22:31:20 redis_queue.1 | -._ -._-.
.-‘.-’ .-’
22:31:20 redis_queue.1 | -._ -..-’ _.-’
22:31:20 redis_queue.1 | -._ _.-' 22:31:20 redis_queue.1 | -.
.-’
22:31:20 redis_queue.1 |
22:31:20 redis_queue.1 | [2480] 26 Feb 22:31:20.931 # Server started, Redis version 2.8.4
22:31:20 redis_queue.1 | [2480] 26 Feb 22:31:20.931 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add ‘vm.overcommit_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit_memory=1’ for this to take effect.
22:31:20 redis_queue.1 | [2480] 26 Feb 22:31:20.931 * The server is now ready to accept connections on port 11000
22:31:20 system | redis_cache.1 started (pid=2460)
22:31:20 redis_cache.1 | [2474] 26 Feb 22:31:20.926 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
22:31:20 redis_cache.1 | .
22:31:20 redis_cache.1 | .-__ ''-._ 22:31:20 redis_cache.1 | _.- . . ‘’-.
Redis 2.8.4 (00000000/0) 32 bit
22:31:20 redis_cache.1 | .- .-```. ```\/ _.,_ ''-._ 22:31:20 redis_cache.1 | ( ' , .-` | `, ) Running in stand alone mode 22:31:20 redis_cache.1 | |`-._`-...-` __...-.-.
|’_.-'| Port: 13000 22:31:20 redis_cache.1 | | -._ ._ / _.-' | PID: 2474 22:31:20 redis_cache.1 | -._ -._ -./ .-’ .-’
22:31:20 redis_cache.1 | |-._-.
-.__.-' _.-'_.-'| 22:31:20 redis_cache.1 | | -.
-._ _.-'_.-' | http://redis.io 22:31:20 redis_cache.1 | -._ -._-..-'.-’ .-’
22:31:20 redis_cache.1 | |-._-.
-.__.-' _.-'_.-'| 22:31:20 redis_cache.1 | | -.
-._ _.-'_.-' | 22:31:20 redis_cache.1 | -._ -._-.
.-‘_.-’ _.-’
22:31:20 redis_cache.1 | -._ -..-’ _.-’
22:31:20 redis_cache.1 | -._ _.-' 22:31:20 redis_cache.1 | -.
.-’
22:31:20 redis_cache.1 |
22:31:20 redis_cache.1 | [2474] 26 Feb 22:31:20.927 # Server started, Redis version 2.8.4
22:31:20 redis_cache.1 | [2474] 26 Feb 22:31:20.927 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add ‘vm.overcommit_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit_memory=1’ for this to take effect.
22:31:20 redis_cache.1 | [2474] 26 Feb 22:31:20.927 * The server is now ready to accept connections on port 13000
22:31:20 system | worker_short.1 started (pid=2472)
22:31:29 socketio.1 | listening on *: 9000
22:31:34 watch.1 | Please install yarn using below command and try again.
22:31:34 watch.1 | npm install -g yarn
22:31:34 worker_short.1 | 22:31:34 RQ worker u’rq:worker:erpnext.2484.short’ started, version 0.8.2
22:31:34 worker_short.1 | 22:31:34 Cleaning registries for queue: short
22:31:34 worker_long.1 | 22:31:34 RQ worker u’rq:worker:erpnext.2455.long’ started, version 0.8.2
22:31:34 worker_default.1 | 22:31:34 RQ worker u’rq:worker:erpnext.2463.default’ started, version 0.8.2
22:31:34 worker_long.1 | 22:31:34 Cleaning registries for queue: long
22:31:34 worker_short.1 | 22:31:34
22:31:34 worker_default.1 | 22:31:34 Cleaning registries for queue: default
22:31:34 worker_default.1 | 22:31:34
22:31:34 worker_default.1 | 22:31:34 *** Listening on default…
22:31:34 worker_long.1 | 22:31:34
22:31:34 worker_long.1 | 22:31:34 *** Listening on long…
22:31:34 worker_short.1 | 22:31:34 *** Listening on short…
22:31:35 web.1 | * Running on http://0.0.0.0:8000/ (Press CTRL+C to quit)
22:31:35 web.1 | * Restarting with inotify reloader
22:31:35 web.1 | * Debugger is active!
22:31:36 web.1 | * Debugger PIN: 269-523-967
22:31:39 watch.1 |
22:31:39 watch.1 | > frappe@ watch /home/frappe/frappe-bench/apps/frappe
22:31:39 watch.1 | > rollup -c -w
22:31:39 watch.1 |
22:31:39 watch.1 | sh: 1: rollup: not found
22:31:39 watch.1 |
22:31:39 watch.1 | npm ERR! Linux 3.13.0-79-generic
22:31:39 watch.1 | npm ERR! argv “/usr/bin/nodejs” “/usr/bin/npm” “run” “watch”
22:31:39 watch.1 | npm ERR! node v5.12.0
22:31:39 watch.1 | npm ERR! npm v3.8.6
22:31:39 watch.1 | npm ERR! file sh
22:31:39 watch.1 | npm ERR! code ELIFECYCLE
22:31:39 watch.1 | npm ERR! errno ENOENT
22:31:39 watch.1 | npm ERR! syscall spawn
22:31:39 watch.1 | npm ERR! frappe@ watch: rollup -c -w
22:31:39 watch.1 | npm ERR! spawn ENOENT
22:31:39 watch.1 | npm ERR!
22:31:39 watch.1 | npm ERR! Failed at the frappe@ watch script ‘rollup -c -w’.
22:31:39 watch.1 | npm ERR! Make sure you have the latest version of node.js and npm installed.
22:31:39 watch.1 | npm ERR! If you do, this is most likely a problem with the frappe package,
22:31:39 watch.1 | npm ERR! not with npm itself.
22:31:39 watch.1 | npm ERR! Tell the author that this fails on your system:
22:31:39 watch.1 | npm ERR! rollup -c -w
22:31:39 watch.1 | npm ERR! You can get information on how to open an issue for this project with:
22:31:39 watch.1 | npm ERR! npm bugs frappe
22:31:39 watch.1 | npm ERR! Or if that isn’t available, you can get their info via:
22:31:39 watch.1 | npm ERR! npm owner ls frappe
22:31:39 watch.1 | npm ERR! There is likely additional logging output above.
22:31:39 watch.1 |
22:31:39 watch.1 | npm ERR! Please include the following file with any support request:
22:31:39 watch.1 | npm ERR! /home/frappe/frappe-bench/apps/frappe/npm-debug.log
22:31:39 system | watch.1 stopped (rc=0)
22:31:39 system | sending SIGTERM to redis_socketio.1 (pid 2446)
22:31:39 system | sending SIGTERM to worker_long.1 (pid 2448)
22:31:39 system | sending SIGTERM to redis_queue.1 (pid 2456)
22:31:39 system | sending SIGTERM to web.1 (pid 2450)
22:31:39 system | sending SIGTERM to schedule.1 (pid 2449)
22:31:39 system | sending SIGTERM to worker_default.1 (pid 2451)
22:31:39 system | sending SIGTERM to socketio.1 (pid 2452)
22:31:39 system | sending SIGTERM to redis_cache.1 (pid 2460)
22:31:39 system | sending SIGTERM to worker_short.1 (pid 2472)
22:31:39 redis_socketio.1 | [2453 | signal handler] (1519713099) Received SIGTERM, scheduling shutdown…
22:31:39 redis_queue.1 | [2480 | signal handler] (1519713099) Received SIGTERM, scheduling shutdown…
22:31:39 redis_cache.1 | [2474 | signal handler] (1519713099) Received SIGTERM, scheduling shutdown…
22:31:39 system | schedule.1 stopped (rc=-15)
22:31:39 system | socketio.1 stopped (rc=-15)
22:31:39 worker_short.1 | 22:31:39 Warm shut down requested
22:31:39 worker_default.1 | 22:31:39 Warm shut down requested
22:31:39 worker_long.1 | 22:31:39 Warm shut down requested
22:31:39 redis_queue.1 | [2480] 26 Feb 22:31:39.832 # User requested shutdown…
22:31:39 redis_queue.1 | [2480] 26 Feb 22:31:39.832 # Redis is now ready to exit, bye bye…
22:31:39 system | redis_queue.1 stopped (rc=-15)
22:31:39 redis_cache.1 | [2474] 26 Feb 22:31:39.832 # User requested shutdown…
22:31:39 redis_cache.1 | [2474] 26 Feb 22:31:39.832 # Redis is now ready to exit, bye bye…
22:31:39 system | redis_cache.1 stopped (rc=-15)
22:31:39 redis_socketio.1 | [2453] 26 Feb 22:31:39.832 # User requested shutdown…
22:31:39 redis_socketio.1 | [2453] 26 Feb 22:31:39.832 # Redis is now ready to exit, bye bye…
22:31:39 system | redis_socketio.1 stopped (rc=-15)
22:31:39 system | worker_default.1 stopped (rc=-15)
22:31:39 system | worker_short.1 stopped (rc=-15)
22:31:39 system | worker_long.1 stopped (rc=-15)
22:31:39 web.1 | Exception in thread Thread-2 (most likely raised during interpreter shutdown):
22:31:39 web.1 | Traceback (most recent call last):
22:31:39 web.1 | File “/usr/lib/python2.7/threading.py”, line 810, in __bootstrap_inner
22:31:39 web.1 | File “/home/frappe/frappe-bench/env/local/lib/python2.7/site-packages/watchdog/observers/api.py”, line 237, in run
22:31:39 web.1 | <type ‘exceptions.AttributeError’>: ‘NoneType’ object has no attribute ‘Empty’
22:31:39 system | web.1 stopped (rc=-15)

I was using the official develop-vm image and updated the instance using bench update

Hi, please try to use master-branch, it works from my side.

Try this command

bench setup requirements