I TRIED TO RUN BENCH START IM STILL GETTING AN ERROR
20:22:38 system | web.1 started (pid=2599)
20:22:38 system | worker_short.1 started (pid=2600)
20:22:38 system | schedule.1 started (pid=2601)
20:22:38 system | redis_socketio.1 started (pid=2598)
20:22:38 redis_socketio.1 | 2611:M 01 Mar 20:22:38.226 * Increased maximum number of open files to 10032 (it was originally set to 1024).
20:22:38 redis_socketio.1 | .
20:22:38 redis_socketio.1 | .-__ ''-._ 20:22:38 redis_socketio.1 | _.- . . ‘’-._ Redis 3.0.6 (00000000/0) 64 bit
20:22:38 redis_socketio.1 | .- .-```. ```\/ _.,_ ''-._ 20:22:38 redis_socketio.1 | ( ' , .-` | `, ) Running in standalone mode 20:22:38 redis_socketio.1 | |`-._`-...-` __...-.-.|'_.-'| Port: 12000 20:22:38 redis_socketio.1 | | -. ._ / _.-' | PID: 2611 20:22:38 redis_socketio.1 | -._ -._ -./ .-’ .-’
20:22:38 redis_socketio.1 | |-._-. -.__.-' _.-'_.-'| 20:22:38 redis_socketio.1 | | -.-._ _.-'_.-' | http://redis.io 20:22:38 redis_socketio.1 | -._ -._-..-'.-’ .-’
20:22:38 redis_socketio.1 | |-._-. -.__.-' _.-'_.-'| 20:22:38 redis_socketio.1 | | -.-._ _.-'_.-' | 20:22:38 redis_socketio.1 | -._ -._-..-‘.-’ .-’
20:22:38 redis_socketio.1 | -._ -..-’ _.-’
20:22:38 redis_socketio.1 | -._ _.-' 20:22:38 redis_socketio.1 | -..-’
20:22:38 redis_socketio.1 |
20:22:38 redis_socketio.1 | 2611:M 01 Mar 20:22:38.235 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
20:22:38 redis_socketio.1 | 2611:M 01 Mar 20:22:38.235 # Server started, Redis version 3.0.6
20:22:38 redis_socketio.1 | 2611:M 01 Mar 20:22:38.235 # 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.
20:22:38 redis_socketio.1 | 2611:M 01 Mar 20:22:38.235 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command ‘echo never > /sys/kernel/mm/transparent_hugepage/enabled’ as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
20:22:38 redis_socketio.1 | 2611:M 01 Mar 20:22:38.235 * The server is now ready to accept connections on port 12000
20:22:38 system | watch.1 started (pid=2604)
20:22:38 system | redis_cache.1 started (pid=2607)
20:22:38 redis_cache.1 | 2623:M 01 Mar 20:22:38.293 * Increased maximum number of open files to 10032 (it was originally set to 1024).
20:22:38 redis_cache.1 | .
20:22:38 redis_cache.1 | .-__ ''-._ 20:22:38 redis_cache.1 | _.- . . ‘’-. Redis 3.0.6 (00000000/0) 64 bit
20:22:38 redis_cache.1 | .- .-```. ```\/ _.,_ ''-._ 20:22:38 redis_cache.1 | ( ' , .-` | `, ) Running in standalone mode 20:22:38 redis_cache.1 | |`-._`-...-` __...-.-.|’_.-'| Port: 13000 20:22:38 redis_cache.1 | | -._ ._ / _.-' | PID: 2623 20:22:38 redis_cache.1 | -._ -._ -./ .-’ .-’
20:22:38 redis_cache.1 | |-._-. -.__.-' _.-'_.-'| 20:22:38 redis_cache.1 | | -.-._ _.-'_.-' | http://redis.io 20:22:38 redis_cache.1 | -._ -._-..-'.-’ .-’
20:22:38 redis_cache.1 | |-._-. -.__.-' _.-'_.-'| 20:22:38 redis_cache.1 | | -.-._ _.-'_.-' | 20:22:38 redis_cache.1 | -._ -._-..-‘.-’ .-’
20:22:38 redis_cache.1 | -._ -..-’ _.-’
20:22:38 redis_cache.1 | -._ _.-' 20:22:38 redis_cache.1 | -..-’
20:22:38 redis_cache.1 |
20:22:38 redis_cache.1 | 2623:M 01 Mar 20:22:38.293 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
20:22:38 redis_cache.1 | 2623:M 01 Mar 20:22:38.293 # Server started, Redis version 3.0.6
20:22:38 redis_cache.1 | 2623:M 01 Mar 20:22:38.293 # 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.
20:22:38 redis_cache.1 | 2623:M 01 Mar 20:22:38.293 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command ‘echo never > /sys/kernel/mm/transparent_hugepage/enabled’ as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
20:22:38 redis_cache.1 | 2623:M 01 Mar 20:22:38.293 * The server is now ready to accept connections on port 13000
20:22:38 system | worker_long.1 started (pid=2609)
20:22:38 system | socketio.1 started (pid=2621)
20:22:38 system | redis_queue.1 started (pid=2626)
20:22:38 redis_queue.1 | 2637:M 01 Mar 20:22:38.402 * Increased maximum number of open files to 10032 (it was originally set to 1024).
20:22:38 redis_queue.1 | .
20:22:38 redis_queue.1 | .-__ ''-._ 20:22:38 redis_queue.1 | _.- . . ‘’-. Redis 3.0.6 (00000000/0) 64 bit
20:22:38 redis_queue.1 | .- .-```. ```\/ _.,_ ''-._ 20:22:38 redis_queue.1 | ( ' , .-` | `, ) Running in standalone mode 20:22:38 redis_queue.1 | |`-._`-...-` __...-.-.|’_.-'| Port: 11000 20:22:38 redis_queue.1 | | -._ ._ / _.-' | PID: 2637 20:22:38 redis_queue.1 | -._ -._ -./ .-’ .-’
20:22:38 redis_queue.1 | |-._-. -.__.-' _.-'_.-'| 20:22:38 redis_queue.1 | | -.-._ _.-'_.-' | http://redis.io 20:22:38 redis_queue.1 | -._ -._-..-'.-’ .-’
20:22:38 redis_queue.1 | |-._-. -.__.-' _.-'_.-'| 20:22:38 redis_queue.1 | | -.-._ _.-'_.-' | 20:22:38 redis_queue.1 | -._ -._-..-‘_.-’ _.-’
20:22:38 redis_queue.1 | -._ -..-’ _.-’
20:22:38 redis_queue.1 | -._ _.-' 20:22:38 redis_queue.1 | -..-’
20:22:38 redis_queue.1 |
20:22:38 redis_queue.1 | 2637:M 01 Mar 20:22:38.403 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
20:22:38 redis_queue.1 | 2637:M 01 Mar 20:22:38.403 # Server started, Redis version 3.0.6
20:22:38 redis_queue.1 | 2637:M 01 Mar 20:22:38.403 # 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.
20:22:38 redis_queue.1 | 2637:M 01 Mar 20:22:38.403 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command ‘echo never > /sys/kernel/mm/transparent_hugepage/enabled’ as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
20:22:38 redis_queue.1 | 2637:M 01 Mar 20:22:38.403 * The server is now ready to accept connections on port 11000
20:22:38 system | worker_default.1 started (pid=2635)
20:22:41 socketio.1 | listening on *: 9000
20:22:49 worker_short.1 | 20:22:49 RQ worker u’rq:worker:ubuntu.2606.short’ started, version 0.10.0
20:22:49 worker_short.1 | 20:22:49 *** Listening on short…
20:22:49 worker_short.1 | 20:22:49 Cleaning registries for queue: short
20:22:49 watch.1 | Please install yarn using below command and try again.
20:22:49 watch.1 | npm install -g yarn
20:22:49 web.1 | * Running on http://0.0.0.0:8000/ (Press CTRL+C to quit)
20:22:49 worker_default.1 | 20:22:49 RQ worker u’rq:worker:ubuntu.2641.default’ started, version 0.10.0
20:22:49 worker_default.1 | 20:22:49 *** Listening on default…
20:22:49 worker_default.1 | 20:22:49 Cleaning registries for queue: default
20:22:49 web.1 | * Restarting with inotify reloader
20:22:49 worker_long.1 | 20:22:49 RQ worker u’rq:worker:ubuntu.2627.long’ started, version 0.10.0
20:22:49 worker_long.1 | 20:22:49 *** Listening on long…
20:22:49 worker_long.1 | 20:22:49 Cleaning registries for queue: long
20:22:50 watch.1 |
20:22:50 watch.1 | > frappe@ watch /home/tluanga/bench-repo/frappe-bench/apps/frappe
20:22:50 watch.1 | > rollup -c -w
20:22:50 watch.1 |
20:22:50 watch.1 | sh: 1: rollup: not found
20:22:50 watch.1 |
20:22:50 watch.1 | npm ERR! Linux 4.4.0-87-generic
20:22:50 watch.1 | npm ERR! argv “/usr/bin/nodejs” “/usr/bin/npm” “run” “watch”
20:22:50 watch.1 | npm ERR! node v4.2.6
20:22:50 watch.1 | npm ERR! npm v3.5.2
20:22:50 watch.1 | npm ERR! file sh
20:22:50 watch.1 | npm ERR! code ELIFECYCLE
20:22:50 watch.1 | npm ERR! errno ENOENT
20:22:50 watch.1 | npm ERR! syscall spawn
20:22:50 watch.1 | npm ERR! frappe@ watch: rollup -c -w
20:22:50 watch.1 | npm ERR! spawn ENOENT
20:22:50 watch.1 | npm ERR!
20:22:50 watch.1 | npm ERR! Failed at the frappe@ watch script ‘rollup -c -w’.
20:22:50 watch.1 | npm ERR! Make sure you have the latest version of node.js and npm installed.
20:22:50 watch.1 | npm ERR! If you do, this is most likely a problem with the frappe package,
20:22:50 watch.1 | npm ERR! not with npm itself.
20:22:50 watch.1 | npm ERR! Tell the author that this fails on your system:
20:22:50 watch.1 | npm ERR! rollup -c -w
20:22:50 watch.1 | npm ERR! You can get information on how to open an issue for this project with:
20:22:50 watch.1 | npm ERR! npm bugs frappe
20:22:50 watch.1 | npm ERR! Or if that isn’t available, you can get their info via:
20:22:50 watch.1 | npm ERR! npm owner ls frappe
20:22:50 watch.1 | npm ERR! There is likely additional logging output above.
20:22:50 watch.1 |
20:22:50 watch.1 | npm ERR! Please include the following file with any support request:
20:22:50 watch.1 | npm ERR! /home/tluanga/bench-repo/frappe-bench/apps/frappe/npm-debug.log
20:22:50 web.1 | * Debugger is active!
20:22:50 web.1 | * Debugger PIN: 167-518-630
20:22:50 system | watch.1 stopped (rc=0)
20:22:50 system | sending SIGTERM to web.1 (pid 2599)
20:22:50 system | sending SIGTERM to redis_socketio.1 (pid 2598)
20:22:50 system | sending SIGTERM to worker_short.1 (pid 2600)
20:22:50 system | sending SIGTERM to schedule.1 (pid 2601)
20:22:50 system | sending SIGTERM to redis_cache.1 (pid 2607)
20:22:50 system | sending SIGTERM to worker_long.1 (pid 2609)
20:22:50 system | sending SIGTERM to socketio.1 (pid 2621)
20:22:50 system | sending SIGTERM to redis_queue.1 (pid 2626)
20:22:50 system | sending SIGTERM to worker_default.1 (pid 2635)
20:22:50 redis_socketio.1 | 2611:signal-handler (1519964570) Received SIGTERM scheduling shutdown…
20:22:50 worker_short.1 | 20:22:50 Warm shut down requested
20:22:50 system | schedule.1 stopped (rc=-15)
20:22:50 redis_cache.1 | 2623:signal-handler (1519964570) Received SIGTERM scheduling shutdown…
20:22:50 worker_long.1 | 20:22:50 Warm shut down requested
20:22:50 system | socketio.1 stopped (rc=-15)
20:22:50 redis_queue.1 | 2637:signal-handler (1519964570) Received SIGTERM scheduling shutdown…
20:22:50 worker_default.1 | 20:22:50 Warm shut down requested
20:22:50 redis_socketio.1 | 2611:M 01 Mar 20:22:50.737 # User requested shutdown…
20:22:50 redis_socketio.1 | 2611:M 01 Mar 20:22:50.737 # Redis is now ready to exit, bye bye…
20:22:50 system | redis_socketio.1 stopped (rc=-15)
20:22:50 redis_queue.1 | 2637:M 01 Mar 20:22:50.809 # User requested shutdown…
20:22:50 redis_queue.1 | 2637:M 01 Mar 20:22:50.809 # Redis is now ready to exit, bye bye…
20:22:50 system | redis_queue.1 stopped (rc=-15)
20:22:50 redis_cache.1 | 2623:M 01 Mar 20:22:50.813 # User requested shutdown…
20:22:50 redis_cache.1 | 2623:M 01 Mar 20:22:50.813 # Redis is now ready to exit, bye bye…
20:22:50 system | redis_cache.1 stopped (rc=-15)
20:22:50 system | worker_short.1 stopped (rc=-15)
20:22:50 system | worker_default.1 stopped (rc=-15)
20:22:50 system | worker_long.1 stopped (rc=-15)
20:22:51 system | web.1 stopped (rc=-15)