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
Back to discussions
Expand all | Collapse all

6.1.3 error whilst upgrading

  • 1.  6.1.3 error whilst upgrading

    Employee
    Posted 12-13-2016 06:24

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

    Originally posted by: khopkins

    Hello all,

    I hope someone can help as we are in the middle of a long awaited upgrade from 4.5.3 to 6.1.3 and i am getting the below error on nodes.

    Error while starting execution of node 'RPTORTCOMMAND.RPTORTCOMMAND'
    Error executing node: Node :'RPTORTCOMMAND.RPTORTCOMMAND' (handle: 57b6bcf74e4e74af) encountered error during initialization
    WARN: Node reported the following messages to stderr:
    Error: Could not find or load main class com.lavastorm.brain.node.old.NodeControl

    Error Code: brain.unhandledLogging


    Could anyone please enlighten me on what this error represents?

    Regards,

    Keith


  • 2.  RE: 6.1.3 error whilst upgrading

    Employee
    Posted 12-13-2016 07:48

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

    Originally posted by: stonysmith

    Every time I've seen this it is because your Client and Server LAL libraries are out of sync.

    Can you please please verify/report back here that your LAL versions are in sync with each other?

    Client:
    - In BRE click on View/Dependent Libraries and note the version for LAL

    Server:
    - Find and open the file on the server <installation dir>/docs/lal/LAL Release Notes.pdf
    - page 1 of the document tells you the version #

    ===========================
    When working in a enterprise environment, the users should set their BRE to NEVER update. The Server and Client must stay in sync with each other, and you only want to update Clients once the Server library has first been updated.


  • 3.  RE: 6.1.3 error whilst upgrading

    Employee
    Posted 12-13-2016 07:55

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

    Originally posted by: khopkins

    HI Stoney,

    the server version is 6.1.47 and the client is 6.1.48.0.19 so it looks like your spot on as usual.

    Whats the prefereed method for updating the LAL on a linux server?

    Regards,

    Keith


  • 4.  RE: 6.1.3 error whilst upgrading

    Employee
    Posted 12-13-2016 08:09

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

    Originally posted by: stonysmith

    0) To be safe, make a backup of your installation first.
    1) Go to this web page http://www.lavastorm.com/current-rel...orm-libraries/
    1a) Download the "Linux" version of the 6.1.48 library
    1b) Download and read the Release Notes
    2) Place that file somewhere on your server and mark it executable
    3) Notify users of a short downtime
    4) Take down all 3 LAE processes: LAE_Server, Jetty, H2 (database)
    5) Run the file above by typing "bash <filename>" at a command line
    6) Accept the Terms&Conditions
    7) The installer will load the updated software
    8) Restart LAE
    9) Notify ALL users that they must upgrade their BRE clients to the version 6.1.48 (also available on the link above)

    Downloading the file may take a few mintues, but the actual installation is only about 3 minutes.

    -stony


  • 5.  RE: 6.1.3 error whilst upgrading

    Employee
    Posted 12-20-2016 07:33

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

    Originally posted by: khopkins

    HI Stoney,

    I have now completed this for both the client and the server and i am still getting the below error.

    Error while starting execution of node 'RPTORTCOMMAND.RPTORTCOMMAND'
    Error executing node: Node :'RPTORTCOMMAND.RPTORTCOMMAND' (handle: 57b6bcf74e4e74af) encountered error during initialization
    WARN: Node reported the following messages to stderr:
    Error: Could not find or load main class com.lavastorm.brain.node.old.NodeControl

    Error Code: brain.unhandledLogging

    Do you or anyone have any idea what could still be the problem?

    Regards,

    Keith


  • 6.  RE: 6.1.3 error whilst upgrading

    Employee
    Posted 12-22-2016 01:58

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

    Originally posted by: khopkins

    HI All,

    I have solved one problem as this was down to the client install picking up different client libraries from previous versions of the client however i am still having issues with all of the new nodes.
    Especially some of the http get Object and obtain Login token nodes the error message is below and any help would be appreciated.

    -- Errors for Login_2
    -- Errors for Login
    Error while starting execution of node 'Get+Object.Login.Login'
    Error executing node: Node :'Get+Object.Login.Login' (handle: 5539b23510d06a83) encountered error during initialization
    WARN: Node reported the following messages to stderr:
    Error: Could not find or load main class com.lavastorm.brain.execution.java.node.NodeWrappe r

    Error Code: brain.unhandledLogging

    Regards,

    Keith


  • 7.  RE: 6.1.3 error whilst upgrading

    Employee
    Posted 12-23-2016 08:42

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

    Originally posted by: gmullin

    As Stony mentioned above, any time you see a nodewrapper error its almost always related to a mismatch with the BRE client and the server (including mismatch with LAL) or else your search paths in the BRE client are referencing the incorrect libraries and need to point to the correct ones.


  • 8.  RE: 6.1.3 error whilst upgrading

    Employee
    Posted 05-11-2017 08:12

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

    Originally posted by: ejones

    I had to troubleshoot this error just now. It was caused by having an old version of core.brg in the same directory as the graph I was opening. Removing that version of core.brg and reopening BRE corrected this.

    The clue to this being the problem was seen when I went to View -> Dependent Libraries...
    I noticed that the version of core.brg that was loaded was 5.1 when I was using 6.1.4


  • 9.  RE: 6.1.3 error whilst upgrading

    Employee
    Posted 05-11-2017 08:20

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

    Originally posted by: khopkins

    Hello,

    I have come across that one also but i also had it where the view dependant libraries was reporting it as 6.1.3 but was actually using 4.5.3 due to the search path not pointing to the right place


  • 10.  RE: 6.1.3 error whilst upgrading

    Employee
    Posted 06-06-2017 13:16

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

    Originally posted by: ejones

    I've learned a new way to get this error today. If you decide to keep a copy of the core.brg, inFlow.brg and lal1.brg files with your library graphs or with the graphs you are working on, it will use that version instead of the version that came with the version of Lavastorm installed. This is ok until you decide to upgrade. After an upgrade the server is configured for a different version of these files than you are using.

    So the solution is to not keep core.brg, lal1.brg, inFlow.brg and any other graphs that are part of Lavastorm with the graphs you have created.


  • 11.  RE: 6.1.3 error whilst upgrading

    Employee
    Posted 06-07-2017 00:03

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

    Originally posted by: khopkins

    Hello,

    Yes i came across that one that one also but it was easily fixed once you looked at the dependant libraries in the graph as it showed it was using the incorrect ones


  • 12.  RE: 6.1.3 error whilst upgrading

    Employee
    Posted 09-05-2017 13:23

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

    Originally posted by: cdc060376

    Stony said: When working in a enterprise environment, the users should set their BRE to NEVER update. The Server and Client must stay in sync with each other, and you only want to update Clients once the Server library has first been updated.

    How do you change the autoupdate and change it to NEVER after the LAE client (BRE) has been installed? I have users that are annoyed that they have to keep ignoring this prompt.


  • 13.  RE: 6.1.3 error whilst upgrading

    Employee
    Posted 09-05-2017 16:46

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

    Originally posted by: stonysmith

    Find the file C:\Program Files\Lavastorm\LAE6.1.4\.install4j\response.varfi le
    It may be in a different folder, based upon where you installed your BRE

    This line should be updated to the word "Never":
    laeUpdateFrequency=Never