SAP Knowledge Base Article - Preview

3329768 - The instance crashed after the XSA was upgraded - SAP EAD

Symptom

  • After migrating to a new server with up to date XSA, EAD is not starting up correctly.

  • Same error is raised in service_xs.log and backend_xs.log
    [API] ERR   Crashed instance [state CRASHED, index 3] of droplet [id 3] of app 'eadesigner-backend' [Org '***', Space '***'] at [***:***, pid 71409] with failure reason: Process terminated with exit code 126

  • From ead_xs.log
    [APP/10-2] ERR   /hana/shared/<SID>/xs/app_working/***/executionroot/<root-id>/startCommand: line 2: /hana/shared/<SID>/xs/app_working/***/executionroot/<root-id>/app/vendor/node8.17/bin/node: cannot execute binary file: Exec format error
    [APP/10-2] ERR   /hana/shared/<SID>/xs/app_working/***/executionroot/<root-id>/startCommand: line 2: /hana/shared/<SID>/xs/app_working/***/executionroot/<root-id>/app/vendor/node8.17/bin/node: Success

  • The upgraded XSA includes node.js 12, 14 and 16.


Read more...

Environment

  • SAP Enterprise Architecture Designer (EAD) 1.0 SP05
  • SAP HANA 2.00.059.07.1674546917
  • XSA version 1.0.152.1100.

Product

SAP Enterprise Architecture Designer, edition for SAP HANA 1.0

Keywords

KBA , BC-EAD , SAP Enterprise Architecture Designer , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.