a year ago
I have deployed a python project with docker and used railway cron to run it every 10 minutes, it worked for some hours, but then only a "Starting container" log was printed for a run, and no more logs were printed for 10 minutes, and then a new run was started, still with a single "Starting container" log.
I tried to make some trivial changes to trigger redeployment, the cron runs are normal now, but a run of an old deployment is still running, it isn't stopped even after more runs have completed. The old deployement is 57017721-60e3-4202-96bf-1bcc5a38d5ef, it was removed already, but the run has been running for ~5h and is still running. I have tried to delete the cron schedule and then recover it, this run is still running.
7 Replies
a year ago
Hello,
There wasn't actually anything running, it was purely incorrect state, but I've marked it as removed!
Best,
Brody
Status changed to Awaiting User Response Railway • about 1 year ago
brody
Hello,There wasn't actually anything running, it was purely incorrect state, but I've marked it as removed!Best,Brody
a year ago
Hi, this problem is gone, thanks!
However, another problem remains, when a run starts, only a "Starting container" log is printed, and then no more logs for 10 minutes, until the next scheduled run is started and this run is forced stopped, but normally this job only runs for ~1min and there are many logs during execution. the deployement is 0dc8468d-ad9e-4509-bb09-2c5108f96537.
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Can you try adding the following line to your Dockerfile? -
ENV PYTHONUNBUFFERED=1Status changed to Awaiting User Response Railway • about 1 year ago
brody
Can you try adding the following line to your Dockerfile? -ENV PYTHONUNBUFFERED=1
a year ago
I had added this line to Dockerfile, and it works for one day currently, since this problem occurred after 2 days for the previous deployment, I guess I need to wait longer to make sure it works...
Status changed to Awaiting Railway Response Railway • about 1 year ago
Status changed to Awaiting User Response Railway • about 1 year ago
brody
Sounds good, please let me know how it works out.
a year ago
Since I don't need the service anymore, I've stopped it (it calls paid APIs so I can't afford to keep it running). So unfortunately I still don't know how it works out in the long term 
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
All good! I'll go ahead and close this out but please feel free to open it if you need anything else!
Status changed to Awaiting User Response Railway • about 1 year ago
Status changed to Solved jake • about 1 year ago