Discuss

discuss@lists.centos.org

34753 discussions

What can I do to UNDERSTAND why I can't reach centos.org (but everyone else can)?
by Rock 02 Mar '13

02 Mar '13

What can I do to UNDERSTAND why, periodically, I can't reach www.centos.org (but everyone else can)? Every few months, http://www.centos.org just drops off for me and for me only. It's not the web site, because I can reach it via a proxy (e.g., TOR browser bundle) and other tests show it to be alive (e.g., http://www.downforeveryoneorjustme.com/centos.org or http://traceroute.monitis.com) But, for me, I just can't reach it by any means. Mike Easter kindly determined "centos.org does not echo ICMP or UDP pings, only TCP, and its associated netblock level3 doesn't echo UDP, but does echo ICMP and TCP." But, for me, this is what a traceroute returned just now on Centos: $ traceroute www.centos.org ... early hops removed ... 16 ae-6-6.ebr2.LosAngeles1.Level3.net (4.69.148.201) 211.850 ms ae-3-3.ebr3.Dallas1.Level3.net (4.69.132.78) 205.221 ms ae-6-6.ebr2.LosAngeles1.Level3.net (4.69.148.201) 207.392 ms 17 ae-3-3.ebr3.Dallas1.Level3.net (4.69.132.78) 128.453 ms ae-73-73.csw2.Dallas1.Level3.net (4.69.151.145) 160.451 ms ae-93-93.csw4.Dallas1.Level3.net (4.69.151.169) 160.437 ms 18 ae-83-83.csw3.Dallas1.Level3.net (4.69.151.157) 165.923 ms ae-1-60.edge3.Dallas1.Level3.net (4.69.145.8) 165.920 ms 178.414 ms 19 LAYERED-TEC.edge3.Dallas1.Level3.net (4.71.170.6) 241.537 ms 244.324 ms ae-3-80.edge3.Dallas1.Level3.net (4.69.145.136) 244.318 ms 20 * LAYERED-TEC.edge3.Dallas1.Level3.net (4.71.170.6) 244.291 ms 244.250 ms 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * Here is a screenshot (modified to remove early hops) using mtr: $ mtr www.centos.org http://www2.picturepush.com/photo/a/12303130/img/12303130.png My related questions are: 1. What can I do (on Centos) to UNDERSTAND this problem? 2. Why does this problem happen every few months to me (and to just me)? 3. How can the net be this arbitrary and still work?

9 28

Re: [CentOS] CentOS 6.4 in the making perhaps?
by Timothy Murphy 02 Mar '13

02 Mar '13

Sorin Srbu wrote: >> > Is CentOS 6.4 brewing yet then? 8-) ... > Hey! We need an exact date!! ;-) > > Nah, just kidding. It will be released when ready, right. I can wait. I have two servers running CentOS-6.3. On one of them I had (inadvertently) enabled the CentOS-CR repository. I noticed that there were a huge number of updates (over 400 packages) from this repository yesterday. I'm wondering if I disabled it now, would that cause confusion with subsequence updates? I'm also wondering if I leave it enabled, is the danger that the system will stop running negligible? (The machine is in another country, so surgery would be difficult!) -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College Dublin

3 4

autofs and LDAP automount maps
by Tim Gustafson 01 Mar '13

01 Mar '13

Hi, We've been using autofs and LDAP automount maps for years now, and it has worked well. We run an environment that has CentOS, RHEL, Solaris and FreeBSD servers and clients. Historically, all our automount maps have looked like this: -vers=3 server:/export/home/& However, we're switching to NFSv4 and therefore we need to remove the -vers=3 flag. For CentOS 6.3, Solaris and FreeBSD clients, this causes them to mount with NFSv4, which is their default. However, the CentOS 5.x boxes are still defaulting to NFSv3 instead. Looking in /etc/sysconfig/autofs, I see a setting for "OPTIONS", but I'm not sure if those are mount options or what. Is there any way to cause CentOS 5.x to default to NFSv4 when using autofs? -- Tim Gustafson tjg(a)ucsc.edu 831-459-5354 Baskin Engineering, Room 313A

