After updating and installing the various packages that seemed to be
missing due to dependancy problems, I was down to only two CentOS
hosts still giving me problems; both fresh installs, rather than the
rest of my host which were upgrades from OMSA 6.1.

Turns out that whereas 6.1 dropped the config for the IPMI start-up
script 'dsm_sa_ipmi' where the script expects to find it...

grep -n sysconfig /etc/init.d/dsm_sa_ipmi
79:CONFIGFILE=/etc/sysconfig/dsm_sa_ipmi

... OMSA 6.2 drops it here:

# rpm -ql srvadmin-hapi | grep sysconfig
/etc/sysconfig/dsm_sa_ipmi.sysconfig

So, one has to rename/copy the .sysconfig suffix off for it to work.

Two questions for Dell:

1) Was this intentional?  If this is the desired behavior, can it at
least be mentioned in the install output for the package? (Not that
everyone reads that, but it'd save some wasted time for a lot of us.)

2) Looking at the file, there is an odd comment at the top: "##
CAUTION: Please do not use this when ipmi or openipmi init is
present." -- does that specifically mean a non-Dell ipmi?  I guess if
you mean a literally-named "/etc/init.d/ipmi" script it makes sense.
If it's taken to mean don't use if there is an init script that starts
ipmi modules, which is what I first thought it meant ... well then
that includes Dell's ipmi initscript which in fact needs this script.
Or maybe I'm the only one that read it that way...  Anyhow, rewriting
to "when a non-Dell ipmi", "when a distro ipmi" or even "when another
ipmi" would help clarify IMO.

Eric

_______________________________________________
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

Reply via email to