I’m encountering the following error while running the easy install script on a Centos server. Is this a bug?
Traceback (most recent call last):
File "install.py", line 400, in <module>
install_bench(args)
File "install.py", line 104, in install_bench
run_playbook('create_user.yml', extra_vars=extra_vars)
File "install.py", line 333, in run_playbook
success = subprocess.check_call(args, cwd=os.path.join(cwd, 'playbooks'))
File "/usr/lib64/python2.7/subprocess.py", line 537, in check_call
retcode = call(*popenargs, **kwargs)
File "/usr/lib64/python2.7/subprocess.py", line 524, in call
return Popen(*popenargs, **kwargs).wait()
File "/usr/lib64/python2.7/subprocess.py", line 711, in __init__
errread, errwrite)
File "/usr/lib64/python2.7/subprocess.py", line 1327, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
I just tired a fresh install in Digital Ocean VPS on Ubuntu 16.04 64bit and I get the same error.
Traceback (most recent call last):
File "install.py", line 400, in <module>
install_bench(args)
File "install.py", line 104, in install_bench
run_playbook('create_user.yml', extra_vars=extra_vars)
File "install.py", line 333, in run_playbook
success = subprocess.check_call(args, cwd=os.path.join(cwd, 'playbooks'))
File "/usr/lib/python2.7/subprocess.py", line 536, in check_call
retcode = call(*popenargs, **kwargs)
File "/usr/lib/python2.7/subprocess.py", line 523, in call
return Popen(*popenargs, **kwargs).wait()
File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1343, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
Thanks a lot for responding quickly. After getting the first error, I suspected there was some issue with pip so I installed it manually. I also installed Node JS. After that I tried again and got the second error
If you’re talking about production install using the easy install scripts, then yes, all errors are taken care of with my PRs. I’ve tested and ensured that.
However, if you’re talking about develop install using the easy install scripts, then I think some errors still persist there. And they are mostly unicode errors, python 2 - 3 fixes, which are yet to be made.
@wale I just tried an install. It worked perfectly again. I’m unable to replicate the issue.
It feels like your user doesn’t have privileges to create a new user. But since you’re root I don’t see any reason for this error to pop up.
Can you try again on a fresh instance. Which VPS are you using?
Thanks for your quick response. It’s a server hosted on-premise
As you rightly mentioned, I was a bit puzzled by the permission error since its a root user. Are there any particular dependencies that may also cause this kind of error or is it strictly related to the permission for creation of new user?
If that’s the only source of the error, maybe I could try creating the user directly? Please advise and let me know which user to create
You could try by creating a password-less user named frappe.
But I don’t believe that’s the solution to the problem. The install script should work without it.
Try running:
In addition, I also tried to search for causes of similar errors and found that it seems to occur a lot when trying to execute a file that is not executable
I’m not sure if that gives any pointers but thought to mention it