Discuss October 2014

discuss@lists.centos.org

199 participants
220 discussions

CentOS-announce Digest, Vol 116, Issue 14
by centos-announce-request＠centos.org 29 Oct '14

29 Oct '14

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. Release for CentOS-6.6 i386 and x86_64 (Johnny Hughes) 2. CESA-2014:1724 Important CentOS 7 kernel Security Update (Johnny Hughes) 3. CEBA-2014:1719 CentOS 6 tuned BugFix Update (Johnny Hughes) 4. CEEA-2014:1718 CentOS 6 qemu-kvm Enhancement Update (Johnny Hughes) 5. CEBA-2014:1720 CentOS 6 libvirt BugFix Update (Johnny Hughes) 6. CEBA-2014:1730 CentOS 7 scl-utils BugFix Update (Johnny Hughes) 7. CEBA-2014:1729 CentOS 7 setup FASTTRACK BugFix Update (Johnny Hughes) 8. CEBA-2014:1730 CentOS 6 scl-utils BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 28 Oct 2014 10:40:13 -0500 From: Johnny Hughes <johnny(a)centos.org> To: CentOS-Announce <centos-announce(a)centos.org>, Ladislav Bodnar <distro(a)distrowatch.com> Subject: [CentOS-announce] Release for CentOS-6.6 i386 and x86_64 Message-ID: <544FB8DD.6010501(a)centos.org> Content-Type: text/plain; charset="utf-8" We are pleased to announce the immediate availability of CentOS-6.6 and install media for i386 and x86_64 Architectures. Release Notes for 6.6 are available at http://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.6 - we recommend everyone review these release notes. CentOS-6.6 is based on source code released by Red Hat, Inc. for Red Hat Enterprise Linux. All upstream variants have been placed into one combined repository to make it easier for end users. Workstation, server, and minimal installs can all be done from our combined repository. There are many fundamental changes in this release, compared with the past CentOS-6 releases, and we highly recommend everyone study the upstream Release Notes as well as the upstream Technical Notes about the changes and how they might impact your installation. (See the 'Further Reading' section if the CentOS release notes link above). All updates since the upstream 6.6 release are also on the CentOS-6.6 mirrors as zero day updates. When installing CentOS-6.6 (or any other version) from any of our media, you should always run 'yum update' after the install. Users consuming our centos-cr repositories will already be running all the packages that make up CentOS-6.6 as of one week ago and will notice only the centos-release rpm update today. For more information on the CR repository for future updates, see this link: http://wiki.centos.org/AdditionalResources/Repositories/CR Release Announcements for all updated packages are available here: http://lists.centos.org/pipermail/centos-cr-announce/2014-October/thread.ht… +++++++++++++++++++++++ Upgrading From Prior Major CentOS Versions: We recommend everyone perform a fresh reinstall rather than attempt an in place upgrade from other major CentOS versions (CentOS-2.1, CentOS-3.x, CentOS-4.x, CentOS-5.x). +++++++++++++++++++++++ Upgrading from CentOS-6.0 / 6.1 / 6.2 / 6.3 / 6.4 or 6.5 CentOS is designed to automatically upgrade between releases within a major version (in this case, CentOS-6). Unless you have edited your yum default configuration, a 'yum update' should move your machines seamlessly from any previous CentOS-6.x release to CentOS-6.6. +++++++++++++++++++++++ Downloading CentOS-6.6 for new installs: When possible, consider using torrents to obtain our ISOs. Usually it is also the fastest means to download the distro. Torrent files for the DVD's are available at : http://mirror.centos.org/centos/6.6/isos/i386/CentOS-6.6-i386-bin-DVD1to2.t… http://mirror.centos.org/centos/6.6/isos/x86_64/CentOS-6.6-x86_64-bin-DVD1t… You can also use a mirror close to you to get any of our ISOs: http://mirror.centos.org/centos/6.6/isos/ If you need to update a local mirror, you can choose from our mirror network: http://www.centos.org/download/mirrors/ Most mirrors will allow downloads over http, ftp and rsync. Please keep in mind that not all mirrors are currently updated, some may take as long as 24 hours after this announcement to receive all CentOS-6.6 content. We have made efforts to ensure that most install types and roles can be done from DVD-1 itself. Note: Some UEFI machines can not use the 'netinstall' ISOs, but either the DVD or minimal ISOs will work with UEFI. Secure Boot must be disabled to install CentOS-6.6. +++++++++++++++++++++++ sha1sum for the CentOS-6.6 ISOS: i386: d16aa4a8e6f71fb01fcc26d8ae0e3443ed514c8e CentOS-6.6-i386-bin-DVD1.iso be31aa5c635363092b944e5d43c6a77f2398c3a0 CentOS-6.6-i386-bin-DVD2.iso 6760e2e2a807081731763fcfa680d8413cf24cb7 CentOS-6.6-i386-minimal.iso 2fd5d721b174e40331e6733368f9c2a0206fc4aa CentOS-6.6-i386-netinstall.iso x86_64: 08be09fd7276822bd3468af8f96198279ffc41f0 CentOS-6.6-x86_64-bin-DVD1.iso 826b1e03238934577cee0359e8d2200b399728b0 CentOS-6.6-x86_64-bin-DVD2.iso 4ed6c56d365bd3ab12cd88b8a480f4a62e7c66d2 CentOS-6.6-x86_64-minimal.iso 2560335ef975907799251ae9d6a0fa2e4d289704 CentOS-6.6-x86_64-netinstall.iso +++++++++++++++++++++++ Cloud Images: Images for various on-premise and off-premise Cloud environments are currently under development for CentOS-6.6 and will be released in the coming days. Everyone looking to join and help with the CentOS Cloud efforts is encouraged to join the CentOS-Virt list where such issues are discussed ( http://lists.centos.org/mailman/listinfo/centos-virt ). +++++++++++++++++++++++ Getting Help: The best place to start when looking for help with CentOS is at the wiki ( http://wiki.centos.org/GettingHelp ) which lists various options and communities who might be able to help. If you think there is a bug in the system, do report it at http://bugs.centos.org/ - but keep in mind that the bugs system is *not* a support mechanism. If you need supported software with Support Level Agreements, people to call and response times then we recommend Red Hat Enterprise Linux. +++++++++++++++++++++++ Meet-ups and training sessions: The next CentOS Dojo is going to take place in Barcelona, Spain, on October 29th, 2014: http://wiki.centos.org/Events/Dojo/Barcelona2014 We also are having a CentOS Dojo in Seattle, WA on November 11th, 2014: http://wiki.centos.org/Events/Dojo/LISA14 Other CentOS events can be found on the wiki: http://wiki.centos.org/Events If you would like to get involved in helping organize, run, present or sponsor a CentOS Dojo or even just want more details then join the CentOS Promo list: http://lists.centos.org/mailman/listinfo/centos-promo +++++++++++++++++++++++ Contributing and joining the project: We are always looking for people to join and help with various things in the project. If you are keen to help out a good place to start is the wiki page at http://wiki.centos.org/Contribute . If you have questions or a specific area you would like to contribute towards that is not covered on that page, feel free to drop in on #centos-devel at irc.freenode.net for a chat or email the centos-devel list (http://lists.centos.org). +++++++++++++++++++++++ Thanks to everyone who contributed towards making CentOS 6.6, especially the effort put in, as always, by the QA (http://wiki.centos.org/QaGroup) and Build teams. A special shout out to all the donors who have contributed hardware, network connectivity, hosting and resources over the years. The CentOS project now has a fairly well setup resource pool, solely thanks to the donors. Enjoy! - -- Johnny Hughes <johnny at centos.org> The CentOS Project {http://www.centos.org} irc: hughesjr at irc.freenode.net ( #centos, #centos-devel, #centos-social )

