-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
transport: Error while dialing dial unix /out/.temp/reproxy_789.sock: connect: connection refused #42
Comments
Hi - rewrapper and reproxy communite through UDS (Unix Domain Sockets) on Linux. The communication happens through a special device file on disk. Android builds by default start reproxy when used with
With rewrapper and reproxy, each build action is its own separate process - so there are multiple |
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:
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?
The text was updated successfully, but these errors were encountered: