Discuss

discuss@lists.centos.org

34753 discussions

[CentOS] http://www.securityweek.com/high-severity-bind-vulnerability-advisory-issued
by Larry Vaden 24 Feb '11

24 Feb '11

US-CERT encourages users and administrators using the affected versions of BIND to upgrade to BIND 9.7.3. Optionally, one can wait on a backport.

15 20

LVM problem after adding new (md) PV
by Tomasz Nowak 24 Feb '11

24 Feb '11

Hello, I have a weird problem after adding new PV do LMV volume group. It seems the error comes out only during boot time. Please read the story. I have couple of 1U machines. They all have two, four or more Fujitsu-Siemens SAS 2,5" disks, which are bounded in Raid1 pairs with Linux mdadm. First pair of disks has always two arrays (md0, md1). Small md0 is used for booting and the rest - md1 is used as PV for volume group (vg0). When I need to enlarge the volume, I just add 2 new disks, create a raid 1 array of their whole space I add it as another mdX to vg0. That has been working fine since yesterday. I received new disks branded by Toshiba (Toshiba bought Fujitsu-Simens hdd business) which were supposed to be added as disk no 3 and 4. As far as I remember I've done everything in the same way as before: - They come out as sdc and sdd, so I - fdisk /dev/sdc, created one primary parition of whole space, type fd - the same with /dev/sdd - mdadm --create /dev/md2 -R -l 1 -n 2 /dev/sdc1 /dev/sdd1 - array has been created and syncronized - pvcreate /dev/md2 - vgextend vg0 /dev/md2 and it looks fine: ---------------------------------------------------------------------- # cat /proc/mdstat Personalities : [raid1] md1 : active raid1 sdb2[1] sda2[0] 140488320 blocks [2/2] [UU] md2 : active raid1 sdd1[1] sdc1[0] 292961216 blocks [2/2] [UU] md0 : active raid1 sdb1[1] sda1[0] 3148608 blocks [2/2] [UU] ---------------------------------------------------------------------- # pvdisplay --- Physical volume --- PV Name /dev/md1 VG Name vg0 PV Size 133.98 GB / not usable 11.62 MB Allocatable yes PE Size (KByte) 32768 Total PE 4287 Free PE 1695 Allocated PE 2592 PV UUID AufZRm-QbFC-xRj1-OxwW-Z2w2-qbkM-qzoEcP --- Physical volume --- PV Name /dev/md2 VG Name vg0 PV Size 279.39 GB / not usable 14.94 MB Allocatable yes PE Size (KByte) 32768 Total PE 8940 Free PE 8940 Allocated PE 0 PV UUID qeDW2q-nq5b-Yh5U-5sKY-7Rkd-1UXh-LAxL8j ---------------------------------------------------------------------- # vgdisplay --- Volume group --- VG Name vg0 System ID Format lvm2 Metadata Areas 2 Metadata Sequence No 1010 VG Access read/write VG Status resizable MAX LV 0 Cur LV 8 Open LV 2 Max PV 0 Cur PV 2 Act PV 2 VG Size 413.34 GB PE Size 32.00 MB Total PE 13227 Alloc PE / Size 2592 / 81.00 GB Free PE / Size 10635 / 332.34 GB VG UUID 5cF1dk-1CMM-qiuf-CyNY-aCmw-8Hx8-4iO12I ---------------------------------------------------------------------- # lvdisplay --- Logical volume --- LV Name /dev/vg0/d0v VG Name vg0 LV UUID q7zmrV-EykH-jPzR-smYJ-eehh-3Gbx-ebu5wK LV Write Access read/write LV Status available # open 1 LV Size 3.00 GB Current LE 96 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0 [...] this part may be skiped as it's very long an irrelevant. There are no errors here. ---------------------------------------------------------------------- And now please take a look what happens during boot: [...] scsi0 : ioc0: LSISAS1078 C2, FwRev=01180400h, Ports=1, MaxQ=276, IRQ=20 mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id 1, phy 0, sas_addr 0x500000e01f975022 Vendor: FUJITSU Model: MBB2147RC Rev: 0105 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sda: 287277984 512-byte hdwr sectors (147086 MB) sda: Write Protect is off SCSI device sda: drive cache: write back SCSI device sda: 287277984 512-byte hdwr sectors (147086 MB) sda: Write Protect is off SCSI device sda: drive cache: write back sda: sda1 sda2 sd 0:0:0:0: Attached scsi disk sda mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id 2, phy 1, sas_addr 0x500000e01f602f42 Vendor: FUJITSU Model: MBB2147RC Rev: 0105 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sdb: 287277984 512-byte hdwr sectors (147086 MB) sdb: Write Protect is off SCSI device sdb: drive cache: write back SCSI device sdb: 287277984 512-byte hdwr sectors (147086 MB) sdb: Write Protect is off SCSI device sdb: drive cache: write back sdb: sdb1 sdb2 sd 0:0:1:0: Attached scsi disk sdb mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id 3, phy 2, sas_addr 0x50000392b8028856 Vendor: TOSHIBA Model: MBF2300RC Rev: 0107 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sdc: 585937500 512-byte hdwr sectors (300000 MB) sdc: Write Protect is off SCSI device sdc: drive cache: write back SCSI device sdc: 585937500 512-byte hdwr sectors (300000 MB) sdc: Write Protect is off SCSI device sdc: drive cache: write back sdc: sdc1 sd 0:0:2:0: Attached scsi disk sdc mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id 4, phy 3, sas_addr 0x50000392b80236da Vendor: TOSHIBA Model: MBF2300RC Rev: 0107 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sdd: 585937500 512-byte hdwr sectors (300000 MB) sdd: Write Protect is off SCSI device sdd: drive cache: write back SCSI device sdd: 585937500 512-byte hdwr sectors (300000 MB) sdd: Write Protect is off SCSI device sdd: drive cache: write back sdd: sdd1 sd 0:0:3:0: Attached scsi disk sdd Loading shpchp.ko module shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Loading libata.ko module Loading ata_piix.ko module GSI 23 sharing vector 0x41 and IRQ 23 ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 18 (level, low) -> IRQ 23 ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ] scsi1 : ata_piix scsi2 : ata_piix ata1: SATA max UDMA/133 cmd 0x3138 ctl 0x314c bmdma 0x3110 irq 23 ata2: SATA max UDMA/133 cmd 0x3130 ctl 0x3148 bmdma 0x3118 irq 23 ata1: SATA link down (SStatus 0 SControl 300) ata2: SATA link down (SStatus 0 SControl 300) GSI 24 sharing vector 0x49 and IRQ 24 ACPI: PCI Interrupt 0000:00:1f.5[D] -> GSI 21 (level, low) -> IRQ 24 ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ] scsi3 : ata_piix scsi4 : ata_piix ata3: SATA max UDMA/133 cmd 0x3128 ctl 0x3144 bmdma 0x30f0 irq 24 ata4: SATA max UDMA/133 cmd 0x3120 ctl 0x3140 bmdma 0x30f8 irq 24 ata3: SATA link down (SStatus 4 SControl 300) ata4: SATA link down (SStatus 0 SControl 300) Loading usb-storage.ko module Initializing USB Mass Storage driver... scsi5 : SCSI emulation for USB Mass Storage devices usbcore: registered new driver usb-storage Waiting for driver initialization. USB Mass Storage support registered. Vendor: TEAC Model: DV-28S-V Rev: 1.0B Type: CD-ROM ANSI SCSI revision: 00 Loading dm-mod.ko module device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: dm-devel(a)redhat.com Loading dm-log.ko module Loading dm-mirror.ko module Loading dm-zero.ko module Loading dm-snapshot.ko module Loading dm-mem-cache.ko module Loading dm-region_hash.ko module Loading dm-message.ko module Loading dm-raid45.ko module device-mapper: dm-raid45: initialized v0.2594l Waiting for driver initialization. Scanning and configuring dmraid supported devices md: Autodetecting RAID arrays. md: autorun ... md: considering sdd1 ... md: adding sdd1 ... md: adding sdc1 ... md: sdb2 has different UUID to sdd1 md: sdb1 has different UUID to sdd1 md: sda2 has different UUID to sdd1 md: sda1 has different UUID to sdd1 md: created md2 md: bind<sdc1> md: bind<sdd1> md: running: <sdd1><sdc1> raid1: raid set md2 active with 2 out of 2 mirrors md: considering sdb2 ... md: adding sdb2 ... md: sdb1 has different UUID to sdb2 md: adding sda2 ... md: sda1 has different UUID to sdb2 md: created md1 md: bind<sda2> md: bind<sdb2> md: running: <sdb2><sda2> raid1: raid set md1 active with 2 out of 2 mirrors md: considering sdb1 ... md: adding sdb1 ... md: adding sda1 ... md: created md0 md: bind<sda1> md: bind<sdb1> md: running: <sdb1><sda1> raid1: raid set md0 active with 2 out of 2 mirrors md: ... autorun DONE. md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. ------------------------ and come the problem ----------------------- Scanning logical volumes Reading all physical volumes. This may take a while... Couldn't find device with uuid qeDW2q-nq5b-Yh5U-5sKY-7Rkd-1UXh-LAxL8j. Found volume group "vg0" using metadata type lvm2 Activating logical volumes Couldn't find device with uuid qeDW2q-nq5b-Yh5U-5sKY-7Rkd-1UXh-LAxL8j. 8 logical volume(s) in volume group "vg0" now active Creating root device. Mounting root filesystem. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Setting up other filesystems. Setting up new root fs no fstab.sys, mounting internal defaults Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys SELinux: Disabled at runtime. type=1404 audit(1298476404.427:2): selinux=0 auid=4294967295 ses=4294967295 INIT: version 2.86 booting Welcome to CentOS release 5.5 (Final) Press 'I' to enter interactive startup. Setting clock (utc): Wed Feb 23 16:53:25 CET 2011 [ OK ] Starting udev: [ OK ] Loading default keymap (us): [ OK ] Setting hostname xen13.local: [ OK ] Setting up Logical Volume Management: 8 logical volume(s) in volume group "vg0" now active [...] I have no idea were the problem is. I could paste vgck result here but its long, is it nessesary? I have yet another machine with the same setup and the same new Toshiba disks and it shows even some more errors: Scanning logical volumes Reading all physical volumes. This may take a while... Couldn't find device with uuid fNeN0H-zeD1-ems8-TfqW-2pyC-ZBdR-3ni250. Found volume group "vg0" using metadata type lvm2 Activating logical volumes Couldn't find device with uuid fNeN0H-zeD1-ems8-TfqW-2pyC-ZBdR-3ni250. Refusing activation of partial LV d1dc. Use --partial to override. 6 logical volume(s) in volume group "vg0" now active [...] but then later: [...] Setting up Logical Volume Management: 7 logical volume(s) in volume group "vg0" now active and after boot all 7 logical volumes work fine. Where could be the problem with these errors? -- Tomasz

2 3

ls returns file doesn't exist, find finds it??
by neubyr 24 Feb '11

24 Feb '11

Howdy, I am getting some errors with find and ls command - such that find is able to see a file whereas ls says the file doesn't exist. Initially I was trying find and ls together as: # find ./ -type f -mtime +15 | xargs ls Similar behavior is seen even when I execute both commands separately. Any thoughts on what might be wrong here? -- thanks, neubyr

8 8

RECALL: http://www.securityweek.com/high-severity-bind-vulnerability-advisory-issued
by Larry Vaden 24 Feb '11

24 Feb '11

On Wed, Feb 23, 2011 at 11:27 AM, Larry Vaden <vaden(a)texoma.net> wrote: > US-CERT encourages users and administrators using the affected > versions of BIND to upgrade to BIND 9.7.3. > > Optionally, one can wait on a backport. This message is RECALLED even though: 1) US-CERT used the word "affected." 2) the "optionally" was directed to those who might have used RHEL/CentOS' excellent facility to draw in code from other repos.

9 8

redirecting traffic using iptables
by Jobst Schmalenbach 24 Feb '11

24 Feb '11

Hi. I have two internet connections, the ADSL2+ is very very cheap (but fast 10mb) and I want to use the SHDSL (2mb) only for mail,ssh,http OUT and the ADSL2+ only for surfing. I all works fine if people specify the proxy in the browser, but in case like flash it of no use. Further if I can make the 80/443 traffic go through the proxy only, its an added bonus. If this can be done, fine. Bue I want all 80/443 traffic go through host2. SHDSL ADSL2+ ------ ------- host 1 host2 SQUID ------ ------- | | ------------ host3 ------------ | eth1 On host 3 I have been trying to do this with IPtables, but I am stuck, I tried to utilise squid too, does not work tried: iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 80 -j DNAT --to $PROXY:3128 iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 443 -j DNAT --to $PROXY:3128 browser tell me "invalid request". All I want is to redirect all traffic through host2 if ports 443 and 80 are encountered, thats all. If it goes through the proxy it is an added bonus, but not required. ANy ideas, anyone? Jobst -- 'Two things are infinite: the universe and human stupidity, and I'm not sure about the first one. - Albert Einstein | |0| | Jobst Schmalenbach, jobst(a)barrett.com.au, General Manager | | |0| Barrett Consulting Group P/L & The Meditation Room P/L |0|0|0| +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia

