After installed ERPNext on Ubuntu not able to open it on brower

sudo bench start
14:10:03 system | redis_socketio.1 started (pid=8356)
14:10:03 redis_socketio.1 | 8360:C 20 Apr 2022 14:10:03.127 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
14:10:03 redis_socketio.1 | 8360:C 20 Apr 2022 14:10:03.127 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=8360, just started
14:10:03 redis_socketio.1 | 8360:C 20 Apr 2022 14:10:03.127 # Configuration loaded
14:10:03 redis_socketio.1 | 8360:M 20 Apr 2022 14:10:03.128 * Increased maximum number of open files to 10032 (it was originally set to 1024).
14:10:03 redis_socketio.1 | 8360:M 20 Apr 2022 14:10:03.128 # Could not create server TCP listening socket 127.0.0.1:12000: bind: Address already in use
14:10:03 system | redis_socketio.1 stopped (rc=1)
14:10:03 system | worker_short.1 started (pid=8377)
14:10:03 system | watch.1 started (pid=8372)
14:10:03 system | socketio.1 started (pid=8374)
14:10:03 system | worker_long.1 started (pid=8378)
14:10:03 system | web.1 started (pid=8361)
14:10:03 system | redis_cache.1 started (pid=8355)
14:10:03 redis_cache.1 | 8365:C 20 Apr 2022 14:10:03.128 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
14:10:03 redis_cache.1 | 8365:C 20 Apr 2022 14:10:03.128 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=8365, just started
14:10:03 redis_cache.1 | 8365:C 20 Apr 2022 14:10:03.128 # Configuration loaded
14:10:03 redis_cache.1 | 8365:M 20 Apr 2022 14:10:03.135 * Increased maximum number of open files to 10032 (it was originally set to 1024).
14:10:03 redis_cache.1 | 8365:M 20 Apr 2022 14:10:03.135 # Could not create server TCP listening socket 127.0.0.1:13000: bind: Address already in use
14:10:03 system | redis_cache.1 stopped (rc=1)
14:10:03 system | redis_queue.1 started (pid=8358)
14:10:03 redis_queue.1 | 8363:C 20 Apr 2022 14:10:03.127 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
14:10:03 redis_queue.1 | 8363:C 20 Apr 2022 14:10:03.127 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=8363, just started
14:10:03 redis_queue.1 | 8363:C 20 Apr 2022 14:10:03.127 # Configuration loaded
14:10:03 redis_queue.1 | 8363:M 20 Apr 2022 14:10:03.128 * Increased maximum number of open files to 10032 (it was originally set to 1024).
14:10:03 redis_queue.1 | 8363:M 20 Apr 2022 14:10:03.128 # Could not create server TCP listening socket 127.0.0.1:11000: bind: Address already in use
14:10:03 system | redis_queue.1 stopped (rc=1)
14:10:03 system | worker_default.1 started (pid=8376)
14:10:03 system | schedule.1 started (pid=8375)
14:10:03 system | sending SIGTERM to web.1 (pid 8361)
14:10:03 system | sending SIGTERM to socketio.1 (pid 8374)
14:10:03 system | sending SIGTERM to watch.1 (pid 8372)
14:10:03 system | sending SIGTERM to schedule.1 (pid 8375)
14:10:03 system | sending SIGTERM to worker_short.1 (pid 8377)
14:10:03 system | sending SIGTERM to worker_long.1 (pid 8378)
14:10:03 system | sending SIGTERM to worker_default.1 (pid 8376)
14:10:03 system | worker_default.1 stopped (rc=-15)
14:10:03 system | watch.1 stopped (rc=-15)
14:10:03 system | socketio.1 stopped (rc=-15)
14:10:03 system | worker_short.1 stopped (rc=-15)
14:10:03 system | schedule.1 stopped (rc=-15)
14:10:03 system | web.1 stopped (rc=-15)
14:10:03 system | worker_long.1 stopped (rc=-15)

This error will occur anytime the previous processes didn’t properly shutdown. You can use supervisor to close all the process. Check this thread.

1 Like

Hi,

Thanks :slight_smile: I used supervisor and it is working.

Hi,

There is one problem, I am not able to login. It gives me an error.

Do you have an idea why it happened?

The super admin username is always “Administrator”

I used the same but not working

It’s possible you made a type when setting up the site.

Try running
bench --site SITE_NAME_HERE set-admin-password admin
To reset the admin password.

Then try to login again

2 Likes