https://linen.dev logo
Powered by
Duplicate deployments
# help
a
When I deploy, it seems to still have previous deployments running (creating a discord bot, each deploy I do, I get one additional message through from the bot) How can I stop these deployments? Doing deployment list command they all show stopped except the last, but I think they aren't actually stopped yet
k
There should only be one instance of your service running at a time, so this is interesting. Is the number of replies perpetually increased, or does it eventually reduce to only one reply?
s
This is happening because our tokio runtime is not shutting down correctly for old deploys. The way to force them down for the moment is 
cargo shuttle project rm
to stop the projects container. Then do a 
cargo shuttle project new
again. We have been working on some code to change our architecture around this but it is not ready yet...
a
Ah okay, thanks! Will do project rm and new in the meantime 🙂 If it's still useful to know if it eventually reduces to one, I don't know right now but can check and post here sometime this week
I have done a project rm and project new and it seems I still have an old deployment running somewhere (though can only see one running the in deployment list) as I have a discord bot that should react to a specific message, and I changed the reaction it uses (one bot will only use one reaction) - I just got both the new and old reaction on the same message
I have one old project (have since changed to a different project name) that is showing as 
destroyed
, and all deployments except the bottom of the list I can see with the deployment list command for the running project are also 
stopped
- would providing my project names help find this rogue deployment that is still running?
After **another **project rm and project new cycle it appears the rogue instance is now stopped (only the new reaction when I send the trigger message)
Will close for now, sorry for spam 😇
PreviousNext
Powered by