3 3

Unicode in C++
by Michael D. Berger 24 Feb '11

24 Feb '11

On my CentOS box, in C++ programs, is there a way to print Unicode characters? Thanks, Mike.

7 10

Air Conditioning - ON!
by John Hinton 23 Feb '11

23 Feb '11

All, (and please do not turn this into the next long thread) We have a small team which volunteers their time to create the CentOS releases. They are pounded right now with getting that done... it is as simple as that. Each of us 'chose' to use CentOS and with that choice comes nothing more. Why are we complaining? To me, it is all very self-centered. Basically we're all complaining because we 'want' something. And yes, I'm on edge wanting something as well... but that is life with RedHat in general. Some of the suggestions made: 1. Send money. OK, so using a very loose or reapplied definition of a word... we want to 'prostitute' the CentOS team. In other words, if we send money we have the 'right' to gripe and press for rapid releases? Demand services? 2. Add more staff. As a small business owner, the very last thing you want to do is add more staff when you are in a slammed state. It takes all of the 'productive' workers time to train the new staff and output slows to a crawl. 3. Make any other number of 'helpful' suggestions. Well, I think by now the CentOS team knows better than us how this needs to be done based on infrastructure and team members. And even if they aren't doing it right, we don't get to make demands that it be done differently as this is how they have decided to do it. Remember, you chose CentOS based on how they operate. You can go away if you like. 4. Bringing up other distros that are ahead of CentOS. This just an attempt at indirect pressure on the CentOS team to get a competition going. Only the team gets to choose their competition. CentOS 'rates' how it rates and that is up to the CentOS team and their decisions. Some cheerleading might be welcomed, as long as it doesn't become an "I cheer for you therefore you owe me". 5. MOST IMPORTANT---- discussing this right now is the wrong time. The CentOS team needs to be focused on the builds. They need to 'feel good'. They do not need these distractions, complaints, suggestions, pressures and generally negative comments at this moment in time. If it really bothers you, save it for later and bring it up when things are back to normal loads. Perhaps some good will come out of it, but not now. I know that most mean well, but look inside of yourself and the rush is about something you want... and YOU chose a FREE distro, which just so happens to convert to the paid version very easily. 6,7,8,9 and 10 (fill in your own but keep them to yourself) If I were a member of the CentOS team right now, I'd likely be looking at the door. I positively would be needing to step back and take some time to myself to try to cool off and feel positive about what I'm doing. To me and from what I have heard from the CentOS team, very little of what is being said on the list is helping but instead is counterproductive at the moment. Obviously the team is 'reading' the list and 'obviously' some of us have pushed them further at a very high stress time, than they have ever been pushed before. You may also note that upstream was also 'very late' with these new releases. Could it be we are discovering why? (please don't try to answer that) Please please please... ease up, give them the time they need. Make notes for future conversations, but quit distracting them and making them feel bad. Or, write your scathing reply to a thread... get really down angry and in the dirt... then when you're done, just delete it. CentOS team, I do have just one suggestion (and I have no rights to ask this). It seems that the list goes quiet and waits for a while and then explodes a few days/weeks/months later with this banter. If you would consider a public release to this list, perhaps once per week during major releases with just some tidbit of how things are going, perhaps these threads wouldn't explode. With that would be the need for it to be an announcement or something that does not allow it to become a drawn out thread with hoards of perceived 'helpful' suggestions. I can't blame you for not doing this prior, as I'm sure it will fuel fires such as the one raging at the moment. Is there a way this could be done with a 'no-reply' setting or something? With Much Appreciation, John Hinton

