IGA Xpress: "Failed to connect to bus: No such file or directory" during install

Products

• CA Identity Suite

Issue/Introduction

When trying to install v15 on a new system, you see the following:

[INFO] Please use "igx" user to login

Attempting to start/restart/check status fails:
[igx@strongbad-test ~]$ igactl start xpress
Failed to connect to bus: No such file or directory

Also running a native UNIX command to checking user lingering is enabled and properly working such as loginctl user-status <username> and loginctl session-status [ID] after logging into the UNIX system as the igx user does not return expected data.

Environment

Identity Suite v15
Linux RHEL 9.3

Cause

With v15, the client uses and manages their own supported OS for the Identity Suite deployment.  The client may require unique security and permissions for the system.  In this case, the system had locked out registering new created user sessions. When trying to generate and register the igx user which is required to install v15, the install would immediate stop with the error discussed here. Also the /run/users folder did not contain the sub-folder that should have been created for the igx user.

This problem is not seen on every deployed system so it is likely an environmental problem caused by specific OS configuration/image used in certain customer environments.

 

Resolution

The required UNIX OS PAM related settings below allows the session to be registered and install to complete. 

Add: "session required pam_systemd.so" to /etc/pam.d/login

#%PAM-1.0
auth       substack     system-auth
auth       include      postlogin
account    required     pam_nologin.so
account    include      system-auth
password   include      system-auth
# pam_selinux.so close should be the first session rule
session    required     pam_selinux.so close
session    required     pam_loginuid.so
# pam_selinux.so open should only be followed by sessions to be executed in the user context
session    required     pam_selinux.so open
session    required     pam_namespace.so
session    optional     pam_keyinit.so force revoke
session    include      system-auth
session    include      postlogin
-session   optional     pam_ck_connector.so
session    required     pam_systemd.so

Also may need to run the following command twice:

sudo authselect select sssd with-sudo with-mkhomedir --force

And verify that running a native UNIX command to check user lingering such as loginctl user-status <username> and loginctl session-status [ID] after logging into the UNIX system as the igx user returns expected data otherwise work further with your UNIX administrators to first resolve OS level problems preventing these UNIX native commands from working properly.

 

Additional Information

pam_systemd.so