OMSA 5.4 dsm_sa_ipmi service not set to auto-start after install

[Mark Baxter]

I'm not so sure. I've seen the described behaviour on a number of RHEL3
and RHEL4 machines that I have been upgrading the OMSA for over the past
few weeks. 

In fact one OMSA 5.1 machine had this issue and the problem with
dsm_sa_ipmi was brought to my attention on this very list on 2008-04-28.

Of course we are running OMSA 5.1 on our RHEL3 machines but I have seen
it with more recent versions as well.


________________________________

Mark Baxter
OnDemand Administrator, Visma Proceedo AB

Switchboard : +46 8 522 930 30 - Direct : +46 8 522 930 60 - Mobile :
+46 73 978 92 60 - Fax : +46 8 58 88 48 29

________________________________

 

It's probably due to running CentOS instead of RHEL.  Several scripts
look
for specific Red Hat strings in /etc/redhat-release, specifically:
  Taroon
  Nahant
  Tikanga
and modify their behaviour accordingly.  The OMSA-provided IPMI service
startup
check does...  CentOS does not include these strings (the RHEL version
names) in their copy of /etc/redhat-release, thus scripts that check
for those and change behavior accordingly fail.  That's what's
happening to you.

OMSA bugs can of course be raised through normal tech support channels
- it is supported software.  Unfortunately, CentOS is not officially
supported by OMSA (yes, even though it's a simple recompile of RHEL),
so there's little tech support could do for you in this instance.  I'm
bcc'ing the OMSA installer team though. :-)

-- 
Matt Domsch
Linux Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge at dell.com
http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq