You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a Docker process was started on the FE machine. When restarting the FE process, the FE process fails to start, and the error log is as follows
The reason is that the Docker process causes a new virtual network card to be added. When FE starts, it retrieves the machine's IP and port, and then verifies it against the IP and port stored in the meta metadata. By default, it only takes the first entry from the list, which in this case is the newly added virtual network card, causing the process to fail and exit immediately.
the possible solution should be to retrieve all local addresses and then iterate through them for validation.
Expected behavior (Required)
Real behavior (Required)
StarRocks version (Required)
3.3.0-19a3f66
The text was updated successfully, but these errors were encountered:
Steps to reproduce the behavior (Required)
a Docker process was started on the FE machine. When restarting the FE process, the FE process fails to start, and the error log is as follows
The reason is that the Docker process causes a new virtual network card to be added. When FE starts, it retrieves the machine's IP and port, and then verifies it against the IP and port stored in the meta metadata. By default, it only takes the first entry from the list, which in this case is the newly added virtual network card, causing the process to fail and exit immediately.
the possible solution should be to retrieve all local addresses and then iterate through them for validation.
Expected behavior (Required)
Real behavior (Required)
StarRocks version (Required)
3.3.0-19a3f66
The text was updated successfully, but these errors were encountered: