LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only

  • 1.  LAE Error - BRX exited with non-zero status: 6

    Employee
    Posted 05-03-2016 09:44

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: abhisek

    There is unexpected issue that we face very often where the graph deployed in the server stops in the middle of execution.
    I have tried to check the log and find the issue, but I could find the root cause of it.

    Here the main graph call the sub graph from the BRX node. How will I know what is issue in sub graph that cause the issue?

    Here is log below.

    PHP Code:
    <logEvent level="ERROR" timestamp="1462259206000"><message xsi:type="rawMessage"><![CDATA[BRX exited with non-zero status: 6]]></message><detail context="execute( ) - Exception" file="ls.brain.node.brainpython.python2implementationfile" line="136" xsi:type="cppDetail"/></logEvent><logEvent level="ERROR" timestamp="1462259206000"><message xsi:type="rawMessage"><![CDATA[BRX exited with non-zero status: 6]]></message><detail context="Salmon::NED::NodeMain::errorMsg()" file="build/linux-x86-64/release/code/source/brain/node/NodeMain.cpp" line="28" xsi:type="cppDetail"/></logEvent><logEvent level="ERROR" timestamp="1462259206000"><message xsi:type="rawMessage"><![CDATA[Error pumping node (Traceback (most recent call last):
          File "/usr/local/lavastorm-4.6.1/lib/python/lavastorm/brain/python1.py", line 917, in Run
            while n.pump(quant):
          File "/usr/local/lavastorm-4.6.1/tmp/brain/SalesOrder_Load/default/temp.null.4788.2339977.1462249437554.54a15b606edc12b4.prop", line 222, in pump
            (brdlogFile, status, headOfLog) = self.executor.execute(self.brx, self.username, self.password, props, self.doProps, self.continueOnError)
          File "/usr/local/lavastorm-4.6.1/tmp/brain/SalesOrder_Load/default/temp.null.4788.2339977.1462249437554.54a15b606edc12b4.prop", line 136, in execute
        raise Exception    , "BRX exited with non-zero status: %d" % (exitCode)
    Exception: BRX exited with non-zero status: 6
    )]]></message><detail context="execute( ) - Exception" file="ls.brain.node.brainpython.python2implementationfile" line="136" xsi:type="cppDetail"/></logEvent><logEvent level="ERROR" timestamp="1462259206000"><message xsi:type="rawMessage"><![CDATA[Error pumping node (Traceback (most recent call last):
          File "/usr/local/lavastorm-4.6.1/lib/python/lavastorm/brain/python1.py", line 917, in Run
            while n.pump(quant):
          File "/usr/local/lavastorm-4.6.1/tmp/brain/SalesOrder_Load/default/temp.null.4788.2339977.1462249437554.54a15b606edc12b4.prop", line 222, in pump
            (brdlogFile, status, headOfLog) = self.executor.execute(self.brx, self.username, self.password, props, self.doProps, self.continueOnError)
          File "/usr/local/lavastorm-4.6.1/tmp/brain/SalesOrder_Load/default/temp.null.4788.2339977.1462249437554.54a15b606edc12b4.prop", line 136, in execute
        raise Exception    , "BRX exited with non-zero status: %d" % (exitCode)
    Exception: BRX exited with non-zero status: 6
    )]]></message><detail context="Salmon::NED::NodeMain::errorMsg()" file="build/linux-x86-64/release/code/source/brain/node/NodeMain.cpp" line="28" xsi:type="cppDetail"/></logEvent><logEvent level="ERROR" timestamp="1462259206000"><message xsi:type="rawMessage"><![CDATA[Got Python exception]]></message><detail context="Salmon::NED::NodeMain::errorMsg()" file="build/linux-x86-64/release/code/source/brain/node/NodeMain.cpp" line="28" xsi:type="cppDetail"/></logEvent><logEvent timestamp="1462259208585" level="WARN"><message xsi:type="errorMessage"><code key="brain.unhandledLogging" bundle="com.lavastorm.brain.ErrorMessages"/><message xsi:type="i18nMessage" mKey="brain.unhandledLogging" bundle="com.lavastorm.brain.ErrorMessages"><arg type="string"><![CDATA[stderr]]></arg><arg type="string"><![CDATA[Error in sys.excepthook:Traceback (most recent call last):  File "/usr/local/lavastorm-4.6.1/lib/python/lavastorm/brain/python1.py", line 952, in <lambda>    return lambda ex]]></arg></message></message></logEvent> 

    Please let me know where can I find the log details with each node error till the point where it is executed.


  • 2.  RE: LAE Error - BRX exited with non-zero status: 6

    Employee
    Posted 05-03-2016 10:44

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: stonysmith

    There is a problem with the child graph. You need to review it's logs to see what was wrong.
    Or.. did you get any output on the 2nd output pin of the ExecuteBRX? The error might be listed there.


  • 3.  RE: LAE Error - BRX exited with non-zero status: 6

    Employee
    Posted 05-04-2016 08:46

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: abhisek

    Thanks Stonysmith, there is indeed problem in the child graph. But how would I identify which node is creating the issue in child graph, as this problem comes sometimes not always. In which log file can I find the issue.


  • 4.  RE: LAE Error - BRX exited with non-zero status: 6

    Employee
    Posted 09-16-2016 11:15

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: Sabyasachi

    Any Update... I have seen lots of post with same issue.The error should be reported by Execute BRX node but we get only the code "6".


  • 5.  RE: LAE Error - BRX exited with non-zero status: 6

    Employee
    Posted 09-16-2016 11:38

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: stonysmith

    Look at the 2nd output pin of the ExecuteBRX - "brdlog output"
    That itemizes the state of every node.. the same information you would get in the graphname.log.brd file(s).