18 24

OT: please moderade or remove Larry Vaden
by Rudi Ahlers 23 Feb '11

23 Feb '11

Can an admin please moderate ALL posts from Larry Vaden, or remove him from the list? -- Kind Regards Rudi Ahlers SoftDux Website: http://www.SoftDux.com Technical Blog: http://Blog.SoftDux.com Office: 087 805 9573 Cell: 082 554 7532

1 0

openldap problems authenticating
by Tim Dunphy 23 Feb '11

23 Feb '11

Hello list, I am running an openldap 2.4 server under FreeBSD that was working well until the config was tweaked by someone on the team without properly documenting their work # /usr/local/etc/ldap.con on ldap server (FreeBSD 8.1) host LBSD.summitnjhome.com base dc=summitnjhome,dc=com sudoers_base ou=sudoers,ou=Services,dc=summitnjhome,dc=com binddn cn=pam_ldap,ou=Services,dc=summitnjhome,dc=com bindpw {SSHA}secret scope sub pam_password exop nss_base_passwd ou=staff,dc=summitnjhome,dc=com nss_base_shadow ou=staff,dc=summitnjhome,dc=com # grep for ldap account shows ldap account on the ldap server itself succeeds [root@LBSD2:/usr/local/etc/openldap] #getent passwd | grep walbs walbs:secret/:1002:1003:Walkiria Soares:/home/walbs:/usr/local/bin/bash [root@LBSD2:/usr/local/etc/openldap] #grep walbs /etc/passwd [root@LBSD2:/usr/local/etc/openldap] # # /etc/ldap.conf on ldap client (centos 5.5) host LBSD2.summitnjhome.com base dc=summitnjhome,dc=com sudoers_base ou=sudoers,ou=Services,dc=summitnjhome,dc=com binddn cn=pam_ldap,ou=Services,dc=summitnjhome,dc=com bindpw {crypt}secret scope sub pam_password exop nss_base_passwd ou=staff,dc=summitnjhome,dc=com nss_base_shadow ou=staff,dc=summitnjhome,dc=com # grep getent passwd for ldap account on the client nothing turns up after a long pause [root@LCENT01:~] #getent passwd | grep walbs [root@LCENT01:~] # # nsswitch on the client passwd: files ldap shadow: files ldap group: files ldap sudoers: ldap #hosts: db files nisplus nis dns hosts: files dns # this is what's going on in the logs on the ldap server during th getent from the #client Feb 22 21:31:18 LBSD2 slapd[51158]: conn=3411 op=0 RESULT tag=97 err=49 text= Feb 22 21:31:18 LBSD2 slapd[51158]: conn=3411 op=1 UNBIND Feb 22 21:31:18 LBSD2 slapd[51158]: conn=3411 fd=22 closed Feb 22 21:31:26 LBSD2 slapd[51158]: conn=3412 fd=22 ACCEPT from IP=192.168.1.42:53811 (IP=192.168.1.44:389) Feb 22 21:31:26 LBSD2 slapd[51158]: conn=3412 op=0 BIND dn="cn=pam_ldap,ou=Services,dc=summitnjhome,dc=com" method=128 Feb 22 21:31:26 LBSD2 slapd[51158]: conn=3412 op=0 RESULT tag=97 err=49 text= Feb 22 21:31:26 LBSD2 slapd[51158]: conn=3412 op=1 UNBIND Feb 22 21:31:26 LBSD2 slapd[51158]: conn=3412 fd=22 closed #ldap search from the client as the pam services account is able to locate the ldap user info [root@LCENT02:~] #ldapsearch -xH 'ldap://LBSD2.summitnjhome.com' -D 'cn=pam_ldap ,ou=Services,dc=summitnjhome,dc=com' -w 'secret' -b 'dc=summitnjhome,dc=com' '(uid=walbs)' # extended LDIF # # LDAPv3 # base <dc=summitnjhome,dc=com> with scope subtree # filter: (uid=walbs) # requesting: ALL # # walbs, People, summitnjhome.com dn: uid=walbs,ou=People,dc=summitnjhome,dc=com uid: walbs cn: Walkiria Soares givenName: Walkiria sn: Soares mail: walbs(a)example.com objectClass: inetLocalMailRecipient objectClass: person objectClass: organizationalPerson objectClass: inetOrgPerson objectClass: posixAccount objectClass: top uidNumber: 1002 gidNumber: 1003 # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 #pam_ldap services account in the ldap directory 3 cn=pam_ldap,ou=Services,dc=summitnjhome,dc=com cn: pam_ldap objectClass: top objectClass: inetOrgPerson sn: PAM userPassword: {SSHA}secret I have also tried doing anonymous binds on the client as well as using plain text passwords. I get the same tag=97 err=49 messages on the client either way. Some advice is sorely needed here. Thank you very kindly in advance! -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

