https://linen.dev logo
Powered by
cargo shuttle deploy -> Deployment has not entered...
# help
s
No doubt I have done something goofy, but when I deploy my new test project, I don't seem to get any errors, but the deployment stops with the message 'Deployment has not entered the running state'. Is there a command I can run to 'look under the hood' and see what is wrong? Project name is jh-hello-htmx if that help.
g
The deploy command usually shows that message at the end, even though the deployment actually goes live.
Check 
cargo shuttle logs
and you might see that it is actually running
You can also check 
cargo shuttle deployment list
a
Typically this can happen if something like sqlx migrations failing happens (ie breaking the build before it can actually fully deploy)
s
Thank you, looks like the goofy thing I have done is have a sub-folder in my static folders. Hmm.
s
Did 
cargo shuttle deployment list
show the deployment crashed?
s
Yes, it did. Turns out I had made a mess of using the Rocket::fs::FileServer as I wasn't passing it the path returned by shuttle_static_folder::StaticFolder - I think I have it fixed now though
s
Okay 👍
Wait, does this also mean you did not get an output along the lines of "run 
cargo shuttle logs <some_id>
to see the error"? But you only got "Deployment has not entered the running state"?
s
^ is correct. Here are last few lines of output:
2023-03-07T08:23:34.203724135Z INFO Entering built state 2023-03-07T08:23:34.475130572Z INFO Entering loading state 2023-03-07T08:23:35.322329278Z TRACE {so_path="/opt/shuttle/shuttle-libs/2aff6ba5-53f5-4dfe-bba7-21d16218446b"} shuttle_service::loader: loading .so path 2023-03-07T08:23:35.570843143Z INFO shuttle_deployer::deployment::provisioner_factory: Fetching secrets for deployment 2023-03-07T08:23:35.572765654Z INFO shuttle_deployer::deployment::provisioner_factory: Done fetching secrets 2023-03-07T08:23:35.575329688Z TRACE shuttle_service::loader: bootstrapping done 2023-03-07T08:23:35.925680867Z TRACE shuttle_service::loader: creating handle done Deployment has not entered the running state
a
this appears to be a thing that's very similar to an issue on gh I opened about the terminal not giving any meaningful outputs if it encounters panic/otherwise unrecoverable errors post-compilation
s
Yeah my code was panicing, sounds like the same issue
s
Okay, we can mark the GH as a good first contribution candidate as this should be easy to fix. And having it fixed will be helpful
11 Views
PreviousNext
Powered by