yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
218900ecfc237f6c0ba9f9684f9afa10f1d5ea9a
doc-exports/docs/cce/umn/cce_10_0490.html
qiujiandong1 ab1e53a279 CCE UMN 20251031 version 
Reviewed-by: Gergo-Bence Lorincz <a200452876@noreply.gitea.eco.tsi-dev.otc-service.com>
Co-authored-by: qiujiandong1 <qiujiandong1@huawei.com>
Co-committed-by: qiujiandong1 <qiujiandong1@huawei.com>
2026-01-15 10:25:22 +00:00

1.6 KiB
Raw Blame History

Node ID File

Check Items

Check the ID file format.

Solutions

  1. On the Nodes page of the CCE console, click the name of the abnormal node to go to the ECS page.
  2. Copy the node ID and save it to the local host.
  3. Log in to the abnormal node and back up the file.

    cp /var/lib/cloud/data/instance-id /tmp/instance-id
cp /var/paas/conf/server.conf /tmp/server.conf

  4. Log in to the abnormal node and write the obtained node ID to the file.

    echo Node ID > /var/lib/cloud/data/instance-id
echo Node ID > /var/paas/conf/server.conf