"Your system is being updated. Please refresh again after a few moments" after running bench migrate

~/frappe-bench/apps/erpnext$ git status
On branch develop
Your branch is up-to-date with ‘upstream/develop’.
nothing to commit, working directory clean

~/frappe-bench/apps/erpnext$ git status
On branch develop
Your branch is up-to-date with ‘upstream/develop’.
nothing to commit, working directory clean

I want to tell you that I am just using from scratch no changes are made

bench --site qf.erp migrate
Migrating qf.erp
Executing erpnext.patches.v9_0.fix_subscription_next_date #2017-10-23 in qf.erp (c9d293b033caf17b)
Traceback (most recent call last):
File “/usr/lib/python2.7/runpy.py”, line 174, in _run_module_as_main
main”, fname, loader, pkg_name)
File “/usr/lib/python2.7/runpy.py”, line 72, in _run_code
exec code in run_globals
File “/home/saeed/frappe-bench/apps/frappe/frappe/utils/bench_helper.py”, line 97, in
main()
File “/home/saeed/frappe-bench/apps/frappe/frappe/utils/bench_helper.py”, line 18, in main
click.Group(commands=commands)(prog_name=‘bench’)
File “/home/saeed/frappe-bench/env/local/lib/python2.7/site-packages/click/core.py”, line 722, in call
return self.main(*args, **kwargs)
File “/home/saeed/frappe-bench/env/local/lib/python2.7/site-packages/click/core.py”, line 697, in main
rv = self.invoke(ctx)
File “/home/saeed/frappe-bench/env/local/lib/python2.7/site-packages/click/core.py”, line 1066, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File “/home/saeed/frappe-bench/env/local/lib/python2.7/site-packages/click/core.py”, line 1066, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File “/home/saeed/frappe-bench/env/local/lib/python2.7/site-packages/click/core.py”, line 895, in invoke
return ctx.invoke(self.callback, **ctx.params)
File “/home/saeed/frappe-bench/env/local/lib/python2.7/site-packages/click/core.py”, line 535, in invoke
return callback(*args, **kwargs)
File “/home/saeed/frappe-bench/env/local/lib/python2.7/site-packages/click/decorators.py”, line 17, in new_func
return f(get_current_context(), *args, **kwargs)
File “/home/saeed/frappe-bench/apps/frappe/frappe/commands/init.py”, line 25, in func
ret = f(frappe.dict(ctx.obj), *args, **kwargs)
File “/home/saeed/frappe-bench/apps/frappe/frappe/commands/site.py”, line 222, in migrate
migrate(context.verbose, rebuild_website=rebuild_website)
File “/home/saeed/frappe-bench/apps/frappe/frappe/migrate.py”, line 39, in migrate
frappe.modules.patch_handler.run_all()
File “/home/saeed/frappe-bench/apps/frappe/frappe/modules/patch_handler.py”, line 29, in run_all
if not run_single(patchmodule = patch):
File “/home/saeed/frappe-bench/apps/frappe/frappe/modules/patch_handler.py”, line 63, in run_single
return execute_patch(patchmodule, method, methodargs)
File “/home/saeed/frappe-bench/apps/frappe/frappe/modules/patch_handler.py”, line 83, in execute_patch
frappe.get_attr(patchmodule.split()[0] + “.execute”)()
File “/home/saeed/frappe-bench/apps/erpnext/erpnext/patches/v9_0/fix_subscription_next_date.py”, line 21, in execute
filters = {‘reference_doctype’: (‘in’, doctypes), ‘docstatus’: 1}):
File “/home/saeed/frappe-bench/apps/frappe/frappe/init.py”, line 1262, in get_all
return get_list(doctype, *args, **kwargs)
File “/home/saeed/frappe-bench/apps/frappe/frappe/init.py”, line 1235, in get_list
return frappe.model.db_query.DatabaseQuery(doctype).execute(None, *args, **kwargs)
File “/home/saeed/frappe-bench/apps/frappe/frappe/model/db_query.py”, line 87, in execute
result = self.build_and_run()
File “/home/saeed/frappe-bench/apps/frappe/frappe/model/db_query.py”, line 99, in build_and_run
args = self.prepare_args()
File “/home/saeed/frappe-bench/apps/frappe/frappe/model/db_query.py”, line 118, in prepare_args
self.build_conditions()
File “/home/saeed/frappe-bench/apps/frappe/frappe/model/db_query.py”, line 287, in build_conditions
self.build_filter_conditions(self.filters, self.conditions)
File “/home/saeed/frappe-bench/apps/frappe/frappe/model/db_query.py”, line 308, in build_filter_conditions
conditions.append(self.prepare_filter_condition(f))
File “/home/saeed/frappe-bench/apps/frappe/frappe/model/db_query.py”, line 316, in prepare_filter_condition
f = get_filter(self.doctype, f)
File “/home/saeed/frappe-bench/apps/frappe/frappe/utils/data.py”, line 834, in get_filter
if frappe.get_meta(df.options).has_field(f.fieldname):
File “/home/saeed/frappe-bench/apps/frappe/frappe/init.py”, line 734, in get_meta
return frappe.model.meta.get_meta(doctype, cached=cached)
File “/home/saeed/frappe-bench/apps/frappe/frappe/model/meta.py”, line 38, in get_meta
meta = Meta(doctype)
File “/home/saeed/frappe-bench/apps/frappe/frappe/model/meta.py”, line 85, in init
super(Meta, self).init(“DocType”, doctype)
File “/home/saeed/frappe-bench/apps/frappe/frappe/model/document.py”, line 104, in init
self.load_from_db()
File “/home/saeed/frappe-bench/apps/frappe/frappe/model/meta.py”, line 90, in load_from_db
super(Meta, self).load_from_db()
File “/home/saeed/frappe-bench/apps/frappe/frappe/model/document.py”, line 141, in load_from_db
frappe.throw(
(“{0} {1} not found”).format(
(self.doctype), self.name), frappe.DoesNotExistError)
File “/home/saeed/frappe-bench/apps/frappe/frappe/init.py”, line 339, in throw
msgprint(msg, raise_exception=exc, title=title, indicator=‘red’)
File “/home/saeed/frappe-bench/apps/frappe/frappe/init.py”, line 325, in msgprint
_raise_exception()
File “/home/saeed/frappe-bench/apps/frappe/frappe/init.py”, line 298, in _raise_exception
raise raise_exception(msg)
frappe.exceptions.DoesNotExistError: DocType Subscription Plan Detail not found

