ERPNext Foundation ERPNext Cloud User Manual Blog Discuss Frappé* Donate

Bench not Working : Stuck on Rebuilding list.min.js JS file


#1

Hi Team,

I reinstall ERPNext on AWS instance.When I run Bench Start command , getting stuck in some js file…

bench@ip-x.x.x.x:~/erpnext$ bench start
05:34:47 system | watch.1 started (pid=2879)
05:34:47 system | worker_long.1 started (pid=2880)
05:34:47 system | redis_queue.1 started (pid=2881)
05:34:47 system | redis_socketio.1 started (pid=2883)
05:34:47 system | schedule.1 started (pid=2882)
05:34:47 system | redis_cache.1 started (pid=2885)
05:34:47 system | worker_default.1 started (pid=2884)
05:34:47 system | web.1 started (pid=2889)
05:34:47 redis_queue.1 | 2892:C 12 Aug 05:34:47.921 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
05:34:47 redis_queue.1 | 2892:C 12 Aug 05:34:47.921 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=2892, just started
05:34:47 redis_queue.1 | 2892:C 12 Aug 05:34:47.921 # Configuration loaded
05:34:47 redis_socketio.1 | 2891:C 12 Aug 05:34:47.923 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
05:34:47 redis_socketio.1 | 2891:C 12 Aug 05:34:47.923 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=2891, just started
05:34:47 redis_socketio.1 | 2891:C 12 Aug 05:34:47.923 # Configuration loaded
05:34:47 redis_socketio.1 | 2891:M 12 Aug 05:34:47.924 * Increased maximum number of open files to 10032 (it was originally set to 1024).
05:34:47 system | socketio.1 started (pid=2896)
05:34:47 redis_queue.1 | 2892:M 12 Aug 05:34:47.930 * Increased maximum number of open files to 10032 (it was originally set to 1024).
05:34:47 redis_cache.1 | 2898:C 12 Aug 05:34:47.931 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
05:34:47 redis_cache.1 | 2898:C 12 Aug 05:34:47.932 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=2898, just started
05:34:47 redis_cache.1 | 2898:C 12 Aug 05:34:47.932 # Configuration loaded
05:34:47 redis_queue.1 | 2892:M 12 Aug 05:34:47.937 * Running mode=standalone, port=11000.
05:34:47 redis_queue.1 | 2892:M 12 Aug 05:34:47.937 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
05:34:47 redis_queue.1 | 2892:M 12 Aug 05:34:47.937 # Server initialized
05:34:47 redis_queue.1 | 2892:M 12 Aug 05:34:47.937 # 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.
05:34:47 redis_queue.1 | 2892:M 12 Aug 05:34:47.938 # 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.
05:34:47 redis_cache.1 | 2898:M 12 Aug 05:34:47.938 * Increased maximum number of open files to 10032 (it was originally set to 1024).
05:34:47 redis_cache.1 | 2898:M 12 Aug 05:34:47.939 * Running mode=standalone, port=13000.
05:34:47 redis_cache.1 | 2898:M 12 Aug 05:34:47.939 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
05:34:47 redis_cache.1 | 2898:M 12 Aug 05:34:47.939 # Server initialized
05:34:47 redis_cache.1 | 2898:M 12 Aug 05:34:47.940 # 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.
05:34:47 redis_cache.1 | 2898:M 12 Aug 05:34:47.940 # 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.
05:34:47 redis_queue.1 | 2892:M 12 Aug 05:34:47.940 * Ready to accept connections
05:34:47 redis_socketio.1 | 2891:M 12 Aug 05:34:47.941 * Running mode=standalone, port=12000.
05:34:47 redis_socketio.1 | 2891:M 12 Aug 05:34:47.941 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
05:34:47 redis_socketio.1 | 2891:M 12 Aug 05:34:47.941 # Server initialized
05:34:47 redis_socketio.1 | 2891:M 12 Aug 05:34:47.941 # 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.
05:34:47 redis_socketio.1 | 2891:M 12 Aug 05:34:47.942 # 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.
05:34:47 redis_socketio.1 | 2891:M 12 Aug 05:34:47.942 * Ready to accept connections
05:34:47 system | worker_short.1 started (pid=2900)
05:34:47 redis_cache.1 | 2898:M 12 Aug 05:34:47.947 * Ready to accept connections
05:34:50 socketio.1 | listening on *: 9000
05:35:01 web.1 | * Running on http://0.0.0.0:8000/ (Press CTRL+C to quit)
05:35:01 web.1 | * Restarting with inotify reloader
05:35:02 watch.1 | yarn run v1.16.0
05:35:02 watch.1 | $ node rollup/watch.js
05:35:03 web.1 | * Debugger is active!
05:35:03 web.1 | * Debugger PIN: 137-688-613
05:35:05 watch.1 |
05:35:05 watch.1 | Rollup Watcher Started
05:35:05 watch.1 |
05:35:05 watch.1 | Watching…
05:35:06 watch.1 | Rebuilding frappe-web.css
05:35:07 watch.1 | Rebuilding frappe-web-b4.css
05:35:07 watch.1 | Rebuilding chat.js
05:35:10 web.1 | 122.171.97.240 - - [12/Aug/2019 05:35:10] “GET / HTTP/1.1” 301 -
05:35:10 web.1 | INFO:werkzeug:122.171.97.240 - - [12/Aug/2019 05:35:10] “GET / HTTP/1.1” 301 -
05:35:10 watch.1 | Rebuilding frappe-recorder.min.js
05:35:13 web.1 | fatal: Needed a single revision
05:35:13 web.1 | fatal: Needed a single revision
05:35:17 watch.1 | Rebuilding frappe-web.min.js
05:35:19 web.1 | fatal: Needed a single revision
05:35:19 web.1 | fatal: Needed a single revision
05:35:19 web.1 | 122.171.97.240 - - [12/Aug/2019 05:35:19] “GET /desk HTTP/1.1” 200 -
05:35:19 web.1 | INFO:werkzeug:122.171.97.240 - - [12/Aug/2019 05:35:19] “GET /desk HTTP/1.1” 200 -
05:35:20 watch.1 | Rebuilding bootstrap-4-web.min.js
05:35:21 web.1 | 122.171.97.240 - - [12/Aug/2019 05:35:21] “POST /api/method/frappe.client.get_hooks HTTP/1.1” 200 -
05:35:21 web.1 | INFO:werkzeug:122.171.97.240 - - [12/Aug/2019 05:35:21] “POST /api/method/frappe.client.get_hooks HTTP/1.1” 200 -
05:35:21 web.1 | 122.171.97.240 - - [12/Aug/2019 05:35:21] “POST /api/method/frappe.utils.change_log.show_update_popup HTTP/1.1” 200 -
05:35:21 web.1 | INFO:werkzeug:122.171.97.240 - - [12/Aug/2019 05:35:21] “POST /api/method/frappe.utils.change_log.show_update_popup HTTP/1.1” 200 -
05:35:21 web.1 | 122.171.97.240 - - [12/Aug/2019 05:35:21] “POST /api/method/frappe.core.doctype.user_permission.user_permission.get_user_permissions HTTP/1.1” 200 -
05:35:21 web.1 | INFO:werkzeug:122.171.97.240 - - [12/Aug/2019 05:35:21] “POST /api/method/frappe.core.doctype.user_permission.user_permission.get_user_permissions HTTP/1.1” 200 -
05:35:21 web.1 | 122.171.97.240 - - [12/Aug/2019 05:35:21] “POST /api/method/erpnext.accounts.doctype.accounting_dimension.accounting_dimension.get_dimension_filters HTTP/1.1” 200 -
05:35:21 web.1 | INFO:werkzeug:122.171.97.240 - - [12/Aug/2019 05:35:21] “POST /api/method/erpnext.accounts.doctype.accounting_dimension.accounting_dimension.get_dimension_filters HTTP/1.1” 200 -
05:35:21 web.1 | 3.14.82.98 - - [12/Aug/2019 05:35:21] “GET /api/method/frappe.realtime.get_user_info?sid=d1b75ea743ee1dd3d9c65a144e8fda068fb8d547ab041fdfe98e5c12 HTTP/1.1” 200 -
05:35:21 web.1 | INFO:werkzeug:3.14.82.98 - - [12/Aug/2019 05:35:21] “GET /api/method/frappe.realtime.get_user_info?sid=d1b75ea743ee1dd3d9c65a144e8fda068fb8d547ab041fdfe98e5c12 HTTP/1.1” 200 -
05:35:22 web.1 | 122.171.97.240 - - [12/Aug/2019 05:35:22] “POST /api/method/frappe.chat.doctype.chat_profile.chat_profile.create HTTP/1.1” 200 -
05:35:22 web.1 | INFO:werkzeug:122.171.97.240 - - [12/Aug/2019 05:35:22] “POST /api/method/frappe.chat.doctype.chat_profile.chat_profile.create HTTP/1.1” 200 -
05:35:22 web.1 | 122.171.97.240 - - [12/Aug/2019 05:35:22] “GET /api/method/frappe.model.db_query.get_list?filters=%7B%22user%22%3A%22pragyad%40appodeepo.com%22%2C%22type%22%3A%5B%22not+in%22%2C%5B%22Review%22%5D%5D%7D&fields=%5B%22name%22%2C%22user%22%2C%22points%22%2C%22reference_doctype%22%2C%22reference_name%22%2C%22reason%22%2C%22type%22%2C%22seen%22%2C%22rule%22%2C%22owner%22%2C%22creation%22%5D&limit=20&order_by=creation+desc&doctype=Energy+Point+Log&=1565588119450 HTTP/1.1" 200 -
05:35:22 web.1 | INFO:werkzeug:122.171.97.240 - - [12/Aug/2019 05:35:22] "GET /api/method/frappe.model.db_query.get_list?filters=%7B%22user%22%3A%22pragyad%40appodeepo.com%22%2C%22type%22%3A%5B%22not+in%22%2C%5B%22Review%22%5D%5D%7D&fields=%5B%22name%22%2C%22user%22%2C%22points%22%2C%22reference_doctype%22%2C%22reference_name%22%2C%22reason%22%2C%22type%22%2C%22seen%22%2C%22rule%22%2C%22owner%22%2C%22creation%22%5D&limit=20&order_by=creation+desc&doctype=Energy+Point+Log&
=1565588119450 HTTP/1.1” 200 -
05:35:22 web.1 | 122.171.97.240 - - [12/Aug/2019 05:35:22] “POST /api/method/frappe.chat.doctype.chat_profile.chat_profile.create HTTP/1.1” 200 -
05:35:22 web.1 | INFO:werkzeug:122.171.97.240 - - [12/Aug/2019 05:35:22] “POST /api/method/frappe.chat.doctype.chat_profile.chat_profile.create HTTP/1.1” 200 -
05:35:22 web.1 | 122.171.97.240 - - [12/Aug/2019 05:35:22] “POST /api/method/frappe.chat.doctype.chat_profile.chat_profile.create HTTP/1.1” 200 -
05:35:22 web.1 | INFO:werkzeug:122.171.97.240 - - [12/Aug/2019 05:35:22] “POST /api/method/frappe.chat.doctype.chat_profile.chat_profile.create HTTP/1.1” 200 -
05:35:23 web.1 | 122.171.97.240 - - [12/Aug/2019 05:35:23] “GET /api/method/frappe.desk.notifications.get_notifications?=1565588119451 HTTP/1.1" 200 -
05:35:23 web.1 | INFO:werkzeug:122.171.97.240 - - [12/Aug/2019 05:35:23] "GET /api/method/frappe.desk.notifications.get_notifications?
=1565588119451 HTTP/1.1” 200 -
05:35:23 web.1 | 122.171.97.240 - - [12/Aug/2019 05:35:23] “POST /api/method/frappe.desk.moduleview.get_desktop_settings HTTP/1.1” 200 -
05:35:23 web.1 | INFO:werkzeug:122.171.97.240 - - [12/Aug/2019 05:35:23] “POST /api/method/frappe.desk.moduleview.get_desktop_settings HTTP/1.1” 200 -
05:35:23 watch.1 | Rebuilding control.min.js
05:35:23 web.1 | 122.171.97.240 - - [12/Aug/2019 05:35:23] “POST /api/method/frappe.chat.doctype.chat_room.chat_room.get HTTP/1.1” 200 -
05:35:23 web.1 | INFO:werkzeug:122.171.97.240 - - [12/Aug/2019 05:35:23] “POST /api/method/frappe.chat.doctype.chat_room.chat_room.get HTTP/1.1” 200 -
05:35:26 watch.1 | Rebuilding dialog.min.js
05:35:27 watch.1 | Rebuilding desk.min.css
05:35:27 watch.1 | Rebuilding frappe-rtl.css
05:35:28 watch.1 | Rebuilding printview.css
05:35:28 watch.1 | Rebuilding desk.min.js
05:35:37 watch.1 | Rebuilding module.min.css
05:35:37 watch.1 | Rebuilding form.min.css
05:35:37 watch.1 | Rebuilding form.min.js
05:35:57 watch.1 | Rebuilding list.min.css
05:35:58 watch.1 | Rebuilding list.min.js

How to solve this ???


#2

hi i have face this problem my ram was 1 so i increase it to 2 or 4 i don’t remember but the problem solved for me