I thought I’m the only one having this. Thanks for reporting.
Is this bash problem @System19 or ERPNext script problem?
I’m using Ubuntu 16.04
I thought I’m the only one having this. Thanks for reporting.
Is this bash problem @System19 or ERPNext script problem?
I’m using Ubuntu 16.04
Yep it drove me crazy on centos7 the other day… Grrr… never happened before?
Sorry… Yes its a bash issue. Is also caused by loads of other random things too… Not a new issue either… Possibly set off by frappe install script… But may just bad linux update?
Doesn’t happen on arch linux (bash 4.4.x)
I wonder about using root to install ERPNext?
The install notes advise do not use root to install, best practice is to use sudo.
While I do all my own sysadmin, very rarely do I login as root.
Misuse of root plays havoc with permission issues for example.
One has to be an expert to use root I am told.
For example problems like this I suspect?
Correction - this is not accurate
The install notes GitHub - frappe/bench: CLI to manage Multi-tenant deployments for Frappe apps
simply advise this:
Install bench as a non root user
so for example
git clone GitHub - frappe/bench: CLI to manage Multi-tenant deployments for Frappe apps bench-repo
sudo pip install -e bench-repo
Yes It might be caused by root/sudo install of frappe script. Using easy install under a user account with sudo I found that sometimes the script crashed shortly after creating a new frappe user (something like error frappe user already exists). So its quite possible that account preferences get crushed in the process.
On CentOS7, I finally found the script responsible. It is the screen_wall.sh. I just remove that script and I get my terminal prompt back to normal.
]# rm /etc/profile.d/screen_wall.sh
rgds,
_Yul
@jcagbay thanks thats a cool discovery. what does screen_wall.sh actually do and what in the frappe script causes it comes crash?
Also more importantly,
Does anybody here know how to change the frappe easy install script to avoid the million and one possible crashes that it invokes? Would it minimise issues if before running the easy install script it was expected there was a wheel user “frappe” already created?
Are we asking too much of an easy install script to create a new user as well as install all dependencies?
User frappe is the target user for easy install so no need to create it in advance. During CentOS7 O/S install you have the option to create a user i.e. admin with sudo access, the one that belongs to group wheel. After the O/S installation, work from that user to install the python script for bench.
$ sudo python install.py --production --user frappe
If you have change to view closely the bench installation, you can glimpse: TASK: SCREEN WALL. I think that is where this screen configuration was installed. But it is not a functional issue. I just don’t used to it.
The bench installation hangs towards the middle of the script. This is more bigger issue. That issue is related to nginx linux package not installed.
$ sudo yum install nginx
Restart bench python installation script. It successfully completes the installation for me. Yours may vary.
rgds,
_Yul
I had a similar situation on an Arch Linux install. I didn’t see the SCREEN WALL message, but the install wouldn’t complete.
After adding nginx every completed smoothly
Below is mentioned under Easy Install
try running bash - from the command line you may be in a basic shell by default. If this fixes it you can run to fix it permanently.
login as root and run below command
chsh -s /bin/bash yourusername
source : command line - Terminal not configured - not showing folder, no tab completion, etc - Ask Ubuntu
Happend to me as non-root as well; root doesn’t seem to be the problem.
thks!
Thank you
This works. But sometimes, the user may not have the permission to change their own terminal. So you can run following as root:
sudo usermod -s /bin/bash username
Source: linux - How do I start in bash when ssh'ing into my server? - Super User