<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)">  <title>DMI error in RHEL5beta kickstart from RHN5 Satellite</title> <style>  </style> </head> <body lang=ES link=blue vlink=blue> <div class=Section1> Hi Philip,<o:p></o:p> <o:p> </o:p> We always get this error message on every box we kickstart and we’ve not seen any implication. In my opinion you can just get used to it.<o:p></o:p> <o:p> </o:p> Regards,<o:p></o:p> Juli <o:p></o:p> <o:p> </o:p> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center tabindex=-1> </div> De: Philip Styles [mailto:Philip.Styles@aems.net] Enviado el: martes, 02 de enero de 2007 16:34 Para: Entrena Perez, Julio [HP]; rhn-satellite-beta-users@redhat.com Asunto: RE: [rhn-satellite-beta-users] DMI error in RHEL5beta kickstart fromRHN5 Satellite<o:p></o:p> </div> <o:p> </o:p> System is an HP DL360 G4 and has run dmidecode from many versions of both RHEL3 and RHEL4 without problems.<o:p></o:p> <o:p></o:p> Nothing apparent in Bugzilla either.<o:p></o:p> <o:p> </o:p> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center tabIndex=-1> </div> From: Entrena Perez, Julio [HP] [mailto:jentrena@mailext.com] Sent: 02 January 2007 15:13 To: Philip Styles; rhn-satellite-beta-users@redhat.com Subject: RE: [rhn-satellite-beta-users] DMI error in RHEL5beta kickstart fromRHN5 Satellite<o:p></o:p> Hi Philip,<o:p></o:p> <o:p> </o:p> No issues that you should be aware of.<o:p></o:p> <o:p> </o:p> http://en.wikipedia.org/wiki/Desktop_Management_Interface#DMI_under_Linux<o:p></o:p> <o:p> </o:p> Regards,<o:p></o:p> Juli<o:p></o:p> <o:p> </o:p> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center tabIndex=-1> </div> De: rhn-satellite-beta-users-bounces@redhat.com [mailto:rhn-satellite-beta-users-bounces@redhat.com] En nombre de Philip Styles Enviado el: martes, 02 de enero de 2007 16:09 Para: rhn-satellite-beta-users@redhat.com Asunto: [rhn-satellite-beta-users] DMI error in RHEL5beta kickstart fromRHN5 Satellite<o:p></o:p> </div> <o:p> </o:p> <o:p> </o:p> Building a RHEL5beta server from an RHN5beta Satellite causes the following error in the ks-post.log file <o:p></o:p> FINISHED --14:15:48-- Downloaded: 3 files, 887K in 0.04s (24.3 MB/s) warning: /tmp/rhn_rpms/optional/pyOpenSSL-0.6-1.p24.7.2.2.i386.rpm: Header V3 DSA signature: NOKEY, key ID 897da07a Preparing... ################################################## pyOpenSSL ################################################## rhnlib ################################################## libxml2-python ################################################## Error reading hardware information: dbus_bindings.DBusException Error reading DMI information: dbus_bindings.DBusException vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ### 2007-01-02:14:15:52 Phil's RHEL5Beta Test Kickstart (from RHN5beta Satellite) ### 2007-01-02:14:15:52 Configuring MOTD ... ### 2007-01-02:14:15:52 ... Done MOTD configuration. ### 2007-01-02:14:15:52 Running post Kickstart script ... <o:p></o:p> The three packages previously downloaded do get installed sucessfully so the issue would appear to be in the following section of the kickstart script.<o:p></o:p> wget -P /tmp/rhn_rpms/optional <a href="http://rhs-test.admin.liffe.com/download/1167791301/0a8b1bb8905fde5e8983fbd1bd608775fa5d6e6e/0/0/redhat/NULL/libxml2-python/2.6.26-2.1.1/i386/libxml2-python-2.6.26-2.1.1.i386.rpm">http://rhs-test.admin.liffe.com/download/1167791301/0a8b1bb8905fde5e8983fbd1bd608775fa5d6e6e/0/0/redhat/NULL/libxml2-python/2.6.26-2.1.1/i386/libxml2-python-2.6.26-2.1.1.i386.rpm</a> <a href="http://rhs-test.admin.liffe.com/download/1167791301/5a8d8ecc34fa3ab379c5bf860e76394b6bd54ff3/0/0/redhat/NULL/rhnlib/2.2.5-1.el5/noarch/rhnlib-2.2.5-1.el5.noarch.rpm">http://rhs-test.admin.liffe.com/download/1167791301/5a8d8ecc34fa3ab379c5bf860e76394b6bd54ff3/0/0/redhat/NULL/rhnlib/2.2.5-1.el5/noarch/rhnlib-2.2.5-1.el5.noarch.rpm</a> <a href="http://rhs-test.admin.liffe.com/download/1167791301/7fcac710d278bd7cb13f50cf42fca129c7d1485c/0/0/redhat/NULL/pyOpenSSL/0.6-1.p24.7.2.2/i386/pyOpenSSL-0.6-1.p24.7.2.2.i386.rpm">http://rhs-test.admin.liffe.com/download/1167791301/7fcac710d278bd7cb13f50cf42fca129c7d1485c/0/0/redhat/NULL/pyOpenSSL/0.6-1.p24.7.2.2/i386/pyOpenSSL-0.6-1.p24.7.2.2.i386.rpm</a> <o:p></o:p> rpm -Uvh --replacepkgs --replacefiles /tmp/rhn_rpms/optional/pyOpenSSL* /tmp/rhn_rpms/optional/rhnlib* /tmp/rhn_rpms/optional/libxml2-python* <o:p></o:p> rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-beta <o:p></o:p> perl -npe 's/xmlrpc.rhn.redhat.com/rhs-test.admin.liffe.com/' -i /etc/sysconfig/rhn/up2date mkdir -p /etc/sysconfig/rhn/allowed-actions/script touch /etc/sysconfig/rhn/allowed-actions/script/all mkdir -p /etc/sysconfig/rhn/allowed-actions/configfiles touch /etc/sysconfig/rhn/allowed-actions/configfiles/all <o:p></o:p> # now copy from the ks-tree we saved in the non-chroot checkout cp -fav /tmp/ks-tree-copy/. / rm -Rf /tmp/ks-tree-copy # --End RHN command section-- <o:p></o:p> <o:p> </o:p> rhnreg_ks --activationkey=c887d36cbf2eff35d43690ef4f043c8f rhn_check <o:p></o:p> ) > /root/ks-post.log 2>&1 <o:p></o:p> <o:p> </o:p> %post ( export KS_NAME="Phil's RHEL5Beta Test Kickstart (from RHN5beta Satellite)" export KS_SCRIPT="ks-post.phils-rhel5beta-test" echo "vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv" echo "### $(date +'%Y-%m-%d:%H:%M:%S') $KS_NAME" <o:p></o:p> The system does sucessfully register with the RHN5beta Satellite and I've not so far been able to determine what the impact of this failure is.<o:p></o:p> Regards, Phil <o:p></o:p> Philip Styles Infrastructure Specialist AEMS 25 Bank Street London E14 5NQ Tel. +44 (0)20 7655 7514 Mobile. +44 (0)7739 760 962 Email: philip.styles@aems.net <o:p></o:p> <a href="file:///\\www.aems.net">www.aems.net</a> <o:p></o:p> _________________________________________<o:p></o:p> <o:p></o:p> The information contained in this e-mail is confidential and solely <o:p></o:p> for the intended addressee(s). Unauthorised reproduction, disclosure, <o:p></o:p> modification, and/or distribution of this email may be unlawful. If you <o:p></o:p> have received this email in error, please notify the sender immediately <o:p></o:p> and delete it from your system. The views expressed in this message <o:p></o:p> do not necessarily reflect those of Atos Euronext Market Solutions.<o:p></o:p> _________________________________________<o:p></o:p> <o:p></o:p> ================================= Atos Euronext Market Solutions Disclaimer ================================= The information contained in this e-mail is confidential and solely for the intended addressee(s). Unauthorised reproduction, disclosure, modification, and/or distribution of this email may be unlawful. If you have received this email in error, please notify the sender immediately and delete it from your system. The views expressed in this message do not necessarily reflect those of Atos Euronext Market Solutions. L'information contenue dans cet e-mail est confidentielle et uniquement destinee a la (aux) personnes a laquelle (auxquelle(s)) elle est adressee. Toute copie, publication ou diffusion de cet email est interdite. Si cet e-mail vous parvient par erreur, nous vous prions de bien vouloir prevenir l'expediteur immediatement et d'effacer le e-mail et annexes jointes de votre systeme. Le contenu de ce message electronique ne represente pas necessairement la position ou le point de vue d'Atos Euronext Market Solutions.<o:p></o:p> </div> </body> </html>