Accepted Solutions
Okay, here's the issue and it's actually a pretty simple one, once you take a look at the install.sh script. APC should probably do a better job of writing the script and providing a better error message as it's not entirely accurate.
If you download PCNS 2.2.4 which is the latest version of the utility and look at line start 238, you'll notice this is where the script figures out what OS you're running as part of the pre-req before installing PCNS:
CheckOS() {
OS=`uname | grep -i Linux`
if ; then
if [ -f /etc/vima-release ] || [ -f /etc/vmware-release ]; then
OS=$VIMA
else
OS=$LINUX
fi
.....
What they're doing is basically checking whether you're trying to install the software on VIMA 1.0 because prior to latest version of vMA 4.0 and 4.1, the build file was named vima-release versus the new name vma-release. The other weird and stupid thing is they also check to see if you're running this on a classic ESX host because they do an "or" statement to see if /etc/vmware-release exists. If either of these files exists, then it's considered an error by setting the OS variable to "VIMA" and later on there is an initialization section which says if OS=VIMA, it's an error which is showed here:
Initialize() {
Echo "Initializing ..."
case "$OS" in
$VIMA)
Echo "This version of PowerChute Network Shutdown does not support VMWare ESX or ESXi. Please consult www.apc.com for the required version of PowerChute Network Shutdown."
exit 1
;;
Again, the error message can be stated a lot more clearer. Basically, APC is only supporting vMA 4.0 or greater and does not support 2.2.4 on classic ESX Service Console. They probably should have done a better job on the error message and instead of checking if the file exists for /etc/vima-release, because if you upgrade from VIMA 1.0 -> vMA 4.0 or vMA 4.1, the file actually exists, but if you look at the contents of the file, the rev has changed.
So the issue that I see here is either you performed an upgrade of VIMA 1.0 to vMA 4.0 or 4.1 and hence you're seeing the error OR you're running on VIMA 1.0 which is not supported. I can confirm this installs perfectly fine on brand new deployment of vMA 4.1. I have not confirmed on vMA 4.0, but it should install fine so long as it does not have /etc/vima-release file.
Hopefully this helps and I would complain to APC to fix their install.sh script.
=========================================================================
William Lam
VMware vExpert 2009,2010
VMware scripts and resources at:
Getting Started with the vMA (tips/tricks)
Getting Started with the vSphere SDK for Perl
VMware Code Central - Scripts/Sample code for Developers and Administrators
If you find this information useful, please award points for "correct" or "helpful".
