When exporting with dumpling, it reports "bind: address already in use", but the export result is fine

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

Original topic: dumpling导出时报bind: address already in use,导出结果又没有问题

| username: yeminhua

[TiDB Usage Environment] Production Environment
[TiDB Version] v6.5.1

May I ask what the following error message means? Is the port occupied? But it finally indicates that the export was successful, and the exported data was checked and is normal.

Error message:
[INFO] [dump.go:1327] [“meet error when stopping dumpling http service”] [error=“start listening: listen tcp :8281: bind: address already in use”]

| username: onlyacat | Original post link

The parameter StatusAddr in dumpling is the dumpling API server and pprof address, defaulting to 8281. It seems that this port is occupied on the machine, check with netstat. It should not affect usage, only reporting and monitoring.

| username: yeminhua | Original post link

Thank you, it should be that there were other processes doing export backups at that time.

| username: wangccsy | Original post link

Since it involves synchronizing from MySQL to MySQL, why not use MySQL’s tools directly instead of TiDB’s tools?

| username: dba远航 | Original post link

It should be caused by other backup processes that have not ended.

| username: yeminhua | Original post link

Yes, there are other backup processes running as well.

| username: yeminhua | Original post link

I did not synchronize from MySQL.

| username: system | Original post link

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