2 1

massive mirror errors
by John R Pierce 23 Feb '11

23 Feb '11

I'm trying to ... yum groupinstall "Development Tools" on a reasonably current 5.5 system and getting massive mirror failures... is there a problem, or is this my employer's network messing up? (45/74): rpm-build-4.4.2.3-20.el5_5.1.i386.rpm | 302 kB 00:03 http://mirror.singleedge.com/pub/centos/5.5/addons/i386/CentOS/imake-1.0.2-…: [Errno 14] HTTP Error 404: Not Found Trying other mirror. http://mirror.nwresd.org/pub/centos/5.5/addons/i386/CentOS/imake-1.0.2-3.i3…: [Errno 14] HTTP Error 404: Not Found Trying other mirror. http://hpc.arc.georgetown.edu/mirror/centos/5.5/addons/i386/CentOS/imake-1.…: [Errno 14] HTTP Error 404: Not Found Trying other mirror. http://mirror.its.uidaho.edu/pub/centos/5.5/addons/i386/CentOS/imake-1.0.2-…: [Errno 14] HTTP Error 404: Not Found Trying other mirror. http://mirror.flhsi.com/centos/5.5/addons/i386/CentOS/imake-1.0.2-3.i386.rpm: [Errno 14] HTTP Error 404: Not Found Trying other mirror. http://mirror.highspeedweb.net/CentOS/5.5/addons/i386/CentOS/imake-1.0.2-3.…: [Errno 14] HTTP Error 404: Not Found Trying other mirror. http://mirror.atlanticmetro.net/centos/5.5/addons/i386/CentOS/imake-1.0.2-3…: [Errno 14] HTTP Error 404: Not Found Trying other mirror. http://ftp.lug.udel.edu/pub/centos/5.5/addons/i386/CentOS/imake-1.0.2-3.i38…: [Errno 14] HTTP Error 404: Not found Trying other mirror. http://mirror.vcu.edu/pub/gnu%2Blinux/centos/5.5/addons/i386/CentOS/imake-1…: [Errno 12] Timeout: <urlopen error timed out> Trying other mirror. http://mirrors.greenmountainaccess.net/centos/5.5/addons/i386/CentOS/imake-…: [Errno 14] HTTP Error 404: Not Found Trying other mirror. http://mirror.singleedge.com/pub/centos/5.5/addons/i386/CentOS/libXaw-1.0.2…: [Errno 14] HTTP Error 404: Not Found Trying other mirror. http://mirror.nwresd.org/pub/centos/5.5/addons/i386/CentOS/libXaw-1.0.2-8.1…: [Errno 14] HTTP Error 404: Not Found Trying other mirror. http://hpc.arc.georgetown.edu/mirror/centos/5.5/addons/i386/CentOS/libXaw-1…: [Errno 14] HTTP Error 404: Not Found Trying other mirror. http://mirror.its.uidaho.edu/pub/centos/5.5/addons/i386/CentOS/libXaw-1.0.2…: [Errno 14] HTTP Error 404: Not Found Trying other mirror. http://mirror.flhsi.com/centos/5.5/addons/i386/CentOS/libXaw-1.0.2-8.1.i386…: [Errno 14] HTTP Error 404: Not Found Trying other mirror. http://mirror.highspeedweb.net/CentOS/5.5/addons/i386/CentOS/libXaw-1.0.2-8…: [Errno 14] HTTP Error 404: Not Found Trying other mirror. http://mirror.atlanticmetro.net/centos/5.5/addons/i386/CentOS/libXaw-1.0.2-…: [Errno 14] HTTP Error 404: Not Found Trying other mirror. http://ftp.lug.udel.edu/pub/centos/5.5/addons/i386/CentOS/libXaw-1.0.2-8.1.…: [Errno 4] IOError: <urlopen error (111, 'Connection refused')> Trying other mirror.

1 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss