Community
Participate
Working Groups
When connecting to the dstore server using a REXEC connection, if a connection timeout occurs, the following error message is shown: Message: Unable to connect to REXEC host service on port 3512 of host xx Detail: Message from host: yy The actual message from host may be nothing or a part of output from the server, and is useless for a user. Since the cause of the failure is a SocketTimeoutException, the message should indicate the timeout and ask a user to retry with the increased timeout value.
This is a concrete incarnation of a more generic problem already known as per bug 153246. I agree that the error reporting for dstore REXEC should be improved because it's currently very hard to diagnose problems. Bug 194584 is also slightly related but refers to the message when a daemon is not running.
I think it's important to note that this does likely *not* require PII change but just a better way of forwarding the remote exception or error message into the Details page of the SystemMessage.
Setting milestone to 3.0.1 in case it's possible to deal with this without any PII.