Ok. I started trying to get the install.py script to run properly on CentOS 7 yesterday and first ran into NGINX errors that were resolved by setting selinux to Permissive BEFORE running the install.py script. You can find more on that at this link:
UPDATE 1/18/2017 This same issue started happening with Debian v8 servers today. A fresh dump further down thread.
Once I was able to get past the selinux issues, the install.py ran into another problem when trying to move /tmp/,bench. So I am posting that error here and hopefully someone will have some idea how I can get past this point in the install:
TASK [Check if /tmp/.bench exists] *****************************************************************************
ok: [localhost]
TASK [Check if bench_repo_path exists] *************************************************************************
ok: [localhost]
TASK [move /tmp/.bench if it exists] ***************************************************************************
fatal: [localhost]: FAILED! => {“changed”: true, “cmd”: [“cp”, “-R”, “/tmp/.bench”, “/home/root/.bench”], "delta
": “0:00:00.005924”, “end”: “2018-01-16 16:18:23.592925”, “failed”: true, “rc”: 1, “start”: “2018-01-16 16:18:23
.587001”, “stderr”: “cp: cannot create directory ‘/home/root/.bench’: No such file or directory”, “stderr_lines”
: [“cp: cannot create directory ‘/home/root/.bench’: No such file or directory”], “stdout”: “”, “stdout_lines”:
}
to retry, use: --limit @/tmp/.bench/playbooks/production/install.retry
PLAY RECAP *****************************************************************************************************
localhost : ok=63 changed=45 unreachable=0 failed=1
Traceback (most recent call last):
File “install.py”, line 388, in
install_bench(args)
File “install.py”, line 114, in install_bench
run_playbook(‘production/install.yml’, sudo=True, extra_vars=extra_vars)
File “install.py”, line 326, in run_playbook
success = subprocess.check_call(args, cwd=os.path.join(cwd, ‘playbooks’))
File “/usr/lib64/python2.7/subprocess.py”, line 542, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command ‘[‘ansible-playbook’, ‘-c’, ‘local’, ‘production/install.yml’, ‘-e’, ‘@/t
mp/extra_vars.json’, ‘–become’, ‘–become-user=erp_jmi’]’ returned non-zero exit status 2
[erp_jmi@cetnos7-test ~]$
Any ideas? It looks like it is running into trouble trying to create a new directory, but again the script is being run as “sudo” so it should not have trouble doing anything it wants.
I do however see this line;
to retry, use: --limit @/tmp/.bench/playbooks/production/install.retry
Does this indicate another valid switch called --limit that can be added to the install.py script start (like --production and --user)? I have never heard of it before. If it is valid, where can I find info about it?
BKM
