Another Ubuntu 16 Version Try

TASK [bench : include_tasks] *******************************************************************************************************************************************
included: /tmp/.bench/playbooks/roles/bench/tasks/setup_bench_production.yml for localhost

TASK [bench : Setup production] ****************************************************************************************************************************************
fatal: [localhost]: FAILED! => {“changed”: true, “cmd”: [“bench”, “setup”, “production”, “frappe”], “delta”: “0:00:14.696643”, “end”: “2018-03-15 09:54:27.454423”, “failed”: true, “msg”: “non-zero return code”, “rc”: 1, “start”: “2018-03-15 09:54:12.757780”, “stderr”: “Aborted!”, “stderr_lines”: [“Aborted!”], “stdout”: "supervisor.conf already exists and this will overwrite it. Do you want to continue? [y/N]: ", “stdout_lines”: ["supervisor.conf already exists and this will overwrite it. Do you want to continue? [y/N]: "]}
to retry, use: --limit @/tmp/.bench/playbooks/site.retry

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

Traceback (most recent call last):
File “”, line 387, in
File “”, line 109, in install_bench
run_playbook(‘site.yml’, sudo=True, extra_vars=extra_vars)
File “”, line 325, in run_playbook
success = subprocess.check_call(args, cwd=os.path.join(cwd, ‘playbooks’))
File “/usr/lib/python2.7/”, line 541, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command ‘[‘ansible-playbook’, ‘-c’, ‘local’, ‘site.yml’, ‘-e’, ‘@/tmp/extra_vars.json’, ‘–become’, ‘–become-user=frappe’]’ returned non-zero exit status 2
You have new mail in /var/mail/root

Running the install as root is never a good idea. Create a user called frappe, and install as them. Use sudo for commands that needs root privileges.

1 Like

So this is the giveaway clue I never noticed til now - thanks for the pointer trentmu!


My personal rule 2) is RTFS. I find that when I make a mistake, it’s generally because I didn’t follow this rule :smile:

1 Like

The install notes could not be more clear and concise, to use sudo and not root (my emphasis)

If you are on a fresh server and logged in as root, use --user flag to create a user and install using that user

python --develop --user frappe
For developer setup:

sudo python --develop
For production:

sudo python --production

1 Like

@clarkej is 1000% right. Seems to happen often