Discuss January 2017

discuss@lists.centos.org

125 participants
118 discussions

[EL6] How to follow upstream updates?
by Leon Fauster 27 Jan '17

27 Jan '17

Sorry, if it was answered already elsewhere. Where exactly are the current EL6 builds done? Or rephrased: I would like to look into the state of following security update: mysql-5.1.73-8.el6_8.src.rpm Looking into https://git.centos.org/repositories/ http://cbs.centos.org http://buildlogs.centos.org/ shows mostly EL7 stuff. Just curious, LF

3 5

Re: [CentOS] CentOS 7 install on one RAID 1 [not-so-SOLVED]
by m.roth＠5-cent.us 26 Jan '17

26 Jan '17

Let me see if I can, um, reboot this thread.... I made a RAID 1 of two raw disks, /dev/sda and /dev/sdb, *not* /dev/sdax /dev/sdbx. Then I installed CentOS 7 on the RAID, with /boot, /, and swap being partitions on the RAID. My problem is that grub2-install absolutely and resolutely refuses to install on /dev/sda or /dev/sdb. I've currently got it up in a half-assed rescue mode, and have mount -o bind /dev, /proc/ and /sys under /mnt/sysimage, and chrooted there. That's where I'm trying to do my grub2-install. So: 1. *Is* there space for grub2 to install the bootloader under where the mdadm starts? Or do I have to partition the disks (/dev/sda1 100%, ditto /dev/sdb1, then create the RAID 1 with the partitions, and *then* grub2-install? 2. I *think* that one thing that grub2-install is complaining about is that it can't find /boot/grub2. I've tried doing it with $ grub2-install --boot-directory=/boot /dev/sda and $ grub2-install --boot-directory=/dev/md127p1/ /dev/sda and $ grub2-install --boot-directory=/dev/md127pw/boot /dev/sda and it tells me it cannot find the canonical path for the grub2 directory. Is there some way to specify where it should fund /boot/grub2 that I've missed? mark

3 2

Re: [CentOS] CentOS 7 install on one RAID 1 [not-so-SOLVED]
by Eugene Poole 26 Jan '17

26 Jan '17

First let me say I am not a true expert, but I am experienced. If this machine you purchased was some name brand, you must be speaking about hardware raid, true? If this is true, it normally presents you with what looks like a standard drive (/dev/sda) for every 2 drives configured as raid-1. Also, most name brand servers give you a bootable machine day one. If you are using software raid, you must have configured it yourself. Here is what my custom machine has: 2 - 120 GB SSD 2 - 4 TB spinning drives During my CentOS 7 install is where I performed the software raid-1 configuration. I never do the default partition configuration so here is my setup (used fdisk -l): Disk /dev/sda: 120.0 GB, 120034123776 bytes, 234441648 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x0001d7e8 Device Boot Start End Blocks Id System /dev/sda1 2048 134604799 67301376 fd Linux raid autodetect /dev/sda2 134604800 184752127 25073664 fd Linux raid autodetect /dev/sda3 184752128 233191423 24219648 fd Linux raid autodetect /dev/sda4 233191424 234440703 624640 5 Extended /dev/sda5 * 233195520 234440703 622592 fd Linux raid autodetect Disk /dev/sdb: 120.0 GB, 120034123776 bytes, 234441648 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x000085a6 Device Boot Start End Blocks Id System /dev/sdb1 2048 134604799 67301376 fd Linux raid autodetect /dev/sdb2 134604800 184752127 25073664 fd Linux raid autodetect /dev/sdb3 184752128 233191423 24219648 fd Linux raid autodetect /dev/sdb4 233191424 234440703 624640 5 Extended /dev/sdb5 * 233195520 234440703 622592 fd Linux raid autodetect Disk /dev/sdc: 4000.8 GB, 4000787030016 bytes, 7814037168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk label type: gpt # Start End Size Type Name 1 2048 1699579903 810.4G Linux RAID 2 1699579904 3399157759 810.4G Linux RAID 3 3399157760 3911510015 244.3G Linux RAID 4 3911510016 5611087871 810.4G Linux RAID Disk /dev/sdd: 4000.8 GB, 4000787030016 bytes, 7814037168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk label type: gpt # Start End Size Type Name 1 2048 1699579903 810.4G Linux RAID 2 1699579904 3399157759 810.4G Linux RAID 3 3399157760 3911510015 244.3G Linux RAID 4 3911510016 5611087871 810.4G Linux RAID My df -h display shows me the following: /dev/md126 583M 317M 224M 59% /boot I have basically the definitions using CentOS 6 and CentOS 7 and it's my understanding you must have a /boot device. Also during installation of CentOS 7 when writing the MBR to the MD device (in my case md126) it writes the information to both sda and sdb. With CentOS 6, according to HowToForge there are extra steps required to get the MBR on both sda and sdb. I have not had to replace either of these SSD, but I have had to replace spinning drives on my CentOS 6 machines in the past. Gene On 1/26/2017 7:00 AM, centos-request(a)centos.org wrote: > > No. Brand new machine, pulled it out of the box and racked it. NOTHING on the > internal SSDs. Made an md RAID 0 on the raw disks - /dev/sda /dev/sdb. No > partitions, nothing. However, when I bring it up, fdisk shows an MBR with no > partitions. I can, however, mount /dev/md127p3 as /mnt/sysimage, and all is there. > > Did I need to make a single partition, on each drive, and then make the RAID 1 > out of *those*? I don't think I need to have /boot not on a RAID. > > mark > > > > ------------------------------ > > -- Eugene Poole Woodstock, Georgia

