-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Optimization not running - Docker Apple M1 #553
Copy link
Copy link
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Describe the bug
Optimization is not running in docker image on Apple M1.
To Reproduce
Steps to reproduce the behavior:
- Docker image according to docs.
- Run strategy in optimization
Expected behavior
Task should be running providing results
[I 2026-02-26 23:59:44,412] A new study created in RDB with name: fiveMinBTCMean_optuna_ray_13221e6e-e751-4b6c-9e08-804c83e63d63
2026-02-26 23:59:48,170 INFO worker.py:2012 -- Started a local Ray instance.
========= DEBUGGING VALUE ==========
('==> Removed finished worker 13221e6e-e751-4b6c-9e08-804c83e63d63 from active '
'workers')
====================================
Different error running Fast Mode:
[2026-02-27 00:00:10,832] [timeloop] [INFO] Starting Timeloop..
[2026-02-27 00:00:10,833] [timeloop] [INFO] Registered job <function Optimizer.__init__.<locals>.check_for_termination at 0x7fffb5f17e20>
[2026-02-27 00:00:10,833] [timeloop] [INFO] Timeloop now started. Jobs will run based on the interval set
(raylet) Raylet is terminated. Termination is unexpected. Possible reasons include: (1) SIGKILL by the user or system OOM killer, (2) Invalid memory access from Raylet causing SIGSEGV or SIGBUS, (3) Other termination signals. Last 20 lines of the Raylet logs:
[state-dump] ReporterService.grpc_client.HealthCheck - 1 total (0 active), Execution time: mean = 50.82ms, total = 50.82ms, Queueing time: mean = 0.00ms, max = -0.00ms, min = 9223372036854.78ms, total = 0.00ms
[state-dump] NodeManager.deadline_timer.record_metrics - 1 total (1 active), Execution time: mean = 0.00ms, total = 0.00ms, Queueing time: mean = 0.00ms, max = -0.00ms, min = 9223372036854.78ms, total = 0.00ms
[state-dump] ObjectManager.UpdateAvailableMemory - 1 total (0 active), Execution time: mean = 0.52ms, total = 0.52ms, Queueing time: mean = 10.97ms, max = 10.97ms, min = 10.97ms, total = 10.97ms
[state-dump] NodeManager.deadline_timer.debug_state_dump - 1 total (1 active), Execution time: mean = 0.00ms, total = 0.00ms, Queueing time: mean = 0.00ms, max = -0.00ms, min = 9223372036854.78ms, total = 0.00ms
[state-dump] DebugString() time ms: 0
[state-dump]
[state-dump]
[2026-02-27 00:00:09,145 I 421 421] (raylet) accessor.cc:847: Received address and liveness notification for node, IsAlive = 1 node_id=97445a2bfa38d72e75ca5947b54d8919ca48a471707455252a6db5e7
[2026-02-27 00:00:10,055 I 421 421] (raylet) worker_pool.cc:530: Started worker process with pid 539, the token is 0
[2026-02-27 00:00:10,056 I 421 477] (raylet) agent_manager.cc:83: Agent process with name runtime_env_agent exited, exit code -1.
[2026-02-27 00:00:10,056 E 421 477] (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 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).
[2026-02-27 00:00:10,056 I 421 477] (raylet) main.cc:408: Raylet shutdown already triggered, ignoring death info: reason: UNEXPECTED_TERMINATION
reason_message: "runtime_env_agent failed and raylet fate-shares with it."
[2026-02-27 00:00:10,730 I 421 438] (raylet) object_store.cc:37: Object store current usage 8e-09 / 1.0085 GB.
[2026-02-27 00:00:10,811 I 421 421] (raylet) worker_pool.cc:739: Job 01000000 already started in worker pool.
========= DEBUGGING VALUE ==========
('==> Removed finished worker f683835a-f57e-47a4-8d4a-f6d115cb12d7 from active '
'workers')
====================================
Enviroment (please complete the following information):
- OS: MacOS M1, 15.7.4 (24G517)
- Docker Image
- Version: 1.13.7
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working