Is the AWS ASE Marketplace server not supposed to work after launch?

[Former Member]

Let me start by saying I do not know SAP and I am trying to get to know SAP ASE.

I launched this Marketplace image
https://aws.amazon.com/marketplace/pp/B07D9SGHD9?ref=cns_srchrow

AMI is ami-84d298fb

Upon logging into the instance, i find that sap has failed to start:

Jul 28 15:07:25 ip-10-8-11-46.development.iod.com systemd[1]: Starting SAP Adaptive Server Enterprise services... -- Subject: Unit ase.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit ase.service has begun starting up. Jul 28 15:07:25 ip-10-8-11-46.development.iod.com bash[4787]: /bin/bash: /ase/config/ASE-16_0/install/asesvcs: No such file or directory Jul 28 15:07:25 ip-10-8-11-46.development.iod.com systemd[1]: ase.service: control process exited, code=exited status=127 Jul 28 15:07:25 ip-10-8-11-46.development.iod.com systemd[1]: Failed to start SAP Adaptive Server Enterprise services.

I dug into this guide: https://help.sap.com/doc/c929440cdf914db1b5c3de3f32dbdba5/16.0.3.2/en-US/SAP_ASE_AWS.pdf

And luckily found this:

At deployment, the master and user-specified databases are created by running the following script as the
sybase user:
/home/sybase/aws_srvbuild

I tried launching it, of course that didn't work without errors:

[sybase@ip-10-8-11-46 ~]$ ./aws_srvbuild
cat: /ase/config/ASE-16_0/init/sample_resource_files/aws_cft.rs: No such file or directory
mkdir: cannot create directory ‘/opt/sap/COCKPIT-4/plugins/’: File exists

It sat for awhile, I finally killed the process

^Ccat: /ase/config/ASE-16_0/init/sample_resource_files/aws_cft.rs: No such file or directory mv: cannot stat ‘tmp1’: No such file or directory

I could then start the server. Is this normal?

Although, when I try to log into the database with

isql -Usa -Psybase123 ipaddress:5000

I get this

ct_connect(): directory service layer: internal directory control layer error: Requested server name not found

I've found articles that include adding a ini/sql.ini file or an interfaces file to include the following data:

[servername]
master=TCP,10.8.11.46:5000
query=TCP,10.8.11.46:5000

Tried restarting. Connecting as isql -Usa -Psybase servername:5000
Didn't help.

[former_member476961]

Hi John,

I just deployed ASE subscription using instance type: m5.4xlarge, ASE is up and running. I did isql to dataserver and run some query. To further identify what might have the issue you have experienced, appreciate if you could provide:

• Instance type you chose.. i.e m5.4xlarge ..
• Is the information you provided from /var/log/messages?

Once I get this info, will try to repro it and see what might have caused failure you noticed. Note that aws_srvbuild is meant to run only once as it creates various environment based on values you entered during deployment via CloudFormation.

Regards,

--Ghaf

[Former Member]

Hi Mark, thanks for the answer. I did try the connection with the -S before server. No dice.

My guess is the AMI wasn't validated after creation.