1 0

ssh debug
by Markus Falb 01 Mar '13

01 Mar '13

Hi, I try to understand the debug messages from ssh $ ssh -vv whateverhost ... debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received ... debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160(a)openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160(a)openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib(a)openssh.com,zlib debug2: kex_parse_kexinit: none,zlib(a)openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 … why are some log entries duplicated? Is it a bug? And how can I tell if it is telling me capabilities of the client or of the server? -- Kind Regards, Markus

1 0

CentOS-announce Digest, Vol 97, Issue 1
by centos-announce-request＠centos.org 01 Mar '13

01 Mar '13

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2013:0568 Important CentOS 5 dbus-glib Update (Johnny Hughes) 2. CEBA-2013:0575 CentOS 5 libvirt Update (Johnny Hughes) 3. CESA-2013:0581 Moderate CentOS 5 libxml2 Update (Johnny Hughes) 4. CESA-2013:0580 Moderate CentOS 5 cups Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 1 Mar 2013 00:41:40 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2013:0568 Important CentOS 5 dbus-glib Update To: centos-announce(a)centos.org Message-ID: <20130301004140.GA20895(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2013:0568 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-0568.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 0223ca642952e05ebc211d0a4c70d384c940ac27b099bc3d75b54ca68f9c0f90 dbus-glib-0.73-11.el5_9.i386.rpm 62777a9ce986e177104fe0e1a0f0426f301da6507598d498e9ce33fe2393455a dbus-glib-devel-0.73-11.el5_9.i386.rpm x86_64: 0223ca642952e05ebc211d0a4c70d384c940ac27b099bc3d75b54ca68f9c0f90 dbus-glib-0.73-11.el5_9.i386.rpm 04b24df1ce6e666a9270a596a472f35feeaf6b838b8c243d4a84b9ca24de2520 dbus-glib-0.73-11.el5_9.x86_64.rpm 62777a9ce986e177104fe0e1a0f0426f301da6507598d498e9ce33fe2393455a dbus-glib-devel-0.73-11.el5_9.i386.rpm 884d110f0c5379c6ca1fffdfbba09f54d92945dd81e6d212139189c113a20f57 dbus-glib-devel-0.73-11.el5_9.x86_64.rpm Source: 35b7f75cbbb1386b4e632c74925555778b07f0701066f92bc336f5e52f6c6fc9 dbus-glib-0.73-11.el5_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Fri, 1 Mar 2013 00:43:34 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2013:0575 CentOS 5 libvirt Update To: centos-announce(a)centos.org Message-ID: <20130301004334.GA21032(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2013:0575 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0575.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 5d226b37e3a94f164d50aef45b3f6b7b0a64788404270fe021f5c6efc9e37dba libvirt-0.8.2-29.el5_9.1.i386.rpm 0a581b651ae75683f2448834b6bf2121d8ce2387c496bbced6999680a2202f83 libvirt-devel-0.8.2-29.el5_9.1.i386.rpm a8ff6a0b9fef2f20c5901bedaa2cb23d7d2350f607e9d04c8fe40949990f8540 libvirt-python-0.8.2-29.el5_9.1.i386.rpm x86_64: 5d226b37e3a94f164d50aef45b3f6b7b0a64788404270fe021f5c6efc9e37dba libvirt-0.8.2-29.el5_9.1.i386.rpm f0d871e9abda492ba0bfb48ae25a0c0594d73c361a95464a5511c4779c844f0d libvirt-0.8.2-29.el5_9.1.x86_64.rpm 0a581b651ae75683f2448834b6bf2121d8ce2387c496bbced6999680a2202f83 libvirt-devel-0.8.2-29.el5_9.1.i386.rpm 5fea1922e24b927f92abe455120d70bbee8251374af868c7af90c7ccee4e8bf5 libvirt-devel-0.8.2-29.el5_9.1.x86_64.rpm 7456a0536afef03552b2b92293017e8bae17fc60536dcd3bf4a6053e62628ba6 libvirt-python-0.8.2-29.el5_9.1.x86_64.rpm Source: 5ca698b978950796c6098fb3c1d3ce8dd7f4f963663daa068cd744b3a4331a41 libvirt-0.8.2-29.el5_9.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Fri, 1 Mar 2013 00:45:13 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2013:0581 Moderate CentOS 5 libxml2 Update To: centos-announce(a)centos.org Message-ID: <20130301004513.GA21167(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2013:0581 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-0581.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 37744da0abe7d75464da9498d9ad2575c550e875cf068f0d00e30d8c9221b0b5 libxml2-2.6.26-2.1.21.el5_9.1.i386.rpm 4a444273456b1fdba7330b37e6033715b7d471530e14c2d6f0e516fc6897f205 libxml2-devel-2.6.26-2.1.21.el5_9.1.i386.rpm 144b9741b82d70cb82de090609482987d34d6cdac657a9fbb9954f569cbdbaa0 libxml2-python-2.6.26-2.1.21.el5_9.1.i386.rpm x86_64: 37744da0abe7d75464da9498d9ad2575c550e875cf068f0d00e30d8c9221b0b5 libxml2-2.6.26-2.1.21.el5_9.1.i386.rpm a68601aad7a108fc5dce83d8d107a8e4850afcd58e378360a34123b6b639435b libxml2-2.6.26-2.1.21.el5_9.1.x86_64.rpm 4a444273456b1fdba7330b37e6033715b7d471530e14c2d6f0e516fc6897f205 libxml2-devel-2.6.26-2.1.21.el5_9.1.i386.rpm f528e385046af9543854df65f50ab7214e2d62812752e52f3a2e98712ad4c268 libxml2-devel-2.6.26-2.1.21.el5_9.1.x86_64.rpm cbe3c0ecbe4dd9f6696e440617862ee876999b7f4c3d7eab36214aee74008d01 libxml2-python-2.6.26-2.1.21.el5_9.1.x86_64.rpm Source: 30a7bb607148784ac9bf6e76a4ab1914df94d4a2cbf2f5d23c7a4665aeef99c7 libxml2-2.6.26-2.1.21.el5_9.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 4 Date: Fri, 1 Mar 2013 10:00:14 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2013:0580 Moderate CentOS 5 cups Update To: centos-announce(a)centos.org Message-ID: <20130301100014.GA16247(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2013:0580 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-0580.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 01fcf6e5d2d17403e58945ea9e3c6b9169d478850a16862fd73615e44eeae598 cups-1.3.7-30.el5_9.3.i386.rpm 54bf5c1b7a4018e77c45877979a5ced5709e46aa4734773695c8fe59c9525e77 cups-devel-1.3.7-30.el5_9.3.i386.rpm cf700a7effa3ffa53b5ca1ccdecc69a4306efc2dd1abc25865a8cc816ba776b9 cups-libs-1.3.7-30.el5_9.3.i386.rpm 48db4fe49ae0c17df7c8e3a35e4546c1a5e5cdef4fe08f0ab74b963001f73fae cups-lpd-1.3.7-30.el5_9.3.i386.rpm x86_64: eb4594812053434feb5567fcbb03d9b88a8065e03df933933560ce36dea1023f cups-1.3.7-30.el5_9.3.x86_64.rpm 54bf5c1b7a4018e77c45877979a5ced5709e46aa4734773695c8fe59c9525e77 cups-devel-1.3.7-30.el5_9.3.i386.rpm a21686b2db1b3dbf9ea742680b86a30275c6334ee80b53b680d6be34c0cbbc9f cups-devel-1.3.7-30.el5_9.3.x86_64.rpm cf700a7effa3ffa53b5ca1ccdecc69a4306efc2dd1abc25865a8cc816ba776b9 cups-libs-1.3.7-30.el5_9.3.i386.rpm 4de955b40a9d352888834671776e44a7b6e512ed8625bb5fc5c32bc1268c18bd cups-libs-1.3.7-30.el5_9.3.x86_64.rpm 42361f5d747d7d8b879916670a1d4ec1d80ab27450790d08432f41462d376d6d cups-lpd-1.3.7-30.el5_9.3.x86_64.rpm Source: ad817337971593f0df4637ad6852a5b2c4007ec9f916ca6a47618d29adecaa95 cups-1.3.7-30.el5_9.3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 97, Issue 1 **********************************************

1 0

Re: [CentOS] CentOS 6.4 in the making perhaps?
by Johnny Hughes 01 Mar '13

01 Mar '13

On 02/28/2013 02:31 AM, Sorin Srbu wrote: > I see Johnny Hughes has released CR-updates for CentOS 6. > > Is CentOS 6.4 brewing yet then? 8-) Eventually, yes ... thats how it goes, right? We are working on the consolidated tree, spinning isos, QA'ing those, etc. CR is for access now, for those what want it ... the tree should be along soon. Not exactly sure when soon will be yet :)

2 1

Reorg of a RAID/LVM system
by Harold Pritchett 01 Mar '13

01 Mar '13

I have a system with 4 disk drives, two 512 Gb and two 1 Tb. It look like this: CentOS release 5.9 (Final) Disk /dev/sda: 500.1 GB, 500107862016 bytes Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes Disk /dev/sdc: 500.1 GB, 500107862016 bytes Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes ================================================================= Disk /dev/sda: 500.1 GB, 500107862016 bytes 16 heads, 63 sectors/track, 969021 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 1985 1000408+ fd Linux raid autodetect /dev/sda2 1986 9923 4000752 82 Linux swap / Solaris /dev/sda3 9924 969021 483385392 fd Linux raid autodetect Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdb1 * 1 125 1004031 fd Linux raid autodetect /dev/sdb2 126 624 4008217+ 82 Linux swap / Solaris /dev/sdb3 625 121601 971747752+ fd Linux raid autodetect Disk /dev/sdc: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdc1 * 1 125 1004031 fd Linux raid autodetect /dev/sdc2 126 4096 31897057+ 82 Linux swap / Solaris /dev/sdc3 4097 60801 455482912+ fd Linux raid autodetect Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdd1 * 1 125 1004031 fd Linux raid autodetect /dev/sdd2 126 624 4008217+ 82 Linux swap / Solaris /dev/sdd3 625 121601 971747752+ fd Linux raid autodetect The four 1 GB partitions (sd[abcd]1) are configured as a RAID 1 array with a single ext4 filesystem mounted as /boot. Swap is Swap... the two smaller drives (sd[ac]3) partitions are configured as a RAID 1 array containing an LVM physical volume (md1). the two larger drives (sd[bd]3) are configured as a RAID 1 array containing an LVM physical volume (md2). # pvdisplay --- Physical volume --- PV Name /dev/md1 VG Name vg0 PV Size 434.38 GB / not usable 7.44 MB Allocatable yes PE Size (KByte) 32768 Total PE 13900 Free PE 7810 Allocated PE 6090 PV UUID z5QGpO-6bKP-k8xm-vUha-CWYj-dkjG-UaHAE5 --- Physical volume --- PV Name /dev/md2 VG Name vg0 PV Size 926.73 GB / not usable 12.31 MB Allocatable yes (but full) PE Size (KByte) 32768 Total PE 29655 Free PE 0 Allocated PE 29655 PV UUID RIliNF-SENU-O2S9-Qo4H-rtOC-2Yzr-7jzuB0 The two physical volumes are defined as a single volume group. # vgdisplay --- Volume group --- VG Name vg0 System ID Format lvm2 Metadata Areas 2 Metadata Sequence No 17 VG Access read/write VG Status resizable MAX LV 0 Cur LV 10 Open LV 10 Max PV 0 Cur PV 2 Act PV 2 VG Size 1.33 TB PE Size 32.00 MB Total PE 43555 Alloc PE / Size 35745 / 1.09 TB Free PE / Size 7810 / 244.06 GB VG UUID dKKD3L-pcHy-F8KQ-6qNX-vFye-tXdv-6Qs98W One of the 512 Gb drives is failing. What I want to do is to replace the two 512 Gb drives with 3 Tb drives, expand the RAID array on them and then expand the LVM PV contained therein. This much I can do. I then want to move all of the date from the other PV into this one, and remove the second PV, RAID array, and the two 1 Tb drives, leaving me with two 3 Tb drves, a large RAID array and a single PV containing everything (except the /boot and SWAP partitions.) What I'm not sure about is how to move the date from the second PV to the first so I can then delete the contents of the drive and physically remove them from the system leaving me with only the two 3 Tb drives. Help! Thanks Harold

2 1

Newer SANE packages for 5.9 ??
by fred smith 01 Mar '13

01 Mar '13

I just got a Canon Canoscan LiDE 210 scanner, which the SANE project pages say works "completely" with Sane. but what isn't obvious without a lot of digging is that the version of Sane in EL5 isn't new enough. it works fine with what's on my eeepc (Fedora 17) but not Centos 5.9. I've been messing around with building sane from source, but have not been fully successful, yet, so thought before butchering my system any further I should ask if anyone has (or can point me to) newer Sane packages for EL5?? Thanks! Fred -- ------------------------------------------------------------------------------- Under no circumstances will I ever purchase anything offered to me as the result of an unsolicited e-mail message. Nor will I forward chain letters, petitions, mass mailings, or virus warnings to large numbers of others. This is my contribution to the survival of the online community. --Roger Ebert, December, 1996 ----------------------------- The Boulder Pledge -----------------------------

3 6

drbd and el6
by John R Pierce 28 Feb '13

28 Feb '13

hey, I have an application for drbd replication between a pair of EL6 servers, and I just realized that drbd is no longer built in. googling found me this blog on doing it using ElRepo distributions... http://www.broexperts.com/2012/06/how-to-install-drbd-on-centos-6-2/ is that still best practice? or is there a better distribution? or really... my application is a BackupPC server replicating its backup volume to a standby server (hey, no backup is really a backup, unless there is a backup of the backup, right?). is there a better/alternate way of maintaining a mirror of a backupPC volume than drbd... the backup volume is initially 8TB and could well grow to 3 times that over time. its stored on an XFS file system, under LVM, on striped raid6 volumes. -- john r pierce 37N 122W somewhere on the middle of the left coast

10 14

remote logging with rsyslog
by Nelson Green 28 Feb '13

28 Feb '13

This is a similar post to one I've made on the rsyslog list that has received no responses after four days, so I figured I'd try here since the problem seems to be CentOS specific. This is also my second attempt to send it to this list as the first seems to have never showed up. I am trying to test remote logging between two CentOS 6.3 systems and unable to get the client logs to show up on the server, using the RELP module. First of all, the client is a stock install of CentOS 6.3 running rsyslog v5.8.10. I inherited the server, but the change logging that we keep indicates it is pretty much stock too, and it is v5.8.10 as well. On the server, I added to /etc/rsyslog.conf: $ModLoad imrelp $InputRELPServerRun 20514 And restarted the daemon: sudo service rsyslog restart Shutting down system logger: [ OK ] Starting system logger: [ OK ] On the client, I added to /etc/rsyslog.conf: $ModLoad omrelp $WorkDirectory /var/spool/rsyslog $ActionQueueType LinkedList $ActionQueueFileName syslogfwd $ActionQueueMaxDiskSpace 10g $ActionResumeRetryCount -1 $ActionQueueSaveOnShutdown on *.* :omrelp:xxx.xxx.xxx.xxx:20514 And restarted the daemon: sudo service rsyslog restart Shutting down system logger: [ OK ] Starting system logger: [ OK ] Nothing ever showed up on the server, so I started going through the troubleshooting steps, which includes running the client in foreground mode and logging debug output: sudo service rsyslog stop sudo /sbin/rsyslogd -dn > /tmp/rsyslog.debug However, as soon as the service started in the foreground, log entries began showing up on the server. But when I stop the foreground service and restart it as a background service, the log entries quit showing up at the server. I can change things around so that tcp is used instead of RELP, and everything works that way. The problem is specific to using RELP in the normal background mode. I also tested the above RELP configuration on two Debian Wheezy boxes, each running rsyslog v5.8.11, and everything worked as expected. So the problem seems to be specific to CentOS with RELP. Has anyone gotten this to work on CentOS? Thanks, Nelson

2 5

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