What is the issue when DM reports an error after stopping and restarting, even though DM display shows everything is normal?

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: dm停止重启后报错是什么问题，dm display都是正常的

| username: Sunward

【TiDB Usage Environment】Production Environment / Testing / PoC
【TiDB Version】
【Reproduction Path】What operations were performed when the issue occurred
【Encountered Issue: Issue Phenomenon and Impact】
【Resource Configuration】
【Attachments: Screenshots / Logs / Monitoring】

image
image1183×147 8.23 KB

image
image1213×179 8.5 KB

2
| username: xfworld | Original post link

Check the DM logs, specifically the master node’s logs.

3
| username: 春风十里 | Original post link

Error Investigation:
Method 1: Execute the query-status command to check the task running status and related error output. For example: tiup dmctl --master-addr 192.168.0.100:8261 query-status task3.yaml
Method 2: If Prometheus and Grafana were correctly deployed when using TiUP to deploy the DM cluster, such as Grafana’s address being 172.16.10.71, you can open http://172.16.10.71:3000 in a browser to enter Grafana, select the DM Dashboard to view DM-related monitoring items. Refer to monitoring and alert settings for specific monitoring metrics.
Method 3: Check the DM running status and related errors through log files.
DM-master log directory: Set through the DM-master process parameter --log-file. If DM is deployed using TiUP, the log directory is located at {log_dir}.
DM-worker log directory: Set through the DM-worker process parameter --log-file. If DM is deployed using TiUP, the log directory is located at {log_dir}.

4
| username: Fly-bird | Original post link

Check the logs, can’t figure out anything without them.

5
| username: dba远航 | Original post link

Check if there are any anomalies in the configuration file.

6
| username: lichunzhu-PingCAP | Original post link

This 1146 error seems to come from the upstream MySQL. It might be an issue with the table lookup in the upstream MySQL. You can check the DM logs and investigate the corresponding SQL execution in the upstream.

7
| username: Jellybean | Original post link

The error code is 1146, which usually means that the corresponding database table cannot be found (Table Not Exists).

  • Please check if the upstream MySQL has specified the database table to be synchronized.
  • Confirm whether the database table name is correctly written in the synchronization stream.
8
| username: Sunward | Original post link

The MySQL system table was accidentally deleted.

9
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.