rob
Missing logs with deployment on Railway Metal
Yesterday I first switched to Railway Metal (and logs were working properly), then after a dependency update on my project logs stopped working on the new deployment.
I tried triggering a new deployment of the same commit and logs came back, if that can be helpful the bugged deployment was
094829ef-cddc-4da8-9230-802aadff7f8c
The project id is f6d25e17-9bb2-457f-8ce2-e55b5ce1dcd8
The service id is 8c4e4e87-7cf3-4ab2-9ec2-b6cc41db7b5b2 replies
Unresponsive deployment after some hours
Hello, I've been using Railway to host my Telegram bot for more than an year and I never experienced this sort of issue until I enabled app sleeping a few days ago.
With that option enabled, the bot would just go to sleep without ever being able to wake (but that's fine, given I didn't take into account that a Telegram bot only pulls for updates).
So, when I noticed that I disabled app sleeping and allowed the bot to redeploy with the new configuration but in the next days the bot became unresponsive after a few hours. I tried to fix it redeploying it but it was always a temporary fix and now it seems to be stuck again (with no issues logged).
Can you please check if there is anything wrong with the configuration or the deployment of my project?
I'd be happy to share any other information needed.
Also, I'd like to have the project back to work as soon as possible but I can keep it broken until the issue is triaged, if needed.
The project is f6d25e17-9bb2-457f-8ce2-e55b5ce1dcd8
The service is 8c4e4e87-7cf3-4ab2-9ec2-b6cc41db7b5b
The deployment is 81cc519b-a7a3-41db-8266-53e08952e935
EDIT: the deploy was triggered yesterday at 2:16 PM CET (GMT+2) and it was working properly at least until today at 1:15 AM CET (GMT+2)
36 replies
Will new developer plan subscribers get their fee waived?
Hi all, a friend of mine is looking to join Railway's developer plan before the pricing changes.
Given he is already a verified user, will he get his fee waived once he activates the plan?
6 replies
Cache mount ID is not prefixed with cache key when deploying test instance
Hello all,
today I tried to boot up my test instance but every attempt at doing so lead the deploys to fail immediately with the error
Cache mount ID is not prefixed with cache key
(no further information are present in build logs).
The Dockerfile used to build the project is the following (as copied from GitHub https://github.com/Stickerifier/Stickerify/blob/migrate-to-telegram-bot-api/Dockerfile):
It's also worth keeping in mind I configured the shared environment variable (used both by Production and Test) RAILWAY_DOCKERFILE_PATH
with value Railway.dockerfile
where I'd execute the following instructions:
This failure seems strange to me since everything works properly in my production environment.
The project ID is f6d25e17-9bb2-457f-8ce2-e55b5ce1dcd815 replies
Is it possible to configure Railway to deploy only after the old deploy is removed?
The project I keep deployed on the site does not allow for multiple instances running at the same time and the current deploy process causes an overlapping of about 20-30 seconds where 2 versions of the project are live concurrently (causing unneeded error logs in both instances)
Is it possible to prevent this by configuring Railway?
13 replies