Re: Issues with syncing mirror/fetching rpms
On Wed, Dec 01, 2010 at 10:53:01PM +, Jefferson Ogata wrote: > On 2010-12-01 21:00, Matt Domsch wrote: > > On Wed, Dec 01, 2010 at 10:23:45AM -0500, Bryan wrote: > >> Can the person who runs linux.dell.com take a look at this and fix > >>it? This occurs from multiple different networks/clients on this same > >>file. > > > > I can reproduce the failure too, though it's not clear why it's > > failing. apache logs show the connection and report the whole file > > was sent... The file is very much readable on the server itself. > > Gremlins... > > Is it being served from an NFS filesystem? If so, maybe you need to turn > EnableSendfile off... Nope, local disks. -- 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: Issues with syncing mirror/fetching rpms
On 2010-12-01 21:00, Matt Domsch wrote: > On Wed, Dec 01, 2010 at 10:23:45AM -0500, Bryan wrote: >> Can the person who runs linux.dell.com take a look at this and fix >>it? This occurs from multiple different networks/clients on this same >>file. > > I can reproduce the failure too, though it's not clear why it's > failing. apache logs show the connection and report the whole file > was sent... The file is very much readable on the server itself. > Gremlins... Is it being served from an NFS filesystem? If so, maybe you need to turn EnableSendfile off... ___ 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: Issues with syncing mirror/fetching rpms
On Wed, Dec 01, 2010 at 10:23:45AM -0500, Bryan wrote: >Hello, > > Can the person who runs linux.dell.com take a look at this and fix >it? This occurs from multiple different networks/clients on this same >file. I can reproduce the failure too, though it's not clear why it's failing. apache logs show the connection and report the whole file was sent... The file is very much readable on the server itself. Gremlins... -- 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: Local mirror of OMSA repository
Or you could just use the cgi to figure it out like dell does. mirrorlist=http://linux.dell.com/repo/hardware/OMSA_6.2/mirrors.cgi?osname=el$releasever&basearch=$basearch&sys_ven_id=$sys_ven_id&sys_dev_id=$sys_dev_id&dellsysidpluginver=$dellsysidpluginver > -Original Message- > From: linux-poweredge-boun...@dell.com [mailto:linux-poweredge- > boun...@dell.com] On Behalf Of Jim Goddard > Sent: Wednesday, December 01, 2010 12:27 PM > To: Frank Wang > Cc: linux-poweredge@dell.com > Subject: RE: Local mirror of OMSA repository > > Hi Frank, and everyone who chimed in to help me out. > > I was hoping to avoid having model-specific .repo files for our > servers, but I really like the idea of having the local rsync of the > dell tools, so I am going to test a fairly simple addition to our > kickstart that pulls the model info and gets the repo file correct. > > Thanks again for all the help, > > Jim > -Original Message- > From: Frank Wang [mailto:w...@yarbs.cn] > Sent: Tuesday, November 30, 2010 5:36 PM > To: Jim Goddard > Cc: linux-poweredge@dell.com > Subject: Re: Local mirror of OMSA repository > > > Hello, > > > > I am stumped on how to get the local mirror I made of the Dell > > repository to work. > > > > I have the portions of the repository mirrored that correspond to our > > hardware (not the full tree). > > > > Is there some guidance to creating the client's repo file so that my > > machines grab from my mirror, instead of over the internet? > > > > I think I am missing something simple here. > > > > Thanks a lot, > > > Here's the solution working for me, > 1. Mirror dell repo according to your hardware and OS (2950, R410 and > R710 in my case for hardware, and RHEL only for OS) rsync -avHz -- > delete-after --delete-excluded --include pe2950/ --include per410/ -- > include per710 --exclude "/hardware/OMSA_5.*/" --exclude > "/hardware/OMSA_6.0.*/" --exclude "/hardware/OMSA_6.1/" --exclude > /hardware/beta/ --exclude "suse1*/" --exclude "rh40*/" --exclude > "pe[[:digit:]]*/" --exclude "pe[rmt][[:digit:]]*/" > rsync://linux.dell.com/repo/hardware /path/to/local/mirror > The local mirror space is 7.3G here. > > 2. Create yum repo config > [dell-omsa-indep] > name=Dell OMSA repository - Hardware independent type=rpm-md > baseurl=http://localmirror/dell/hardware/latest/platform_independent/rh > 50_64 > gpgcheck=1 > gpgkey=http://localmirror/dell/hardware/latest/RPM-GPG-KEY-dell > http://localmirror/dell/hardware/latest/RPM-GPG-KEY-libsmbios > enabled=1 > failover=priority > bootstrapurl=http://localmirror/dell/hardware/latest/bootstrap.cgi > > [dell-omsa-specific] > name=Dell OMSA repository - Hardware specific type=rpm-md > baseurl=http://localmirror/dell/hardware/latest/per710/rh50_64 > gpgcheck=1 > gpgkey=http://localmirror/dell/hardware/latest/RPM-GPG-KEY-dell > http://localmirror/dell/hardware/latest/RPM-GPG-KEY-libsmbios > enabled=1 > failover=priority > bootstrapurl=http://localmirror/dell/hardware/latest/bootstrap.cgi > > Note, the above is for a R710 server with Centos x86_64 OS, thus > the > /rh50_64 in the baseurl of dell-omsa-indep, and /per710/rh50_64 in the > baseurl of dell-omsa-specific. You should modify yours according to > your server's specification and OS. > > > ___ > 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: Local mirror of OMSA repository
Hi Jim, I currently rsync the latest branch/x86_64. Then I have cobbler manage both my kickstart templates and our internal yum repo. Cobbler is a frontend that manages the repo with commands with createrepo. Good luck with your setup! Cheers, Benjamin Coles Senior Systems Engineer Stanford University - School of Medicine On Dec 1, 2010, at 9:27 AM, "Jim Goddard" wrote: > Hi Frank, and everyone who chimed in to help me out. > > I was hoping to avoid having model-specific .repo files for our servers, but > I really like the idea of having the local rsync of the dell tools, so I am > going to test a fairly simple addition to our kickstart that pulls the model > info and gets the repo file correct. > > Thanks again for all the help, > > Jim > -Original Message- > From: Frank Wang [mailto:w...@yarbs.cn] > Sent: Tuesday, November 30, 2010 5:36 PM > To: Jim Goddard > Cc: linux-poweredge@dell.com > Subject: Re: Local mirror of OMSA repository > >> Hello, >> >> I am stumped on how to get the local mirror I made of the Dell >> repository to work. >> >> I have the portions of the repository mirrored that correspond to our >> hardware (not the full tree). >> >> Is there some guidance to creating the client's repo file so that my >> machines grab from my mirror, instead of over the internet? >> >> I think I am missing something simple here. >> >> Thanks a lot, >> > Here's the solution working for me, > 1. Mirror dell repo according to your hardware and OS (2950, R410 and R710 in > my case for hardware, and RHEL only for OS) rsync -avHz --delete-after > --delete-excluded --include pe2950/ --include per410/ --include per710 > --exclude "/hardware/OMSA_5.*/" --exclude "/hardware/OMSA_6.0.*/" --exclude > "/hardware/OMSA_6.1/" --exclude /hardware/beta/ --exclude "suse1*/" --exclude > "rh40*/" --exclude "pe[[:digit:]]*/" --exclude "pe[rmt][[:digit:]]*/" > rsync://linux.dell.com/repo/hardware /path/to/local/mirror >The local mirror space is 7.3G here. > > 2. Create yum repo config > [dell-omsa-indep] > name=Dell OMSA repository - Hardware independent type=rpm-md > baseurl=http://localmirror/dell/hardware/latest/platform_independent/rh50_64 > gpgcheck=1 > gpgkey=http://localmirror/dell/hardware/latest/RPM-GPG-KEY-dell >http://localmirror/dell/hardware/latest/RPM-GPG-KEY-libsmbios > enabled=1 > failover=priority > bootstrapurl=http://localmirror/dell/hardware/latest/bootstrap.cgi > > [dell-omsa-specific] > name=Dell OMSA repository - Hardware specific type=rpm-md > baseurl=http://localmirror/dell/hardware/latest/per710/rh50_64 > gpgcheck=1 > gpgkey=http://localmirror/dell/hardware/latest/RPM-GPG-KEY-dell >http://localmirror/dell/hardware/latest/RPM-GPG-KEY-libsmbios > enabled=1 > failover=priority > bootstrapurl=http://localmirror/dell/hardware/latest/bootstrap.cgi > >Note, the above is for a R710 server with Centos x86_64 OS, thus the > /rh50_64 in the baseurl of dell-omsa-indep, and /per710/rh50_64 in the > baseurl of dell-omsa-specific. You should modify yours according to your > server's specification and OS. > > > ___ > 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: Local mirror of OMSA repository
Hi Frank, and everyone who chimed in to help me out. I was hoping to avoid having model-specific .repo files for our servers, but I really like the idea of having the local rsync of the dell tools, so I am going to test a fairly simple addition to our kickstart that pulls the model info and gets the repo file correct. Thanks again for all the help, Jim -Original Message- From: Frank Wang [mailto:w...@yarbs.cn] Sent: Tuesday, November 30, 2010 5:36 PM To: Jim Goddard Cc: linux-poweredge@dell.com Subject: Re: Local mirror of OMSA repository > Hello, > > I am stumped on how to get the local mirror I made of the Dell > repository to work. > > I have the portions of the repository mirrored that correspond to our > hardware (not the full tree). > > Is there some guidance to creating the client's repo file so that my > machines grab from my mirror, instead of over the internet? > > I think I am missing something simple here. > > Thanks a lot, > Here's the solution working for me, 1. Mirror dell repo according to your hardware and OS (2950, R410 and R710 in my case for hardware, and RHEL only for OS) rsync -avHz --delete-after --delete-excluded --include pe2950/ --include per410/ --include per710 --exclude "/hardware/OMSA_5.*/" --exclude "/hardware/OMSA_6.0.*/" --exclude "/hardware/OMSA_6.1/" --exclude /hardware/beta/ --exclude "suse1*/" --exclude "rh40*/" --exclude "pe[[:digit:]]*/" --exclude "pe[rmt][[:digit:]]*/" rsync://linux.dell.com/repo/hardware /path/to/local/mirror The local mirror space is 7.3G here. 2. Create yum repo config [dell-omsa-indep] name=Dell OMSA repository - Hardware independent type=rpm-md baseurl=http://localmirror/dell/hardware/latest/platform_independent/rh50_64 gpgcheck=1 gpgkey=http://localmirror/dell/hardware/latest/RPM-GPG-KEY-dell http://localmirror/dell/hardware/latest/RPM-GPG-KEY-libsmbios enabled=1 failover=priority bootstrapurl=http://localmirror/dell/hardware/latest/bootstrap.cgi [dell-omsa-specific] name=Dell OMSA repository - Hardware specific type=rpm-md baseurl=http://localmirror/dell/hardware/latest/per710/rh50_64 gpgcheck=1 gpgkey=http://localmirror/dell/hardware/latest/RPM-GPG-KEY-dell http://localmirror/dell/hardware/latest/RPM-GPG-KEY-libsmbios enabled=1 failover=priority bootstrapurl=http://localmirror/dell/hardware/latest/bootstrap.cgi Note, the above is for a R710 server with Centos x86_64 OS, thus the /rh50_64 in the baseurl of dell-omsa-indep, and /per710/rh50_64 in the baseurl of dell-omsa-specific. You should modify yours according to your server's specification and OS. ___ 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: Issues with syncing mirror/fetching rpms
Confirmed here as well: r...@hou [~]# wget -O /dev/null http://linux.dell.com/repo/hardware/latest/platform_independent/rh50_64/firmware-tools/libsmbios-devel-2.2.19-10.1.el5.x86_64.rpm --2010-12-01 09:37:55-- http://linux.dell.com/repo/hardware/latest/platform_independent/rh50_64/firmware-tools/libsmbios-devel-2.2.19-10.1.el5.x86_64.rpm Resolving linux.dell.com... 143.166.82.43 Connecting to linux.dell.com|143.166.82.43|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 408884 (399K) [application/octet-stream] Saving to: `/dev/null' 57% [===>] 234,278 --.-K/s eta 21s [r...@toolbox ~]# wget -O /dev/null http://linux.dell.com/repo/hardware/latest/platform_independent/rh50_64/firmware-tools/libsmbios-devel-2.2.19-10.1.el5.x86_64.rpm --2010-12-01 09:38:35-- http://linux.dell.com/repo/hardware/latest/platform_independent/rh50_64/firmware-tools/libsmbios-devel-2.2.19-10.1.el5.x86_64.rpm Resolving linux.dell.com... 143.166.82.43 Connecting to linux.dell.com|143.166.82.43|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 408884 (399K) [application/octet-stream] Saving to: `/dev/null' 57% [===>] 234,278 --.-K/s eta 7s ___ 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: Issues with syncing mirror/fetching rpms
Hello, Can the person who runs linux.dell.com take a look at this and fix it? This occurs from multiple different networks/clients on this same file. TIA, On 11/30/10 11:50 PM, "Bryan" wrote: > I seem to have an issue where no matter where I try from, the following file > hangs: > > (11:48pm) [se...@renoir] [~] > wget -O /dev/null > http://linux.dell.com/repo/hardware/latest/platform_independent/rh50_64/firmwa > re-tools/libsmbios-devel-2.2.19-10.1.el5.x86_64.rpm > --2010-11-30 23:48:17-- > http://linux.dell.com/repo/hardware/latest/platform_independent/rh50_64/firmwa > re-tools/libsmbios-devel-2.2.19-10.1.el5.x86_64.rpm > Resolving linux.dell.com... 143.166.224.62 > Connecting to linux.dell.com|143.166.224.62|:80... connected. > HTTP request sent, awaiting response... 200 OK > Length: 408884 (399K) [application/octet-stream] > Saving to: `/dev/null' > > 57% > [= > => > ] 234,278 --.-K/s eta 43s > > > Same place each time. > > Any thoughts? > > > > ___ > 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: OMSA bug with new H700 controller firmware
Hi, OM6.4.0 (which will be released very soon) will have the fix for this issue. Thanks, Mohan -Original Message- From: linux-poweredge-bounces-Lists On Behalf Of Trond Hasle Amundsen Sent: Wednesday, December 01, 2010 4:07 PM To: linux-poweredge-Lists Cc: bryan_se...@symantec.com Subject: OMSA bug with new H700 controller firmware Hi, OMSA has issues with the latest firmware for H700 controllers. There seems to be a bug related to parsing the version numbers, which in turn makes OMSA complain about the firmware being too old: # omreport storage controller Controller PERC H700 Integrated (Embedded) Controllers ID: 0 Status: Non-Critical Name : PERC H700 Integrated Slot ID : Embedded State : Degraded Firmware Version : 12.10.0-0025 Minimum Required Firmware Version : 12.3.0-0032 Driver Version: 00.00.04.17-4.31.z-RH1 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 : 30% Check Consistency Rate: 30% Reconstruct Rate : 30% Alarm State : Not Applicable Cluster Mode : Not Applicable SCSI Initiator ID : Not Applicable Cache Memory Size : 512 MB Patrol Read Mode : Auto Patrol Read State : Stopped Patrol Read Rate : 30% Patrol Read Iterations: 2 Abort Check Consistency on Error : Disabled Allow Revertible Hot Spare and Replace Member : Enabled Load Balance : Auto Auto Replace Member on Predictive Failure : Disabled Redundant Path view : Not Applicable Persistent Hot Spare : Disabled Security Capable : Yes Security Key Present : No Spin Down Unconfigured Drives : Disabled Spin Down Hot Spares : Disabled (Output from a brand new R710 running RHEL5.5 and OMSA 6.3.0). I'm hoping that the Dell engineers are already aware of this. Can we expect an update to OMSA 6.3.0 that fixes this, or will we have to wait until 6.4.0 is released? Regards, -- Trond H. Amundsen Center for Information Technology Services, University of Oslo ___ 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: OpenManage on Fedora?
On 01/12/10 06:59, Nathan Rich wrote: > We're using Fedora 10 at the moment You do realise that Fedora 10 is long out of support? I'd seriously recommend using preupgrade to update to Fedora 14 on the fly. Jonathan Jonathan Gazeley Systems Support Specialist ResNet | Wireless & VPN Team Information Services University of Bristol ___ 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
OMSA bug with new H700 controller firmware
Hi, OMSA has issues with the latest firmware for H700 controllers. There seems to be a bug related to parsing the version numbers, which in turn makes OMSA complain about the firmware being too old: # omreport storage controller Controller PERC H700 Integrated (Embedded) Controllers ID: 0 Status: Non-Critical Name : PERC H700 Integrated Slot ID : Embedded State : Degraded Firmware Version : 12.10.0-0025 Minimum Required Firmware Version : 12.3.0-0032 Driver Version: 00.00.04.17-4.31.z-RH1 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 : 30% Check Consistency Rate: 30% Reconstruct Rate : 30% Alarm State : Not Applicable Cluster Mode : Not Applicable SCSI Initiator ID : Not Applicable Cache Memory Size : 512 MB Patrol Read Mode : Auto Patrol Read State : Stopped Patrol Read Rate : 30% Patrol Read Iterations: 2 Abort Check Consistency on Error : Disabled Allow Revertible Hot Spare and Replace Member : Enabled Load Balance : Auto Auto Replace Member on Predictive Failure : Disabled Redundant Path view : Not Applicable Persistent Hot Spare : Disabled Security Capable : Yes Security Key Present : No Spin Down Unconfigured Drives : Disabled Spin Down Hot Spares : Disabled (Output from a brand new R710 running RHEL5.5 and OMSA 6.3.0). I'm hoping that the Dell engineers are already aware of this. Can we expect an update to OMSA 6.3.0 that fixes this, or will we have to wait until 6.4.0 is released? Regards, -- Trond H. Amundsen Center for Information Technology Services, University of Oslo ___ 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
