Dell OMSA on RH 2.1

[Patrick_Boyd at Dell.com]

Jonas,
 
A couple of questions/suggestions.
 
1) Is there any hardware in the system that was not shipped with the system?
2) Can you tell us exactly what is installed. On the latest version of OMSA you can do this by running `rpm -qa | grep srvadmin` that should work for 4.3 as well.
3) You may want to uninstall OMSA and try installing a component at a time using the install scripts in interactive mode. This would show the offending component and give us a better idea of how to proceed.
 
Thanks,
Patrick Boyd 
Dell Storage Software Engineer 
(512)728-3182 


________________________________

From: linux-poweredge-bounces at dell.com [mailto:linux-poweredge-bounces at dell.com] On Behalf Of Jonas Blåberg
Sent: Tuesday, June 20, 2006 5:08 AM
To: linux-poweredge-Lists
Subject: Dell OMSA on RH 2.1


Hello!
 
We have been using an old version of Dell OMSA on RH 2.1 AS since the machines were installed. The version used is 1.6.0 (the tgz package is named 3.6).
 
 
So I downloaded the latest supported for RH 2.1 from Dell's download pages which is 4.3 (when installed it says 2.0.0) and installed it with srvadmin-install.sh -dsw. 
 
But when trying to start it using srvadmin-services.sh start, dcstor32d says FAILED but processes are running, and nothing seems to be working. The omaws32 process is not listening to port 1311, so I am not able to check what is working and what is not. 
 
When stopping the agent the processes die, some pid files are usually left in /var/run, and semaphores created are not cleaned up (I have to ipcrm them manually).
 
 
I have also tried to install Dell OMSA 4.2 (which says 1.9.2 with omreport system version) with identical problems.
 
 
I know the operating system patch level is a little bit low, but at least we have patched the kernel to 2.4.9-e.68. Since this is an Oracle RAC production system I don't want to just try any applicable patch - I need a hint of where the problem could be located when behaving like this... I guess the semaphores could be the key but since they are part of the kernel that could not be the whole solution.
 
Regards
/blåberg
 

_________________________________________ 
Jonas Blåberg               
Mandator Infrastructure
Kruthusgatan 17
411 04  Göteborg
Sweden

E-Mail:     Jonas.Blaberg at mandator.com <mailto:Jonas.Blaberg at mandator.com>  
Phone:     +46 (0)31 739 84 54 
Switch:    +46 (0)31 739 83 00 
Fax:         +46 (0)31 739 84 01 
www.mandator.se/infra <http://www.mandator.se/infra>  
_________________________________________

 

 

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20060620/a6a1f94e/attachment-0001.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1001 bytes
Desc: image002.gif
Url : http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20060620/a6a1f94e/attachment-0001.gif