2 years ago
Still seeing "activity StartToClose timeout" error message in the build logs for both a cron service and then also sometimes on other services on fresh deploys.
The cron service runs every hour and seems like maybe 30% of the time I see in the build logs:
Jul 15 12:15:44 =========================
Jul 15 12:15:44 Container failed to start
Jul 15 12:15:44 =========================
Jul 15 12:15:44
Jul 15 12:15:44 activity StartToClose timeout
6 Replies
2 years ago
Hi thanks for the response, let me know if this works for the link https://railway.app/project/9843f346-a12b-4123-a83d-6e17122da584/service/aa6e63dd-a192-448c-b3c1-7e4fb521b3a4?id=c5492797-8a61-446d-a4d5-3fa904420c43
2 years ago
Just wanted to check in if someone can take a look to see what the issue was, I've seen from other reports that reducing image size may help but was hoping to get more direction before going down that route if there is a different root cause. Thanks!
2 years ago
That depends, what is your image size? if it's much larger than 2GB you could see this issue.
2 years ago
Image size is ~6GB which is what I saw around the size of what others reported with issues. What I thought was odd is that it would still deploy sometimes so wasn't sure if size was actually the issue?
2 years ago
The size is definitely an issue and you will likely continue to experience intermittent deploy failures with an image of that size, please work on reducing the size of your image as much as possible.
