安装过程中,修改了sshd的端口,通过tiup deploy 在copy file就报错

1、tiup 通过deploy部署过程中,报错copyfile失败,topology.yaml中,我也针对monitor,prometheus这些添加了sshd_port端口
2、能否提供通过tiup 迁移监控组件节点的文档提供,文档:https://asktug.com/t/topic/33165是针对ansible迁移的

你好,

可以上传下 topology 文件看下。和 tiup 的 debug 日志。

目前还没有。我们记录一下

迁移文档ok了,麻烦给我们反馈一下

第1条,后面我还原了sshd端口,现阶段已经ok了

tiup 支持指定 sshd 端口的,可以上传下上面的信息我们帮忙看下。

现在没这个错误了,当时我直接修改了默认sshd端口,我可以提供我当时的topology.yaml:

global:
user: “tidb”
ssh_port: 22
deploy_dir: “/data1”
data_dir: “/data1”

monitored:
node_exporter_port: 9100
blackbox_exporter_port: 9115
deploy_dir: “/opt/midd/monitored-9100”
data_dir: “/opt/midd/monitored-9100/data”
log_dir: “/opt/midd/monitored-9100/log”

server_configs:
tidb:
log.slow-threshold: 300
tikv:
readpool.unified.max-thread-count: 6
readpool.storage.use-unified-pool: false
readpool.coprocessor.use-unified-pool: true
storage.block-cache.capacity: 15GB
raftstore.capacity: 400GB
pd:
replication.location-labels: [“host”]
schedule.leader-schedule-limit: 4
schedule.region-schedule-limit: 2048
schedule.replica-schedule-limit: 64

pd_servers:

  • host: 10.0.0.67
    name: “pd-1”
    client_port: 2379
    peer_port: 2380
    deploy_dir: “/data1/pd-2379”
    data_dir: “/data1/pd-2379/data”
    log_dir: “/data1/pd-2379/log”
    config:
    schedule.max-merge-region-size: 20
    schedule.max-merge-region-keys: 200000
  • host: 10.0.0.68
    name: “pd-2”
    client_port: 2379
    peer_port: 2380
    deploy_dir: “/data1/pd-2379”
    data_dir: “/data1/pd-2379/data”
    log_dir: “/data1/pd-2379/log”
    config:
    schedule.max-merge-region-size: 20
    schedule.max-merge-region-keys: 200000
  • host: 10.0.0.69
    name: “pd-3”
    client_port: 2379
    peer_port: 2380
    deploy_dir: “/data1/pd-2379”
    data_dir: “/data1/pd-2379/data”
    log_dir: “/data1/pd-2379/log”
    config:
    schedule.max-merge-region-size: 20
    schedule.max-merge-region-keys: 200000

tikv_servers:

  • host: 10.0.0.64
    port: 20160
    status_port: 20180
    deploy_dir: “/data1/tikv-20160”
    data_dir: “/data1/tikv-20160/data”
    log_dir: “/data1/tikv-20160/log”
    numa_node: “0”
    config:
    server.labels: { host: “tikv1” }

  • host: 10.0.0.65
    port: 20160
    status_port: 20180
    deploy_dir: “/data1/tikv-20160”
    data_dir: “/data1/tikv-20160/data”
    log_dir: “/data1/tikv-20160/log”
    numa_node: “0”
    config:
    server.labels: { host: “tikv2” }

  • host: 10.0.0.66
    port: 20160
    status_port: 20180
    deploy_dir: “/data1/tikv-20160”
    data_dir: “/data1/tikv-20160/data”
    log_dir: “/data1/tikv-20160/log”
    numa_node: “0”
    config:
    server.labels: { host: “tikv3” }

monitoring_servers:

  • host: 10.20.134.207
    ssh_port: 1122
    port: 9090
    deploy_dir: “/opt/midd/prometheus-8249”
    data_dir: “/opt/midd/prometheus-8249/data”
    log_dir: “/opt/midd/prometheus-8249/log”

grafana_servers:

  • host: 10.20.134.207
    ssh_port: 1122
    port: 3000
    deploy_dir: /opt/midd/grafana-3000

alertmanager_servers:

  • host: 10.20.134.207
    ssh_port: 1122
    web_port: 9093
    cluster_port: 9094
    deploy_dir: “/opt/midd/alertmanager-9093”
    data_dir: “/opt/midd/alertmanager-9093/data”
    log_dir: “/opt/midd/alertmanager-9093/log”
    上述配置,然后执行tiup cluster deploy tidb-prod -v v4.0.2 -u root,然后就报了copy文件报错

copy file 报错可以尝试重复执行,或者看下目录权限问题,如果有当时的 debug 日志会好一些