[TiDB Usage Environment] Production Environment
[TiDB Version] v6.5.3
[Reproduction Path]
Regular user executes pre-installation check command $ tiup cluster check ./topology.yaml --user jhdcp --ssh system
Error: Error: failed to fetch cpu-arch or kernel-name: executor.ssh.execute_failed: Failed to execute command over SSH for ‘jhdcp@xx.xx.xx.122:22’ {ssh_stderr: Connection timed out during banner exchange, ssh_stdout: , ssh_command: export LANG=C; PATH=$PATH:/bin:/sbin:/usr/bin:/usr/sbin /usr/bin/sudo -H bash -c “uname -s”}, cause: exit status 255
121 and 122 need to establish mutual trust. You can try SSH to 122 to see if a password is required.
Log in to the control machine as the tidb user and use ssh to log in to the target machine’s IP. If you can log in successfully without entering a password, it means the SSH mutual trust configuration is successful.
Yes, and after executing multiple times, the machines that fail are different. For example, 122 and 123 fail, and after executing again, it might be 122 and 125 that fail.
When an SSH connection encounters the error “connection timed out during banner exchange” during the handshake phase, it is usually due to one of the following reasons:
Network Connection Issues: There may be network connection failures or blockages preventing the establishment of the SSH connection. You can try checking if the network connection is normal and ensure smooth communication between the server and the client.
Firewall or Security Group Configuration: There may be configuration issues with the firewall or security group that are blocking the establishment of the SSH connection. Ensure that the firewall or security group settings allow SSH connection traffic and verify your network security policies.
SSH Service Configuration Issues: There may be configuration issues with the SSH service, such as incorrect port settings or invalid SSH configuration parameters. Check the SSH server’s configuration file (usually /etc/ssh/sshd_config) to ensure that the port number, authentication options, and other settings are correct.
SSH Server Issues: There may be issues with the SSH server itself, such as resource limitations, service anomalies, or other problems causing the SSH connection to fail. You can try restarting the SSH server and checking the system logs for more detailed information.
When debugging this issue, it is recommended to use some tools and methods to resolve it. You can try using the ping command to check the network connection, the telnet command to test the accessibility of the SSH port, and view system log files for more error information. If the problem persists, it is advisable to consult a system administrator or network expert for more detailed help and support.
Why do so many people encounter SSH issues? I always use a regular user with sudo privileges to directly use the automatically configured SSH from check apply, and I’ve never had any problems.
|
username: fish
|
username: 
|
username: 
|
username: 
This is some advanced syntax, I can’t understand it~~~
|
username: 
|
username: 
|
username: 
|
username: