2 months ago
I am experiencing an issue with a MySQL database service in my project. The database keeps suspending itself, causing connection drops in my Strapi backend. The deployment logs explicitly show the message: "The database deployment is sleeping". Here are the troubleshooting steps I've already verified:
The Serverless toggle is completely DISABLED in the Settings > Deploy section specifically for the MySQL service.
I checked the project metrics, and there are no spikes indicating OOM (Out of Memory) kills or CPU limits being hit.
The internal MySQL logs show Received SHUTDOWN from user right before it goes to sleep. Is there a specific idle timeout rule for databases enforcing this sleep state? Any help getting this container to respect the non-serverless configuration would be greatly appreciated.
Attachments
2 Replies
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
i think even when serverless shows as "off" in the ui, the change might not have actually been applied. the fix is to toggle serverless on, then back off, then actually hit deploy to save the change. that's what pushes the real "false" value to the backend instead of leaving it in a null/unapplied state. after redeploying the mysql service should stop sleeping
ilyass012
i think even when serverless shows as "off" in the ui, the change might not have actually been applied. the fix is to toggle serverless on, then back off, then actually hit deploy to save the change. that's what pushes the real "false" value to the backend instead of leaving it in a null/unapplied state. after redeploying the mysql service should stop sleeping
2 months ago
I'm going to try this, and if the database doesn't go to sleep in the next few hours, I will close the thread. Thanks!
Status changed to Solved lomposs • 2 months ago