Blog Posts

28. Service Start Failed - Job /org/freedesktop/ errors during SAP Installation ?

All Basis persons who have done SAP Installations will definitely experience this error.

Main Error:

StartService
FAIL: Service start failed: systemdI_msg_handler: job '/org/freedesktop/systemd1/job/673403' cancelled with 'failed'

Service Start Failed - Job /org/freedesktop/ errors during SAP Installation

Let's discuss three cases which usually happens/results in this above error.

Case 1:

Linux /var/log/messages file will have the below error message.

"SELinux is preventing /usr/bin/bash from execute access on the file /usr/sap/hostctrl/exe/saphostexec"

It's usually caused by SELinux Enforcing mode only.

Note 3253160 - SAP Host Agent or  instance fails due to SELinux vers3

Resolution is simple.

Set SELinux to "permissive" mode.

This info would be available in corresponding OS Installation Release notes as well.

Example:

2772999 - Red Hat Enterprise Linux 8 - Installation vers29

2936683 - Oracle Linux 8: SAP Installation and Upgrades vers8

You can use "getenforce" command to check whether policy set to Enforce/Permissive/Disabled.

If enforce, It won't allow to EXECUTE any programs/executables. Hence, Subjected error will be shown.

Use "setenforce Permissive" for temporary change.

Use /etc/selinux/config and change Permissive for Permanent change.

Case 2:

SAP service (SAP<SID>_00.service) will have the below error message.

"Unable to open() the lock file /tmp/.sapstartsrv00_sapstartsrv.log"

Note 3587376 - Linux: Service start failed: systemdI_msg_handler vers2

Resolution is simple.

✨Set permission - sudo chmod 1777 /tmp

Case 3:

In above two cases, we will see those errors in log files which we can easily resolve the issue. However, for case 3, there is no such explicit error visible in log files. Common statement would be there - "/org/freedesktop/ cancelled with failed".

Just check case 1 and case 2 first, If everything fine, then error could be due to FS containing the directory (which process access) mounted with noexec.

Example:

Consider Host Agent Installation. It would fail since FS directory (/usr/sap/hostctrl) is mounted with "noexec" option.

/dev/mapper/usr_sap_lv /usr/sap xfs rw,seclabel,noexec,relatime,attr2,inode64,logbufs=8,logbsize=32k,sunit=8,swidth=8,noquota 0 0

"noexec" option disables program executions from the filesystem.

Note 3383055  - Linux: SAP Host Agent installation fails with systemdI_msg_handler vers3

Resolution is simple.

💫Check with linux team and remove "noexec" option on Host Agent related filesystem from /etc/fstab and execute mount -a to activate the change.

*** It's simple tick but 3 cases in single link would help a lot to revise concepts quickly ***

There would be another error which can occur rarely since usually linux team would be sharp to avoid this error. Let's have this as case 4.

Case 4:


Main Error:

StartService

FAIL: Service start failed: systemdI_msg_handler: job '/org/freedesktop/systemd1/job/184239' canceled with 'dependency'

SWPM logs itself will have error - Failed to mount /sapmnt, /hana/shared, etc.,

Linux team/Server team needs to resolve this filesystem issue.

Note 3531973 - "Service start failed" error during SWPM installation with message "canceled with 'dependency'"

Thanks for visiting !!!

No comments:

Post a Comment

Featured Post

32. How to check Import Prerequisites to install SAP ADD ON or DO SP Updates?

Considering Ariba CIG Add on for example. Most of the projects use Ariba CIG Add on. It's widely used in both ECC and S/4 HANA Sy...

Popular Posts