I'm hitting this problem inside Precise KVM nodes. The bottom of cloud-init-output.log has this:
+ start jujud-machine-3
jujud-machine-3 start/running, process 2244
Traceback (most recent call last):
File "/usr/lib/python2.7/logging/handlers.py", line 807, in emit
self._connect_unixsocket(self.address)
File "/usr/lib/python2.7/logging/handlers.py", line 745, in _connect_unixsocket
self.socket.connect(address)
File "/usr/lib/python2.7/socket.py", line 224, in meth
return getattr(self._sock,name)(*args)
error: [Errno 111] Connection refused
Logged from file __init__.py, line 116
I'm hitting this problem inside Precise KVM nodes. The bottom of cloud-init- output. log has this:
+ start jujud-machine-3 python2. 7/logging/ handlers. py", line 807, in emit _connect_ unixsocket( self.address) python2. 7/logging/ handlers. py", line 745, in _connect_unixsocket socket. connect( address) python2. 7/socket. py", line 224, in meth self._sock, name)(* args)
jujud-machine-3 start/running, process 2244
Traceback (most recent call last):
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
return getattr(
error: [Errno 111] Connection refused
Logged from file __init__.py, line 116
The MAAS KVM node is on Saucy.