-
assigned issue to
Error while Installing Open Source Environment using ACS
Hi, While installing the Open source environment on system (IBM i version 7.3) it prompts with a window showing error message below and hangs. clear;exec /tmp/bootstrap.sh: Cannot execute
Appreciate your help on getting this resolved.
Thanks Arun
Comments (11)
-
-
I suspect that the permissions are not getting set correctly, though if you are
*ALLOBJ
(which is needed to install) the execute permission doesn't matter.@Arun can you do an
ls -l /tmp/bootstrap.sh
andhead -n 5 /tmp/bootstrap.sh
?@ThePrez any clue why this could happen from ACS?
-
reporter Hi Kevin,
Thanks a lot for your quick response. I do have *ALLOBJ authority for my profile. I ran the commands and see below the details.
ls -l '/tmp/bootstrap.sh'
-rw-r--r-- 1 $
head -n 5 /tmp/bootstrap.sh
#!/QOpenSys/usr/bin/kshset -eu
Thanks, Arun
-
@Arun make sure to put triple ` around your text input or it will get interpreted as Markdown
#!/QOpenSys/usr/bin/ksh
vs
#!/QOpenSys/usr/bin/ksh
-
reporter @Kevin Thanks .
$
ls -l '/tmp/bootstrap.sh'
-rw-r--r-- 1
$
head -n 5 /tmp/bootstrap.sh
#!/QOpenSys/usr/bin/ksh
set -eu
function finished
$
-
I am not sure. I wonder if
/tmp/bootstrap.sh
is owned by someone else (though I still don't see why that would matter because of the *ALLOBJ) -
@Arun, can you give us output of
ls -l /QOpenSys/usr/bin/ksh
?Also, does anyone know why the
ls -l
output is so terse? (I am guessing an alias, but it just looks "off") -
Could also try
chmod +x /tmp/bootstrap.sh
(though again I don't think the execute bit matters because of *ALLOBJ).Also, it might be worth a try to manually remove /tmp/bootstrap.sh and try again, though the current failure is an unsolved mystery.
-
reporter @Jesse G Thanks.
My user profile is the owner for
/tmp/bootstrap.sh
$
ls -l /QOpenSys/usr/bin/ksh
lrwxrwxrwx 1 qsys 0 76 Nov 08 2008 /QOpenSys/usr/bin/ksh -> ../../QIBM/ProdData/OS400/PASE/bin/ksh
$
-
reporter @Jesse G I tried again after manually removing the /tmp/bootstrap.sh but it ended up having the same error.
-
- changed status to resolved
I am sorry to close this issue, but we will need your engagement in a more interactive support channel to pursue resolution. Please open a support ticket with IBM.
- Log in to comment