python2.7/socket.py error during reinstall

[Don R]

I am getting the following error during reinstall on Ubuntu 12.04

TASK: [supervisor | update supervisor configuration] **************************

failed: [localhost] => {"changed": true, "cmd": "/edx/app/devpi/venvs/supervisor/bin/supervisorctl -c /edx/app/devpi/supervisor/supervisord.conf update ", "delta": "0:00:00.078784", "end": "2013-12-18 11:31:44.287673", "item": "", "rc": 2, "start": "2013-12-18 11:31:44.208889", "stdout_lines": ["error: <class 'socket.error'>, [Errno 2] No such file or directory: file: /usr/lib/python2.7/socket.py line: 224"]}

stdout: error: <class 'socket.error'>, [Errno 2] No such file or directory: file: /usr/lib/python2.7/socket.py line: 224

FATAL: all hosts have already failed -- aborting

PLAY RECAP ********************************************************************

           to retry, use: --limit @/home/<user>/edx_sandbox.retry

localhost                  : ok=77   changed=15   unreachable=0    failed=1

I have not found any other posts that deal with this error, nor been able to figure out how to solve it. Anyone have an idea?

[Feanil Patel]

I believe this is an ansible issue, what version are you running?  Does upgrading to 1.3.2 fix the issue?

[Don R]

I am not certain how to find what version is being used; I've been following these instructions https://github.com/edx/configuration/wiki/edX-Ubuntu-12.04-Installation

[John Jarvis]

That error can occur when supervisorctl tries to connect to supervisor
and it's not running.
Can you see if the supervisor daemon is running? And as a sanity check
are you installing on ubuntu 12.04? We don't currently support debian
variants that do not use upstart though I have a branch that I'm
testing that switches over to plain sysv scripts so we can support
wheezy.
-John

[Don R]

It appears to be running:

$ sudo service supervisor status

supervisor start/running, process 4816

Are there different instructions on how to use upstart than the ones I already posted, or should I be building this on a different platform?

[John Jarvis]

Hm, then that's not the problem.
Are you able to run supervisorctl?

`sudo /edx/bin/supervisorctl -c /edx/etc/supervisord.conf`

-John

[Liyuan Zheng]

Hi,

I had the same problem. I run `sudo /edx/bin/supervisorctl -c /edx/etc/supervisord.conf`, it gave me the following.

unix:///edx/var/supervisor/supervisor.sock no such file

supervisor> 

Thanks

Liyuan

[Diego Rabatone Oliveira]

Hi friends, any news on this issue? I'm facing the same error here (using Ubuntu 12.04 also).

Thanks.

[Anas El Hadj Amor]

Hi guys, I had the same error. I followed this procedure 
https://github.com/edx/configuration/wiki/edX-Managing-the-Production-Stack#unable-to-connect-to-the-lms

starting from the "If you are still unable..." part, and I didn't restart anything, so I did :

• sudo service nginx stop
• sudo service supervisor stop
• sudo service supervisor.devpi stop
• sudo pkill -u www-data

It worked for me, hoped it will do the same for you.