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

Frappe Framework
15

Try this (adjust to your needs)

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

16

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

1 Like
17

Is this delete my datas?

18

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

1 Like
19

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

18 Likes
20

works also by setting the value to 0

5 Likes
21

It worked.

2 Likes
22

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

23

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
25

@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.

26

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
27

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

28

Disable maintenance mode by : bench set-config maintenance_mode 0

5 Likes
29
4 Likes
30

Thanks!! this work…

31

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

32

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

33

It worked for me too.
Thank you…

34

thx it works with me

35

Thanx Worked for me !