3423956 - SAP start service fails on code=exited, status=1/FAILURE

sapstartsrv service failed to start during OS restart or manual start from "systemctl start SAP<SID>_<nr>.service" call. Check from command 

 "systemctl status SAP<SID>_<nr>" by <SID>adm user returns similar pattern of output to below  

dummyhost:# systemctl  status SAPJ07_02.service
● SAPJ07_02.service - SAP Instance SAPJ07_02
   Loaded: loaded (/etc/systemd/system/SAPJ07_02.service; enabled; vendor preset: disabled)
   Active: activating (auto-restart) (Result: exit-code) since Tue 2024-01-30 10:26:27 CST; 18s ago
  Process: 3202 ExecStart=/usr/sap/J07/J02/exe/sapstartsrv pf=/usr/sap/J07/SYS/profile/J07_J02_dummyhost -setup_env (code=exited, status=1/FAILURE)
 Main PID: 3202 (code=exited, status=1/FAILURE)

Jan 30 10:26:27 dummyhost systemd[1]: Failed to start SAP Instance SAPJ07_02.
Jan 30 10:26:27 dummyhost systemd[1]: SAPJ07_02.service: Unit entered failed state.
Jan 30 10:26:27 dummyhost systemd[1]: SAPJ07_02.service: Failed with result 'exit-code'.

In this example 

<SID>=J07

<nr>=02 (instance number)

<hostname>=dummyhost 

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

sapstartsrv of SAP Hostagent/SAP ABAP and JAVA instances/HANA DB instance are migrated into systemd managed mode or on recent SAP product releases by default sapstartsrv being managed by systemd.

Check on /usr/sap/sapservices to find out whether sapstartsrv is managed by systemd from command grep "systemctl /usr/sap/sapservices". 

• The command returns at least one line. This means sapstartsrv is managed by systemd.
• Returning empty output means the sapstartsrv is still managed by SysV not systemd. This KBA doesn't apply.

systemd, /usr/sap/sapservices, code=exited, sapstartsrv, systemctl , KBA , BC-OP-LNX , Linux , Problem