White Papers
Abstract
New installation of Secure+ fails with Semaphore ownership/permissions not as expected during initializing the Parmfile
Content
During a new install of Connect:Direct for UNIX you receive an error during the Secure+ part of the install while Initializing the Secure+ Parmfile. For example:
**********************************************************
Install Connect:Direct Secure+ Option for Linux UNIX ...
... Extracting Connect:Direct Secure+ Option for UNIX Module files
from the media. Actual time taken varies depending on the
system configuration.
... Done.
Verify Connect:Direct Secure+ Option for UNIX Module files are extracted.
Configuring the JRE, please wait...
... Done.
Initializing the Secure+ Parmfile.
Please enter the name of Connect:Direct node you want to customize:[ironman42]
The Initialize Secure+ operation failed. Please use SPAdmin to initialize the parmfile
once this installation is complete.
Please see the installation log file saved at:
/home/cdunix/work/ironman42/install_4.2.log
Message from SPCli:
SPCLI> SPCG000E rc=8 com.stercomm.csg.SPAdmin.SPAFileWriteException:
The Secure+ installation failed.
Install Connect:Direct Secure+ Option for Linux UNIX ...
... Extracting Connect:Direct Secure+ Option for UNIX Module files
from the media. Actual time taken varies depending on the
system configuration.
... Done.
Verify Connect:Direct Secure+ Option for UNIX Module files are extracted.
Configuring the JRE, please wait...
... Done.
Initializing the Secure+ Parmfile.
Please enter the name of Connect:Direct node you want to customize:[ironman42]
The Initialize Secure+ operation failed. Please use SPAdmin to initialize the parmfile
once this installation is complete.
Please see the installation log file saved at:
/home/cdunix/work/ironman42/install_4.2.log
Message from SPCli:
SPCLI> SPCG000E rc=8 com.stercomm.csg.SPAdmin.SPAFileWriteException:
The Secure+ installation failed.
************************************************************
Follow these instructions to debug the Secure+ Option using the spcli script.
If you have this type of failure you can run the following debug parameters with the spcli.sh script to help debug the issue.
[cd62@ironman] /home/cd62 $ cd ndm/bin
[cd62@ironman] /home/cd62/ndm/bin $ spcli.sh -d y -li y > spcli.log 2>&1
debug output from spcli.log:
[Debug]:args[4]=-li args[5]=y
[Debug]:Opening Log File: /home/cdunix/ndm/secure+/log/SP20160121.001
[Debug]:Opening parmfile: /home/cdunix/ndm/secure+/nodes
[Debug]:About to init SP...
cdspssl debug: startSPEnv entered
cdspssl debug: CdSPImpl::CdSPImpl entered
cdspssl debug: startSPEnv exited: Succeeded
[Debug]:Return Code from startSPEnv( ) = 0
[Debug]:The Local Node File Name is: .Local
[Debug]:OK, NO ACF FILE
[Debug]:NOT A VALID PARM DIR
SPCG031E rc=8 The specified Secure+ Parameters File Directory "/home/cdunix/ndm/secure+/nodes"
does not contain a Secure+ control file.
SPCG035E rc=8 Unable to open default parmfile in "/home/cdunix/ndm/secure+/nodes" directory.
[Debug]:default certdir: /home/cdunix/ndm/secure+/certificates
**************************************************************
* Secure+ Command Line Interface *
* IBM(R) Connect:Direct(R) Secure Plus v6.2.0.7 *
*------------------------------------------------------------------------------------------*
* Licensed Materials - Property of IBM *
* (C) Copyright IBM Corp. 1999, 2023 All Rights Reserved. *
* US Government Users Restricted Rights - Use, duplication *
* or disclosure restricted by GSA ADP Schedule Contract *
* with IBM Corp. *
**************************************************************
SPCLI> init Parmfile
LocalNode=ironman62
Path=/home/cdunix/ndm/secure+/nodes;
[Debug]:The Local Node File Name is: .Local
cdspssl debug: CdSPImpl::SPACreateACF entered
cdspssl debug: SPMutex::constructor: Calculating semaphore key
cdspssl debug: SPMutex::constructor: Creating SPMutex for NodePath /home/cdunix/ndm/secure+/nodes
cdspssl debug: SPMutex::constructor: semaphore key is 9e63e931
cdspssl debug: SPMutex::waitForSemaphoreInitialization: Semaphore ownership/permissions not as expected. Is (1066,99,600), expected (1066,199,600)
cdspssl debug: CdSPImpl::SPACreateACF exited, lock could not be acquired.
[Debug]:EXCEPTION !!!
SPCG000E rc=8 com.stercomm.csg.SPAdmin.SPAFileWriteException:
Access Control File (ACF)
Error #3 - Lock Process Failed
[Debug]:CRC IS 8 PRC IS 0 SESSION_RC 8
SPCLI> q;
[Debug]:Highest rcode 8
- Make sure you are logged in as the admin id for Connect:Direct. Run the command: umask
Verify that this value is equal to 022. If not, you should set this value in the user profile before proceeding with installing the application.
- Delete the semaphore key 9e63e931. Run the command as root: ipcrm -S 9e63e931
- Delete the Connect:Direct installation. Run the command as root: rm -fr /C:D_install_Dir/*
- Log in as the Connect:Direct installer id, reinstall Connect:Direct and Secure+
- Verify the problem is resolved.
[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSKTYY","label":"IBM Sterling Connect:Direct for UNIX"},"ARM Category":[{"code":"a8m0z000000cwUZAAY","label":"ABEND"},{"code":"a8m0z000000cwUtAAI","label":"SECURE+"}],"ARM Case Number":"","Platform":[{"code":"PF061","label":"UNIX"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
04 April 2024
UID
swg27047775