CRON service failed
tbedrnik
HOBBYOP

2 years ago

Hello, I have a CRON service which runs every 15 minutes and dumps the DB into S3. I was notified couple days ago (around Railway degraded performance) that a build failed. Inspecting the Build logs showed:

=========================
Container failed to start
=========================
We failed to create a container for this image.

Every subsequent CRON scheduled run was in "skipped" state. Triggering the "Run now" button showed "Cannot redeploy without a snapshot" error.
I resolved this with an empty commit to trigger a new build.

Now it happened again. What can I do to prevent this? Is there a way to rebuild without having to commit to the connected GitHub repo?

View Deploy details

ⓘ Deployment information is only viewable by project members and Railway employees.

Solved

4 Replies

angelo-railway
EMPLOYEE

2 years ago

Hey there Tbedrik,

I have executed the cron manually and I was able to get it to run but I am not taking this likely. Workflows should run with finality. I have a request, what happens if we change the workflow to every 60 minutes. Reason why I ask is I want to see if load on our end impacts the finality of the cron.

Let me know when you have done this or if 15 minutes is a hard requirement.

tbedrnik
HOBBYOP

2 years ago

Hello, I'd rather not increase the interval. 15 minutes gives me the minimum backup granularity I need.

brody
EMPLOYEE

2 years ago

FWIW, I'm seeing a decent amount of the "cron not running reports" even with frequencies of once a day.

angelo-railway
EMPLOYEE

2 years ago

Understood, I have raised this to the team to gather more data.

Railway
BOT

7 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 7 months ago

Loading...