A create&x on the FssagentRpc named pipe triggers the start of the FSRVP service. Such requests receive STATUS_PIPE_NOT_AVAILABLE errors until the service is available.
rpcclient should be changed to retry on STATUS_PIPE_NOT_AVAILABLE named pipe open responses, until either:
- the server responds with success
- the client timeout is reached
- the server responds with any other error code
This bug is fixed in master with:
Author: David Disseldorp <firstname.lastname@example.org>
Date: Mon Mar 3 19:49:35 2014 +0100
rpc_client: retry open on STATUS_PIPE_NOT_AVAILABLE
4.1 and 4.0 backports to follow.
Created attachment 9749 [details]
patch for 4.0.next, differs from master due to lack of 46d29d46bc065d51e3f7ca6892
Created attachment 9751 [details]
patch for 4.1.next, differs from master due to lack of 46d29d46bc065d51e3f7ca6892
Re-assigning to Karolin for inclusion in 4.1.next, 4.0.next.
Pushed to autobuild-v4-0-test and autobuild-v4-1-test.
(In reply to comment #4)
> Pushed to autobuild-v4-0-test and autobuild-v4-1-test.
Pushed to v4-1-test and v4-0-test.
Closing out bug report.