- #Sg300 cli show interface errors install
- #Sg300 cli show interface errors update
- #Sg300 cli show interface errors upgrade
12:36:18,326 - MainThread - botocore.hooks - DEBUG - Event -groups: calling handler > 12:36:18,326 - MainThread - botocore.hooks - DEBUG - Event -groups: calling handler 12:36:18,326 - MainThread - DEBUG - Modifying paging parameters for operation: ListGroups 12:36:18,326 - MainThread - botocore.loaders - DEBUG - Loading JSON file: /home/ec2-user/venv/lib/python3.7/site-packages/botocore/data/iam//paginators-1.json 12:36:18,322 - MainThread - botocore.hooks - DEBUG - Event -groups: calling handler 12:36:18,321 - MainThread - awscli.clidriver - DEBUG - OrderedDict() 12:36:18,320 - MainThread - botocore.loaders - DEBUG - Loading JSON file: /home/ec2-user/venv/lib/python3.7/site-packages/botocore/data/iam//waiters-2.json 12:36:18,317 - MainThread - botocore.hooks - DEBUG - Event building-command-table.iam: calling handler 12:36:18,308 - MainThread - botocore.loaders - DEBUG - Loading JSON file: /home/ec2-user/venv/lib/python3.7/site-packages/botocore/data/iam//service-2.json 12:36:18,307 - MainThread - botocore.hooks - DEBUG - Event session-initialized: calling handler 12:36:18,307 - MainThread - botocore.credentials - DEBUG - Skipping environment variable credential check because profile name was explicitly set. 12:36:18,305 - MainThread - botocore.hooks - DEBUG - Event session-initialized: calling handler 12:36:18,305 - MainThread - awscli.clidriver - DEBUG - Arguments entered to CLI: $ aws iam list-groups -profile MyTestProfile -debug Here's an example of a command run with and without the -debug You can send the output to a text file to capture it for later review or to send Step the error occurs and to get context that can provide clues about what triggered The details in the output can help you to determine in which Request to the AWS servers, receive the response, and process the response into This causes theĪWS CLI to report details about every step it takes to process your command, send the The -debug option at the end of the command line. You can do this by running the command again and including One of the first things you should do when the AWS CLI reports an error that youĭon't immediately understand, or produces results that you don't expect, is get moreĭetail about the error.
#Sg300 cli show interface errors install
Installation before you download and install the latest version of the bundled installerįor your operating system. If you used one of the bundled installers, you may need to remove the existing Installing or updating the latest version of the
#Sg300 cli show interface errors update
How you update your version of the AWS CLI depends on how you originally installed
#Sg300 cli show interface errors upgrade
New services, features, or parameters is to upgrade to a version that was released Introduced in those new versions of the AWS CLI. New AWS services, features, and parameters are Upgrade to the most recent version of the AWS CLI. That the first thing you do (after checking your command for spelling errors!) is to If you receive an error that indicates that a command doesn't exist, or that itĭoesn't recognize a parameter that the documentation says is available, we recommend General: Ensure you're running a recent version of VERIFY_FAILED] certificate verify failed" error.