OMSA daemons appear to crash a minute after startup
I am having a (yet another) peculiar problem with OMSA on Dell PE 2950 running CentOS 5.4 (64 bit). (I list the details of configuration further in my post.) As installed, OMSA daemons seem to work only for around 30-60 seconds, and then some of them quit (crash?).
Immediately after reboot of the machine:
# srvadmin-services.sh status dell_rbu (module) is running ipmi driver is stopped dsm_sa_datamgrd (pid 4398 4128) is running dsm_sa_eventmgrd (pid 4375) is running dsm_om_shrsvcd (pid 3575) is running dsm_om_connsvcd (pid 4394 4393) is running
# omreport storage controller Controller PERC 5/i Integrated (Embedded) [...]
Web-based GUI also works OK at this point.
A minute later (without doing anything else on the machine):
# srvadmin-services.sh status dell_rbu (module) is stopped ipmi driver is running dsm_sa_datamgrd is stopped dsm_sa_eventmgrd is stopped dsm_om_shrsvcd (pid 3575) is running dsm_om_connsvcd (pid 4394 4393) is running
# omreport storage controller No controllers found
The web-based GUI shows "Main Chassis" and "Storage" empty, while "Software" has only "Operating System", which is also empty.
However, everything works fine (indefinitely) if I restart the daemons:
# srvadmin-services.sh restart
Shutting down DSM SA Shared Services: [ OK ] Shutting down DSM SA Connection Service: [ OK ] Stopping Systems Management Data Engine: Stopping dsm_sa_eventmgrd: Not started [FAILED] Stopping dsm_sa_datamgrd: Not started [FAILED] Stopping Systems Management Device Drivers: Stopping dell_rbu: Not started [ OK ] Starting Systems Management Device Drivers: Starting dell_rbu: [ OK ] Starting ipmi driver: Already started [ OK ] Starting Systems Management Data Engine: Starting dsm_sa_datamgrd: [ OK ] Starting dsm_sa_eventmgrd: [ OK ] Starting DSM SA Shared Services: [ OK ] Starting DSM SA Connection Service: [ OK ]
# omreport storage controller Controller PERC 5/i Integrated (Embedded) [...]
To make the OMSA daemons start properly without manual intervention, I disabled all deamons by chkconfig at all runlevels, and instead put the following lines into /etc/rc.d/rc.local:
Both lines are necessary, so, in essence, OMSA needs to be started twice in order to work properly. It seems to me that this is a result of some circular dependencies in initialization order between OMSA components. The workaround works, but I find it quite ugly and would prefer some nicer solution. Has anyone else encountered this problem?
Details of my configuration:
Hardware: DELL PowerEdge 2950 System: Centos 5.4 64 bit
# uname -a Linux peta.swmed.edu 2.6.18-164.9.1.el5 #1 SMP Tue Dec 15 20:57:57 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
PERC Controller: PERC 5/i Integrated
# omreport storage controller Controller PERC 5/i Integrated (Embedded)
Controllers ID : 0 Status : Ok Name : PERC 5/i Integrated Slot ID : Embedded State : Ready Firmware Version : 5.2.2-0072 Minimum Required Firmware Version : Not Applicable Driver Version : 00.00.04.08-RH2
I get a similar problem on every single Dell server I have (4x PE2900, 1x PE1950) all running CentOS 5.4 64bit or 32bit and OMSA 6.2.0 and wih PERC{5,6}/{i,e} controlers, except a restart for me doesn't fix it.
Every thing has been working fine for 3 years with all previous versions of OMSA, but 6.2.0 is broken.
for me, dsm_sa_datamgrd takes about 10 minutes to decide whether it can start or not and then end up with a red FAILED, although when doing a status it claims it is started.
and dsm_sa_snmpd just segfaults:
dsm_sa_snmpd[10108]: segfault at 0000000000000008 rip 0000000000b4e49d rsp 00000000ffe6fad4 error 4 dsm_sa_snmpd[12040]: segfault at 0000000000000008 rip 0000000000b4e49d rsp 00000000ff86f644 error 4 dsm_sa_snmpd[16331]: segfault at 0000000000000008 rip 0000000000b4e49d rsp 00000000ffb12b84 error 4
When accessing the web interface, every thing is blank, you can login, get the normal interface and the tree on the left but no information is available at all.
I know CentOS is not officially supported but as it used to work just fine until now, it would be nice if this got fixed at some point in the fairly near future.<
Similar problem here. two servers PE 1950 with PERC5/i and PERC6/i CentOS 4.8 (64 bit), OMSA 6.2, srvadmin-services.sh restart fixes some things, but temperatures and storage still not shown. Earlier OMSA versions were working fine (5.5 was fine for sure).
# omreport chassis temps Error! No temperature probes found on this system.
In my case omreport chassis temps works, though it shows one temperature reading only. I wonder if this is correct...
# omreport chassis temps Temperature Probes Information
------------------------------------ Main System Chassis Temperatures: Ok ------------------------------------
Index : 0 Status : Ok Probe Name : System Board Ambient Temp Reading : 22.0 C Minimum Warning Threshold : 8.0 C Maximum Warning Threshold : 42.0 C Minimum Failure Threshold : 3.0 C Maximum Failure Threshold : 47.0 C
Just wondering if anyone found a resolution to this. I just installed this with a new Centos 5.4 build on a PE 2850 with a Perc 4e/di RAID controller. I am having the same frustrations.
This issue is intermittent. Once in a while, I will get a report. More than often I get "no controllers found."
At the moment (mysteriously) datamgrd is running, usually it is not and when I run srvadmin-services.sh restart I get an error message reporting that it is not running.
# srvadmin-services.sh status Checking Remote Access Controller (RAC4) Service... not run[ OK ] dell_rbu (module) is stopped ipmi driver is stopped dsm_sa_datamgrd (pid 20088) is running dsm_sa_eventmgrd (pid 20106) is running dsm_om_shrsvcd (pid 17618) is running dsm_om_connsvcd (pid 17652 17651) is running
# uname -a Linux ******* 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
# omreport storage controller Controller PERC 4e/Di (Embedded)
Controllers ID : 0 Status : Ok Name : PERC 4e/Di Slot ID : Embedded State : Ready Firmware Version : 5B2D Minimum Required Firmware Version : Not Applicable Driver Version : Not Applicable Minimum Required Driver Version : Not Applicable Storport Driver Version : Not Applicable Minimum Required Storport Driver Version : Not Applicable Number of Connectors : 2 Rebuild Rate : 30% BGI Rate : Not Applicable Check Consistency Rate : Not Applicable Reconstruct Rate : Not Applicable Alarm State : Not Applicable Cluster Mode : Not Applicable SCSI Initiator ID : 7 Cache Memory Size : 256 MB Patrol Read Mode : Auto Patrol Read State : Stopped Patrol Read Rate : Not Applicable Patrol Read Iterations : 2836 Abort check consistency on error : Not Applicable Allow Revertible Hot Spare and Replace Member : Not Applicable Auto replace member on predictive failure : Not Applicable Load balance : Not Applicable Security Capable : Not Applicable Security Key Present : Not Applicable Redundant Path view : Not Applicable
I am having a very similar problem as well. I am using the same version of hardware, and am running VMware's ESXi 4.1 as the host platform. However, I am using Ubuntu 10.04.2 (64-bit) opposed to CentOS. I have the respository setup and every thing for Dell OM installed, but when I attempt to start the services:
$ sudo service dataeng start
I recieve the following error message:
Starting Systems Management Data Engine: Failed to start because system is not supported
phantomtiger
1 Message
3196
0
Posted January 6th, 2010 15:00
I'm having this same exact problem on a Dell PE 6850 running CentOS 5.4 (32 Bit).