Issues with OpenManage + CentOs 5.4

Chris Szilagyi chris at apex-internet.com
Thu Sep 30 08:08:08 CDT 2010


Thanks... so from that I can see that since I have a PE2400, that the script
is complaining about the hardware.  Does anybody know how to get the script
to accept the PE2400 (or any other "unsupported" hardware)?  Or am I pretty
much out of luck?  I don't know how to find and modify that script, or if
that is even possible.  I've looked around and haven't been able to find any
information on this.

I appreciate all of the help and feedback....

--
Chris


> Here are the scripts that rpm runs....
>
>
> preinstall scriptlet (using /bin/sh):
>       [ ! -f "/etc/omreg.cfg" ] && "/etc/omreg.cfg file is not found" &&
> exit 1
>       REG_KEY="openmanage.omilcore.installpath"
>       INSTALL_DIR=`grep -i "^[[:space:]]*${REG_KEY}[[:space:]]*="
> /etc/omreg.cfg | sed 's#^[^=]*=##; s#^[[:space:]]*##;
> s#[[:space:]]*$##'`
>       FUNCS="${INSTALL_DIR}/omil/prereqcheck/Funcs.sh"
>       . ${FUNCS}
>
>       # check for proper system id
>       SYSIDFILEPATH=`GetTemp`
>       cat <<EOF >${SYSIDFILEPATH}
> [OPTIONS]
> VENDOR=DELL
> ProductVersion=5.5.0
> BuildNumber=364
>
> [SystemsSupported]
> 0106=PE4600
> 0109=PE6600
> 010A=PE6650
> 0121=PE2650
> 011B=PE1650
> 0123=PE2600
> 0124=PE1655MC
> 0141=PE650
> 014A=PE1750
> 0134=PE600SC
> 0135=PE1600SC
> 0165=PE750
> 0167=PE700SC
> 016C=PE1850
> 016D=PE2850
> 016E=PE2800
> 016F=PE6800
> 0170=PE6850
> 0183=PE1800
> 0185=PE800
> 018A=PE1855MC
> 01B6=PE850
> 01B7=PE830
> 01B8=PE1900
> 01B3=PE1950
> 01BB=PE1955
> 01B1=PE2900
> 01B2=PE2950
> 01E6=PE860
> 01E7=PE840
> 02C7=NX100
> 01EA=PE6950
> 0205=PE2970
> 01F0=PER900
> 0208=PEM600
> 020C=PEM605
> 020F=PER300
> 023C=PER200
> 023E=PVNF100
> 0210=PET300
> 025C=PEM805
> 027B=PEM905
> 0221=PER805
> 0223=PER905
> 020B=PET605
> 0295=DL2000
>
> [HardwareSupported]
> 8086:1000=INTEL
> 8086:1001=INTEL
> 8086:1002=INTEL
> 8086:1004=INTEL
> 8086:1008=INTEL
> 8086:1009=INTEL
> 8086:100c=INTEL
> 8086:100d=INTEL
> 8086:100e=INTEL
> 8086:100f=INTEL
> 8086:1010=INTEL
> 8086:1011=INTEL
> 8086:1012=INTEL
> 8086:1026=INTEL
> 8086:1027=INTEL
> 8086:105e=INTEL
> 8086:1075=INTEL
> 8086:1076=INTEL
> 8086:107b=INTEL
> 8086:107d=INTEL
> 8086:107e=INTEL
> 8086:108a=INTEL
> 8086:10c7=INTEL
> 8086:10d6=INTEL
> 8086:10f0=INTEL
> 8086:10f1=INTEL
> 8086:1229=INTEL
> 14e4:163a=BROADCOM
> 14e4:1644=BROADCOM
> 14e4:1645=BROADCOM
> 14e4:1647=BROADCOM
> 14e4:1648=BROADCOM
> 14e4:164c=BROADCOM
> 14e4:164d=BROADCOM
> 14e4:164e=BROADCOM
> 14e4:1659=BROADCOM
> 14e4:165a=BROADCOM
> 14e4:1677=BROADCOM
> 14e4:167a=BROADCOM
> 14e4:16a7=BROADCOM
> 14e4:16ac=BROADCOM
> 14e4:16ae=BROADCOM
> 14e4:16c7=BROADCOM
> 101e:9063=DRAC2
> 1028:0007=DRAC3
> 1028:0008=DRAC3
> 1028:0009=DRAC3
> 1028:000c=DRAC3
> 1028:000d=DRAC3
> 1028:0010=DRAC4
> 1028:0011=DRAC4
>
> [BladeSystems]
> 0124=PE1655MC
> 018A=PE1855MC
> 01BB=PE1955
> 0208=PEM600
> 020C=PEM605
> 025C=PEM805
> 027B=PEM905
> EOF
>       KEY="openmanage.sysidchkutlpath"
>       FILE="/etc/omreg.cfg"
>
>       # if SYSID is to be ignored, do not check for systemid!
>       if [ -z "${OMIIGNORESYSID}" ];
>       then
>           # if SYSID is NOT to be ignored
>           [ ! -f "${FILE}" ] && ErrorMsg "srvadmin-syscheck: ${FILE} file is
> not found" && exit 1
>           SYSIDCHECKPATH=`grep -i "^[[:space:]]*${KEY}[[:space:]]*=" ${FILE}
> | sed 's#^[^=]*=##; s#^[[:space:]]*##; s#[[:space:]]*$##'`
>           [ ! -f "${SYSIDCHECKPATH}" ] && ErrorMsg "srvadmin-syscheck:
> ${SYSIDCHECKPATH} file is not found" && exit 1
>
>           # look the sysid up in the syslist variable
>           SYSID=`${SYSIDCHECKPATH} | grep "System ID" | sed 's#^.*0x##;
> s#[[:space:]].*$##'`
>           VAL=`grep -i "^[[:space:]]*${SYSID}[[:space:]]*=" ${SYSIDFILEPATH}
> | sed 's#^[^=]*=##; s#^[[:space:]]*##; s#[[:space:]]*$##'`
>           [ -z "${VAL}" ] && ErrorMsg "srvadmin-syscheck: This RPM is not
> supported on this system (sysid=${SYSID})" && exit 1
>       fi
>       rm -f ${SYSIDFILEPATH}
>
>   true
>
> #------------------------------------------------------------------------------
> # post script
> #------------------------------------------------------------------------------
> postinstall scriptlet (using /bin/sh):
>   true
>
> #------------------------------------------------------------------------------
> # preun script
> #------------------------------------------------------------------------------
> preuninstall scriptlet (using /bin/sh):
>   true
>
> #------------------------------------------------------------------------------
> # postun script
> #------------------------------------------------------------------------------
> postuninstall scriptlet (using /bin/sh):
>     # Erase, not ugrade
>     if [ $1 == 0 ]; then
>       [ -d "${RPM_INSTALL_PREFIX}" ] &&
>         rmdir --ignore-fail-on-non-empty "${RPM_INSTALL_PREFIX}"
>       [ -d /opt/dell ] &&
>         rmdir  --ignore-fail-on-non-empty /opt/dell >/dev/null 2>&1
>     fi
>   true
>
>
> ###############################################################################
> #
> # Files List - indicates to RPM which files are to be packaged from the
> #              build system and installed on the target system at install
> time
> #
> ###############################################################################
>
>
>
>
> Regards
>
>
> Steve Tempest
>
> -----Original Message-----
> From: linux-poweredge-bounces at dell.com
> [mailto:linux-poweredge-bounces at dell.com] On Behalf Of Chris Szilagyi
> Sent: Thursday, 30 September 2010 1:01 PM
> To: Wayne_Weilnau at dell.com
> Cc: linux-poweredge at lists.us.dell.com
> Subject: RE: Issues with OpenManage + CentOs 5.4
>
> Wayne,
>
> I tried installing the RPMs for OMSA 5.5 as you suggested.  It seems that
> they too are doing some sort of system check.  "srvadmin-omilcore" installs
> fine.  But, the remaining packages fail to install with the error:
>
> srvadmin-syscheck: This RPM is not supported on this system (sysid=009B)
> error: %pre(srvadmin-syscheck-5.5.0-364.i386) scriptlet failed, exit status
> 1
> error:   install: %pre scriptlet failed (2), skipping
> srvadmin-syscheck-5.5.0-364
>
> I've tried adding "Tikanga" to /etc/redhat-release , however it does not
> help.
>
> Does anybody know of a way to get this to install?
>
> Thanks again in advance!
>
> --
> Chris
>
>
>> In OM 6.1 we removed many of the install blockages.  In the past, the
>> installation scripts would prevent installation on any unsupported
>> distribution or version.  In 6.1, these checks have been replaced with
>> standard RPM dependency checks.  At run time, there are a few checks
>> within
>> our processes to ensure that we are running on Dell hardware that is not
>> too
>> old.  Note that the ability to install on a version/distribution does not
>> imply that it is officially supported or that it will work.
>>
>> The net of this is that you should be able to install OMSA on SELinlux if
>> the RPMs we are dependent on are installed.  I believe there is a good
>> chance OMSA will work, but no guarantees.  Try it and see.
>>
>> Wayne Weilnau
>> Systems Management Technologist
>> Dell | OpenManage Software Development
>>
>> Please consider the environment before printing this email.
>>
>> Confidentiality Notice | This e-mail message, including any attachments,
>> is
>> for the sole use of the intended recipient(s) and may contain confidential
>> or proprietary information. Any unauthorized review, use, disclosure or
>> distribution is prohibited. If you are not the intended recipient,
>> immediately contact the sender by reply e-mail and destroy all copies of
>> the
>> original message.
>>
>> -----Original Message-----
>> From: linux-poweredge-bounces-Lists On Behalf Of Liberty Young
>> Sent: Wednesday, September 22, 2010 11:59 AM
>> To: Chris Szilagyi
>> Cc: linux-poweredge-Lists
>> Subject: Re: Issues with OpenManage + CentOs 5.4
>>
>> what about SELinux? Is it enabled?
>>
>> On Thu, Sep 16, 2010 at 8:29 PM, Chris Szilagyi <chris at apex-internet.com>
>> wrote:
>>> Hello:
>>>
>>> I recently set up a PowerEdge 2400 server running CentOS 5.4.  I'm
>>> trying
>>> to
>>> get OpenManage 4.5 installed (last version that I could find, that
>>> supports
>>> the PowerEdge 2400).  I installed everything using the supplied scripts,
>>> however when I try to start the services with "srvadmin-services.sh
>>> start",
>>> I get the following:
>>>
>>> Starting Systems Management Device Drivers:
>>> Starting dcdbas device driver:                            
>>> [
>>>  OK  ]
>>> Starting Systems Management Data Engine:
>>> Starting dcstor32d:                                    
>>>    [  OK  ]
>>> Starting dcevt32d:                                    
>>>     [  OK  ]
>>> Starting OM Common Services:                              
>>> [  OK  ]
>>> invcol Error: extract(): Unable to create temporary files. Please ensure
>>> that there is enough space in the
>>> tmp folder.
>>> Starting Secure Port Server:                              
>>> [  OK  ]
>>>
>>> The disk has over 7 GB of free space, and permissions look OK on /tmp.
>>>  Has
>>> anybody seen this problem or know of a solution?  So far I'm stumped.
>>>
>>> Thank you !!
>>> --
>>> Chris
>>>
>
>
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge at dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
> Please read the FAQ at http://lists.us.dell.com/faq
>
> Notice
>
>
>
> This email and any attachments are strictly confidential and subject to
> copyright.  They may
> contain privileged information.  If you are not the intended recipient
> please delete the message
> and notify the sender. You should not read, copy, use, change, alter or
> disclose this email or
> its attachments without authorisation.  The company and any related or
> associated companies do
> not accept any liability in connection with this email and any attachments
> including in connection
> with computer viruses, data corruption, delay, interruption, unauthorised
> access or unauthorised
> amendment. Any views expressed in this email and any attachments do not
> necessarily reflect the
> views of the company or the views of any of our related or associated
> companies.
>




More information about the Linux-PowerEdge mailing list