# Fail to ray.init on Apple M3 Pro **URL:** \ **Category:** Ray Core\ **Created:** [October 14, 2025, 10:47pm UTC](https://discuss.ray.io/t/fail-to-ray-init-on-apple-m3-pro/23246 "2025-10-14T22:47:24Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Eser\_Kandogan](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/eser_kandogan/32/8247_2.png) [@Eser\_Kandogan](https://discuss.ray.io/u/Eser_Kandogan)\ **Post date:** [October 14, 2025, 10:47pm UTC](https://discuss.ray.io/t/fail-to-ray-init-on-apple-m3-pro/23246/1 "2025-10-14T22:47:24Z")
I am getting the following errors (raylet.err): The raylet fate shares with the agent. This can happen because - The version of `grpcio` doesn’t follow Ray’s requirement. Agent can segfault with the incorrect `grpcio` version. Check the grpcio version `pip freeze | grep grpcio`. - The agent failed to start because of unexpected error or port conflict. Read the log `cat /tmp/ray/session_latest/logs/{dashboard_agent|runtime_env_agent}.log`. - The agent is killed by the OS (e.g., out of memory). [2025-10-14 15:40:35,254 E 185 254] (raylet) agent\_manager.cc:87: The raylet exited immediately because one Ray agent failed, agent\_name = runtime\_env\_agent. The raylet fate shares with the agent. This can happen because - The version of `grpcio` doesn’t follow Ray’s requirement. Agent can segfault with the incorrect `grpcio` version. Check the grpcio version `pip freeze | grep grpcio`. - The agent failed to start because of unexpected error or port conflict. Read the log `cat /tmp/ray/session_latest/logs/{dashboard_agent|runtime_env_agent}.log`. You can find the log file structure here [Configuring Logging — Ray 3.0.0.dev0](https://docs.ray.io/en/master/ray-observability/user-guides/configure-logging.html#logging-directory-structure) . - The agent is killed by the OS (e.g., out of memory). ray\_client\_server.err: (base) ray@blue\_server\_ray:/blue\_data/data/ray/session\_latest/logs$ cat ray\_client\_server.err 2025-10-14 15:39:26,767 INFO server.py:901 – Starting Ray Client server on 172.18.0.4:10001, args Namespace(host=‘172.18.0.4’, port=10001, mode=‘proxy’, address=‘172.18.0.4:6380’, redis\_username=None, redis\_password=None, runtime\_env\_agent\_address=‘[http://172.18.0.4:50278](http://172.18.0.4:50278)’) 2025-10-14 15:40:33,975 INFO proxier.py:697 – New data connection from client 936507d607a24baba9c084f0cf1534c0: WARNING: All log messages before absl::InitializeLog() is called are written to STDERR I0000 00:00:1760481634.007812 352 fork\_posix.cc:71] Other threads are currently calling into gRPC, skipping fork() handlers 2025-10-14 15:40:34,017 INFO proxier.py:342 – SpecificServer started on port: 23000 with PID: 359 for client: 936507d607a24baba9c084f0cf1534c0 2025-10-14 15:40:35,603 ERROR proxier.py:825 – Proxying Logstream failed! Traceback (most recent call last): File “/home/ray/anaconda3/lib/python3.10/site-packages/ray/util/client/server/proxier.py”, line 822, in Logstream for resp in resp\_stream: File “/home/ray/anaconda3/lib/python3.10/site-packages/grpc/\_channel.py”, line 543, in \__next_\_ return self.\_next() File “/home/ray/anaconda3/lib/python3.10/site-packages/grpc/\_channel.py”, line 969, in \_next raise self grpc.\_channel.\_MultiThreadedRendezvous: \<\_MultiThreadedRendezvous of RPC that terminated with: status = StatusCode.UNAVAILABLE details = “Socket closed” debug\_error\_string = “UNKNOWN:Error received from peer ipv4:127.0.0.1:23000 {grpc\_message:“Socket closed”, grpc\_status:14}” \> 2025-10-14 15:40:35,604 ERROR proxier.py:750 – Proxying Datapath failed! Traceback (most recent call last): File “/home/ray/anaconda3/lib/python3.10/site-packages/ray/util/client/server/proxier.py”, line 743, in Datapath for resp in resp\_stream: File “/home/ray/anaconda3/lib/python3.10/site-packages/grpc/\_channel.py”, line 543, in \__next_\_ return self.\_next() File “/home/ray/anaconda3/lib/python3.10/site-packages/grpc/\_channel.py”, line 969, in \_next raise self grpc.\_channel.\_MultiThreadedRendezvous: \<\_MultiThreadedRendezvous of RPC that terminated with: status = StatusCode.UNAVAILABLE details = “Socket closed” debug\_error\_string = “UNKNOWN:Error received from peer {grpc\_status:14, grpc\_message:“Socket closed”}” \> 2025-10-14 15:40:56,928 INFO proxier.py:392 – Specific server 936507d607a24baba9c084f0cf1534c0 is no longer running, freeing its port 23000 2025-10-14 15:41:05,611 INFO proxier.py:769 – 936507d607a24baba9c084f0cf1534c0 last started stream at 1760481633.9639764. Current stream started at 1760481633.963976 **1. Severity of the issue: (select one)** None: I’m just curious or want clarification. Low: Annoying but doesn’t hinder my work. Medium: Significantly affects my productivity but can find a workaround. x High: Completely blocks me. **2. Environment:** - Ray version: 2.46.0 - Python version: 3.10.12 - OS: 15.0.1 (24A348) - Cloud/Infrastructure: - Other libs/tools (if relevant):Package Version **3. What happened vs. what you expected:** - Expected: ray.init to initialize - Actual: receiving error ---
**Author:** ![RunLLM](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/runllm/32/8249_2.png) [@RunLLM](https://discuss.ray.io/u/RunLLM)\ **Post date:** [October 14, 2025, 10:48pm UTC](https://discuss.ray.io/t/fail-to-ray-init-on-apple-m3-pro/23246/2 "2025-10-14T22:48:03Z")
Your error message indicates that Ray’s “raylet” process is exiting because a required agent (dashboard\_agent or runtime\_env\_agent) failed. The most common causes are: (1) an incompatible grpcio version, (2) a port conflict or agent startup failure, or (3) the agent being killed by the OS (e.g., out of memory) ([agent\_manager.cc](https://github.com/ray-project/ray/blob/master/src/ray/raylet/agent_manager.cc), [Ray issue #56580](https://github.com/ray-project/ray/issues/56580)). For Ray 2.46.0 and Python 3.10.12, you should use grpcio \>=1.42.0 (your grpcio==1.74.0 is compatible per [setup.py](https://github.com/ray-project/ray/blob/master/python/setup.py)). However, some users have reported segfaults or agent crashes with certain grpcio versions or when installing Ray via non-pip methods (e.g., uv) ([Ray issue #53631](https://github.com/ray-project/ray/issues/53631), [Ray issue #54587](https://github.com/ray-project/ray/issues/54587), [Discourse: uv breaks dashboard](https://discuss.ray.io/t/installing-via-uv-breaks-dashboard/22609)). Also, port conflicts or missing dependencies can cause the agent to fail. Check the logs at /tmp/ray/session\_latest/logs/{dashboard\_agent|runtime\_env\_agent}.log for more details, and ensure your environment is not running out of memory ([agent\_manager.cc](https://github.com/ray-project/ray/blob/master/src/ray/raylet/agent_manager.cc), [Ray issue #56580](https://github.com/ray-project/ray/issues/56580)). Would you like a step-by-step troubleshooting guide? Sources: - [agent\_manager.cc](https://github.com/ray-project/ray/blob/master/src/ray/raylet/agent_manager.cc) - [Ray issue #56580](https://github.com/ray-project/ray/issues/56580) - [Ray issue #53631](https://github.com/ray-project/ray/issues/53631) - [Ray issue #54587](https://github.com/ray-project/ray/issues/54587) - [Discourse: uv breaks dashboard](https://discuss.ray.io/t/installing-via-uv-breaks-dashboard/22609) - [setup.py](https://github.com/ray-project/ray/blob/master/python/setup.py) Hint: Mention @RunLLM in the post for followups.