xinushio

Results 8 comments of xinushio

使用ansiblefate部署fate2.0.0版本后，节点无法通信

时间过了挺久了，应该是按照这个流程来的https://github.com/FederatedAI/FATE/blob/v2.0.0/deploy/cluster-deploy/allinone/fate-allinone_deployment_guide.zh.md

terminate called after throwing an instance of 'std::runtime_error' what(): error in network setup: daa4eabb64cf : Receiving error - 1 : Connection reset by peer

I have not yet started party 0, but based on the running conditions on the host machine, under normal circumstances, party 1 should retry connecting to party 0 multiple times...

terminate called after throwing an instance of 'std::runtime_error' what(): error in network setup: daa4eabb64cf : Receiving error - 1 : Connection reset by peer

However, when running in the container, party 1 fails immediately.

terminate called after throwing an instance of 'std::runtime_error' what(): error in network setup: daa4eabb64cf : Receiving error - 1 : Connection reset by peer

If party 0 is started first, the computation proceeds normally.

terminate called after throwing an instance of 'std::runtime_error' what(): error in network setup: daa4eabb64cf : Receiving error - 1 : Connection reset by peer

Based on my testing, under normal circumstances, when party 1 tries to connect to party 0 and party 0 is not started, party 1 receives a "connection refused" exception. MP-SPDZ...

terminate called after throwing an instance of 'std::runtime_error' what(): error in network setup: daa4eabb64cf : Receiving error - 1 : Connection reset by peer

I hope MP-SPDZ can catch exceptions and retry in both scenarios until after 1 minute. Can MP-SPDZ help resolve this issue? Thank you.

terminate called after throwing an instance of 'std::runtime_error' what(): error in network setup: daa4eabb64cf : Receiving error - 1 : Connection reset by peer

I first started party0, then started party1, and was able to obtain the computation result successfully. ![Image](https://github.com/user-attachments/assets/ae3d6f04-518e-408d-9a86-83f7fd175812) However, when I start party1 first, it still shows a connection failure. ![Image](https://github.com/user-attachments/assets/6fca52b1-0069-44b1-adcf-3d1a2abcc318)

terminate called after throwing an instance of 'std::runtime_error' what(): error in network setup: daa4eabb64cf : Receiving error - 1 : Connection reset by peer

I've observed that this issue only arises when using docker-proxy mode, which suggests that it may not be caused by MP-SPDZ itself.