Error during SCC_DAEMON installation

When installing the SAP Cloud Connector, I am getting the following errors.  The installation is being performed by the user root as instructed.

 

<servername>:/opt/sap/scc # journalctl -xeu scc_daemon.service

Aug 24 13:41:35 <servername> scc_daemon[5574]: scc_Daemon start failed, see logfile: /opt/sap/scc/scc_daemon.log

Aug 24 13:41:35 <servername> systemd[1]: scc_daemon.service: Control process exited, code=exited, status=1/FAILURE

░░ Subject: Unit process exited

░░ Defined-By: systemd

░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel

░░

░░ An ExecStart= process belonging to unit scc_daemon.service has exited.

░░

░░ The process' exit code is 'exited' and its exit status is 1.

Aug 24 13:41:35 <servername> systemd[1]: scc_daemon.service: Failed with result 'exit-code'.

░░ Subject: Unit failed

░░ Defined-By: systemd

░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel

░░

░░ The unit scc_daemon.service has entered the 'failed' state with result 'exit-code'.

Aug 24 13:41:35 <servername> systemd[1]: scc_daemon.service: Unit process 5657 (su) remains running after unit stopped.

Aug 24 13:41:35 <servername> systemd[1]: Failed to start LSB: LJS Daemon.

░░ Subject: A start job for unit scc_daemon.service has failed

░░ Defined-By: systemd

░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel

░░

░░ A start job for unit scc_daemon.service has finished with a failure.

░░

░░ The job identifier is 2958 and the job result is failed.

Aug 24 13:55:16 <servername> systemd[1]: Starting LSB: LJS Daemon...

░░ Subject: A start job for unit scc_daemon.service has begun execution

░░ Defined-By: systemd

░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel

░░

░░ A start job for unit scc_daemon.service has begun execution.

░░

░░ The job identifier is 3575.

Aug 24 13:55:16 <servername> scc_daemon[6005]: Starting scc_Daemon

Aug 24 13:55:16 <servername> su[6088]: gkr-pam: couldn't get the password from user: Conversation error

Aug 24 13:55:16 <servername> su[6088]: pam_unix(su:auth): auth could not identify password for [sccadmin]

Aug 24 13:55:16 <servername> su[6088]: pam_sss(su:auth): authentication failure; logname= uid=0 euid=0 tty= ruser=root rhost= user=sccadmin

Aug 24 13:55:16 <servername> su[6088]: pam_sss(su:auth): received for user sccadmin: 10 (User not known to the underlying authentication module)

Aug 24 13:55:16 <servername> su[6088]: FAILED SU (to sccadmin) root on none

Aug 24 13:55:17 <servername> scc_daemon[6005]: scc_Daemon start failed, see logfile: /opt/sap/scc/scc_daemon.log

Aug 24 13:55:17 <servername> systemd[1]: scc_daemon.service: Control process exited, code=exited, status=1/FAILURE

░░ Subject: Unit process exited

░░ Defined-By: systemd

░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel

░░

░░ An ExecStart= process belonging to unit scc_daemon.service has exited.

░░

░░ The process' exit code is 'exited' and its exit status is 1.

Aug 24 13:55:17 <servername> systemd[1]: scc_daemon.service: Failed with result 'exit-code'.

░░ Subject: Unit failed

░░ Defined-By: systemd

░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel

░░

░░ The unit scc_daemon.service has entered the 'failed' state with result 'exit-code'.

Aug 24 13:55:17 <servername> systemd[1]: scc_daemon.service: Unit process 6088 (su) remains running after unit stopped.

Aug 24 13:55:17 <servername> systemd[1]: Failed to start LSB: LJS Daemon.

░░ Subject: A start job for unit scc_daemon.service has failed

░░ Defined-By: systemd

░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel

░░

░░ A start job for unit scc_daemon.service has finished with a failure.

░░

░░ The job identifier is 3575 and the job result is failed.

lines 91-152/152 (END)

 

<server>s:/opt/sap/scc # systemctl status scc_daemon.service

× scc_daemon.service - LSB: LJS Daemon

     Loaded: loaded (/etc/init.d/scc_daemon; generated)

     Active: failed (Result: exit-code) since Thu 2023-08-24 13:55:17 BST; 10min ago

       Docs: man:systemd-sysv-generator(8)

    Process: 6005 ExecStart=/etc/init.d/scc_daemon start (code=exited, status=1/FAILURE)

 

Aug 24 13:55:16 <servername> su[6088]: gkr-pam: couldn't get the password from user: Conversation error

Aug 24 13:55:16 <servername> su[6088]: pam_unix(su:auth): auth could not identify password for [sccadmin]

Aug 24 13:55:16 <servername> su[6088]: pam_sss(su:auth): authentication failure; logname= uid=0 euid=0 tty= ruser=root rhost= user=sccadmin

Aug 24 13:55:16 <servername> su[6088]: pam_sss(su:auth): received for user sccadmin: 10 (User not known to the underlying authentication module)

Aug 24 13:55:16 <servername> su[6088]: FAILED SU (to sccadmin) root on none

Aug 24 13:55:17 <servername> scc_daemon[6005]: scc_Daemon start failed, see logfile: /opt/sap/scc/scc_daemon.log

Aug 24 13:55:17 <servername> systemd[1]: scc_daemon.service: Control process exited, code=exited, status=1/FAILURE

Aug 24 13:55:17 <servername> systemd[1]: scc_daemon.service: Failed with result 'exit-code'.

Aug 24 13:55:17 <servername> systemd[1]: scc_daemon.service: Unit process 6088 (su) remains running after unit stopped.

Aug 24 13:55:17 <servername> systemd[1]: Failed to start LSB: LJS Daemon.

 

Log File: /opt/sap/scc/scc_daemon.log = Empty:

 

<servername>:/opt/sap/scc # ls -ltr *.log

-rw-rw-r-- 1 sccadmin sccgroup 0 Aug 24 13:55 scc_daemon.log

 

Can any assistance be offered?

 

Regards

 

Paul Maber | Snr. Technical/Security Consultant |North, Energy and Utilities BU

Financial Services, Digital, IP & Alliances | CGI

Waterton Industrial Estate, Moor Rd, Bridgend CF31 3TR | United Kingdom.

Paul.maber@xxxxxxx | www.CGI-group.com

Now available, the fifth in our highly successful “For Dummies” series – “GB Electricity Industry for Dummies”. Register for your copy here.

 

Upcoming Holiday:  August - 4th, 11th, 18th, 25th and 30^th October to 8^th November

 

CGI IT UK Ltd’s registered office address: 14th Floor, 20 Fenchurch Street, London EC3M 3BY, United Kingdom
Registered in England and Wales - Number 2843595

CONFIDENTIALITY NOTICE: Proprietary/Confidential Information belonging to CGI Group Inc. and its affiliates may be contained in this message. If you are not a recipient indicated or intended in this message (or responsible for delivery of this message to such person), or you think for any reason that this message may have been addressed to you in error, you may not use or copy or deliver this message to anyone else. In such case, you should destroy this message and are asked to notify the sender by reply e-mail