- Mais recentes
- Mais votos
- Mais comentários
One of the first things you can do when the AWS CLI produces results that you don't expect, is get more detail by running the command again and including the --debug option at the end of the command line. This causes the AWS CLI to report details about every step it takes to process your command, send the request to the AWS servers, receive the response, and process the response into the output you see.
Hi! Along with what other users have suggested: using the debug option at the end of the command line commands can help.
As for help troubleshooting the lightsail deploy, the following additional API calls may help:
- lightsail get-container-log: https://docs.aws.amazon.com/cli/latest/reference/lightsail/get-container-log.html
- lightsail get-cloud-formation-stack-records (I don't think this will help as your error most likely isn't with the CFT, but with the container): https://docs.aws.amazon.com/cli/latest/reference/lightsail/get-cloud-formation-stack-records.html
If there's enough progress, you can also look at the system status check or the instance status check for more information: https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-viewing-instance-health-metrics#viewing-instance-metrics-console
You may also want to try bumping up the lightsail server to one with more memory, CPU, space, etc depending on what your error is and see if that helps.
Conteúdo relevante
- AWS OFICIALAtualizada há 7 meses
- AWS OFICIALAtualizada há um ano
I did try the--debug
flag in my deploy automation script. The problem is I need to capture the JSON output and process it. Getting the cli to output its debug information means debug output will be mixed with the JSON I'm trying to parse; so the whole process won't work. I haven't worked out how to both turn on debug output and still be able to process the command output.Scratch that. --debug flag sends its output to stderr. I must have been confused by something else.