Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Feature] better error message for "ERROR node.py:1286 -- ERROR as"

See original GitHub issue

Search before asking

I searched the issues and found no similar issues.

Ray Component

Ray Core

What happened + What you expected to happen

Installed ray using the helm charts from 95d1476:

helm -n ray upgrade --install example-cluster --create-namespace deploy/charts/ray

Open a shell on the head node and try and connect:

❯ kubectl exec -i -t -n ray example-cluster-ray-head-type-dqhkd -- /bin/bash
(base) ray@example-cluster-ray-head-type-dqhkd:~$ python
Python 3.7.7 (default, May  7 2020, 21:25:33)
[GCC 7.3.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import ray
>>> ray.init(address='127.0.0.1:10001')
2022-01-16 03:22:37,246	INFO worker.py:843 -- Connecting to existing Ray cluster at address:  10.42.1.3:10001
2022-01-16 03:22:57,309	ERROR node.py:1286 -- ERROR as
2022-01-16 03:23:19,330	ERROR node.py:1286 -- ERROR as
2022-01-16 03:23:41,363	ERROR node.py:1286 -- ERROR as
2022-01-16 03:24:03,429	ERROR node.py:1286 -- ERROR as
2022-01-16 03:24:25,463	ERROR node.py:1286 -- ERROR as
2022-01-16 03:24:47,491	ERROR node.py:1286 -- ERROR as
2022-01-16 03:25:09,518	ERROR node.py:1286 -- ERROR as
2022-01-16 03:25:31,585	ERROR node.py:1286 -- ERROR as
2022-01-16 03:25:53,618	ERROR node.py:1286 -- ERROR as
2022-01-16 03:26:15,755	ERROR node.py:1286 -- ERROR as
2022-01-16 03:26:37,789	ERROR node.py:1286 -- ERROR as
2022-01-16 03:26:59,853	ERROR node.py:1286 -- ERROR as
2022-01-16 03:27:21,876	ERROR node.py:1286 -- ERROR as
2022-01-16 03:27:43,902	ERROR node.py:1286 -- ERROR as
2022-01-16 03:28:05,930	ERROR node.py:1286 -- ERROR as