Hello,
I have currently on my server the warning message about a newer version of bench, but I have already successfully upgraded the bench and restarted it, as you can see with the bottom image
Do you think this warning message is the bug itself, the update don’t work properly or do I need to restart a service instead of just doing bench restart ?
Thank you.
Just following because I’m having the same issue.
I have tried two different commands from previous forum posts but the bench version doesn’t change.
sudo -H pip3 install frappe-bench --upgrade
sudo -H pip3 install --upgrade frappe-bench
Does this command have to be run in the bench directory, or above, or for each individual bench created?
pip install --upgrade frappe-bench
It doesn’t work.
I have personnally used
sudo pip3 install --upgrade frappe-bench
pip install without any sudo as you propose throws a permission error.
The one I used correctly showed the successfully installed message so it should be good.
But the warning is still present.
I seriously consider the possibility it comes from bench --version giving back the wrong version.
Hello,
I found the answer.
Most tutorial about frappe-bench installation use sudo pip install, which is a bad practice.
Pip install is indeed the right way.
By using both we manage to install Frappe twice and it causes some issues.
The bench --version fetch the version of the non sudo one by default so it returns a version different from the real one if the sudo is used.
So to fix this.
sudo pip uninstall frappe-bench
pip uninstall frappe-bench
pip install frappe-bench (to be sure to have a good installation, if no successful message, try again)
cd (name of your bench directory)
bench setup supervisor
sudo reboot
I can’t edit the previous message anymore.
If you use the command
sudo bench setup lets-encrypt, the pip install frappe-bench won’t work because this command needs superuser permission so use the sudo pip install instead.
So just do :
pip uninstall frappe-bench
sudo pip install frappe-bench
sudo reboot
go in your bench
bench setup supervisor
accept
sudo reboot
Brilliant! Thanks for finding this solution.