[TiDB Usage Environment] Production Environment / Testing / PoC
Testing
[TiDB Version]
V5.0.0
[Reproduction Path] What operations were performed when the issue occurred
tiup cluster list, unable to fetch the image.
[Encountered Issue: Issue Phenomenon and Impact]
TiDB was installed online in the testing environment. Due to changes in the network environment, it could not access the internet, causing TiDB to fail to start normally.
Then, I downloaded the offline image using tiup mirror clone tidb-community-server-v5.0.0-linux-x86_64 v5.0.0 --os=linux --arch=x86_64. After compressing it, I transferred it to the target server and decompressed it. I also downloaded the latest root.json and timestamp.json.
I re-specified the mirror using tiup mirror set /home/tidb-community-server-v5.0.0-linux-x86_64.
tiup cluster list reported an error.
[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]
It has nothing to do with the mirror. Even if it is still an online mirror now, this error would still occur. This is because the signature has expired due to long periods of inactivity.
But judging from the error, it should be this issue. Try reinstalling tiup in a different directory. Just reinstall tiup, not the TiDB cluster, and don’t delete the original tiup directory. After reinstalling, still use the original tiup to manage the cluster. The reinstallation is just to reacquire the signature.
This is for checking the component version. If it’s not the latest, it will inform you of the latest version, but it won’t affect your use of the current version. If tiup mirror is set to offline, this action will still occur.
Problem solved. I re-downloaded the offline package from the official website and reset it, and it worked normally. The first downloaded package probably had issues and was missing many components.
|
username: TiDBer_VtkBZH6I
|
username: 
|
username: 
I just turned around to discuss a problem, and the first reply is no longer mine. Everyone is too active.