1 0

CentOS 6.6: Lost connection to tape library
by Mogens Kjaer 29 Oct '14

29 Oct '14

Hello, After updating to 6.6 I've lost my connection to my tape library. Old log file (6.5): Sep 13 08:17:51 server1 kernel: scsi 1:2:0:0: Sequential-Access HP Ultrium 5-SCSI Z65W PQ: 0 ANSI: 6 Sep 13 08:17:51 server1 kernel: scsi 1:2:0:1: Medium Changer HP 1x8 G2 AUTOLDR 4.20 PQ: 0 ANSI: 5 New log file (6.6): Oct 28 18:15:06 server1 kernel: scsi1 : hpsa Oct 28 18:15:06 server1 kernel: hpsa 0000:0b:00.0: RAID device c1b3t0l0 added. Oct 28 18:15:06 server1 kernel: hpsa 0000:0b:00.0: Sequential-Access device c1b2t0l0 added. Oct 28 18:15:06 server1 kernel: scsi 1:3:0:0: RAID HP P212 5.14 PQ: 0 ANSI: 5 Oct 28 18:15:06 server1 kernel: scsi 1:2:0:0: Sequential-Access HP Ultrium 5-SCSI Z65W PQ: 0 ANSI: 6 No sign of 1:2:0:1 after reboot, /dev/changer does not exist. Do I have to do something special to have the new hpsa driver look for multiple LUN's? Mogens -- Mogens Kjaer, mk(a)lemo.dk http://www.lemo.dk

3 11

CentOS-6.6 is Released
by Johnny Hughes 29 Oct '14

29 Oct '14

