Installation of ERPNext stuck on verifying

When installing ERPNext on ubuntu 18.04 ,on registering in ERPNext wizard it got stuck in ‘verifying’ step. I have no idea what has gone wrong.Please someone kindly help me with this.

please copy and paste that traceback here which is visible in your browser’s console

bench start
11:11:08 system | redis_socketio.1 started (pid=2079)
11:11:08 system | redis_queue.1 started (pid=2085)
11:11:08 system | redis_cache.1 started (pid=2094)
11:11:08 system | worker_default.1 started (pid=2095)
11:11:08 system | worker_long.1 started (pid=2082)
11:11:08 system | schedule.1 started (pid=2093)
11:11:08 system | web.1 started (pid=2089)
11:11:08 system | worker_short.1 started (pid=2101)
11:11:08 system | watch.1 started (pid=2096)
11:11:08 system | socketio.1 started (pid=2110)
11:11:08 redis_cache.1 | 2098:C 26 Dec 11:11:08.252 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
11:11:08 redis_cache.1 | 2098:C 26 Dec 11:11:08.252 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=2098, just started
11:11:08 redis_cache.1 | 2098:C 26 Dec 11:11:08.252 # Configuration loaded
11:11:08 redis_cache.1 | 2098:M 26 Dec 11:11:08.253 * Increased maximum number of open files to 10032 (it was originally set to 1024).
11:11:08 redis_socketio.1 | 2083:C 26 Dec 11:11:08.259 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
11:11:08 redis_socketio.1 | 2083:C 26 Dec 11:11:08.259 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=2083, just started
11:11:08 redis_socketio.1 | 2083:C 26 Dec 11:11:08.259 # Configuration loaded
11:11:08 redis_socketio.1 | 2083:M 26 Dec 11:11:08.261 * Increased maximum number of open files to 10032 (it was originally set to 1024).
11:11:08 redis_queue.1 | 2090:C 26 Dec 11:11:08.269 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
11:11:08 redis_queue.1 | 2090:C 26 Dec 11:11:08.269 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=2090, just started
11:11:08 redis_queue.1 | 2090:C 26 Dec 11:11:08.269 # Configuration loaded
11:11:08 redis_queue.1 | 2090:M 26 Dec 11:11:08.270 * Increased maximum number of open files to 10032 (it was originally set to 1024).
11:11:08 redis_socketio.1 | 2083:M 26 Dec 11:11:08.288 * Running mode=standalone, port=12000.
11:11:08 redis_socketio.1 | 2083:M 26 Dec 11:11:08.288 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
11:11:08 redis_socketio.1 | 2083:M 26 Dec 11:11:08.288 # Server initialized
11:11:08 redis_socketio.1 | 2083:M 26 Dec 11:11:08.288 # 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.
11:11:08 redis_socketio.1 | 2083:M 26 Dec 11:11:08.288 # 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.
11:11:08 redis_socketio.1 | 2083:M 26 Dec 11:11:08.288 * Ready to accept connections
11:11:08 redis_queue.1 | 2090:M 26 Dec 11:11:08.288 * Running mode=standalone, port=11000.
11:11:08 redis_queue.1 | 2090:M 26 Dec 11:11:08.288 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
11:11:08 redis_queue.1 | 2090:M 26 Dec 11:11:08.288 # Server initialized
11:11:08 redis_queue.1 | 2090:M 26 Dec 11:11:08.288 # 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.
11:11:08 redis_queue.1 | 2090:M 26 Dec 11:11:08.288 # 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.
11:11:08 redis_queue.1 | 2090:M 26 Dec 11:11:08.289 * Ready to accept connections
11:11:08 redis_cache.1 | 2098:M 26 Dec 11:11:08.288 * Running mode=standalone, port=13000.
11:11:08 redis_cache.1 | 2098:M 26 Dec 11:11:08.288 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
11:11:08 redis_cache.1 | 2098:M 26 Dec 11:11:08.288 # Server initialized
11:11:08 redis_cache.1 | 2098:M 26 Dec 11:11:08.288 # 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.
11:11:08 redis_cache.1 | 2098:M 26 Dec 11:11:08.288 # 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.
11:11:08 redis_cache.1 | 2098:M 26 Dec 11:11:08.288 * Ready to accept connections
11:11:19 socketio.1 | listening on *: 9000
11:11:34 web.1 | * Running on http://0.0.0.0:8000/ (Press CTRL+C to quit)
11:11:34 web.1 | * Restarting with inotify reloader
11:11:35 web.1 | * Debugger is active!
11:11:37 web.1 | * Debugger PIN: 303-951-427
11:11:54 watch.1 | yarn run v1.12.3
11:12:07 watch.1 | $ node rollup/watch.js
11:12:35 watch.1 |
11:12:35 watch.1 | Rollup Watcher Started

