ETD on AWS: Appliance Agent detected an error and terminated

[Former Member]

I'm trying to run the ETD on AWS demo. The backend server displays the following message when I ssh to it:

---

The Appliance Agent detected an error and terminated.

When asked, please provide the file /tmp/applianceagent_20160805-043524.tar.bz2.

---

The file is here: applianceagent_20160805-043524.tar.bz2 - Google Drive. An error log includes:

---

02:37:00.787 - INFO:          Starting on 'sid-erp': hdbdaemon, hdbindexserver, hdbwebdispatcher, hdbxsengine

04:35:23.770 - ERR :      Timeout reached

04:35:23.770 - ERR :    Start instance 02 on host 'vhcalhdbdb' (worker) failed.

04:35:23.781 - INFO:    Messages from trace files

04:35:23.774 - INFO:      daemon_vhcalhdbdb.30200.001.trc: [25835]{-1}[-1/-1] 2016-08-05 02:35:22.411898 e Configuration    ConfigStoreManager.cpp(00693) : Configuration directory does not exist.

04:35:23.774 - INFO:      daemon_vhcalhdbdb.30200.001.trc: [25835]{-1}[-1/-1] 2016-08-05 02:35:22.411902 e Configuration    ConfigStoreManager.cpp(00693) : Configuration directory does not exist.

04:35:23.776 - INFO:      xsengine_vhcalhdbdb.30207.026.trc: More than 50 relevant messages found, check file.

04:35:23.778 - INFO:      nameserver_alert_vhcalhdbdb.trc: [25852]{-1}[-1/-1] 2016-08-05 02:36:32.040236 e NameServer      TREXNameServer.cpp(15364) : Cannot retrieve master nameserver address !!!

04:35:23.779 - INFO:      nameserver_vhcalhdbdb.30201.000.trc: [25852]{-1}[-1/-1] 2016-08-05 02:36:32.040236 e NameServer      TREXNameServer.cpp(15364) : Cannot retrieve master nameserver address !!!

04:35:23.780 - INFO:      xsengine_alert_vhcalhdbdb.trc: More than 50 relevant messages found, check file.

04:35:23.781 - ERR :    Check the log file for SAP HANA Database error messages

04:35:23.781 - ERR :  Cannot start instance HDB (HDB02) on host 'vhcalhdbdb'

04:35:23.781 - ERR : Renaming master failed!

04:35:23.781 - ERR : Renaming SAP HANA instance failed!

---

How can I get the backend into a usable state? This is the second time I've run the installation, and the second time the backend has failed to start listening on its ports.

Thanks,

e

[Former Member]

I've had exactly the same issue, posted separately.  Sorry, should be in same discussion thread.

  --Anil