You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi guys. Pulling the project´s docker files starting it all up, it only takes a while before requests stepping out of the SPA FE app, for example auth/profile or tickets/reserve keep hanging forever. After a couple of interactions with the app, I can inside inside the logs of the web container:
ERROR server no free workers in the pool, wait timeout exceed {"reason": "no free workers", "internal_event_name": "EventNoFreeWorkers", "error": "worker_watcher_get_free_worker: NoFreeWorkers:\n\tcontext deadline exceeded"}
Dockerfile uses the following version ARG ROAD_RUNNER_IMAGE=2023.3.12. I tried to set num_workers to 0, but to no avail. Would you have any suggestion for me as to what might be wrong? The specs of the machine within which the error is encountered is a Linux one with 8 CPUs and 16 GB of RAM. When I observe the load on CPUs and RAM sideways, there are plenty of available resources even with the error in place.
The text was updated successfully, but these errors were encountered:
Hi guys. Pulling the project´s docker files starting it all up, it only takes a while before requests stepping out of the SPA FE app, for example auth/profile or tickets/reserve keep hanging forever. After a couple of interactions with the app, I can inside inside the logs of the web container:
ERROR server no free workers in the pool, wait timeout exceed {"reason": "no free workers", "internal_event_name": "EventNoFreeWorkers", "error": "worker_watcher_get_free_worker: NoFreeWorkers:\n\tcontext deadline exceeded"}
Dockerfile uses the following version ARG ROAD_RUNNER_IMAGE=2023.3.12. I tried to set num_workers to 0, but to no avail. Would you have any suggestion for me as to what might be wrong? The specs of the machine within which the error is encountered is a Linux one with 8 CPUs and 16 GB of RAM. When I observe the load on CPUs and RAM sideways, there are plenty of available resources even with the error in place.
The text was updated successfully, but these errors were encountered: