-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
cli: enhance errors reported upon conn failures
Prior to this patch, the various CLI commands were making a halfhearted attempt at decorating the underlying error with some troubleshooting instructions. Unfortunately, this was mixing up situations where the TCP connection failed outright, those where the security settings were incorrect, and connections dropped later, after the initial handshake was successful. In practice, we've noticed that the troubleshooting steps are rather different for both kinds of situations. So this patch enhances the code to clarify what is going on. It attempts to distinguish: - TCP connection problem ("check --host vs --advertise-host"). - secure conn to insecure server ("use --insecure?") - invalid TLS settings / TLS auth error ("check credentials"). - timeouts. - connection lost (e.g. conn closed by server). Release note (cli change): The various `cockroach` client comments now better attempt to inform the user about why a connection is failing.
- Loading branch information
Showing
6 changed files
with
345 additions
and
107 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.