Topics

Railway•4mo ago

Debugging "killed replica" message

6a6c4123-f4c9-4c41-ba5f-c3115ddc1753 Every so often when performing a long task my deployment dies and the log simply states "Killed"

@replica: ff7bfdfa-8cb1-4e17-8ac0-c03a0fd886b7
View in Context

@replica: ff7bfdfa-8cb1-4e17-8ac0-c03a0fd886b7
View in Context

Is there any way I can debug why?

1 Reply

Percy•4mo ago

Project ID: 6a6c4123-f4c9-4c41-ba5f-c3115ddc1753,ff7bfdfa-8cb1-4e17-8ac0-c03a0fd886b7

Hang out with other likeminded developers & talk about all things https://railway.app on the Railway Community Server.

24KMembers

View on Discord

Want results from more Discord servers?

Add your server

More Posts

My project costs went from an estimated $5 to an actual $15 suddenly overnight.My project costs went from an estimated $5 to an actual $15 suddenly overnight. This is impossible, Flask application failed to respondIts running according to the logs, but it displays on the screen it failed to respond Project deploys successfully then crashes after a minute or 2Project-id:a152df40-b98b-4053-afe7-e4c47c064cca My Golang application builds and deploys successful Strapi/Postgres template data lossMy Railway account became frozen at the beginning of the month because the attached credit card got