Problem is the following:
- /usr/bin/clearesm at some point runs /opt/dell/dset/bin/omsaliteinstall.sh
- that in turns sources /opt/dell/dset/bin/dsetfunctions, and then executes
the function Get_OMSA_Versions from dsetfunctions. This function fails to
correctly set the variable $OMSAversion, this causes omsaliteinstall.sh to
fail.
Reason is that dsetfunctions does:
export OMSApath=`grep -i "openmanage.omacore.installpath"
/etc/omreg.cfg | awk -F "=" '{print $2}'`
this will set OMSApath to /opt/dell/srvadmin, then
if [ -e "$OMSApath/OMIVER.DB" ]; then
export OMSAversion=`grep -i "OMI_OM_VERSION" $OMSApath/OMIVER.DB
| awk -F "=" '{print $2}'`
else
if [ -e "$OMSApath/omil" ]; then
echo "OMSA installed is very old. Strongly recommend to ..."
OMSAversion="2.0"
OMSAomssversion="2.0"
fi
fi
the file OMIVER.DB does not exist at that location, and where it actually
exists
/opt/dell/srvadmin/var/lib/srvadmin-omilcore/OMIVER.DB
it has just
OMI_OM_VERSION=%{PACKAGE_VERSION}
so it would fail regardless.
I edited omsaliteinstall.sh and manually forced the OMSA version
Get_OMSA_Versions
OMSAversion=6.2.0 <=== brute force method
and now I can use clearesm and it runs in a few seconds
# time /usr/bin/clearesm
Dell System E-Support Tool
@Copyright Dell Inc. 2004-2009 Version 1.8.1 build 100
* Collecting Dell OpenManage information ... [Please wait]
* Clearing Hardware Log ...
real 0m7.526s
user 0m3.105s
sys 0m0.232s
#
On Tue, 26 Jan 2010 09:10:54 +0100, Giulio <[email protected]> wrote:
>PET300, CENTOS 5.4, OMSA 6.2.
>
>I downloaded DSET 1.8.1 from here
>http://support.dell.com/support/topics/global.aspx/support/en/dell_system_tool
>and chose to install it permanently on hard disk into /opt/dell/dset
>
>Then I issued
>
> # time /usr/bin/clearesm
> Dell System E-Support Tool
> @Copyright Dell Inc. 2004-2009 Version 1.8.1 build 100
> * Collecting Dell OpenManage information ... [Please wait]
> There was a problem loading the OMSA driver/service
>
> real 5m1.722s
> user 0m1.466s
> sys 0m0.056s
> #
>
>After this I could see these 2 processes still active (ps ax):
> S 0:00 /bin/bash ./omsaliteinstall.sh
> D 0:00 rmmod ipmi_devintf --wait
>
>I was connected remotely via telnet.
>I issued
> # reboot
>the system would not reboot correctly, I went to the console and saw it was
>stuck at "stopping IPMI drivers".
>
>I wanted to simulate a situation in which I could not go to the console, so
>I tried resetting it remotely.
>
>Many network services had been shut down, luckily OMSA web service was still
>active, so I used
> OMSA -> shutdown -> no os shutdown + power cycle
>and the system came back up.
>
>Then I retried the very same thing, but this time in OMSA I chose
> OMSA -> shutdown -> OS shutdown first (default setting in OMSA)
>this didn't succeed, and after that OMSA wouldn't let me power cycle
>anymore, because when going to the shutdown page I got
> Operating system shutdown is disabled.
> Remote Shutdown Action is disabled
>I could only press "shutdown" which wouldn't work.
>So I had to walk to the system and manually power cycle it.
>
>
>The DSET README says
>====
>* This Hotfix is for supporting Dell Systems having OM6.1 on
> * PER710, PER610, PEM610, PER905, PE6950, PE1950
> * Red Hat Enterprise Linux (AS, ES) 4 update 6 for i386 and x86_64
> * Red Hat Enterprise Linux (AS, ES) 4 update 7 for i386 and x86_64
> * Red Hat Enterprise Linux (AS, ES) 5 update 3 for i386 and x86_64
>
>NOTE: It is certified only for the above mentioned Dell Systems & operating
>systems having OM6.1 on System Under Test(SUT)
>====
>
>Does the above mean I cannot use DSET 1.8.1 with OMSA 6.2?
>If so, where do I get a DSET which will work with OMSA 6.2?
>
>I downloaded the DSET from the default link on the offical DSET page, so I
>thought I was ok.
>
>Since unloading kernel modules is not always a good thing, should I just
>edit the /etc/rc.d/init.d/ipmi and make stop() a noop?
>
>
>Thanks
--
[email protected]
_______________________________________________
Linux-PowerEdge mailing list
[email protected]
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
