Re: libsmbios and smbios-* from EPEL conflicts with dell-community repository
On Fri, Jun 18, 2010 at 9:46 PM, Matt Domsch wrote: > On Fri, Jun 18, 2010 at 08:06:49PM -0700, Brandon Ooi wrote: > > That's a bogus dependency in yum-dellsysid. There's no reason for it > to depend on exactly that version of smbios-utils-python. > > Something strange is happening, as yum-dellsysid is from the same SRPM > as smbios-utils-python, meaning the yum-dellsysid noarch package must > have gotten pushed out, while the smbios-utils-python packages that > match it didn't. But that isn't what happened - they're both present > in the repo together... > > ./isv:/dell:/community/el5-x86_64/x86_64/smbios-utils-python-2.2.21-3.2.el5.x86_64.rpm > ./isv:/dell:/community/el5-x86_64/x86_64/yum-dellsysid-2.2.21-3.2.el5.x86_64.rpm > > > As as shot in the dark, perhaps upgrade only the > dell-community-repository RPM first, and then try the full yum > upgrade. It may be that the new repository RPM needs to be installed > first to provide proper (maybe fixed?) pointers to the community repo, > so subsequent upgrades will find the right content. > > Michael Brown has been working on this code again this last week - > hopefully he can look into it - but likely not over the weekend. > > > Thanks, > Matt > > -- > Matt Domsch > Technology Strategist > Dell | Office of the CTO > I did a yum upgrade dell-community-repository to see if that solved the problem but it did not. It was good to isolate the problem though. Here's the latest update attempt. Is there an SRPM for yum-dellsysid? I didn't find it in http://linux.dell.com/repo/community/repositories/isv:/dell:/community/el5-x86_64/src/ Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package yum-dellsysid.x86_64 0:2.2.21-3.2.el5 set to be updated --> Processing Dependency: smbios-utils-python = 2.2.21-3.2.el5 for package: yum-dellsysid --> Finished Dependency Resolution yum-dellsysid-2.2.21-3.2.el5.x86_64 from dell-community has depsolving problems --> Missing Dependency: smbios-utils-python = 2.2.21-3.2.el5 is needed by package yum-dellsysid-2.2.21-3.2.el5.x86_64 (dell-community) Error: Missing Dependency: smbios-utils-python = 2.2.21-3.2.el5 is needed by package yum-dellsysid-2.2.21-3.2.el5.x86_64 (dell-community) You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest The program package-cleanup is found in the yum-utils package. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
RSS feeds of Dell Linux mailing lists
Some of these lists are lower traffic than others, and I find it handy to have mailing list posts appear in my daily RSS stream. So, with thanks to a handy mailman-archive-to-rss script[1], there are now RSS feeds for each of the mailing lists on lists.us.dell.com. http://lists.us.dell.com/rss/ has the RSS feeds to subscribe to. I hope this makes it easier to keep track of conversations on the lists. Thanks, Matt [1] http://jmason.org/software/scripts/mailman-archive-to-rss.txt -- Matt Domsch Technology Strategist Dell | Office of the CTO ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: libsmbios and smbios-* from EPEL conflicts with dell-community repository
On Fri, Jun 18, 2010 at 08:06:49PM -0700, Brandon Ooi wrote: > Hey guys, > > It seems like the smbios packages from dell-community are conflicting > with the same packages in EPEL. Does anybody know what the recommended > way to resolve this? > > Seems like there are 2 choices, use --disablerepo and go with either > EPEL or dell-community. > > epel - smbios-utils-python.2.2.16-2.1.el5 > dell-community - smbios-utils-python.2.2.21-3.2.el5 > > Might not matter too much but wanted to see if you guys have seen a > similar problem. > > Thanks! > > > yum update > Resolving Dependencies > --> Running transaction check > ---> Package dell-community-repository.noarch 0:1-11.1.el5 set to be updated > ---> Package yum-dellsysid.x86_64 0:2.2.21-3.2.el5 set to be updated > --> Processing Dependency: smbios-utils-python = 2.2.21-3.2.el5 for > package: yum-dellsysid > --> Finished Dependency Resolution > yum-dellsysid-2.2.21-3.2.el5.x86_64 from dell-community has depsolving > problems > --> Missing Dependency: smbios-utils-python = 2.2.21-3.2.el5 is That's a bogus dependency in yum-dellsysid. There's no reason for it to depend on exactly that version of smbios-utils-python. Something strange is happening, as yum-dellsysid is from the same SRPM as smbios-utils-python, meaning the yum-dellsysid noarch package must have gotten pushed out, while the smbios-utils-python packages that match it didn't. But that isn't what happened - they're both present in the repo together... ./isv:/dell:/community/el5-x86_64/x86_64/smbios-utils-python-2.2.21-3.2.el5.x86_64.rpm ./isv:/dell:/community/el5-x86_64/x86_64/yum-dellsysid-2.2.21-3.2.el5.x86_64.rpm As as shot in the dark, perhaps upgrade only the dell-community-repository RPM first, and then try the full yum upgrade. It may be that the new repository RPM needs to be installed first to provide proper (maybe fixed?) pointers to the community repo, so subsequent upgrades will find the right content. Michael Brown has been working on this code again this last week - hopefully he can look into it - but likely not over the weekend. Thanks, Matt -- Matt Domsch Technology Strategist Dell | Office of the CTO ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
libsmbios and smbios-* from EPEL conflicts with dell-community repository
Hey guys, It seems like the smbios packages from dell-community are conflicting with the same packages in EPEL. Does anybody know what the recommended way to resolve this? Seems like there are 2 choices, use --disablerepo and go with either EPEL or dell-community. epel - smbios-utils-python.2.2.16-2.1.el5 dell-community - smbios-utils-python.2.2.21-3.2.el5 Might not matter too much but wanted to see if you guys have seen a similar problem. Thanks! > yum update Resolving Dependencies --> Running transaction check ---> Package dell-community-repository.noarch 0:1-11.1.el5 set to be updated ---> Package yum-dellsysid.x86_64 0:2.2.21-3.2.el5 set to be updated --> Processing Dependency: smbios-utils-python = 2.2.21-3.2.el5 for package: yum-dellsysid --> Finished Dependency Resolution yum-dellsysid-2.2.21-3.2.el5.x86_64 from dell-community has depsolving problems --> Missing Dependency: smbios-utils-python = 2.2.21-3.2.el5 is needed by package yum-dellsysid-2.2.21-3.2.el5.x86_64 (dell-community) Error: Missing Dependency: smbios-utils-python = 2.2.21-3.2.el5 is needed by package yum-dellsysid-2.2.21-3.2.el5.x86_64 (dell-community) You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest The program package-cleanup is found in the yum-utils package. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Monitoring
We are using Nagios to monitor our servers as well (most of them are Dell's PE 1950 or PE R610). Nagios NRPE can communicate with OMSA and we are monitoring all of the critical parts this way. Nagios is sending us critical errors via GSM modems and provides us with the alert status summary page for the hotline technicians. -- Best Regards, David Brůha 1st ART Studio s.r.o. Koněvova 1271/101 Praha 3, 130 00 tel.: +420-277-779-559 fax: +420-277-779-555 e-mail: d.br...@1art.cz Dne pátek 18 Červen 2010 20:42:24 Stewart St. Dennis napsal(a): > Ruslan: > Nagios is a very powerful monitoring platform that would duplicate part of > ITA and supplement other components. Nagios can proactively monitor the > Dell node using "public" functionality (ping, http, etc.) or "private" > funtionality (using SNMP queries, Nagios's remote plugin executer (nrpe), > ssh calls, etc.). As well, Nagios can be configure to consume SNMP Traps > to reactively monitor the nodes. Nagios has rich notification and > escalation functionality. > > Depending on what you already have in place, Nagios may duplicate what you > are already doing. If you don't have procative and reactive monitring and > notification functionality (from a secure web platform), then > investigating Nagios is a worthwhile investment of time. > > Stewart > > -Original Message- > From: Ruslan Sivak > Date: Fri, 18 Jun 2010 14:04:05 > To: > Subject: Monitoring > > I have installed server administrator from the repos, configured SNMP > and I have at least some alerts going into Dell ITA, but I'm having > issues getting ITA to see the server. > > What are people using for monitoring? I saw that there was a Nagios > plugin, but I'm not familiar enough with nagios and didn't see any > documentation on getting the plugin to work. > > Russ > > ___ > Linux-PowerEdge mailing list > Linux-PowerEdge@dell.com > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > Please read the FAQ at http://lists.us.dell.com/faq > > ___ > Linux-PowerEdge mailing list > Linux-PowerEdge@dell.com > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > Please read the FAQ at http://lists.us.dell.com/faq ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Monitoring
Ruslan: Nagios is a very powerful monitoring platform that would duplicate part of ITA and supplement other components. Nagios can proactively monitor the Dell node using "public" functionality (ping, http, etc.) or "private" funtionality (using SNMP queries, Nagios's remote plugin executer (nrpe), ssh calls, etc.). As well, Nagios can be configure to consume SNMP Traps to reactively monitor the nodes. Nagios has rich notification and escalation functionality. Depending on what you already have in place, Nagios may duplicate what you are already doing. If you don't have procative and reactive monitring and notification functionality (from a secure web platform), then investigating Nagios is a worthwhile investment of time. Stewart -Original Message- From: Ruslan Sivak Date: Fri, 18 Jun 2010 14:04:05 To: Subject: Monitoring -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have installed server administrator from the repos, configured SNMP and I have at least some alerts going into Dell ITA, but I'm having issues getting ITA to see the server. What are people using for monitoring? I saw that there was a Nagios plugin, but I'm not familiar enough with nagios and didn't see any documentation on getting the plugin to work. Russ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFMG7UVGUZBYlCheYcRAvWNAJ44a5+wtqel2nPW+WsuqHuWOtfYjQCeM7ML 5CzaFN8z7tq0YsnTfpQva2o= =4cH6 -END PGP SIGNATURE- ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Enabling console redirection with omconfig fails
Any idea why the following command would work but the next command would fail? [r...@server ~]# omconfig chassis biossetup attribute=serialcom setting=on BIOS setup configured successfully. Change will take effect after the next reboot. [r...@server ~]# omconfig chassis biossetup attribute=serialcom setting=onwithconsole Error! BIOS setting failed. I'm running this on a PowerEdge R610 that does have support for this (which I can enable in the BIOS without issue). Any help would be greatly appreciated. -- Jeremy Smith Systems Administrator eSilo, LLC. signature.asc Description: OpenPGP digital signature ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Monitoring
On 18/06/10 19:04, Ruslan Sivak wrote: > What are people using for monitoring? I saw that there was a Nagios > plugin, but I'm not familiar enough with nagios and didn't see any > documentation on getting the plugin to work. Hi Ruslan, I'm using OpenNMS for monitoring. See these pages: http://www.opennms.org/wiki/Dell_OMSA_Agent http://www.opennms.org/wiki/Dell_OpenManage_Storage R. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Buyback Program?
On Fri, June 18, 2010 14:03, Cris Rhea wrote: >> From: "Chase Bolt" >> Subject: Buyback Program? >> >> We are looking at replacing about 50 servers and was wondering if Dell >> has >> a buyback program? Or does anyone know of a company that purchases old >> Dell equipment? >> > > I don't know about Dell itself, but I'd suggest: > > Stallard Technologies (http://www.stikc.com/We-Buy) > > This Old Store (http://thisoldstore.com/Vendors.shtml) > > I've used both of these companies to purchase older Dell equipment. > They're decent to deal with. > I can attest to Stallard also. I'm still running machines bought from them 5 years ago. They're good merchants, so I'd expect they're good to sell to as well. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Monitoring
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have installed server administrator from the repos, configured SNMP and I have at least some alerts going into Dell ITA, but I'm having issues getting ITA to see the server. What are people using for monitoring? I saw that there was a Nagios plugin, but I'm not familiar enough with nagios and didn't see any documentation on getting the plugin to work. Russ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFMG7UVGUZBYlCheYcRAvWNAJ44a5+wtqel2nPW+WsuqHuWOtfYjQCeM7ML 5CzaFN8z7tq0YsnTfpQva2o= =4cH6 -END PGP SIGNATURE- ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Buyback Program?
> From: "Chase Bolt" > Subject: Buyback Program? > > We are looking at replacing about 50 servers and was wondering if Dell has > a buyback program? Or does anyone know of a company that purchases old > Dell equipment? > I don't know about Dell itself, but I'd suggest: Stallard Technologies (http://www.stikc.com/We-Buy) This Old Store (http://thisoldstore.com/Vendors.shtml) I've used both of these companies to purchase older Dell equipment. They're decent to deal with. -- Cris -- Cristopher J. Rhea Mayo Clinic - Research Computing Facility 200 First St SW, Rochester, MN 55905 cr...@mayo.edu (507) 284-0587 ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: rpm cannot verify fwupdate packages' PGP signatures
On 2010-06-18 at 13:00-04 James Ralston wrote: > warning: rpmts_HdrFromFdno: V3 DSA signature: NOKEY, key ID 5e3d7775 > Public key for system_bios_PowerEdge_2850-A06-20.noarch.rpm is not installed > Retrieving GPG key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-libsmbios > GPG key at file:///etc/pki/rpm-gpg/RPM-GPG-KEY-libsmbios (0x5E3D7775) is > already installed > > The GPG keys listed for the "Firmware updates" repository are already > installed but they are not correct for this package. > Check that the correct key URLs are configured for this repository. An additional piece of information that might help: we rsync the fwupdate repository locally on a nightly basis, and we verify the PGP signatures after we do so. I went back and checked our logs, and found: As of 2010-05-25 at 04:00-04, we had no difficulty verifying the PGP signatures of the RPM packages in the fwupdate repository. As of 2010-05-26 at 04:42-04, PGP signature verification of packages in the fwupdate repository failed. Looking at our local copies of the rpm files, they all have mtime values that fall between: 2010-05-25 12:35:22-04 2010-05-25 12:36:19-04 E.g.: $ ls -lsa system_bios_ven_0x1028_dev_0x02fb-A00-20.noarch.rpm 876 -rw-r--r-- 1 root root 885675 May 25 12:36 system_bios_ven_0x1028_dev_0x02fb-A00-20.noarch.rpm So, I strongly suspect that on 2010-05-25 at 12:35:22-04, something or someone went through and re-signed all of the RPMs in the fwupdate repository. But I think the version of rpm used to do so produced corrupted signatures. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
rpm cannot verify fwupdate packages' PGP signatures
This pretty much says it all: $ yum -y update system_bios_PowerEdge_2850 Setting up Update Process Setting up repositories Reading repository metadata in from local files Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package system_bios_PowerEdge_2850.noarch 50:A06-20 set to be updated --> Running transaction check Dependencies Resolved = Package Arch Version RepositorySize = Updating: system_bios_PowerEdge_2850 noarch 50:A06-20fwupdate 406 k Transaction Summary = Install 0 Package(s) Update 1 Package(s) Remove 0 Package(s) Total download size: 406 k Downloading Packages: warning: rpmts_HdrFromFdno: V3 DSA signature: NOKEY, key ID 5e3d7775 Public key for system_bios_PowerEdge_2850-A06-20.noarch.rpm is not installed Retrieving GPG key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-libsmbios GPG key at file:///etc/pki/rpm-gpg/RPM-GPG-KEY-libsmbios (0x5E3D7775) is already installed The GPG keys listed for the "Firmware updates" repository are already installed but they are not correct for this package. Check that the correct key URLs are configured for this repository. But as the above message indicates, I have the correct key installed: $ rpm -qi gpg-pubkey-5e3d7775 Name: gpg-pubkey Relocations: (not relocatable) Version : 5e3d7775 Vendor: (none) Release : 42d297af Build Date: 2010-06-18T12:36:18 EDT Install Date: 2010-06-18T12:36:18 EDT Build Host: localhost Group : Public Keys Source RPM: (none) Size: 0License: pubkey Signature : (none) Summary : gpg(libsmbios (This key is used to sign all libsmbios tarballs) ) Description : -BEGIN PGP PUBLIC KEY BLOCK- Version: rpm-4.7.2 (NSS-3) mQGiBELSl68RBACDhWn3X8Ls6mvdpgmPaDqSMVH2GjfWp7Zwto21cFCa8uBDvCSv bzta922bBDYny1rJNBWOlniI4VaMLPkvUzznYm2rf/f+fuTC6FTQd4yi7VP8X8vp V7BKlQDMln3CuZcI1ajFMS1pp1551IRkcskZ6sGgWv5BHjyNWxbp481+2wCglK21 +zR5H34O2kShFGLJxBWp8x0D/2rFQk8JIAIyY7ikkBDtPBGfJHGOwych4fVJJnVq Fz9JqHAYZ3P+WO3sMG5nHkhx8IekOGk+TGbdfYwuGBCuFDkY8UY9fyC+NIGBHF3z mKpWpBu5mwATLeZhYbEhnItxZ7yq8w59LHCeZBbwwfG/6KKaxhgCoK1toSi+1lHL ItRQA/43mWKyVW6fZkmDZcOfRRIOjfKCbk8g+3P2msPkBtsZtbA7ANMk7MgPFBur JHcCjUekOfR4TN/xQ0sl85kec8hIW3ygCyvc3bO8IsdOMOJO40MoYfNI9nFuWqg2 rL63TrnyMw4/uzV5bNwAZUopXftD+dPuQ6+8Y/l6b7X6po6V5LRfbGlic21iaW9z IChUaGlzIGtleSBpcyB1c2VkIHRvIHNpZ24gYWxsIGxpYnNtYmlvcyB0YXJiYWxs cykgPGxpYnNtYmlvcy1kZXZlbEBsaXN0cy51cy5kZWxsLmNvbT6IWwQTEQIAGwUC QtKXrwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRDnRDPiXj13dU3RAJ9CgkwbJ/SU DoHZT6RP55iFuszt6wCfYVTyntyO/1NGnKxo33m2WXq+WRm5AQ0EQtKXsBAEAKQL 5zlThVPRuBs6yQ4TYPIx7cY+Fnw/xp0F/ltLgWuldmejeMbgkMrUS9d6JzNVfuSB tZCNZz+rYKOm0wTBgqef/1xe1jJv7ML47eh2gXvSiwTctvfwOMuL6rFisruq/hCQ dFofLK4oovfn5B06Q8b66CDytwRRfzQO7Ohe6EAbAAMFBACd5c0GvGe6o2/iNbs9 fNNXSc0SK7Yrax1thgLRNMZPPis+csmdMcgmygbICaiFUI0lgUtq5hGVnahd9fCs YME0uH5cPRfAPWQgukLKyKu3qjCQJ8CnD2uwIMvPfiwk4qKWt/fNwYaMx+xs6PKb b7pj9euvC+K4aXVmc3h1YtzKnYhGBBgRAgAGBQJC0pewAAoJEOdEM+JePXd1yeoA mgPExN9943OWP1yY5xhBgFKO0FH/AJ0ZLgscaCv+lpvZM7Eh22lWaQa2jA== =cO2g -END PGP PUBLIC KEY BLOCK- Just to rule out any possibility that the key was corrupt somehow in RPM, I removed it and re-added it from: http://linux.dell.com/files/libsmbios/download/RPM-GPG-KEY-libsmbios But the results are the same. The key is a simple 1024-bit DSA key, which all versions of rpm that I know of can handle: $ gpg2 --check-sigs 5E3D7775 pub 1024D/5E3D7775 2005-07-11 uid libsmbios (This key is used to sign all libsmbios tarballs) sig!35E3D7775 2005-07-11 libsmbios (This key is used to sign all libsmbios tarballs) sub 1024g/75C1F13F 2005-07-11 sig! 5E3D7775 2005-07-11 libsmbios (This key is used to sign all libsmbios tarballs) Finally, this above error happens for me on the following distributions: Red Hat Enterprise Linux 4.8 Red Hat Enterprise Linux 5.5 Fedora 12 So, it's a fairly widespread problem: I can't find any system that can actually verify the PGP signatures on these packages. Matt et. al., can you guys verify these packages? If so, what OS and rpm version are you using to sign/verify the packages? ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Buyback Program?
We are looking at replacing about 50 servers and was wondering if Dell has a buyback program? Or does anyone know of a company that purchases old Dell equipment? (Resending this out as I had an issue with the mailing list and wasn't receiving any new posts) ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
