dxprepare.shlib unary operator expected messages

Products

• CA Directory

Issue/Introduction

When I attempt to run the dxserver silent installer, I'm receiving errors in the console related to dxprepare.shlib when the installer first fires:

/disk/staging/dxserver/linux_x86_64/dxserver/install/dxprepare.shlib: line 2257: [: -lt: unary operator expected
/disk/staging/dxserver/linux_x86_64/dxserver/install/dxprepare.shlib: line 2259: [: -eq: unary operator expected

============================= CURRENT INSTALLATION ============================

  No Directory DXagent detected
  No Directory Management UI detected
  No DXserver detected

The installation does appear to complete successfully, however I am concerned that there may be underlying issues. 

 

Environment

Release: 14.1.6
Component: CA Directory

Cause

The two messages were part of checking to see if a prior version of CAPKI were in place. Since this was a fresh installation, the error messages are actually harmless.

Resolution

To verify the installaion contains no underlying issues. In the insallation log file, we can log for messages similar to the following:

=========================== CA OpenSSL INSTALLATION ===========================

[CAPKI] Parameters: mode=install, caller=ETRDIR, instdir=/disk/apps/dxserver, env=all, verbose=true
[CAPKI] This installer contains CAPKI Version 6.0.0
[CAPKI] Using install directory as specified by CASHCOMP
[CAPKI] Installation directory: /disk/apps/dxserver/CAPKI
[CAPKI] Checking for Permissions
[CAPKI] Proper permissions are set for installation directory
[CAPKI] Disk space is available
[CAPKI] Existing Version RV=1
[CAPKI] Updated installed files log: /disk/apps/dxserver/CAPKI/CAPKI6/Linux/amd64/64/files.dat
[CAPKI] CAPKI Install Successful, return Value is 0

that shows the CAPKI6 has been installed successfully.

Futher, one can also use the samples provided under $DXHOME/samples, the samples/democorp is the simplest one that can be used to verify the success of the overall installation.

 

Additional Information

If a customer still has any concern with regard to use cases like this, please open a new ticket with Broad Support and reference this KB to allow Support to further investigate your particular use cases.