Debian 8 Bench beta error - playbook

Hi all,

Was looking to install V7 and star to play with it in our organization as we will be upgrading when it is stable.

When doing the beta bench install I encountered this error:

TASK [Rename default nginx.conf to nginx.conf.old] *****************************
fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["mv", "/etc/nginx/nginx.conf", "/etc/nginx/nginx.conf.old"], "delta": "0:00:00.015197", "end": "2016-07-07 03:50:05.446384", "failed": true, "rc": 1, "start": "2016-07-07 03:50:05.431187", "stderr": "mv: cannot stat ‘/etc/nginx/nginx.conf’: No such file or directory", "stdout": "", "stdout_lines": [], "warnings": []}

NO MORE HOSTS LEFT *************************************************************
	to retry, use: --limit @production/install.retry

PLAY RECAP *********************************************************************
localhost                  : ok=6    changed=0    unreachable=0    failed=1

Traceback (most recent call last):
  File "", line 264, in <module>
  File "", line 99, in install_bench
    run_playbook('production/install.yml', sudo=True, extra_vars=extra_vars)
  File "", line 217, in run_playbook
    success = subprocess.check_call(args, cwd=os.path.join(tmp_bench_repo, 'playbooks'))
  File "/usr/lib/python2.7/", line 540, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['ansible-playbook', '-c', 'local', 'production/install.yml', '-e', '@/tmp/extra_vars.json', '--become', '--become-user=frappe']' returned non-zero exit status 2

@shreyasp @vjFaLk

Sorry, currently we don’t support Debian with our Beta installer, there’s a good chance that it will work just fine, but we need to put it through testing.

Ah ok, so is installing manually the best way to go for debian 8? Or should I just continue to use debian 7 as I currently am?


For the sake of stability you can continue using Debian 7, manually installing on 8 will also work. We plan to support Debian in the future.

1 Like