‘sapstartsrv’ service not started

‘sapstartsrv’ service not started error after SAP HANA installation:

sapstartsrv1

Check if the service is started on the server:

sapstartsrv2

With netstat you know which port the process is using:

Try to telnet to the port (50213 in this case) from outside of server. If you are able to reach you will have to reach out to your Infrastructure team to get the port open on firewall.

Or if you you are on cloud, you need to add this to the inbound rule of your secuirty group.

sapstartsrv3

 

Advertisements

SAP HANA Cockpit 2.0 – Installation and configuration

SAP HANA Cockpit is a Web-Based  tool for administration, monitoring and maintenance of SAP HANA systems.

Below we discuss installation steps and some key points with respect to cockpit:

  1. Download the required SAP file from SAP Market Place.cockpitdown
  2. Extract the SAR file and trigger installation using hdblcm.
    Note that installer installs a HANA instance (Express edition) of its own.
    More details hereco1
  3. Verify the details, enter the password and continue. Like any HANA installation user SYSTEM is created on the DB which will be used to login to Cockpit also.
    Along with SYSTEM, the other key user created is COCKPIT_ADMIN.
    co2.png
    Note that 51021 and 51023 are the default ports for Cockpit and Cockpit manager respectively.
  4. First it is required to login to Cockpit manager to assign yourself required roles using user COCKPIT_ADMIN.
    co3
    CO4
  5. Now you are ready to login to the HANA Cockpit.
    co5
  6. If you want to add additional users or resources (HANA systems) to cockpit, you can do so via SAP HANA Cockpit manager.
    co6
    co7

 

Important SAP Notes:

2496215 – You’re not authorized to open the SAP HANA Cockpit

2618617 – Launching SAP HANA Cockpit 2.5.5 in Firefox

2496215 – You’re not authorized to open the SAP HANA Cockpit

2185556 – FAQ: SAP HANA Cockpit

2595496 – Register a Resource in HANA Cockpit

2149157 – Unable to access the SAP HANA Cockpit due to error “Failure – Unable to load groups”.

 

AWS Certified Solution Architect – Points to remember (EC2)

  1. Uptime SLA for EC2 and EBS within a region is 99.99%
  2. Default cooling period of a Autoscaling group is 5 mins.
  3. Cooling period can be adjusted based on requirement.
  4. AWS lambda scales automatically. No end-user actions required.
  5. User Lambda Environment variables to pass parameters to function. For sensitive information you can use encrypted environment variables.
  6. Remember that both EBS and EFS does not scale automatically.
  7. EFS to expensive compared to EBS. So EBS is cost effective compared to EFS.
  8. EBS volumes cannot be shared between different instances.
  9. Since EFS is network file system, a latency is expected.
  10. Use Lambda instead of EC2 where ever possible. Example there are simple computations to be done which does not need a big EC2 instance or a scenario where your computations should scale to millions of requests automatically.
  11. Regional Reserved Instances do not provide a capacity reservation.
  12. Standard and Convertible Reserved Instances provide a capacity reservation in a specific availability zone.
  13. Application Load Balancer is the most comprehensive ELB available and most cost effective.

Check your ports before you install the application

I have come across situations where it was necessary to check the ports before even installing an application to see if firewall is open or if no other application is already using the port.

Linux:

On Linux environments this can be done using command ln:

Use yum or zypper or apt-get to install the tool:

ln1

Now simulate your port and test:

nc2

Windows:

On windows I did not find a ready-made way to do the same. So designed my own, with some help from internet.

No installation required and it is version independent. Just download and run it from below link:

Simulate Port on Windows

Instructions:

Unzip the file to your desktop.

Double click to execute the file:

porttest

porttest1

If prompted allow firewall access.

porttest3

And you are ready to test.

telnetport

Once you are connected, you get a message in your simulator:

simutt

Note: After the test is done end the test process from your task manager. Otherwise the port will be kept occupied.

servvee

Check used port – Linux

Sometimes you might find issues starting up your SAP services, with a error that the service is not able to bind to a particular port.

In the example below, I was not able to start the SMTP service from SMICM.

icm

This mean, there could be another service that is already using this port.

Lets find out:

netstat -nepal | grep 25

icm1

Now we have the process ID. Lets see what is this process all about:

ps -ef | grep 6760

icm2

Postfix was using my service, which was not required.

Kill/Stop the service that is not required before starting your service again.

In my example:

# postfix stop 

Make sure that you disable the unwanted service from starting up next time when you reboot the server using chkconfig:

# chkconfig postfix off

How to check HDB startup issues

#HDB info showed that not all index servers are started.

hdb info

Since this is multitenant database, looked in following directory for the error logs:

/usr/sap/<SYSTEM SID>/HDB<Instance Number>/<Host Name>/trace/DB_<TENANT SID>/.

For SAP HANA single database, trace files can be found at:

/usr/sap/<SYSTEM SID>/HDB<Instance Number>/<Host Name>/trace/

Found the issue, resolved and restarted to get all my index servers running again.

hdbin