Skye
Explore posts from serversNNormal
•Created by Skye on 9/9/2024 in #🤝ask-a-question
RequestingRoom
Troubleshooting an issue in Unity that seems to keep cropping up. We instantiate different avatars depending on the platform. For some reason, entering play mode in the game while attempting to instantiate the "screen player" avatar for non-XR players leads to a permanent "RequestingRoom" message on the Realtime component.
A "Realtime: RealtimeView attempting to unregister, but is not found in this instance of Realtime's scene view list." error occurs when exiting play mode, but I assume this is because the connection was never established in the first place?
The avatar spawning process is fairly complicated, but it seems like that shouldn't be particularly relevant since we have JoinRoomOnStart enabled?
(Unfortunately, I can't test the XR player at this exact moment as I'm away from my typical workstation).
Any insight would be appreciated. Thanks!
15 replies
Celery worker container dies while Starting Pool
Project ID: 1639f59c-5c44-42c3-9a46-6b7566be82f3
Running a Django application with Postgres + Redis... setup has been fine so far, a few silly misconfigurations on my part, but I'm a little stumped on this one since there's very little data to suggest what might be going wrong.
I'm attempting to deploy the Celery worker as a separate service based off the same repo that holds the Django project. I looked briefly over one of the templates and didn't see anything drastically different from my configuration, or perhaps I'm just not experienced enough to identify it. Here's some of the logs prior to failure:
-------------- celery@dce1163c1a98 v5.4.0 (opalescent)
--- -----
-- ** ---- Linux-6.1.0-9-cloud-amd64-x86_64-with-glibc2.39 2024-07-26 15:14:01
- * --- * ---
- ---------- [config]
- ---------- .> app: akashi:0x7fd6d473ef50
- ---------- .> transport: redis://default:@redis.railway.internal:6379/0
- ---------- .> results: redis://default:@redis.railway.internal:6379/0
- * --- * --- .> concurrency: 32 (prefork)
-- ** ---- .> task events: ON
--- ** -----
-------------- [queues]
.> celery exchange=celery(direct) key=celery
[tasks] ... [2024-07-26 15:14:01,600: DEBUG/MainProcess] | Worker: Starting Hub [2024-07-26 15:14:01,600: DEBUG/MainProcess] ^-- substep ok [2024-07-26 15:14:01,600: DEBUG/MainProcess] | Worker: Starting Pool container event container died
[tasks] ... [2024-07-26 15:14:01,600: DEBUG/MainProcess] | Worker: Starting Hub [2024-07-26 15:14:01,600: DEBUG/MainProcess] ^-- substep ok [2024-07-26 15:14:01,600: DEBUG/MainProcess] | Worker: Starting Pool container event container died
14 replies