[
https://issues.apache.org/jira/browse/IGNITE-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16524876#comment-16524876
]
Peter Ivanov edited comment on IGNITE-8619 at 6/27/18 10:27 AM:
----------------------------------------------------------------
[~ivanan.fed], do you have solid proof of ssh timeout cause of the problem.
I would not like to update ssh configuration in 100 agent instances not being
100% sure.
Also -- how do you start remote node via ssh? Via shell command, Java code os
something else?
was (Author: vveider):
[~ivanan.fed], do you have solid proof of ssh timeout cause of the problem.
I would not like to update ssh configuration in 100 agent instances not being
100% sure.
Also -- ho do you start remote node via ssh? Via shell command, Java code os
something else?
> 'Remote node could not start' in ssh connection
> -----------------------------------------------
>
> Key: IGNITE-8619
> URL: https://issues.apache.org/jira/browse/IGNITE-8619
> Project: Ignite
> Issue Type: Bug
> Reporter: Ivan Fedotov
> Assignee: Ivan Fedotov
> Priority: Major
>
> Now there is a problem with launch remote node via ssh. Initially was an
> assumption that it's due to remote process has not enough time to write
> information into log:
> [IGNITE-8085|https://issues.apache.org/jira/browse/IGNITE-8085]. But this
> correction didn't fix [TeamCity
> |https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=6814497542781613621&tab=testDetails].
>
> So it's necessary to make launch remote node via ssh always succesful.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
