BMC Service Resolution 3.5.00.001 install fails with "Cannot run program (in directory "$MCELLDIR/bin"): error=2, No such file or directory errors.

Knowledge Article

Article Number

000309623

Old Article Number

000101756

Article Type

Solutions to a Product Problem

Title

BMC Service Resolution 3.5.00.001 install fails with "Cannot run program (in directory "$MCELLDIR/bin"): error=2, No such file or directory errors.

Summary

Product

BMC Service Resolution

Component

BMC Service Resolution - ITSM Integration

Applies to

BSR 3.5.01 silent install on Linux TSIM 10.0.500

Problem

TSIM 10.0.500
RHEL Linux 6.6 x86-64

Getting the following errors when trying to install BSR 3.5.00.001 on TSIM 10.0.500 ..

(Feb 02 2016 02:51:49.485 PM +0100),SEVERE,com.bmc.install.product.bppmhotfix.tasks.ServicesExecutions,
LOG EVENT {Description=[IOException for execute command!],Detail=[java.io.IOException: Cannot run program "./mkill" (in directory "$MCELLDIR/bin"): error=2, No such file or directory

....
LOG EVENT {Description=[IOException for execute command!],Detail=[java.io.IOException: Cannot run program "./mccomp" (in directory "$MCELLDIR/bin"): error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)

....
LOG EVENT {Description=[IOException for execute command!],Detail=[java.io.IOException: Cannot run program "./mcell" (in directory "$MCELLDIR/bin"): error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)

..

Cause

The install script is reading literal values from /usr/pw/server/bin/setup_env.sh, rather than picking up the env variables properly.

Solution

This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers.

1 - modify the setup_env.sh to have:

MCELLDIR="/opt/bmc/TrueSight/pw/server"
export MCELLDIR
MCELL_HOME="/opt/bmc/TrueSight/pw/server " (provide the correct path)

2 - re-run the install

Attachment(s):