grpcd connects "as peer" to swapd if relaunched manually
Lederstrumpf opened this issue · 0 comments
Lederstrumpf commented
after relaunching manually using grpcd -d ~/.farcaster -m {data_dir}/msg -x {data_dir}/ctl -i {data_dir}/info -S {data_dir}/sync --grpc-port 50051 --grpc-ip 0.0.0.0:
[2022-12-09T15:31:59Z INFO farcaster_node::farcasterd::runtime] Service grpcd is now connected
[2022-12-09T15:31:59Z INFO farcaster_node::swapd::runtime] 0x3923…21ac | Peer grpcd reconnected
[2022-12-09T15:31:59Z INFO farcaster_node::swapd::runtime] 0x25dd…80ae | Peer grpcd reconnected
[2022-12-09T15:31:59Z INFO farcaster_node::swapd::runtime] 0x4fed…7676 | Peer grpcd reconnected
[2022-12-09T15:31:59Z INFO farcaster_node::swapd::runtime] 0x5334…05de | Peer grpcd reconnected
[2022-12-09T15:31:59Z INFO farcaster_node::swapd::runtime] 0x65fc…b333 | Peer grpcd reconnected
[2022-12-09T15:31:59Z INFO farcaster_node::swapd::runtime] 0x69cd…7ca6 | Peer grpcd reconnected
[2022-12-09T15:31:59Z INFO farcaster_node::swapd::runtime] 0x94ec…1e71 | Peer grpcd reconnected