[IGNITE-15683] CLI tool says 'Can't start the node' even though the node is successfully started

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Duplicate
• Fix Version/s: 3.0.0-alpha3
• Labels: ignite-3 ignite-3-cli-tool
• Assignee: Valentin Kulichenko
• Reporter: Valentin Kulichenko
• Created: 05/Oct/21 22:50
• Updated: 08/Oct/21 11:30
• Resolved: 06/Oct/21 10:45

Description

ignite node start command fails with the following message even though the node actually starts:

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

Looks like this happens because there is the following line in the log:

Oct 05, 2021 3:41:45 PM org.apache.ignite.lang.IgniteLogger logInternalExceptional

The tool treats it as a failure because of this condition (see NodeManager class):

else if (content.contains("Exception"))
    throw new IgniteCLIException("Can't start the node. Read logs for details: " + file);

Issue Links

• duplicates: IGNITE-15538 Starting node via CLI can lead to NullPointerException
• links to: GitHub Pull Request #380