Bench start got stuck

ERPNext
1

Hello,
I am a newbie to erpnext, I followed the steps of easy install of erpnext then created new site: $ bench new-site mysite.com, then $ bench start. But I just got stuck there, I left the command to run for about 3 hours but just nothing happens, I also checked the site but it can not be loaded. The output as follows:

/opt/erpnext/frappe-bench$ bench start
02:26:01 system | worker_long.1 started (pid=6163)
02:26:01 system | watch.1 started (pid=6165)
02:26:01 system | redis_socketio.1 started (pid=6161)
02:26:01 redis_socketio.1 | 6167:C 08 Apr 02:26:01.835 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
02:26:01 redis_socketio.1 | 6167:C 08 Apr 02:26:01.835 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=6167, just started
02:26:01 redis_socketio.1 | 6167:C 08 Apr 02:26:01.835 # Configuration loaded
02:26:01 redis_socketio.1 | 6167:M 08 Apr 02:26:01.836 * Increased maximum number of open files to 10032 (it was originally set to 1024).
02:26:01 redis_socketio.1 | 6167:M 08 Apr 02:26:01.837 * Running mode=standalone, port=12001.
02:26:01 redis_socketio.1 | 6167:M 08 Apr 02:26:01.837 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
02:26:01 redis_socketio.1 | 6167:M 08 Apr 02:26:01.837 # Server initialized
02:26:01 redis_socketio.1 | 6167:M 08 Apr 02:26:01.837 # 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.
02:26:01 redis_socketio.1 | 6167:M 08 Apr 02:26:01.837 # 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.
02:26:01 redis_socketio.1 | 6167:M 08 Apr 02:26:01.837 * Ready to accept connections
02:26:01 system | web.1 started (pid=6173)
02:26:01 system | redis_queue.1 started (pid=6171)
02:26:01 redis_queue.1 | 6185:C 08 Apr 02:26:01.839 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
02:26:01 redis_queue.1 | 6185:C 08 Apr 02:26:01.839 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=6185, just started
02:26:01 redis_queue.1 | 6185:C 08 Apr 02:26:01.839 # Configuration loaded
02:26:01 redis_queue.1 | 6185:M 08 Apr 02:26:01.841 * Increased maximum number of open files to 10032 (it was originally set to 1024).
02:26:01 redis_queue.1 | 6185:M 08 Apr 02:26:01.842 * Running mode=standalone, port=11001.
02:26:01 redis_queue.1 | 6185:M 08 Apr 02:26:01.842 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
02:26:01 redis_queue.1 | 6185:M 08 Apr 02:26:01.842 # Server initialized
02:26:01 redis_queue.1 | 6185:M 08 Apr 02:26:01.842 # 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.
02:26:01 redis_queue.1 | 6185:M 08 Apr 02:26:01.842 # 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.
02:26:01 redis_queue.1 | 6185:M 08 Apr 02:26:01.842 * Ready to accept connections
02:26:01 system | schedule.1 started (pid=6177)
02:26:01 system | worker_short.1 started (pid=6191)
02:26:01 system | redis_cache.1 started (pid=6189)
02:26:01 system | socketio.1 started (pid=6190)
02:26:01 system | worker_default.1 started (pid=6180)
02:26:01 redis_cache.1 | 6196:C 08 Apr 02:26:01.846 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
02:26:01 redis_cache.1 | 6196:C 08 Apr 02:26:01.846 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=6196, just started
02:26:01 redis_cache.1 | 6196:C 08 Apr 02:26:01.846 # Configuration loaded
02:26:01 redis_cache.1 | 6196:M 08 Apr 02:26:01.847 * Increased maximum number of open files to 10032 (it was originally set to 1024).
02:26:01 redis_cache.1 | 6196:M 08 Apr 02:26:01.847 * Running mode=standalone, port=13001.
02:26:01 redis_cache.1 | 6196:M 08 Apr 02:26:01.847 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
02:26:01 redis_cache.1 | 6196:M 08 Apr 02:26:01.847 # Server initialized
02:26:01 redis_cache.1 | 6196:M 08 Apr 02:26:01.847 # 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.
02:26:01 redis_cache.1 | 6196:M 08 Apr 02:26:01.847 # 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.
02:26:01 redis_cache.1 | 6196:M 08 Apr 02:26:01.848 * Ready to accept connections
02:26:02 socketio.1 | listening on *: 9001
02:26:03 watch.1 | yarn run v1.15.2
02:26:04 watch.1 | $ node rollup/watch.js
02:26:04 web.1 | * Running on http://0.0.0.0:8001/ (Press CTRL+C to quit)
02:26:04 web.1 | * Restarting with inotify reloader
02:26:04 web.1 | * Debugger is active!
02:26:04 web.1 | * Debugger PIN: 933-809-480
02:26:05 watch.1 |
02:26:05 watch.1 | Rollup Watcher Started
02:26:05 watch.1 |
02:26:05 watch.1 | Watching…
02:26:05 watch.1 | Rebuilding frappe-web.css
02:26:05 watch.1 | Rebuilding frappe-web-b4.css
02:26:05 watch.1 | Rebuilding chat.js
02:26:07 watch.1 | Rebuilding frappe-recorder.min.js
02:26:10 watch.1 | Rebuilding frappe-web.min.js
02:26:12 watch.1 | Rebuilding bootstrap-4-web.min.js
02:26:13 watch.1 | Rebuilding control.min.js
02:26:15 watch.1 | Rebuilding dialog.min.js
02:26:16 watch.1 | Rebuilding desk.min.css
02:26:16 watch.1 | Rebuilding frappe-rtl.css
02:26:16 watch.1 | Rebuilding desk.min.js
02:26:19 watch.1 | Rebuilding module.min.css
02:26:19 watch.1 | Rebuilding form.min.css
02:26:19 watch.1 | Rebuilding form.min.js
02:26:20 watch.1 | Rebuilding list.min.css
02:26:20 watch.1 | Rebuilding list.min.js
02:26:21 watch.1 | Rebuilding report.min.css
02:26:21 watch.1 | Rebuilding report.min.js
02:26:22 watch.1 | Rebuilding web_form.min.js
02:26:23 watch.1 | Rebuilding web_form.css
02:26:23 watch.1 | Rebuilding print_format_v3.min.js
02:26:23 watch.1 | Rebuilding email.css
02:26:23 watch.1 | Rebuilding social.min.js
02:26:24 watch.1 | Rebuilding modules.min.js