Not your terminal, the browser console

Traceback (most recent call last):
File “/opt/erpnext/erpnext/apps/frappe/frappe/app.py”, line 55, in application
response = frappe.handler.handle()
File “/opt/erpnext/erpnext/apps/frappe/frappe/handler.py”, line 20, in handle
data = execute_cmd(cmd)
File “/opt/erpnext/erpnext/apps/frappe/frappe/handler.py”, line 55, in execute_cmd
return frappe.call(method, **frappe.form_dict)
File “/opt/erpnext/erpnext/apps/frappe/frappe/init.py”, line 1007, in call
return fn(*args, **newargs)
File “/opt/erpnext/erpnext/apps/frappe/frappe/core/doctype/user/user.py”, line 784, in sign_up
user.insert()
File “/opt/erpnext/erpnext/apps/frappe/frappe/model/document.py”, line 248, in insert
self.run_post_save_methods()
File “/opt/erpnext/erpnext/apps/frappe/frappe/model/document.py”, line 915, in run_post_save_methods
self.run_method(“on_update”)
File “/opt/erpnext/erpnext/apps/frappe/frappe/model/document.py”, line 780, in run_method
out = Document.hook(fn)(self, *args, **kwargs)
File “/opt/erpnext/erpnext/apps/frappe/frappe/model/document.py”, line 1058, in composer
return composed(self, method, *args, **kwargs)
File “/opt/erpnext/erpnext/apps/frappe/frappe/model/document.py”, line 1041, in runner
add_to_return_value(self, fn(self, *args, **kwargs))
File “/opt/erpnext/erpnext/apps/frappe/frappe/model/document.py”, line 774, in
fn = lambda self, *args, **kwargs: getattr(self, method)(*args, **kwargs)
File “/opt/erpnext/erpnext/apps/frappe/frappe/core/doctype/user/user.py”, line 95, in on_update
self.send_password_notification(self.__new_password)
File “/opt/erpnext/erpnext/apps/frappe/frappe/core/doctype/user/user.py”, line 203, in send_password_notification
self.send_welcome_mail_to_user()
File “/opt/erpnext/erpnext/apps/frappe/frappe/core/doctype/user/user.py”, line 269, in send_welcome_mail_to_user
site_url=get_url(),
File “/opt/erpnext/erpnext/apps/frappe/frappe/core/doctype/user/user.py”, line 295, in send_login_mail
delayed=(not now) if now!=None else self.flags.delay_emails, retry=3)
File “/opt/erpnext/erpnext/apps/frappe/frappe/init.py”, line 451, in sendmail
inline_images=inline_images, header=header, print_letterhead=print_letterhead)
File “/opt/erpnext/erpnext/apps/frappe/frappe/email/queue.py”, line 70, in send
sender = email_account.default_sender
AttributeError: ‘NoneType’ object has no attribute ‘default_sender’
website.js:162:20

I think it because you didn’t config email account, so when ERPNext trying to send you an email, it will cause this error.

You should try login as administrator.

2 Likes

how to login as administrator…I mean what are the credentials?

When you created the site, you were asked a password. That was the Administrator password.

Credentials :

User: Administrator
Password: The above mentioned

In case you don’t remember and want to reset it, you can use this command in your frappe-bench or bench instance folder

bench set-admin-password [type your new password here]

ok I am trying wait

thanks it does now!

1 Like

How to install apps ?? I mean the dashboard has no apps in it.

@Sadikur

Dear, if you follow these steps you will get all apps installed on your desk. please check whether you missed anything from this step by step instructions.

thanks

Yeah I did but still no apps

Those are icons not apps !

However, Have you installed erpnext or just frappe ?

I have followed this -

so I guess erpnext is not installed … I dont know

try this command
bench --site site_name install-app erpnext

1 Like

not a problem.

Step 1 : bench switch-to-master to ensure your frappe is on master branch

Step 2 : bench get-app erpnext --branch master https://github.com/frappe/erpnext to download the app.

Step 3: bench --site [mention your created site] install-app erpnext will install the app.


NOTE

  • master is the stable branch, develop is the experimental branch. In case you are a developer, your feature branches should stem from master and constantly updated wrt master to ensure easy merge
  • AVOID Edit Doctype route to change/add features in Doctypes. Never ever do any changes and commit them. I’ll link some videos to help you out later. This will save you a LOT of issues when doing bench update

on performing step 2, it shows this error

erpnextuser@sadikur-PC:/opt/erpnext/erpnext$ bench get-app erpnext https://github.com/frappe/erpnext --erpnext-branch master
Usage: bench get-app [OPTIONS] [NAME]… GIT_URL
Try “bench get-app --help” for help.

Error: no such option: --erpnext-branch

bench --site example.com install-app erpnext
Could not find app “erpnext”

Oh I’m sorry it is --branch master