Thank you for fast reply @lasalesi
I do bench update on development instance, a clone of production instance with same IP, thus all sites will still accessible using domain name. So production instance is still untouched.
This is the text that shown on front end when I say that erpnext is broken:
We will be back soon.
Don’t panic. It’s not you, it’s us.
Most likely, our engineers are updating the code, and it should take a minute for the new code to load into memory.
Try refreshing after a minute or two.
I am currently running apt-get update and upgrade on development instance, a newly restored instance from production instance, so it may take a while. When it is updated, I will edit this post.
However, the problem is on
SSH’ed as root, I believe I do not need sudo.
I prefer to use this as solution, it looks like previous installer run install script as root, and I believe it is not the way erpnext suggest. The result is python apps have problem when upgrading, not enough permission, so that I have to
sudo pip install --upgrade some-apps
Can you elaborate how to restore the backup from v8.x.x to new instance installed with easy install on ubuntu 18.04?
as far as I know, this is what should I do on fresh ubuntu 18.04:
apt-get update && sudo apt-get upgrade
apt-get install python-minimal
apt-get install build-essential python-setuptools
python install.py --develop --user frappe
what I did on my previous attempt is not finishing the wizard on front end and do this:
bench switch-to-branch v8.x.x
then I can see every component on login page on front end, but without username and password box, hence I cannot login.
Can you explain what is wrong with my previous step?
I now understand my fault that I should
bench switch-to-branch v9.x.x
instead of straight
Here is interactive window when doing apt-get upgrade with my answer in bold
Configuration file ‘/etc/sudoers’
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer’s version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** sudoers (Y/I/N/O/D/Z) [default=N] ? N
┌──────────────────────────┤ Configuring grub-pc ├──────────────────────────┐
│ A new version of configuration file /etc/default/grub is available, but │
│ the version installed currently has been locally modified. │
│ What do you want to do about modified configuration file grub? │
│ install the package maintainer’s version │
│ keep the local version currently installed this is my choice │
│ show the differences between the versions │
│ show a side-by-side difference between the versions │
│ show a 3-way difference between available versions │
│ do a 3-way merge between available versions (experimental) │
│ start a new shell to examine the situation │
│ Continue without installing GRUB? YES
do-release-upgrade error result will update tomorrow