Please help me figure this out.
Thanks.

2

Looks to me like it started OK
If you point a browser to the IP of that box at port 8001 do you see the config wizard prompting you for the setup values?

If not, maybe try
sudo netstat -plnt
is 0.0.0.0:8001 in the list?
Maybe look at ufw or iptables or whatever your distro uses for firewall

3

First thanks for your reply, If I point the browser to mysite.com:8000, the page does not load. Is that what you mean?
I tried sudo netstat-plnt, but I got this error: sudo: netstat-plnt: command not found.

4

There’s a space between netstat and -pint.

Are you trying to access the site from the same machine that runs bench start? If so, try accessing localhost:8000.

5

Hello Igrekus, Thanks for your reply.
I tried sudo netstat -plnt but still I get the same no command error.
I tried accessing localhost:8000, but can not load too.
What shall I run now?

6

What does this give you?

cd ~/frappe-bench
sudo systemctl status supervisor

7

Hello Trentmu, thanks for your reply.
This is the output of ‘sudo systemctl status supervisor’:
ctl status supervisor
● supervisor.service
Loaded: masked (/dev/null; bad)
Active: inactive (dead)

8

The supervisor process has exited/ended - restart it with this

sudo systemctl restart supervisor

9

I got this output for ‘sudo systemctl restart supervisor’:
Failed to restart supervisor.service: Unit supervisor.service is masked.

10

Hello trentmu,
-I installed the supervisor
-ran ‘sudo systemctl restart supervisor’
-then ran ‘sudo systemctl status supervisor’ again
and got this output :
● supervisor.service - Supervisor process control system for UNIX
Loaded: loaded (/lib/systemd/system/supervisor.service; enabled; vendor prese
Active: active (running) since Mon 2019-04-08 15:02:10 EET; 53s ago
Docs: http://supervisord.org
Process: 8950 ExecStop=/usr/bin/supervisorctl $OPTIONS shutdown (code=exited,
Main PID: 8951 (supervisord)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/supervisor.service
└─8951 /usr/bin/python /usr/bin/supervisord -n -c /etc/supervisor/sup

Apr 08 15:02:10 hagar-HP-OMEN-Notebook-PC-15 systemd[1]: Started Supervisor proc
Apr 08 15:02:10 hagar-HP-OMEN-Notebook-PC-15 supervisord[8951]: 2019-04-08 15:02
Apr 08 15:02:10 hagar-HP-OMEN-Notebook-PC-15 supervisord[8951]: 2019-04-08 15:02
Apr 08 15:02:10 hagar-HP-OMEN-Notebook-PC-15 supervisord[8951]: 2019-04-08 15:02
Apr 08 15:02:10 hagar-HP-OMEN-Notebook-PC-15 supervisord[8951]: 2019-04-08 15:02
Apr 08 15:02:10 hagar-HP-OMEN-Notebook-PC-15 supervisord[8951]: 2019-04-08 15:02
lines 1-16/16 (END)

11

OK - that should be better. Now try your other commands

12

Hi trentmu,
I tried bench start but got stuck again. I do not know why when this line
‘15:17:51 watch.1 | Rebuilding modules.min.js’
is reached, the command just gets stuck .

13

I reread your original post - and saw the ports that are assigned both have the extra 1 (normally they are 8000 and 9000) - which implies that a 2nd copy of the system is already running but on different ports. I recommend that you restart the machine or VM

14

Hi,
Just restart the vm? btw I m using ubuntu but not on vm.
What do I do now?

15

If you are in GUI mode, you can use the bottom left “start button”, otherwise in a terminal, run

sudo reboot

or

sudo shutdown -r now

16

Hi,
Ok I will reboot ubuntu, and then run bench start again?

17

If you installed production mode, then it should start by itself. If you did development, you need to run bench start

18

Hello trentmu,
I rebooted ubuntu and ran bench start again, tried mysite1.com:8001, but still can not load.

19

By default it is port 8000 (not 8001)

20

Hello
Tried port 8000 but still can not load, also bench start is still stuck. Can I try something else?
And why do I always get stuck when line:
16:41:11 watch.1 | Rebuilding modules.min.js
is reached