pingcap / pingcap/tiup

TiUP deploy error :` if killed, check the password prompt}, cause: signal: killed`

Open
#900 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status/TODO type/question
Dominant language
Go
Stars
466
Forks
338
Avg merge
3d 7h
Merged PRs (30d)
8

Description

General Question

是否添加到 TiUP FAQ?

Linux 主机之间使用带有密码保护的 ssh-key 互信
TiUP deploy 部署时,出现 if killed, check the password prompt}, cause: signal: killed 错误
需要通过 -i 指定该 ssh-key 文件,如 -i /root/.ssh/id_rsa

tiup cluster deploy nji nightly db.yaml  --ssh=system -u root 
Starting component `cluster`: /root/.tiup/components/cluster/v1.2.3/tiup-cluster deploy nji nightly db.yaml --ssh=system -u root

  - Prepare 172.16.4.178:22 ... Error

Error: Failed to initialize TiDB environment on remote host '172.16.4.178' (task.env_init.failed)
  caused by: Failed to create new system user 'tidb' on remote host
    caused by: Failed to execute command over SSH for 'root@172.16.4.178:22'
      caused by: exit status 255

Verbose debug logs has been written to /root/logs/tiup-cluster-debug-2020-11-03-16-06-17.log.

Command output on remote host 172.16.4.178:
Permission denied, please try again.
Permission denied, please try again.
Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
TiUP debug logs:

  if killed, check the password prompt}, cause: signal: killed

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Locate the TiUP FAQ or deployment documentation and review how SSH options are currently documented. Add the password-protected SSH-key case, including the -i /root/.ssh/id_rsa example and the related error, then verify that the guidance clearly explains how to avoid the failed password prompt.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
devops, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.