ERPNext Conference 2019* ERPNext.com Blog

ERPNext - Setup failed: Could not start up: Error in setup

installation_problem
error
basics

#1

I installed ERPNext and it doesn´t work, ERPNext is showing the following error:

Setup failed

Could not start up: Error in setup

Do someone knows how to fix it?


#2

You’ll have to share/show more than that before anyone will be able to help you


#3

shows this image when I’m setting up the company in ERPNext

image


#4

We need to see the traceback screen (where you see the bench start errors etc)


#5

I´m new in ERPNext. Where do I can to see the traceback screen?


#6

It is in the terminal part where you ran the setup.
Normally you log in as the install-user (eg. frappe)
Then open a terminal, and run

cd ~/frappe-bench
bench start

In that terminal, you should see the descriptions and details of the errors


#7

Show me this:

PNext:~/erpnext$ bench start
12:30:05 system | web.1 started (pid=16051)
12:30:06 system | redis_socketio.1 started (pid=16047)
12:30:06 system | watch.1 started (pid=16052)
12:30:06 system | redis_cache.1 started (pid=16066)
12:30:06 system | worker_long.1 started (pid=16054)
12:30:06 system | worker_default.1 started (pid=16056)
12:30:06 system | redis_queue.1 started (pid=16055)
12:30:06 system | schedule.1 started (pid=16064)
12:30:06 system | socketio.1 started (pid=16073)
12:30:06 system | worker_short.1 started (pid=16074)
12:30:06 redis_cache.1 | 16071:C 30 Jun 12:30:06.185 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
12:30:06 redis_cache.1 | 16071:C 30 Jun 12:30:06.185 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=16071, just started
12:30:06 redis_cache.1 | 16071:C 30 Jun 12:30:06.185 # Configuration loaded
12:30:06 redis_queue.1 | 16069:C 30 Jun 12:30:06.192 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
12:30:06 redis_queue.1 | 16069:C 30 Jun 12:30:06.192 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=16069, just started
12:30:06 redis_queue.1 | 16069:C 30 Jun 12:30:06.192 # Configuration loaded
12:30:06 redis_socketio.1 | 16060:C 30 Jun 12:30:06.194 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
12:30:06 redis_socketio.1 | 16060:C 30 Jun 12:30:06.194 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=16060, just started
12:30:06 redis_socketio.1 | 16060:C 30 Jun 12:30:06.194 # Configuration loaded
12:30:06 redis_socketio.1 | 16060:M 30 Jun 12:30:06.195 * Increased maximum number of open files to 10032 (it was originally set to 1024).
12:30:06 redis_socketio.1 | 16060:M 30 Jun 12:30:06.195 # Creating Server TCP listening socket 127.0.0.1:12000: bind: Address already in use
12:30:06 redis_queue.1 | 16069:M 30 Jun 12:30:06.195 * Increased maximum number of open files to 10032 (it was originally set to 1024).
12:30:06 system | redis_socketio.1 stopped (rc=1)
12:30:06 system | sending SIGTERM to worker_long.1 (pid 16054)
12:30:06 system | sending SIGTERM to watch.1 (pid 16052)
12:30:06 system | sending SIGTERM to redis_queue.1 (pid 16055)
12:30:06 system | sending SIGTERM to web.1 (pid 16051)
12:30:06 system | sending SIGTERM to schedule.1 (pid 16064)
12:30:06 system | sending SIGTERM to worker_default.1 (pid 16056)
12:30:06 system | sending SIGTERM to socketio.1 (pid 16073)
12:30:06 system | sending SIGTERM to redis_cache.1 (pid 16066)
12:30:06 system | sending SIGTERM to worker_short.1 (pid 16074)
12:30:06 redis_cache.1 | 16071:M 30 Jun 12:30:06.199 * Increased maximum number of open files to 10032 (it was originally set to 1024).
12:30:06 redis_cache.1 | 16071:M 30 Jun 12:30:06.200 # Creating Server TCP listening socket 127.0.0.1:13000: bind: Address already in use
12:30:06 system | redis_cache.1 stopped (rc=1)
12:30:06 system | watch.1 stopped (rc=-15)
12:30:06 redis_queue.1 | 16069:M 30 Jun 12:30:06.204 # Creating Server TCP listening socket 127.0.0.1:11000: bind: Address already in use
12:30:06 system | redis_queue.1 stopped (rc=1)
12:30:06 system | worker_long.1 stopped (rc=-15)
12:30:06 system | socketio.1 stopped (rc=-15)
12:30:06 system | schedule.1 stopped (rc=-15)
12:30:06 system | worker_short.1 stopped (rc=-15)
12:30:06 system | worker_default.1 stopped (rc=-15)
12:30:06 system | web.1 stopped (rc=-15)


#8

this is the log that shows


#9

if you’re in develop then you may have to try run the setup a couple of times including rebooting the machine. Faced the same issue 24 hours ago and setup eventually completed after series of tries. Didn’t record the trace back though.

EDIT

you may need to check this though.


#10

Try this… (as user erpnext)

cd ~/frappe-bench; sudo supervisorctl restart all

or

cd ~/frappe-bench; bench restart


#11

I already did it but it doesn’t work