Discuss July 2012

discuss@lists.centos.org

166 participants
157 discussions

CentOS6.2: installation at specific kernel level
by Cal Sawyer 12 Jul '12

12 Jul '12

Hi, all I have a number of machines that are out of sync with one another by virtue of having done a yum update after a base 6.2 install at different times (all were previous CentOS 5.3) Consequently, systems are a mix of 2.6.32-220.7.1, 2.6.32-220.13.1 or 2.6.32-220.17.1. So 2 questions: - Is it possible to perform a yum update (or another other kind of update), specifying installation of, say, kernel 2.6.32-220.17.1 along with the packages that were relevant at the time when 2.6.32-220.17.1 was current? - Is it possible to capture and save for future installations the current kernel rev and associated packages as exist in the repos today and install as a "frozen-in-time" distribution? thanks! - c sawyer

5 4

CentOS-announce Digest, Vol 89, Issue 4
by centos-announce-request＠centos.org 12 Jul '12

12 Jul '12

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-2012:1068 Important CentOS 6 openjpeg Update (Johnny Hughes) 2. CEBA-2012:1071 CentOS 5 openldap Update (Johnny Hughes) 3. CEBA-2012:1067 CentOS 6 389-ds-base Update (Johnny Hughes) 4. CEBA-2012:1070 CentOS 6 pulseaudio Update (Johnny Hughes) 5. CEBA-2012:1069 CentOS 6 openswan Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 11 Jul 2012 20:43:18 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2012:1068 Important CentOS 6 openjpeg Update To: centos-announce(a)centos.org Message-ID: <20120711204318.GA3633(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2012:1068 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-1068.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: e2b205d8c434f1bf8435acf92067904c24d61cbb5524ed6a2ece33accbcb5237 openjpeg-1.3-8.el6_3.i686.rpm 97a1c11ed9e15e427fa2daf9e100a814b5a4defb00a44b0b3b1933f122e8cdea openjpeg-devel-1.3-8.el6_3.i686.rpm b835b2d36e9926fbe00597c5d0a70a52b9a7db0110107a4b0f8fe8d88eda137b openjpeg-libs-1.3-8.el6_3.i686.rpm x86_64: 3ce0d45db49b0b7a466a62074df9f7e19af15cf545a5ce6cfd14f4f7f394dd0d openjpeg-1.3-8.el6_3.x86_64.rpm 97a1c11ed9e15e427fa2daf9e100a814b5a4defb00a44b0b3b1933f122e8cdea openjpeg-devel-1.3-8.el6_3.i686.rpm 0f668bbc392096771274f5965340e5bc71b97e920fbb67dc7e43d667971ee953 openjpeg-devel-1.3-8.el6_3.x86_64.rpm b835b2d36e9926fbe00597c5d0a70a52b9a7db0110107a4b0f8fe8d88eda137b openjpeg-libs-1.3-8.el6_3.i686.rpm 9cfb3b5dcbaf3fd331642caf37a9b347eb937609ae3c03c24928aaa0299aaa6e openjpeg-libs-1.3-8.el6_3.x86_64.rpm Source: 76654f1ad60a5fb41d975232408ff113ef5eeeb9dcc06921ccbd15f374de928f openjpeg-1.3-8.el6_3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Thu, 12 Jul 2012 11:29:10 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2012:1071 CentOS 5 openldap Update To: centos-announce(a)centos.org Message-ID: <20120712112910.GA13964(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2012:1071 Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-1071.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 73e406d166b3e593553ae90f42282960b53ae035e61343b69d396e7b02fb1ac5 compat-openldap-2.3.43_2.2.29-25.el5_8.1.i386.rpm 9ccecf7c37dde0760b98404afe1c1d91a086ae5599b90ac3fb9c1dafbd35890e openldap-2.3.43-25.el5_8.1.i386.rpm f254de5769ca4abc2d2d9622ba8ffce629265adcfb89b70a71c74edaf716ccd4 openldap-clients-2.3.43-25.el5_8.1.i386.rpm 4d88e1cc5f48fa41c091424967bad0a2a94a122d6287ead09325a83505f7710d openldap-devel-2.3.43-25.el5_8.1.i386.rpm c254764348770c69ebc8cf425d231993316e4bad5ee29336e2d91ea0e070818d openldap-servers-2.3.43-25.el5_8.1.i386.rpm da0082050d566e23a7b1fd1b35a1e2dfb46a33f867cf77b7fb9eef16aaa8f676 openldap-servers-overlays-2.3.43-25.el5_8.1.i386.rpm 22bec7276bd2db9a8620fd81e3468a19cd7497b9f5eb1bc563df8a4043bc6ed5 openldap-servers-sql-2.3.43-25.el5_8.1.i386.rpm x86_64: 73e406d166b3e593553ae90f42282960b53ae035e61343b69d396e7b02fb1ac5 compat-openldap-2.3.43_2.2.29-25.el5_8.1.i386.rpm 0c575d515bd02f04aa4c2c1de8fa9cdc5ce774382b14dd7d6333bca6a2e0575c compat-openldap-2.3.43_2.2.29-25.el5_8.1.x86_64.rpm 9ccecf7c37dde0760b98404afe1c1d91a086ae5599b90ac3fb9c1dafbd35890e openldap-2.3.43-25.el5_8.1.i386.rpm 1c0f012f0801f51d767eb3667ee774621ed828f5e52768af307b80267e5df450 openldap-2.3.43-25.el5_8.1.x86_64.rpm 8b85bee5ff62577205aa4771239611bf2eb85d9f138e2f9bd43ab2d991a50f21 openldap-clients-2.3.43-25.el5_8.1.x86_64.rpm 4d88e1cc5f48fa41c091424967bad0a2a94a122d6287ead09325a83505f7710d openldap-devel-2.3.43-25.el5_8.1.i386.rpm ae3d3a88c49f701743e3aee4c9cffb298861e5aba01e32a25c3a39cb1483e259 openldap-devel-2.3.43-25.el5_8.1.x86_64.rpm 7dc2fa78749322889ee44b1f77dd8cf49dec5d42817d89803d1cf8b59850cb82 openldap-servers-2.3.43-25.el5_8.1.x86_64.rpm 12bdf2376102b3a374d8293b719bc80909961f4fa20b64d48e158ec206ca5061 openldap-servers-overlays-2.3.43-25.el5_8.1.x86_64.rpm 866eb54e5ed58d5f0fe82136d81eee2b522f2fdac422329d26277d4a1f5ab777 openldap-servers-sql-2.3.43-25.el5_8.1.x86_64.rpm Source: 26fa3b8d387c94dc08adb0ccb0d7d9bf51f219730aa20d000085e7e1819cc178 openldap-2.3.43-25.el5_8.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Thu, 12 Jul 2012 12:08:43 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2012:1067 CentOS 6 389-ds-base Update To: centos-announce(a)centos.org Message-ID: <20120712120843.GA16922(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2012:1067 Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-1067.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 33b16aeeb867d99dd0903123ff1a3806199eb6a58a50ea4cc76d6b5b38f8577f 389-ds-base-1.2.10.2-20.el6_3.i686.rpm 0a62bf34bfc78e22b175062475ed237e7417258143e51c6c027fb8887ab68389 389-ds-base-devel-1.2.10.2-20.el6_3.i686.rpm ba3e38f1668371d1a8a937bfb28639bd747c57b0c8cbe80f48e2bd3181d4f21a 389-ds-base-libs-1.2.10.2-20.el6_3.i686.rpm x86_64: 5debe9a04c2768b2dd962d323a67a548cfeefa4c49812ec314d38a2fa67f82d7 389-ds-base-1.2.10.2-20.el6_3.x86_64.rpm 0a62bf34bfc78e22b175062475ed237e7417258143e51c6c027fb8887ab68389 389-ds-base-devel-1.2.10.2-20.el6_3.i686.rpm bfa5bedb25d2f221da9029a712712e1a16ac6fee53842b1ba243684caf77e1e3 389-ds-base-devel-1.2.10.2-20.el6_3.x86_64.rpm ba3e38f1668371d1a8a937bfb28639bd747c57b0c8cbe80f48e2bd3181d4f21a 389-ds-base-libs-1.2.10.2-20.el6_3.i686.rpm b80ce0c4c7d69f8a851a8d585c32c8262fc0abf47763cfcde438c75b325bf214 389-ds-base-libs-1.2.10.2-20.el6_3.x86_64.rpm Source: 187d6595017883bfdb0856a0928684fa1bbe1a1f201b01e56d910aca5f6f247e 389-ds-base-1.2.10.2-20.el6_3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 4 Date: Thu, 12 Jul 2012 12:08:56 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2012:1070 CentOS 6 pulseaudio Update To: centos-announce(a)centos.org Message-ID: <20120712120856.GA17057(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2012:1070 Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-1070.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 563c1205e53c4aad7bf835fdc1aa16171632213bbc43f0de628c2b9dfbfacb6b pulseaudio-0.9.21-14.el6_3.i686.rpm a5c3649f95fcecb8cf5e0994cf201f6ce666a84267eb276f1a3670349af070be pulseaudio-esound-compat-0.9.21-14.el6_3.i686.rpm 7ffabbb7c90377f75c89f77a008b2f0adfc3fbaf6aa7383f28cce2a95a79baa3 pulseaudio-gdm-hooks-0.9.21-14.el6_3.i686.rpm 15bdd671557aaa2cc54899af2c299f3d50997c2dc4feac699fde66968c7fb132 pulseaudio-libs-0.9.21-14.el6_3.i686.rpm a07d42bd3eec1e42a5e32994f7d28437b56b47d92253c492a2c76317c2e9854e pulseaudio-libs-devel-0.9.21-14.el6_3.i686.rpm 2469297bbb7be3e94a5aa2d4c1cde22b85061166244b5c753aa5da0c3aa6b714 pulseaudio-libs-glib2-0.9.21-14.el6_3.i686.rpm e556f8cd9b2169f45c89f954fd49c3c32029d76cd9ab4fb91d3f476b7f52e8ec pulseaudio-libs-zeroconf-0.9.21-14.el6_3.i686.rpm 7ae7288a39a66b4819bb44dc7d94ba2d04e565ef2af2c9f1cdde9c9f94cbb367 pulseaudio-module-bluetooth-0.9.21-14.el6_3.i686.rpm a5482bc23a8486d317a0522d0ee03d087ae9ef3ed5729d42ba2af1d8e7b4d47a pulseaudio-module-gconf-0.9.21-14.el6_3.i686.rpm caa582f9c5f4d09f7370716d9da601e11feebefb636a8cc5ef6942f5e2b70f08 pulseaudio-module-x11-0.9.21-14.el6_3.i686.rpm efc5d200acf0f5ed93d67da7cf1a2c2f06dfc42581a82a840feab553c525b4a2 pulseaudio-module-zeroconf-0.9.21-14.el6_3.i686.rpm 519fdec212681891e1838743edf1a49d1f000fe7c57a2fa2cba3c66c37dee73a pulseaudio-utils-0.9.21-14.el6_3.i686.rpm x86_64: ab74a88d7bb619f013844fa40f3b12dec4f48a0f44f58ba05af183d03b013f1d pulseaudio-0.9.21-14.el6_3.x86_64.rpm feacd4b01ff1f24cdaf7302d42c7f0f525a14f0169b94dba82cb2ca8129bfc01 pulseaudio-esound-compat-0.9.21-14.el6_3.x86_64.rpm 6ac2db058953914f607b25f1828b5e924561144f37f58ec4343c980a147f82b2 pulseaudio-gdm-hooks-0.9.21-14.el6_3.x86_64.rpm 15bdd671557aaa2cc54899af2c299f3d50997c2dc4feac699fde66968c7fb132 pulseaudio-libs-0.9.21-14.el6_3.i686.rpm 64e7d98e50d50b8491fdf2119238b271126e838ae79a815fcde468a2923d4a24 pulseaudio-libs-0.9.21-14.el6_3.x86_64.rpm a07d42bd3eec1e42a5e32994f7d28437b56b47d92253c492a2c76317c2e9854e pulseaudio-libs-devel-0.9.21-14.el6_3.i686.rpm c37f4d9964b9cf38a03113e8d7e89fb8634459d8a8bbfca3e4d8d424d876bca7 pulseaudio-libs-devel-0.9.21-14.el6_3.x86_64.rpm 2469297bbb7be3e94a5aa2d4c1cde22b85061166244b5c753aa5da0c3aa6b714 pulseaudio-libs-glib2-0.9.21-14.el6_3.i686.rpm be09b1ad65a51d9fa246319ca03f247e8824b71a3edc8e5c60be6360d5c6fbc1 pulseaudio-libs-glib2-0.9.21-14.el6_3.x86_64.rpm e556f8cd9b2169f45c89f954fd49c3c32029d76cd9ab4fb91d3f476b7f52e8ec pulseaudio-libs-zeroconf-0.9.21-14.el6_3.i686.rpm 21528f3cd369dbae82cc818d96c84a9293e53d6fd016cfdae1e53f5529ddf58f pulseaudio-libs-zeroconf-0.9.21-14.el6_3.x86_64.rpm 29056269d472bd65d8ff1444c7d9db2194e15bf73e8bc2c1a0b8ca6aeed74a6c pulseaudio-module-bluetooth-0.9.21-14.el6_3.x86_64.rpm 952e983d4711dffafbf8ef54d126b9a0bb7a173f8d87f06071a2e55aba1d28cf pulseaudio-module-gconf-0.9.21-14.el6_3.x86_64.rpm dceebc456b74bb6dc184a42bd69452eee99b78417eefc8bedbc69cdc4ec3bab3 pulseaudio-module-x11-0.9.21-14.el6_3.x86_64.rpm 2ca97c9fa0d0533310eee07ca278530f2ffbfaebe20780bc7ef36719590db9db pulseaudio-module-zeroconf-0.9.21-14.el6_3.x86_64.rpm 519fdec212681891e1838743edf1a49d1f000fe7c57a2fa2cba3c66c37dee73a pulseaudio-utils-0.9.21-14.el6_3.i686.rpm 5769794cd11edb7e7e2ae99dbc232ba878b24a235e79f8e8f77931911af4daf5 pulseaudio-utils-0.9.21-14.el6_3.x86_64.rpm Source: 06eff80719e4699b4305f688a4ae948be86ac2e84cdb6ecd3714824b952dc03d pulseaudio-0.9.21-14.el6_3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 5 Date: Thu, 12 Jul 2012 12:09:10 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2012:1069 CentOS 6 openswan Update To: centos-announce(a)centos.org Message-ID: <20120712120910.GA17135(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2012:1069 Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-1069.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 90f5f916437ff1bb0677a15a3f941ab07114e892693943c7095e184be148621b openswan-2.6.32-18.el6_3.i686.rpm f7516fb086d8a4ed6976fb703c6ee2b885dfe62f87d8243a3f6efc7228d21378 openswan-doc-2.6.32-18.el6_3.i686.rpm x86_64: 314425e965f8d63138a266275e399f2d58d22a88e4aa680172800e102ba69e18 openswan-2.6.32-18.el6_3.x86_64.rpm 569285c742103e12f68a8850aad06936d6795070529f2fd9e73b815ed9f2650e openswan-doc-2.6.32-18.el6_3.x86_64.rpm Source: b2c548198b718ec7694fdecf3679087387d3864794f836bb01e4a76d46fe18a4 openswan-2.6.32-18.el6_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 89, Issue 4 **********************************************

1 0

AMD Opteron 1218 wrong CPU metrics in 6.3
by Vlad K. 12 Jul '12

12 Jul '12

Hello all, since upgrade to 6.3 (and kernel 2.6.32-279.x) it looks like only one core of the AMD Dualcore Opteron 1218 is functional. Reverting to previous kernel shows everything working as expected. I've filed a bug report here after failing to figure out if it is just a configuration problem: http://bugs.centos.org/view.php?id=5821 I can't find anything on the net that would explain where the problem is. /proc/cpuinfo shows two cores, but top and /proc/stat show basically one core working: - top shows cpu0 idle constantly at 0%, and sporadic 100%sy or 50%sy 50%us, which can't be right - /proc/stat shows cpu0 idle and iowat at 0 - Munin CPU graph shows 200% available but metrics go only up to 100% - mpstat -P ALL shows proper %idle for both cores, but still core0 gets either 100%sy or 50%sy 50%us sporadically. I've also got this in the logs, possibly due to BIOS, and I don't know if it is related, I've seen it with 6.2 too. Jul 11 20:44:57 app1 kernel: [Firmware Bug]: powernow-k8: No compatible ACPI _PSS objects found. Jul 11 20:44:57 app1 kernel: [Firmware Bug]: powernow-k8: Try again with latest BIOS. Any ideas what the possible cause could be or what can I do to figure this out? It's a rented server so I don't have the ability to toy with the BIOS. Thanks. -- .oO V Oo.

1 0

Problem with RAID on 6.3
by Stephen Harris 12 Jul '12

12 Jul '12

I have 4 ST2000DL003-9VT166 (2Tbyte) disks in a RAID 5 array. Because of the size I built them as a GPT partitioned disk. They were originally built on a CentOS 5.x machine but more recently plugged into a CentOS 6.2 machine where they were detected just fine e.g. % parted /dev/sdj print Model: ATA ST2000DL003-9VT1 (scsi) Disk /dev/sdj: 2000GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 3 2097kB 2000GB 2000GB Linux RAID raid The MBR is empty except for the standard "protection" partition % fdisk -l /dev/sdj WARNING: GPT (GUID Partition Table) detected on '/dev/sdj'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sdj: 2000.4 GB, 2000398934016 bytes 256 heads, 63 sectors/track, 242251 cylinders Units = cylinders of 16128 * 512 = 8257536 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdj1 1 242252 1953514583+ ee GPT % dd if=/dev/sdj count=1 2> /dev/null | hexdump 0000000 0000 0000 0000 0000 0000 0000 0000 0000 * 00001c0 0002 ffee ffff 0001 0000 88af e8e0 0000 00001d0 0000 0000 0000 0000 0000 0000 0000 0000 * 00001f0 0000 0000 0000 0000 0000 0000 0000 aa55 0000200 So far, so normal. This works fine under 2.6.32-220.23.1.el6.x86_64 Personalities : [raid1] [raid10] [raid6] [raid5] [raid4] md127 : active raid5 sdj3[2] sdi2[1] sdk4[3] sdh1[0] 5860537344 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU] However, I just patched to CentOS 6.3 and on reboot this array failed to be built. The 2.6.32-279 kernel complained that /dev/sdj was too similar to /dev/sdj3. But I reboot to -220.23.1 then it works. And, indeed, if I run "mdadm --examine /dev/sdj" then it _does_ look like mdadm thinks the raw device is part of the array! But with a different name... % mdadm --examine /dev/sdj /dev/sdj: Magic : a92b4efc Version : 0.90.00 UUID : 79b0ccbb:8f11154b:7df88b83:4a0b6975 Creation Time : Thu Sep 8 22:14:01 2011 Raid Level : raid5 Used Dev Size : 1953512448 (1863.01 GiB 2000.40 GB) Array Size : 5860537344 (5589.04 GiB 6001.19 GB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 5 Update Time : Tue Jul 10 09:10:38 2012 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Checksum : 8cc92232 - correct Events : 36410 Layout : left-symmetric Chunk Size : 64K Number Major Minor RaidDevice State this 2 8 147 2 active sync /dev/sdj3 0 0 8 113 0 active sync /dev/sdh1 1 1 8 130 1 active sync /dev/sdi2 2 2 8 147 2 active sync /dev/sdj3 3 3 8 164 3 active sync /dev/sdk4 This is the same output as if I'd run it against /dev/sdj3 What's odd is that I also have 4*1Tbyte disks in another raid array but these are partitioned with standard MBR partitions, and these are not reporting this problem. % dd if=/dev/sdd count=1 2> /dev/null | hexdump 0000000 0000 0000 0000 0000 0000 0000 0000 0000 * 00001b0 0000 0000 0000 0000 0000 0000 0000 0100 00001c0 0001 fefd ffff 003f 0000 5982 7470 0000 00001d0 0000 0000 0000 0000 0000 0000 0000 0000 * 00001f0 0000 0000 0000 0000 0000 0000 0000 aa55 0000200 % mdadm --examine /dev/sdd /dev/sdd: MBR Magic : aa55 Partition[0] : 1953520002 sectors at 63 (type fd) So, finally, the question: Is there anything I could do inside the MBR of these GPT disks to stop mdadm from thinking the whole disk is part of the array? Is there anything I can do that'll let the new kernel assemble the array? Thanks! -- rgds Stephen

1 1

FYI, minor change in anaconda behaviour between 6.2 and 6.3
by Stephen Harris 11 Jul '12

11 Jul '12

If you use a kickstart file to build unattended servers (eg virt-install) then new disks or virtual volumes will cause problems unless you have "zerombr true" in the kickstart file eg zerombr yes clearpart --all --initlabel part /boot --fstype=ext4 --asprimary --size=100 part swap --asprimary --size=512 part / --fstype=ext4 --asprimary --grow --size=1 (CentOS 6.2 didn't need zerombr). Also FWIW, lines such as repo --name="CentOS" --baseurl=http://repo/CentOS/DVD/CentOS-6 repo --name="Updates" --baseurl=http://repo/CentOS/updates/centos6/x86_64 now work. In CentOS6.2 this would fail with dependency problems. Whether that's just 'cos the updates repo doesn't have conflicting packages so far and it'll break in the future, but it's working today :-) -- rgds Stephen

1 0

question on initrd.img file from images/pxeboot
by Jerry Geis 11 Jul '12

11 Jul '12

What format is the images/pxeboot/initrd.img file on the DVD ? Its not gzip its not straight cpio What is it? I wish to change it. I'm finding information on changing the gzip version of initrd but not the PXE one. If I do "file initrd.img" it just says data. Thanks, Jerry

5 4

So, just wondering, is OpenJDK7 in CentOS 6.3??
by Fernando Cassia 11 Jul '12

11 Jul '12

http://www.redhat.com/about/news/archive/2012/6/red-hat-enterprise-linux-63… "Developer Tools: In addition to OpenJDK6 support in Red Hat Enterprise Linux 6, the newly introduced OpenJDK7 allows customers running Red Hat Enterprise Linux 6.3 to develop and test with the latest version of open source Java. " Yet in the CentOS 6.3 release notes, the only mention about "OpenJDK" is for OpenJDK 6... http://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.3 "7.4. Packages released as 6.2 updates with older packages on the 6.3 install media apr-1.3.9-5.el6_2 apr-devel-1.3.9-5.el6_2 java-1.6.0-openjdk-src-1.6.0.0-1.48.1.11.3.el6_2 java-1.6.0-openjdk-demo-1.6.0.0-1.48.1.11.3.el6_2 java-1.6.0-openjdk-devel-1.6.0.0-1.48.1.11.3.el6_2 java-1.6.0-openjdk-javadoc-1.6.0.0-1.48.1.11.3.el6_2 java-1.6.0-openjdk-1.6.0.0-1.48.1.11.3.el6_2 " Is this because OpenJDK7 is not included, or because it is included but not worth mentioning in the rel notes?. (No intention to offend anyone, just thinking aloud). I am downloading CentOS 6.3 as I write this, so I'll soon find out... yet I wanted to ask anyhow (because perhaps the addition of OpenJDK7 -if present- could be added to the wiki?). Regards, FC -- During times of Universal Deceit, telling the truth becomes a revolutionary act - George Orwell

3 3

Re: [CentOS] Best way to duplicate a live Centos 5 server?
by Cal Sawyer 11 Jul '12

11 Jul '12

Subject: Re: [CentOS] Best way to duplicate a live Centos 5 server? To: CentOS mailing list <centos(a)centos.org> On Mon, Jun 18, 2012 at 11:21 AM, Cal Sawyer <cal-s(a)blue-bolt.com> wrote: >> > >> > ReaR has suddenly become very interesting to me, probably explaining why >> > it utterly fails to work properly (for me).I'm using 1.13 to pull a >> > USB-based recovery image, but there's an error in the >> > backup/NETFS/default/50_make_backup.sh script that doesn't mount the USB >> > device after the mkrecovery step, so subsequent tar fails on write to >> > the non-existent mountpoint. I fixed that, but on recovery it fails to >> > mount the necessary directories on the restore drive as well, so "rear >> > recover" quickly bombs out. Is anyone having any success actually using >> > ReaR on CentOS 6.x? - csawyer > It intentionally doesn't deal with drives the kernel has marked as > removable. I had trouble with that with the main drives on a SAS > hotswap backplane in an earlier version but I think that is fixed now. > > I'd recommend asking how to override this on the ReaR mail list. > While the code seems usable (and yes, I have succeeded in using it on > Centos 6x.), the documentation either doesn't exist yet or is very out > of date. But, the authors are very responsive and it would be good > to let them know about any bugs or usability problems. The mail list > is still at sourceforge although the code has been moved to github and > there is talk of moving the list elsewhere. > > -- Les Mikesell lesmikesell(a)gmail.com ReaR hasn't posed any insurmountable problems with USB removable media but i can see SATA/SAS needing some massaging in the device detection dep't. Yes, i've gotten myself on the ReaR mailing list now. You're right - documentation is pretty dire. Guess i'm not alone in hating doing it. USB backup is broken due to the order in which path variables get set - sure is lot of fun trawling through the scripts to find out what gets set when. Hope the ReaR maintainers are interested in this and haven't gotten themselves mired in tape archive integration - i would have thought USB backup was the winner in terms of getting broad acceptance as a bare-metal DR solution. However, when it works - wow. Just restored an HP dl360 w/HWRAID to a Presario desktop machine and it lives! No network, but that's small beans compared to the larger win. - csawyer

22 41

KVM upgrade to 6.3
by Chris 11 Jul '12

11 Jul '12

Hello, I upgraded my centos 6.2 machine (KVM virtualization host) to 6.3. Do I need to upgrade my virtual machine config files? Result: /etc/libvirt/qemu/*.xml <type arch='x86_64' machine='rhel6.2.0'>hvm</type> Expected result: <type arch='x86_64' machine='rhel6.3.0'>hvm</type> -- Chris

2 1

[CentOS 6.3] rsyslog 5.8.10-2 - PreserveFQDN directive ignored
by SilverTip257 11 Jul '12

11 Jul '12

Hello, I recently upgraded a server from CentOS 6.2 to 6.3 I found a change in the behavior of rsyslog's configuration file that I found particularly interesting. The "$PreserveFQDN on" directive was not being recognized as the config remained unchanged during the upgrade. This incorrect behavior caused the host to syslog with only the host name and not it's fully qualified domain name. ** Has anyone else experienced this odd behavior? ** I did find a workaround [0] [1], but feel this behavior is a bug. Note the bugreport linked previously was for version 5.4.0 and reported in July 2010. If I make $PreserveFQDN the _first_ directive it syslogs with the FQDN otherwise the directive is ignored. The official 6.2 mirror has rsyslog-4.6.2-12.el6.i686.rpm and 6.3 has rsyslog-5.8.10-2.el6.i686.rpm For the record here's my output from `yum info rsyslog`: Name : rsyslog Arch : i686 Version : 5.8.10 Release : 2.el6 Size : 2.1 M Repo : installed >From repo : base Summary : Enhanced system logging and kernel message trapping daemons URL : http://www.rsyslog.com/ License : (GPLv3+ and ASL 2.0) Description : Rsyslog is an enhanced, multi-threaded syslog daemon. It supports MySQL, : syslog/TCP, RFC 3195, permitted sender lists, filtering on any message part, : and fine grain output format control. It is compatible with stock sysklogd : and can be used as a drop-in replacement. Rsyslog is simple to set up, with : advanced features suitable for enterprise-class, encryption-protected syslog : relay chains. I've not found other reports of this issue with CentOS 6.3 so far and there's no recent mention of this bug [yet] on the Rsyslog Bugzilla [2]. But the following ticket [3] submitted this past April makes me wonder. Config Snippet: <config> #rsyslog v3 config file $PreserveFQDN on # if you experience problems, check # http://www.rsyslog.com/troubleshoot for assistance #### MODULES #### $ModLoad imuxsock.so # provides support for local system logging (e.g. via logger command) $ModLoad imklog.so # provides kernel logging support (previously done by rklogd) #$ModLoad immark.so # provides --MARK-- message capability # Provides UDP syslog reception #$ModLoad imudp.so #$UDPServerRun 514 # Provides TCP syslog reception #$ModLoad imtcp.so #$InputTCPServerRun 514 #### GLOBAL DIRECTIVES #### # Use default timestamp format $ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat # # (BUG!) # FQDN must be the first directive or it is not honored # http://bugzilla.adiscon.com/show_bug.cgi?id=192 #$PreserveFQDN on ... omitted... </config> [0] http://bugzilla.adiscon.com/show_bug.cgi?id=192 [1] http://serverfault.com/questions/274625/how-do-i-get-rsyslogd-to-log-a-serv… [2] http://bugzilla.adiscon.com/buglist.cgi?query_format=advanced&short_desc_ty… [3] http://bugzilla.adiscon.com/show_bug.cgi?id=321 ---~~.~~--- Mike // SilverTip257 //

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss July 2012