You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2021/10/06 10:48:00 UTC
[jira] [Comment Edited] (IGNITE-15683) CLI tool says 'Can't start
the node' even though the node is successfully started
[ https://issues.apache.org/jira/browse/IGNITE-15683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424921#comment-17424921 ]
Vyacheslav Koptilin edited comment on IGNITE-15683 at 10/6/21, 10:47 AM:
-------------------------------------------------------------------------
Duplicates IGNITE-15538 (The proposed fix was already applied under IGNITE-15538)
was (Author: slava.koptilin):
Duplicates IGNITE-15538
> CLI tool says 'Can't start the node' even though the node is successfully started
> ---------------------------------------------------------------------------------
>
> Key: IGNITE-15683
> URL: https://issues.apache.org/jira/browse/IGNITE-15683
> Project: Ignite
> Issue Type: Bug
> Reporter: Valentin Kulichenko
> Assignee: Valentin Kulichenko
> Priority: Blocker
> Labels: ignite-3, ignite-3-cli-tool
> Fix For: 3.0.0-alpha3
>
>
> {{ignite node start}} command fails with the following message even though the node actually starts:
> {code}
> Starting a new Ignite node...
> Can't start the node. Read logs for details: /Users/vkulichenko/GridGain/ignite-3/target/apache-ignite-3.0.0-alpha3/ignite-log/node-1.log
> {code}
> Looks like this happens because there is the following line in the log:
> {noformat}
> Oct 05, 2021 3:41:45 PM org.apache.ignite.lang.IgniteLogger logInternalExceptional
> {noformat}
> The tool treats it as a failure because of this condition (see {{NodeManager}} class):
> {code}
> else if (content.contains("Exception"))
> throw new IgniteCLIException("Can't start the node. Read logs for details: " + file);
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)