reclient icon indicating copy to clipboard operation
reclient copied to clipboard

transport: Error while dialing dial unix /out/.temp/reproxy_789.sock: connect: connection refused

Open DarkMatterV opened this issue 10 months ago • 1 comments

Hi, I'm using AOSP RBE 0.57.0.4865132 and buildfarm 2.4.0 to build. And the number of concurrent actions is 500.

Lately, Occasional failures occur, it‘s log like:

F0410 19:58:46.227496  552492 main.go:143] Command failed: rpc error: code = Unavailable desc = retry budget exhausted (10 attempts): connection error: desc = "transport: Error while dialing dial unix /out/.temp/reproxy_789.sock: connect: connection refused"
goroutine 1 [running]:
github.com/golang/glog.stacks(0x0)
	external/com_github_golang_glog/glog.go:769 +0x8a
github.com/golang/glog.(*loggingT).output(0xc296a0, 0x3, 0xc00034e1c0, {0x9bc8da, 0xc00040df20}, 0x1, 0x0)
	external/com_github_golang_glog/glog.go:720 +0x46e
--
	external/com_github_golang_glog/glog.go:1148
main.main()
	cmd/rewrapper/main.go:143 +0x775

This seems to be caused by rewrapper failing to connect to reproxy, but I'm not sure

And I noticed that rewrapper and reproxy interact through the rpc protocol, on the same machine, whether this is a waste of resources (such as occupying socks port, etc.) or not stable enough. rewrapper is used to encapsulate commands and then pass them to reproxy, Is it considered to switch to the goroutine+channel mode to implement the reproxy function when the reproxy executes tasks and interacts with the server?

Someone who can help me?

DarkMatterV avatar Apr 10 '24 13:04 DarkMatterV