sapstartsrv is not started or sapcontrol is not working

What is sapstartsrv ?

The SAP start service runs on every computer where an instance of an SAP system is started. It is implemented as a service on Windows, and as a daemon on UNIX. The process is called sapstartsrv.exe on Windows, and sapstartsrv on UNIX platforms.

The SAP start service provides the following functions for monitoring SAP systems, instances, and processes.

Starting and stopping
Monitoring the runtime state
Reading logs, traces, and configuration files
Technical information, such as network ports, active sessions, thread lists, etc.

These services are provided on SAPControl SOAP Web Service, and used by SAP monitoring tools (SAP Management Console, SAP NetWeaver Administrator, etc.).

For more understanding use this link : https://help.sap.com/doc/saphelp_nw73ehp1/7.31.19/enUS/b3/903925c34a45e28a2861b59c3c5623/content.htm?no_cache=true

How to check if it is working or not ?

In case of linux , you can simply ps -ef | grep sapstartsrv

In case of windows, you need to check the task running similarly

If it is not running you can get a error FAIL : NIECONN_REFUSED

If sapstartsrv is not starting :-

Troubleshooting :-

1. Check sapstartsrv executable size in file is not 0

[You can simply compare DIR_EXECUTABLE/sapstartsrv with DIR_CT_RUN/sapstartsrv]

2. Check sapstartsrv.log

Start the sap startsrv if not running :

sapcontrol -nr <instance number> -function StartService <SID>

if above does not work

/usr/sap/<SID>/<instance>/exe/sapstartsrv pf = /usr/sap/<SID>/SYS/profile/<profile> -D -u <sidadm> under <sidadm> user

-D here means run as daemon user and run as sidadm user.

when you use the above command you will be able to get the exact issue with your sapstartsrv

sapstartsrv needs to create/access lock file (/tmp/.sapstartsrv<instance number>_sapstartsrv.log) and trace file (/usr/sap/<SID>/instance/work/sapstartsrv.log)

if any of files are not created for whatever reason sapstarting would be failed Error would be something like "Unable to open trace file sapstartsrv.log"

You can run [exe as run file] "usr/sap/<SID>/<instance/exe/sapstartsrv pf = <full path of instance profile>"

Typical Errors: Unable to open trace file sapstartsrv.log [Error 11 : Resource Temporary unavailable, Error 13 : Permission denies , Error 20 Not a directory , Error 30 Read only file system]

1. Check the profile parmaters are maintained for the SAP system in profile :

pf = /usr/sap/<SID>/SYS/profile/<instance or start profile> , Profile paramater SAP SYSTEM is available on this profile

https://blogs.sap.com/2012/07/28/change-sap-profile-parameters/

https://help.sap.com/doc/saphelp_nw73ehp1/7.31.19/en-US/46/9cad77d5f63eefe10000000a1553f7/content.htm?no_cache=true#:~:text=The%20instance%20profile%20contains%20the,name%3E_.

2. Check the ownership and permissions of the file :

[trace file] usr/sap/<instance>/work/sapstartsrv.log ---> 666 under <sidadm>:sapsys

[lock file] /tmp/sapstartsrv<instance_number>_sapstartsrv.log ---> 644 under <sidadm>:sapsys

3. if /usr/sap/<SID> is a mounted directory , make sure it is NOT a read only file system.

4. /tmp is accessible by everyone

/tmp directory is accesible by everyone : ls -lad /tmp

<permissions> <user> <group> <date> /tmp

user and group should be root in this case

Changing the /tmp file ownership (it should be 777)

chmod 777 /tmp

chown root:root /tmp

chmod o+t /tmp