1 0

CentOS 7 install on one RAID 1
by m.roth＠5-cent.us 26 Jan '17

26 Jan '17

Hi, folks, I'm building a new box, and I want three partitions - /boot, /, and swap, on *one* RAID 1, not three separate partitions. Other than <alt-f2> mdadm..., *is* there any way in the graphical installer to do this? All I see is a way to make three separate partitions. Pointers to links happily accepted. mark, back to googling

9 18

samba rpm deps - with yum downgrade = kind of a mayhem
by lejeczek 26 Jan '17

26 Jan '17

hi guys, gals do you see this: ~]$ yum downgrade samba Resolving Dependencies --> Running transaction check ---> Package samba.x86_64 0:4.4.4-9.el7 will be a downgrade --> Processing Dependency: samba-libs = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: samba-common-tools = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: samba-common-libs = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: samba-common = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: samba-client-libs = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: libwbclient = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 ---> Package samba.x86_64 0:4.4.4-12.el7_3 will be erased --> Running transaction check ---> Package libwbclient.i686 0:4.4.4-9.el7 will be installed ---> Package samba.x86_64 0:4.4.4-9.el7 will be a downgrade --> Processing Dependency: samba-common-tools = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: samba-common-libs = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: samba-common = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 ---> Package samba.x86_64 0:4.4.4-12.el7_3 will be erased ---> Package samba-client-libs.i686 0:4.4.4-9.el7 will be installed --> Processing Dependency: samba-common = 4.4.4-9.el7 for package: samba-client-libs-4.4.4-9.el7.i686 --> Processing Dependency: libtevent.so.0(TEVENT_0.9.9) for package: samba-client-libs-4.4.4 ..and process fails. chained are i686 arch? Is it only us(centos) or redhat's bugzilla should be notified. Samba downgrade used to work I remember. bw. L.

2 4

SELinux file permissions
by Tim Smith 25 Jan '17

25 Jan '17

Hi, I'm trying to grant dovecot the ability to manage its socket within the postfix spool directory. I have added the below to file_contexts.local : /var/spool/postfix/private/dovecot-auth system_u:system_r:dovecot_t:s0 However, running "restorecon -v /var/spool/postfix/private/dovecot-auth" gives me the following error : restorecon: lstat(/var/spool/postfix/private/dovecot-auth) failed: No such file or directory I cannot create the socket file in advance, because dovecot manages it, and if you "touch" the file, dovecot complains. Where am I going wrong ? Thanks ! Tim

4 5

I'm making the change to a new OS
by TE Dukes 24 Jan '17

24 Jan '17

Decided to upgrade to 7.x. It's been a good ride 6.x, but you're living in the past. Everything is backed up, just waiting on my new 4TB HD to arrive for a fresh install. See ya'll on the other side!!

3 4

CentOS dojo in Brussels 3rd Feb
by Karanbir Singh 24 Jan '17

24 Jan '17

hi everyone, just a quick reminder that we only have a few more places available at the CentOS Dojo next week Friday : https://wiki.centos.org/Events/Dojo/Brussels2017 If you are in the area, or able to make it into the area, do come by. regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

CentOS-announce Digest, Vol 143, Issue 10
by centos-announce-request＠centos.org 23 Jan '17

