Not able to install a software using bash scripts

[S2S]

I’m having issues installing new software on Redhat 8 and 7 machines using bash script, the same command works perfectly from the command line as root but will not work from the fixlet even though it exits with 0 exit code.

Command succeeded (Exit Code=0) wait bash -c “(cd ‘/var/opt/BESClient/__BESData/CustomSite_TEST/__Download/SOMESOFTWARE_FOR_REDHAT/’ && ./setup -i /opt -D ‘myhost.name’ -P 8080)”

From my observation, root user and BESClinet behaviors is not the same.

I did review other post and tried different command but no luck so far:

Trying to Run a Linux sh Script in BigFix

Yeah, in my original post, I was browsing out to the agents-linux.zip file as creating the task using the extracted agents-linux folder wasn’t working and giving me the 127 exit code. That’s why I was unzipping it. We got that same exit code for MAC’s. So browsing out to the zipped folder worked when we created this agent installer for MAC’s using the the MAC software distribution wizard. I’ll give this suggestion a try tomorrow. Thank you!

Trying to run shell script via BigFix action script but it fails, Please suggest remediation

Hi All, I am trying to run the below script via BigFix action script but it shows Exit Code 2. I also used shell to action converter but if failed as well, not sure if there something wrong with the context which works manually on the linux box:-1: Script for a in ls /proc/net/bonding/bond* | awk -F"/" '{print $NF}' do echo -e “$a: \c” cat /proc/net/bonding/$a | awk -F"addr:" ‘/addr/ {printf $NF}’ echo done > /tmp/abc.txt Fixlet action:-1: [image] Used Shell to action script converto…

Trying to Run a Linux/Mac sh Script in a BigFix Action

This is not needed. You can do it all in 1 action. Another work around for issues like this is running a shell script that uses CD to get to the correct directory, and then the rest of the commands run from within that directory as the base. I don’t generally do this for simple commands if I can just use absolute paths instead, but it does work. You can have a single action that uses a prefetch to download files, then uses a create file command to create a script, then mark the script executa…

Any suggestions would be appreciated.

Thanks.

[JasonWalker]

It can vary -a lot- based on whatever the installer shell script is trying to do.

In particular the shell launched by BigFix is a non-login shell - so it doesn’t source .profile or .login or .bashrc or whatever the shell init files are that usually supply you with environment variables. So if the bash script depends on something in the environment, it may not be there.

You could try the /bin/bash --login -c parameter and see whether that helps.

It might also be useful to redirect the output and stderr to a file to read whether there are any errors messages
.

[S2S]

That worked!, Thanks for your support Jason.