You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Khitrin (Jira)" <ji...@apache.org> on 2023/05/31 12:49:00 UTC

[jira] [Created] (IGNITE-19608) Startup errors are ignored in ignite3db script

Andrey Khitrin created IGNITE-19608:
---------------------------------------

             Summary: Startup errors are ignored in ignite3db script
                 Key: IGNITE-19608
                 URL: https://issues.apache.org/jira/browse/IGNITE-19608
             Project: Ignite
          Issue Type: Bug
    Affects Versions: 3.0.0-beta1
            Reporter: Andrey Khitrin


Ignite3 node is started by `bin/ignite3db` shell script. Unfortunately, this script follows some shell scripting bad practices that makes troubleshooting harder when something goes wrong.

Particullary, there are following issues:
1. No guarding bash options (like `nounset`, `errexit`, or `pipefile`) is set.
2. When starting Java application, its stderr and stdout are redirected into `/dev/null`.

{code:bash}
  CMD="${JAVA_CMD_WITH_ARGS} ${APPLICATION_ARGS}"
  $CMD >>/dev/null 2>&1 </dev/null & echo $! >${IGNITE_HOME}/pid
{code}

Just for comparison: [control.sh in AI2|https://github.com/apache/ignite/blob/master/bin/control.sh] do not suffer from such behavior. This should be fixed in AI3 too.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)