Try this (adjust to your needs)

bench clear-cache
bench --site [sitename] reload-doctype “Subscription Plan Detail”
bench update

You should run
bench start
And then bench update on a new window

1 Like

Is this delete my datas?

It shouldn’t, but it is always a GOOD idea to take backups (often)

1 Like

This is very simple, after i had struggled for hours in the night i simply edited the common_site_config.json from {
“auto_update”: false,
“background_workers”: 1,
“maintenance mode”:1
“file_watcher_port”: 6787,
“frappe_user”: “mukane”,
“gunicorn_workers”: 3,
“rebase_on_pull”: false,
“redis_cache”: “redis://localhost:13000”,
“redis_queue”: “redis://localhost:11000”,
“redis_socketio”: “redis://localhost:12000”,
“restart_supervisor_on_update”: true,
“restart_systemd_on_update”: false,
“serve_default_site”: true,
“shallow_clone”: true,
“socketio_port”: 9000,
“update_bench_on_update”: true,
“webserver_port”: 8000
} to {
“auto_update”: false,
“background_workers”: 1,
“file_watcher_port”: 6787,
“frappe_user”: “mukane”,
“gunicorn_workers”: 3,
“rebase_on_pull”: false,
“redis_cache”: “redis://localhost:13000”,
“redis_queue”: “redis://localhost:11000”,
“redis_socketio”: “redis://localhost:12000”,
“restart_supervisor_on_update”: true,
“restart_systemd_on_update”: false,
“serve_default_site”: true,
“shallow_clone”: true,
“socketio_port”: 9000,
“update_bench_on_update”: true,
“webserver_port”: 8000
}
So I erased the maintenance mode section to remove the site from maintenance mode.
Thanks

17 Likes

works also by setting the value to 0

5 Likes

It worked.

2 Likes

At least is helps to continue working on other things while the patches failing are fixed

To check and change that setting from the bench, do this:

bench set-config maintenance_mode 0

frappe@ubuntu:~/frappe-bench$ bench show-config | grep maintenance_mode
maintenance_mode 0
frappe@ubuntu:~/frappe-bench$ bench set-config maintenance_mode 1
frappe@ubuntu:~/frappe-bench$ bench show-config | grep maintenance_mode
maintenance_mode 1

4 Likes

@Mukane_Onesimas Thank you for your answer. It’s work for me. But each I do an update “maintenance mode.”: move back to 1. I have to set it manually each in order to start my site.
But no matter what I do “bench update”, here is the message output in terminal:

Cannot proceed with update: You have local changes in app “frappe” that are not committed.

Here are your choices:

  1. Merge the frappe app manually with “git pull” / “git pull --rebase” and fix conflicts.
  2. Temporarily remove your changes with “git stash” or discard them completely
    with “bench update --reset” or for individual repositries “git reset --hard”
  3. If your changes are helpful for others, send in a pull request via GitHub and
    wait for them to be merged in the core.

So I just want to know finally if bench update should behave like that.

bench set-config maintenance_mode 0

This is just for per site config.

This is very simple, after i had struggled for hours in the night i simply edited the common_site_config.json

And this mentioned by @Mukane_Onesimas is the config for all sites.

Both configs have maintenance_mode so better check both files.

4 Likes

cd ~/frappe-bench/apps/frappe && git stash
cd …/… && bench update

Disable maintenance mode by : bench set-config maintenance_mode 0

5 Likes
4 Likes

Thanks!! this work…

Encountered this problem will try the maintenance mode changes.
when this problem occured ping to the instance is Timing Out

first do “bench --site {site name} migrate”. then if you see any error make sure to solve the error that you got(it might be installing a module or do other thing) then set maintenance mode off otherwise it will not work

It worked for me too.
Thank you…