Failed Ansible Install Step: restart jupyterhub with supervisor
jkuruzovich opened this issue · comments
When installing on UBUNTU Ansible goes through 63 steps successfully but then fails at the step below.
TASK [jupyterhub : restart jupyterhub with supervisor] *************************
fatal: [notebooks.analyticsdojo.com]: FAILED! => {"changed": false, "failed": true, "msg": "jupyterhub: stopped\njupyterhub: ERROR (spawn error)\n"}
NO MORE HOSTS LEFT *************************************************************
RUNNING HANDLER [common : restart ntp] *****************************************
RUNNING HANDLER [nginx : reload nginx] *****************************************
[WARNING]: Could not create retry file 'deploy.retry'. [Errno 2] No such file or directory: ''
PLAY RECAP *********************************************************************
notebooks.analyticsdojo.com : ok=63 changed=54 unreachable=0 failed=1
I've tried multiple times but haven't been able to get past this step.
Best,
Jason
I would try to ssh into the machine and run both supervisorctl restart and
reloading NGINX manually to have more details about the error.
On Wed, Sep 21, 2016, 08:28 Jason Kuruzovich notifications@github.com
wrote:
When installing on UBUNTU Ansible goes through 63 steps successfully but
then fails at the step below.TASK [jupyterhub : restart jupyterhub with supervisor]
fatal: [notebooks.analyticsdojo.com]: FAILED! => {"changed": false,
"failed": true, "msg": "jupyterhub: stopped\njupyterhub: ERROR (spawn
error)\n"}NO MORE HOSTS LEFT
RUNNING HANDLER [common : restart ntp]
RUNNING HANDLER [nginx : reload nginx]
[WARNING]: Could not create retry file 'deploy.retry'. [Errno 2] No such
file or directory: ''PLAY RECAP
notebooks.analyticsdojo.com : ok=63 changed=54 unreachable=0 failed=1
I've tried multiple times but haven't been able to get past this step.
Best,
Jason—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#22, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAXYctVMWt_axEeQCguGBF-IN8-Rqtphks5qsU0RgaJpZM4KC8ew
.
Thank you! After further investigation of the logs I realized the error was from a user that had not been created on the server but was listed in the host file.