a year ago
[2025-06-25 04:57:27 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:2)
--
[2025-06-25 04:57:29 +0000] [1] [ERROR] Worker (pid:2) was sent SIGKILL! Perhaps out of memory?
--
[2025-06-25 04:57:29 +0000] [101] [INFO] Booting worker with pid: 101
3 Replies
a year ago
See other threads here on Central Station for similar issues, for example:
Status changed to Awaiting User Response Railway • 11 months ago
christian
See other threads here on Central Station for similar issues, for example: * <https://station.railway.com/questions/critical-worker-timeout-ee432a02> * <https://station.railway.com/questions/critical-worker-timeout-32a23061>
a year ago
Christan, thank you very much
I don't have that much skill with railway and redis. I'll try to see how to do it, but I'm having trouble... I'm a data engineer... but software engineering isn't really my thing
Status changed to Awaiting Railway Response Railway • 11 months ago
christian
See other threads here on Central Station for similar issues, for example: * <https://station.railway.com/questions/critical-worker-timeout-ee432a02> * <https://station.railway.com/questions/critical-worker-timeout-32a23061>
a year ago
The problem with my application occurs in the response from an endpoint where I do the integration.
I have a call to the API where I query a product, which only receives one barcode at a time and each item I call can have up to 5 barcodes. So I execute at least 75 calls to the API... this takes a long time to return. But in Railway this product call does not return even when I query an item.