Problems with TASK: [supervisor | wait for web port to be available]

[Tum Chaturapruek]

I followed the edX Ubuntu 12.04 Installation instructions, but I encountered:


TASK: [supervisor | create pre_supervisor upstart job] ************************
skipping: [localhost]

TASK: [supervisor | write the pre_suprevisor python script] *******************
skipping: [localhost]

TASK: [supervisor | create supervisor master config] **************************
ok: [localhost]

TASK: [supervisor | create a symlink for supervisortctl] **********************
ok: [localhost]

TASK: [supervisor | create a symlink for supervisor cfg] **********************
ok: [localhost] => (item=/edx/app/supervisor/supervisord.conf)
ok: [localhost] => (item=/edx/app/supervisor/conf.d)

TASK: [supervisor | start supervisor] *****************************************
changed: [localhost]

TASK: [supervisor | wait for web port to be available] ************************
failed: [localhost] => {"elapsed": 5, "failed": true, "item": ""}
msg: Timeout when waiting for 127.0.0.1:9001

FATAL: all hosts have already failed -- aborting

PLAY RECAP ********************************************************************
           to retry, use: --limit @/home/ubuntu/edx_sandbox.retry

localhost                  : ok=70   changed=6    unreachable=0    failed=1  


Any ideas why this port is not available? I tried  sudo unlink /tmp/supervisor.sock but it doesn't work. I also checked through sudo lsof -i tcp | grep LISTEN to confirm that no process is listening to 9001. I also called

sudo service supervisor stop
sudo service supervisor.devpi stop

but I got response like

stop: Unknown instance:

But status looks OK.

$sudo service supervisor status
supervisor stop/waiting

$ sudo service supervisor.devpi status
supervisor.devpi stop/waiting

I'm very confused. Please help. Thanks!
- Tum

[Tum Chaturapruek]

Still having the same problem, even with the release_himbasha version.
- Tum

[praa...@azrisolutions.com]

i also came across this error any solution?

[Feanil Patel]

So the issue is not with supervisor starting up improperly.  After supervisor starts up, ansible checks to see if the web server is running as expected and that is what is failing.  You can try to start supervisor and then manually verify that the server is running on port 9001.  Also take a look at the supervisor config (/edx/etc/supervisord.conf) to make sure that the web server is enabled.