Just letting everyone here know, CentOS-6.6 is now released: http://lists.centos.org/pipermail/centos-announce/2014-October/020709.html

5 4

Update from 6.5 to 6.6 breaks epel qt5
by Devin Reade 29 Oct '14

29 Oct '14

Just a heads up, if anyone is doing QT development with the EPEL RPMs, the update from RHEL 6.5 to 6.6 breaks the current qt5 RPMS. In fact, I had to uninstall qt5 to perform the update. I've submitted a bug report upstream, so hopefully it'll get resolved before too much longer. In the interim, you either get to update, or you get to stop your qt5 development ... <https://bugzilla.redhat.com/show_bug.cgi?id=1157202> Devin

2 1

"No free sectors available" while try to extend logical volumen in a virtual machine running CentOS 6.5
by reynierpm＠gmail.com 28 Oct '14

28 Oct '14

I'm trying to extend a logical volume and I'm doing as follow: 1- Run `fdisk -l` command and this is the output: Disk /dev/sda: 85.9 GB, 85899345920 bytes 255 heads, 63 sectors/track, 10443 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00054fc6 Device Boot Start End Blocks Id System /dev/sda1 * 1 64 512000 83 Linux Partition 1 does not end on cylinder boundary. /dev/sda2 64 10444 83371008 8e Linux LVM Disk /dev/mapper/vg_devserver-lv_swap: 4194 MB, 4194304000 bytes 255 heads, 63 sectors/track, 509 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/mapper/vg_devserver-lv_root: 27.5 GB, 27523022848 bytes 255 heads, 63 sectors/track, 3346 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 2- Run `fdisk /dev/sda`and print partition using `p`: Disk /dev/sda: 85.9 GB, 85899345920 bytes 255 heads, 63 sectors/track, 10443 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00054fc6 Device Boot Start End Blocks Id System /dev/sda1 * 1 64 512000 83 Linux Partition 1 does not end on cylinder boundary. /dev/sda2 64 10444 83371008 8e Linux LVM Try to create the partition by running: Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 3 No free sectors available I also check the free available space using vgdisplay and watching the Free PE / Size part near the end and seems like I've free space available (Free PE / Size 7670 / 29.96 GiB) so I tried to extend the LV by using the command:lvextend -L+29G /dev/vg_devserver/lv_root but I got some errors and don't know where to go from here. The first error I see at console is this /dev/root: read failed after 0 of 4096 at 27522957312: Input/output error /dev/root: read failed after 0 of 4096 at 27523014656: Input/output error Couldn't find device with uuid vSbuSJ-o1Kh-N3ur-JYkM-Ktr4-WEO2-JWe2wS. Cannot change VG vg_devserver while PVs are missing. Consider vgreduce --removemissing. Then following the suggestion from the previous command results I run this other command vgreduce --removemissing vg_devserver but again got this error: WARNING: Partial LV lv_root needs to be repaired or removed. There are still partial LVs in VG vg_devserver. To remove them unconditionally use: vgreduce --removemissing --force. Proceeding to remove empty missing PVs. so I change the command to the one suggested but once again another message Removing partial LV lv_root. Logical volume vg_devserver/lv_root contains a filesystem in use. so at this point I don't know what else to do,can any give me some ideas or help? Don't kill me if is something basic I'm not a Linux Admin or a Linux Advanced User just a developer trying to setup their development environment. How I can get this done? What I'm doing wrong? I'm following [this][1] guide because my filesytem is Ext4. Also [this][2] is helpful too but applies to Ext3 only [1]: http://www.uptimemadeeasy.com/vmware/grow-an-ext4-filesystem-on-a-vmware-es… [2]: http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docType…

7 32

Getting SATA Controller working
by Ashley M. Kirchner 28 Oct '14

28 Oct '14