23 Jan '17

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://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. Announcing the release for Gluster 3.9 on CentOS Linux 7 x86_64 (Niels de Vos) 2. Announcing the release for Gluster 3.9 on CentOS Linux 6 x86_64 (Niels de Vos) ---------------------------------------------------------------------- Message: 1 Date: Mon, 23 Jan 2017 10:45:53 +0100 From: Niels de Vos <ndevos(a)redhat.com> To: centos-announce(a)centos.org Subject: [CentOS-announce] Announcing the release for Gluster 3.9 on CentOS Linux 7 x86_64 Message-ID: <20170123094553.GA7857(a)ndevos-x240.usersys.redhat.com> Content-Type: text/plain; charset="us-ascii" I am happy to announce the General Availability of Gluster 3.9 for CentOS 7 on x86_64. These packages are following the upstream Gluster Community releases, and will receive monthly bugfix updates. Gluster 3.9 is a Short-Term-Maintenance release, and will only receive updates until the next version (3.10) becomes available. The difference between Long-Term-Maintenance and Short-Term-Maintenance releases is explained on the Gluster release schedule page: https://www.gluster.org/community/release-schedule/ Users of CentOS 7 can now simply install Gluster 3.9 with only these two commands: # yum install centos-release-gluster39 # yum install glusterfs-server The centos-release-gluster39 package is delivered via CentOS Extras repos. This contains all the metadata and dependancy information, needed to install Gluster 3.9. Note that the standard centos-release-gluster (virtual) package is still available and points to the 3.8 version. This is intentional because 3.8 is a Long-Term-Maintenance version and does not require users to update the major versions avery couple of months. Some deployments may need to install the centos-release-gluster package as well as centos-release-gluster39 to fullfill dependencies (most recent versions of oVirt possibly). We have a quickstart guide specifically built around the packages are available, it makes for a good introduction to Gluster and will help get you started in just a few simple steps, this quick start is available at https://wiki.centos.org/SpecialInterestGroup/Storage/gluster-Quickstart More details about the packages that the Gluster project provides in the Storage SIG is available in the documentation: https://wiki.centos.org/SpecialInterestGroup/Storage/Gluster The centos-release-gluster* repositories offer additional packages that enhance the usability of Gluster itself. Utilities and tools that were working with previous versions of Gluster are expected to stay working fine. If there are any proboems, or requests for additional tools and applications to be provided, just send us an email with your suggestions. The current list of packages that is (planned to become) available can be found here: https://wiki.centos.org/SpecialInterestGroup/Storage/Gluster/Ecosystem-pkgs We welcome all feedback, comments and contributions. You can get in touch with the CentOS Storage SIG on the centos-devel mailing list ( https://lists.centos.org ) and with the Gluster developer and user communities at https://www.gluster.org/mailman/listinfo , we are also available on irc at #gluster on irc.freenode.net, and on twitter at @gluster . Cheers, Niels de Vos Storage SIG member & Gluster maintainer

1 0

Re: [CentOS] [CentOS-virt] Increase CPU usage on HV after upgrade (7.2 -> 7.3)
by Subscriber 22 Jan '17

22 Jan '17

Hello Sandro, Friday, January 20, 2017, 6:54:02 PM, you wrote: > On Thu, Jan 19, 2017 at 3:40 PM, Subscriber <ml-lists(a)agoris.net.ua> wrote: > Hello Sandro, > Thursday, January 19, 2017, 12:12:25 PM, you wrote: >> Discussed with KVM guys, here's the answer: >> 1% per VM seems to much on idle VM; if the VM is not idle you are >> getting better performance in exchange. For idle VMs the difference >> should be roughly 0.1% per VM. > I compared the graphics load on the CPU before and after the upgrade. > After the upgrade is clearly increased CPU System time load. In all > of this mode and load VM themselves became approximately the same. > Can you share exact version of kvm, libvirt and qemu-kvm / qemu-kvm-ev you're using? kvm_intel In CentOS 7.2.1511: kernel-3.10.0-327.36.3.el7.x86_64 qemu-kvm-1.5.3-105.el7_2.7.x86_64 libvirt-daemon-kvm-1.2.17-13.el7_2.5.x86_64 After upgrade from 7.2.1511 to 7.3.1611: It was (after upgrading to this version, I noticed described in the first report the situation): kernel-3.10.0-514.2.2.el7.x86_64 qemu-kvm-1.5.3-126.el7.x86_64 libvirt-daemon-kvm-2.0.0-10.el7_3.2.x86_64 Now (as of 2017/01/22): kernel-3.10.0-514.6.1.el7.x86_64 qemu-kvm-1.5.3-126.el7_3.3.x86_64 libvirt-daemon-kvm-2.0.0-10.el7_3.4.x86_64 It takes 1-2 days for monitoring, to determine whether the situation has changed since the last update.

1 0

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss January 2017