Mycroft Community Forum

ConnectionRefusedError kills Mycroft's start process

Is anyone else seeing error messages like this on (re)start? I’m running into this intermittently, but generally if I stop the Docker container (not remove the container, just stop it) and then start it again, this is more likely to happen.

I have a Mark 1 on my desk that dies on the regular. Could this be what’s causing it?

mycroft_1  | 2020-05-23 19:27:53.553 | ERROR    |    63 | mycroft.messagebus.client.client:on_error:81 | === ConnectionRefusedError(111, 'Connection refused') ===
mycroft_1  | Traceback (most recent call last):
mycroft_1  |   File "/opt/mycroft/.venv/lib/python3.6/site-packages/websocket/_app.py", line 254, in run_forever
mycroft_1  |     proxy_type=proxy_type)
mycroft_1  |   File "/opt/mycroft/.venv/lib/python3.6/site-packages/websocket/_core.py", line 220, in connect
mycroft_1  |     options.pop('socket', None))
mycroft_1  |   File "/opt/mycroft/.venv/lib/python3.6/site-packages/websocket/_http.py", line 120, in connect
mycroft_1  |     sock = _open_socket(addrinfo_list, options.sockopt, options.timeout)
mycroft_1  |   File "/opt/mycroft/.venv/lib/python3.6/site-packages/websocket/_http.py", line 190, in _open_socket
mycroft_1  |     raise err
mycroft_1  |   File "/opt/mycroft/.venv/lib/python3.6/site-packages/websocket/_http.py", line 170, in _open_socket
mycroft_1  |     sock.connect(address)
mycroft_1  | ConnectionRefusedError: [Errno 111] Connection refused
mycroft_1  | 2020-05-23 19:27:53.556 | ERROR    |    63 | mycroft.messagebus.client.client:on_error:88 | Exception closing websocket: ConnectionRefusedError(111, 'Connection refused')
mycroft_1  | 2020-05-23 19:27:53.557 | WARNING  |    63 | mycroft.messagebus.client.client:on_error:91 | Message Bus Client will reconnect in 5 seconds.