(O means for all other user, in shor the program when executed by any other user then it will be executed as root but other users still have some limitations which are mentioned below A sticky bit is a permission bit that is set on a directory that allows only the owner of the file within that directory, the owner of the directory or the root user to delete or rename the file. No other user has the needed privileges to delete the file created by some other user.This is a security measure to avoid deletion of critical folders and their content (sub-directories and files though other users have full permissions.

Why do we use t ? The /tmp directory can be used by different Linux users to create temporary files. Now, what if an user deletes/rename a file created by some other user in this directory? Well, to avoid these kind of issues, the concept of sticky bit is used. So for that a 777 is given but preserving the sticky bit is not a bad idea.)

SAP NOTE 2396062 - sapcontrol fails with connection reset by peer

sapcontrol fails with connection reset by peer

Scenario 1 : sapcontrol to perform operation on a remote server

sapcontrol -nr <Instance Number> -host <a remote server> -function <anymethod> -debug , shows that the sapcontrol is connceting to local server through uds

NilConnectSocket: connection pf hd1 established to /tmp/.sapstream5NN13

niping -s -H 1.1.1 (use any invalid ip addr)

NIPING is a tool delivered by SAP in the SAP executable directory (..\usr\sap\<SID>\D<instance enumeration>\exe. The tool is used by SAP support to check on the network connectivity and more important latency and throughput on the network. link for more info (https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/niping-8211-a-useful-tool-from-sap/ba-p/367109)

but After using this if have output as ready for client

this means that your configuration was not configured properly Incorrect Configuration

After this involve your linux team and ask them to set "net.ipv4.ip_nonlocal_bind" to 0 at the "/etc/sysctl.conf" (or removing this setting from file as default value is 0)

To avoid the need of server restart , sysctl net.ipv4.ip_nonlocal_bind=0 as root dynamically restart

if you use this command again niping -s -H 1.1.1 (use any invalid ip addr) it should work fine if you get a ERROR SiBind Failed , that means the configuration was done properly

Scenario 2 : sapcontrol to perform operation on local server

sapcontrol -nr <Instance Number> -function <anymethod>

Verify the active value for parameter "DefaultTaskMax" with the command systemctl show -p DefaultTaskMax if the reported value is less than 65536 Edit the file "/etc/systemd/system.conf" and change the value of DefaultTaskMax to 65536

It is required to reboot the server

Use case of SAPSTARTSRV

SAPSTARTSRV (through SAPCONTROL interface) offers a variety of web methods that can be used to monitor/manage the instances of the system. They are specially useful for handling startup error scenarios. The “must-know” ones are listed below and also the general pattern for executing them

Web methods that are usually used :

GetSystemInstanceList : list of active instances for the system, along with component list and the current status.

GetProcessList : the component list currently in place on any of the instances seen in the first command.

GetVersionInfo : Great for kernel consistency checks, this output will return the current kernel release + patch for each and every of its components within the instance informed as argument in the command line.

Comments

You might find these interesting

How to properly Start/Stop SAP system through command line ?

Starting/stopping an SAP system is not a critical task, but the method that most of us follow to achieve this is sometimes wrong. A common mistake that most of the SAP admins do is, making use of the 'startsap' and 'stopsap' commands for starting/stopping the system. These commands got deprecated in 2015 because the scripts were not being maintained anymore and SAP recommends not to use them as many people have faced errors while executing those scripts. For more info and the bugs in scripts, you can check the sap note 809477. These scripts are not available in kernel version 7.73 and later. So if these are not the correct commands, then how to start/stop the sap system? In this post, we will see how to do it in the correct way. SAP SYSTEM VS INSTANCE In SAP, an instance is a group of resources such as memory, work processes and so on, usually in support of a single application server or database server with

HANA System Replication - Prerequisites & Setup

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out operation & replication modes in hana system replication. If you haven't gone though that blog, you can checkout this link In this blog we will be talking about the prerequisites of hana replication and it's setup. So let's get started. When we plan to setup hana system replication, we need to make sure that all prerequisite steps have been followed. Let's have a look at these prerequisites. HANA System Replication Prerequisites: Primary & secondary systems should be up & running HDB version of secondary should be greater than or equal to Primary database sever But, for Active/Active(read enabled config), HDB version should be same on both sites. System configuration/ini files should be identical on both sides Replication happe

HANA hdbuserstore

The hdbuserstore (hana secure user store) is a tool which comes as an executable with the SAP Hana Client package. This secure user store allows you to store SAP HANA connection information, including user passwords, securely on clients. With the help of secure store, the client applications can connect to SAP HANA without the user having to enter host name or logon credentials. You can also use the secure store to configure failover support for application servers in a 3-tier scenario (for example, SAP Business Warehouse) by storing a list of all the hosts that the application server can connect to. To access the system using secure store, there are two connect options: (1)key and (2)virtualHostName. key is the hdbuserstore key that you use to connect to SAP HANA, while virtualHostName specifies the virtual host name. This option allows you to change where the hdbuserstore searches for the data and key files. Note

ST03N : The chapter for all BASIS Admins

This blog is targeted to BASIS ADMINS Transaction for workload analysis statistical data changed over time are monitored using transaction code ST03 , now ST03N (from SAP R/3 4.6C) . With SAP Web AS 6.4 the transaction ST03 is available again. From time to time ST03 and ST03N has seen many changes but later in SAP NW7.0 ST03N has reworked in detail specially processing time is now shown in separate column. Main Use of ST03N is to get detailed information on performance of any ABAP based SAP system. Workload monitor analyzes the statistical data originally collected by kernel. You can compare or analyze the performance of a single application server or multiple application server. Using this you start checking from the entire system and finding your way to that one application server and narrowing down to exact issue. By Default :- You see data of current day as default view , you can change the default view. Source of the image : sap-perf.ca Let's discuss the WORKLOAD MONITOR By D

Work Process and Memory Management in SAP

Let’s talk about the entire concepts that are related to memory when we talk about SAP Application. Starting with few basic terminologies, Local Memory : Local process memory, the operating system keeps the two allocation steps transparent. The operating system does the other tasks, such as reserving physical memory, loading and unloading virtual memory into and out of the main memory. Shared Memory : If several processes are to access the same memory area, the two allocation steps are not transparent. One object is created that represents the physical memory and can be used by various processes. The processes can map the object fully or partially into the address space. The way this is done varies from platform to platform. Memory mapped files, unnamed mapped files, and shared memory are used. Extended Memory : SAP extended memory is the core of the SAP memory management system. Each SAP work process has a part reserved in its virtual address space for extended memory. You can set

ABAP Dumps Analysis

Ever now and then have you heard about ABAP Dumps, We also have a joke everything in temporary in life except ABAP dumps for SAP Consultants. Lets try to understand ABAP dumps from perspective of a SAP BASIS Consultant. Dumps happen when an ABAP program runs and something goes wrong that cannot be handled by the program We have two broad categories of Dumps , In custom program Dumps and SAP provided program Dumps. Dumps that happen in the customer namespace ranges (i.e. own-developed code) or known as Custom Program , can usually be fixed by the ABAP programmer of your team. Dumps that happen in SAP standard code probably need a fix from SAP. You do not have to be an "ABAPer" in order to resolve ABAP dump issues. The common way to deal with them is to look up in ST22 How to correct the error ? Hints are given for the keywords that may be used to search on the note system. Gather Information about the issue Go to System > Status and Check the Basis SP level as well as info

How to resolve Common Error : Standard Template "sap_sm.xls" missing

Hey everyone, putting forward a common error we usually face when we have “ Excel inplace” functionality enabled in our SAP system. This error occurs when validity of the signature of SAP standard templates expired or were incorrectly delivered via support packages. We can reproduce the error by doing as below.. Click on “spreadsheet” icon after any SAP ALV grid view of data is on screen to make this data to export into excel directly from SAP.

SAP application log tables: BALHDR (Application Log: Header Data) and BALDAT (Application Log: Detail Data)

BALHDR (Application Log: Header Data): Usage : The BALHDR table stores the header information for application logs. It serves as a central repository for managing and organizing log entries. Example Data Stored: The table may contain entries for various system activities, such as error messages, warnings, or information logs generated during SAP transactions or custom programs. Columns Involved: LOGNUMBER: Unique log number assigned to each log entry. OBJECT: Identifies the object associated with the log entry (e.g., a program, transaction, or process). SUBOBJECT: Further categorizes the object. USERNAME: User ID of the person who created the log entry. TIME: Date and time when the log entry was created. ADD_OBJECT: Additional information or details related to the log entry. BALDAT (Application Log: Detail Data): Usage : The BALDAT table contains the detailed data for each log entry, linked to the corresponding entry in the BALHDR table. It stores the specific log details and me

"DST Switch" - All you need to know about Daylight Saving Time Switch in SAP

Daylight Saving Time(DST) : DST is the practice of advancing clocks during part of the year, typically by one hour around spring and summer , so that daylight ends at a later time of the day. How SAP systems are affected due to DST : Many kinds of software that deal with local time, such as the SAP system, have serious problems in this hour, because operations which use local times can fail if time does not increase continuously, and points in time can "happen" twice. Double Hour Concept : In many northern hemisphere countries (i.e., Europe: European Union, Russia; North America: USA, Canada, Mexico) At the end of daylight-saving period, one hour occurs twice as the clocks are put back an hour. In Europe, for example, this hour is between 2:00 a.m. and 3:00 a.m., whereas in the USA it occurs between 1:00 a.m. and 2:00 a.m. This means that the clock will move twice in the same day from 1am to 2am. Double hour refers to the duration of the hour that the cloc

Let's Talk SAP

Search This Blog