I have an SIIG SC-SA4011 (V1.0) SATA controller that doesn't appear to come up. The system has CentOS 6.5 installed on it, and everything on it works, except for this one controller - the other SATA controller, a RocketRAID 1640 works fine. lspci lists the offending controller: $> lspci [... snip ...] 04:01.0 Mass storage controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller (rev 02) When I look in dmesg though, I see this: pci 0000:04:01.0: no compatible bridge window for [io 0x4800-0x4807] pci 0000:04:01.0: can't reserve [io 0x4800-0x4807] pci 0000:04:01.0: no compatible bridge window for [io 0x4400-0x4403] pci 0000:04:01.0: can't reserve [io 0x4400-0x4403] pci 0000:04:01.0: no compatible bridge window for [io 0x4000-0x4007] pci 0000:04:01.0: can't reserve [io 0x4000-0x4007] pci 0000:04:01.0: no compatible bridge window for [io 0x3800-0x3803] pci 0000:04:01.0: can't reserve [io 0x3800-0x3803] pci 0000:04:01.0: no compatible bridge window for [io 0x3400-0x340f] pci 0000:04:01.0: can't reserve [io 0x3400-0x340f] and: pci 0000:04:01.0: BAR 4: assigned [io 0xa000-0xa00f] pci 0000:04:01.0: BAR 4: error updating (0x00a001 != 0x002001) pci 0000:04:01.0: BAR 4: set to [io 0xa000-0xa00f] (PCI address [0xa000-0xa00f] pci 0000:04:01.0: BAR 0: assigned [io 0xa010-0xa017] pci 0000:04:01.0: BAR 0: error updating (0x00a011 != 0x002011) pci 0000:04:01.0: BAR 0: set to [io 0xa010-0xa017] (PCI address [0xa010-0xa017] pci 0000:04:01.0: BAR 2: assigned [io 0xa018-0xa01f] pci 0000:04:01.0: BAR 2: error updating (0x00a019 != 0x002019) pci 0000:04:01.0: BAR 2: set to [io 0xa018-0xa01f] (PCI address [0xa018-0xa01f] pci 0000:04:01.0: BAR 1: assigned [io 0xa020-0xa023] pci 0000:04:01.0: BAR 1: error updating (0x00a021 != 0x002021) pci 0000:04:01.0: BAR 1: set to [io 0xa020-0xa023] (PCI address [0xa020-0xa023] pci 0000:04:01.0: BAR 3: assigned [io 0xa024-0xa027] pci 0000:04:01.0: BAR 3: error updating (0x00a025 != 0x002025) pci 0000:04:01.0: BAR 3: set to [io 0xa024-0xa027] (PCI address [0xa024-0xa027] Any suggestions on how I can get this controller up and running or is it too old to work with?

1 0

Is there a kernel available that doesn't have kernel module signing enabled?
by Jamie Risk 28 Oct '14

28 Oct '14

I'm developing a driver on Centos 7: # uname -a && cat /etc/redhat-release Linux czlab04.coveloz.local 3.10.0-123.8.1.el7.x86_64 #1 SMP Mon Sep 22 19:06:58 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux CentOS Linux release 7.0.1406 (Core) When I install my module it's 'tainting' the kernel. Rather than rebuilding the kernel, is there a package that has the kernel available without the module signing enabled? - Jamie

1 0

Booting using another kernel
by Jason T. Slack-Moehrle 28 Oct '14

28 Oct '14

Hi Guys, I am encountering this bug: https://bugs.centos.org/view.php?id=7656 I put in the CentOS 7 DVD and it starts to install and hangs with starting x. The suggestion was made in the bug report to boot using the 'kernel-ml' and to be honest I don't know how to do that. I build a machine that has 4 video cards in it. (2 x nVidia Geforce GT 970 and 2 x Sapphire Toxic R9 270x). Can anyone give me a hand? Jason

2 1

Upgrading to CentOS-7 on a new partition
by Timothy Murphy 28 Oct '14

28 Oct '14

I would like to upgrade a CentOS-6.5 home server to CentOS-7 on a new partition. What is the simplest way to achieve this? I would like to be able to boot into either version of CentOS until I am sure the new version is running OK. Incidentally, I think most people today must have enough space on their hard drive to install a new OS on a new partition - it is surprising that this option never seems to be mentioned in upgrade documentation. -- Timothy Murphy e-mail: gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin 2, Ireland

4 10

tinydns exceeds "holdoff time" on startup under CentOS 7
by Boris Epstein 27 Oct '14

27 Oct '14

Hello listmates, Somehow or other my DNS services that are part of the ndjbdns-1.06-1.el7.x86_64 package would not start properly at startup. When I then start them up using systemctl: systemctl start dnscache systemctl start tinydns they start just fine. >From the log I got the following for tinydns: Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: version 1.06: starting: Oct-24 2014 15:01:43 EDT Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: DEBUG_LEVEL set to `1' Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: DATALIMIT set to `300000' bytes Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: could not bind UDP socket Oct 24 15:01:43 ns99 systemd[1]: tinydns.service holdoff time over, scheduling restart. Any idea why that would happen? Any idea how to increase the holdoff time in the configuration? The config for the service looks as follows: [root@ns99 etc]# more /usr/lib/systemd/system/tinydns.service [Unit] Description=A DNS server daemon Documentation=man:tinydns(8) Requires=network.target After=network.target [Service] Restart=always PIDFile=/var/run/tinydns.pid ExecStart=/usr/sbin/tinydns [Install] WantedBy=multi-user.target [root@ns99 etc]# I can't possibly spot anything wrong there. Any help much appreciated. Cheers, Boris.

2 3

← Newer
1
2
3
4
5
6
7
8
...
22
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss October 2014