-
Title
The install.sh script may fail with an unexpected error -
Description
While running the Authentication Services Installer, the install.sh script may fail with an unexpected error similar to these:
One Identity Safeguard Authentication Services Installation Script
Script Build Version: 5.0.4.51162Copyright 2021 One Identity LLC. ALL RIGHTS RESERVED.Protected by U.S. Patent Nos. 7,617,501, 7,895,332, 7,904,949, 8,086,710, 8,087,075, 8,245,242. Patents pending.: not found [No such file or directory]: not found [No such file or directory]: not found [No such file or directory]: unknown option: .[20]: set: -Usage: set [-sabefhkmnprtuvxBCGH] [-A name] [-o[option]] [arg ...]
-
Cause
The Authentication Services tar.gz. the package was extracted in a Windows Computer and then moved or copied to the destination Unix/Linux system.
The scripts (*.sh) had a control character (^M) at the end of each line thus preventing the Unix interpreter to execute properly.
Also, all the *.sh scripts were missing the executable bit (+x) because Windows does not have such an equivalent attribute.
-
Resolution
Please make sure that you always unpack the compressed packages made for Unix/Linux environments in the corresponding operating systems and not onto a windows operating system. This will ensure proper extraction and restoration of Unix/Linux style attributes and permissions.
-
Additional Information
If you have a similar issue with packages coming from a Windows system you can always use
# dos2unix
# chmod +x
Example:
# for f in `find . -name "*.sh"`; do echo $f; dos2unix $f $f; chmod +x $f; echo; done