"Setup: command not found..." when installing CAPKI for SCM Client
Article ID: 100669
Updated On:
Products
Issue/Introduction
When trying to install the CAPKI client for SCM, we are seeing this:
[root@example-server scm]# cd /tmp/scm
[root@example-server scm]# mkdir etpki
[root@example-server scm]# mv etpki.tar.gz etpki
[root@example-server scm]# cd etpki
[root@example-server etpki]# ls
etpki.tar.gz
[root@example-server etpki]# gunzip etpki.tar.gz
[root@example-server etpki]# tar xvf etpki.tar
etpki_linux/
etpki_linux/setup
etpki_linux/readme.txt
[root@example-server etpki]# cd etpki_linux/
[root@example-server etpki_linux]# ls
readme.txt setup
[root@example-server etpki_linux]# setup install caller=SCMCLIENT verbose env=all
bash: setup: command not found...
[root@example-server etpki_linux]#
Why, when we're in the folder where the setup executable is, do we get the message that the command is not found?
Environment
CA Harvest SCM v12 and up
Unix and Linux platforms
Cause
By default, the "$PATH" environment variable does not normally include the "." directory (current directory). When this is not included, the Linux or Unix operating system doesn't include the current directory in its search for the "setup" command, and therefore reports that the command was not found.
Resolution
If you’ll put “./” in front of the setup command you will have a better result.
Try this command:
./setup install caller=SCMCLIENT verbose env=all
Additional Information
Installation instructions for CAPKI on Linux and Unix are here: Install CAPKI for All the Users on a Computer
Note: the installation instructions in the documentation suggests to use the command "setup" without the leading "./", which could result in the problem described above. If you encounter this, simply add "./" to the front of your command and it will work as expected.
Feedback
