Discuss

discuss@lists.centos.org

2 participants
34758 discussions

Update of cloud-init in CentOS 7 Extras
by Pierre Riteau 14 Sep '17

14 Sep '17

Hello, The version of cloud-init packaged in CentOS 7 Extras is rather old (0.7.5, which was released in 2014). It is missing some functionality that we would like to use, as well as important bug fixes. Before I tackle rebuilding the package myself, I would like to know if there is a plan to update extras to a newer cloud-init version, or if has anyone has already updated cloud-init and would be happy to share the spec? Many thanks, Pierre Riteau Chameleon Lead DevOps Engineer

2 4

Apache 2.2 EOL - what is Red Hat's story for RHEL6?
by Alan McKay 13 Sep '17

13 Sep '17

Hi folks, I have been googling for a few weeks now and not finding anything. Apache 2.2 is EOL at the end of this year. Has Red Hat announced a plan yet on what they are doing in RHEL6? I am assuming they will up-version from 6.9 to 6.10 and as part of that upgrade from Apache 2.2 to Apache 2.4 ? thanks, -Alan -- "You should sit in nature for 20 minutes a day. Unless you are busy, then you should sit for an hour" - Zen Proverb

7 9

cyrus spool on btrfs?
by hw 13 Sep '17

13 Sep '17

Hi, is there anything that speaks against putting a cyrus mail spool onto a btrfs subvolume?

12 45

[CentOS] https://ctan.org/tex-archive/graphics/pstricks/contrib/pst-barcode/
by hw 13 Sep '17

13 Sep '17

Hi, https://ctan.org/tex-archive/graphics/pstricks/contrib/pst-barcode/ says that pst-barcode is included in texlive. I installed texlive, and it can´t find pst-barcode.sty. Is that a bug in the packaging Centos does, or is texlive in Centos some derelict version?

3 3

system slowdown
by Larry Martell 13 Sep '17

13 Sep '17

I have a CentOS 6 system that has suddenly starting significantly slowing down. It runs a django app with an Apache server and MySQL server. There is plenty of disk space and no process seems to be hogging the memory or CPU. But operations that used to take 5 minutes are now taking hours and hours. Coinciding with this slow down I see these messages in /var/log/messages (this is hand typed, as I can't copy/paste or send email from this system, although for a change I do have remote access via 2 VPN hops): kernel: BUG: soft lockup - CPU#5 stuck for 67s! [khungtaskd] kernel: BUG: soft lockup - CPU#7 stuck for 67s! [khugepaged] These messages started appearing today around 7 AM, which is when users started reporting the slowdown. They are still occurring periodically and the system is still slow. Are these messages caused by the slowdown or are they the reason for it? Are they useful in tracking down the problem?

2 3

CentOS-announce Digest, Vol 151, Issue 2
by centos-announce-request＠centos.org 13 Sep '17

13 Sep '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. CESA-2017:2681 Important CentOS 6 kernel Security Update (Johnny Hughes) 2. CESA-2017:2685 Moderate CentOS 6 bluez Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 12 Sep 2017 23:15:02 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:2681 Important CentOS 6 kernel Security Update Message-ID: <20170912231502.GA63829(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:2681 Important Upstream details at : https://access.redhat.com/errata/RHSA-2017:2681 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 7a7e756bdd778e6b552e95e51ec2b38f8492b755929fafd37ee80341a05a2fe0 kernel-2.6.32-696.10.2.el6.i686.rpm 6b2e9e78a22faba659b12ea2775604009bb6b41e243179df49ce5c187b4cd76b kernel-abi-whitelists-2.6.32-696.10.2.el6.noarch.rpm a79b93e88aa475510db88b2f0503b752c69ab0797a32b1a3b46e7ab455f52bfa kernel-debug-2.6.32-696.10.2.el6.i686.rpm 3f37d2c6befe9bd7d9d4afc1bb5024e589285e30e5a758ed3755764dfff0f5cd kernel-debug-devel-2.6.32-696.10.2.el6.i686.rpm fea84013ef28f95125c2a6175af0eaac4876e575a0a62e5d5c04f00898780844 kernel-devel-2.6.32-696.10.2.el6.i686.rpm ea414d9514476ed940bb33ad39b3ab9c58b2f7ac4e72fbb667a706ea8349bf56 kernel-doc-2.6.32-696.10.2.el6.noarch.rpm 5566fbb87f5c6f1a3d267487ea6ca417ca6ec60ff610d0421d40d30d5f8a1c98 kernel-firmware-2.6.32-696.10.2.el6.noarch.rpm 5ddf34e914c3a51d4b1887a44fd1e2eb70c7189be716b6c0906c101a303e17ee kernel-headers-2.6.32-696.10.2.el6.i686.rpm 133bd9bbe4b85cba6ce8153f20d83c9456abd755944384d597de556b200bff08 perf-2.6.32-696.10.2.el6.i686.rpm c0f48d37c0adeca7aa7847353288eecadbbafe8e5c4470679bd8425deb521d64 python-perf-2.6.32-696.10.2.el6.i686.rpm x86_64: 5a068ea731cace53bfce2ead23a15536f258424fab34f1213daea933e8966d78 kernel-2.6.32-696.10.2.el6.x86_64.rpm 6b2e9e78a22faba659b12ea2775604009bb6b41e243179df49ce5c187b4cd76b kernel-abi-whitelists-2.6.32-696.10.2.el6.noarch.rpm 6ee990b5ee67f5cefcee70ddeb7feeeccffc6457d18ff3c0f1a82c375535c0b7 kernel-debug-2.6.32-696.10.2.el6.x86_64.rpm 3f37d2c6befe9bd7d9d4afc1bb5024e589285e30e5a758ed3755764dfff0f5cd kernel-debug-devel-2.6.32-696.10.2.el6.i686.rpm 6027e42601a185c0f4bf6c290c971678922b1e31cad4c2aedbef8e1c80f2f922 kernel-debug-devel-2.6.32-696.10.2.el6.x86_64.rpm 709c68c776d8db6d03e08b4fb609e5f9c0b6b293531a8cb59bb1c5c4b2389b7b kernel-devel-2.6.32-696.10.2.el6.x86_64.rpm ea414d9514476ed940bb33ad39b3ab9c58b2f7ac4e72fbb667a706ea8349bf56 kernel-doc-2.6.32-696.10.2.el6.noarch.rpm 5566fbb87f5c6f1a3d267487ea6ca417ca6ec60ff610d0421d40d30d5f8a1c98 kernel-firmware-2.6.32-696.10.2.el6.noarch.rpm e412035e84b763214b8dd9f679ba6c7c4c22e07107c000fdd193b613c492d5af kernel-headers-2.6.32-696.10.2.el6.x86_64.rpm 0b4eeb2ac18fa4da9998621b5595a6492929b0258c936056e2a3e1c19e261eff perf-2.6.32-696.10.2.el6.x86_64.rpm 93163e180b9f2927220805b39b10b97e7b74bd202b0abb22d8ecb92bd213d60d python-perf-2.6.32-696.10.2.el6.x86_64.rpm Source: 187fa35692f8a9f2c294a3f9a20713e78351e6e662a9983ab65533aff437ecfc kernel-2.6.32-696.10.2.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Tue, 12 Sep 2017 23:15:38 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:2685 Moderate CentOS 6 bluez Security Update Message-ID: <20170912231538.GA64188(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:2685 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2017:2685 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: f55b99ac9aeb545e217b69fa3f9bf1570ec4c59f5c6d121c22c2af788345ae7d bluez-4.66-2.el6_9.i686.rpm 57b7082172ce050457c8767b0c71cb3ea1333b63d4c371b790e267b2d5fbb369 bluez-alsa-4.66-2.el6_9.i686.rpm 4c70d6a7409019bfc72d131abb0456715738f24e0a3da38d5f5fd69aeebebe16 bluez-compat-4.66-2.el6_9.i686.rpm 668e314d0f092255fab6d18627ee93ae0ee5ce583d0753f1a66c87efee26591f bluez-cups-4.66-2.el6_9.i686.rpm 3706f759e384c00379bb3619118e8d576a141ebbdcad34e830fadf28885021ad bluez-gstreamer-4.66-2.el6_9.i686.rpm 26062fdd3ef719101c7c6c1be8069f74e7844fae8efeff18ab2b77e7b23c2e6e bluez-libs-4.66-2.el6_9.i686.rpm 381ed986c23d2fcd177e9020131a1c29f2906505bb735c79b8a491da930dd457 bluez-libs-devel-4.66-2.el6_9.i686.rpm x86_64: 160a385295a5d3087a5001c08372c9273d6f31e03242f134de45a54548adb630 bluez-4.66-2.el6_9.x86_64.rpm 57b7082172ce050457c8767b0c71cb3ea1333b63d4c371b790e267b2d5fbb369 bluez-alsa-4.66-2.el6_9.i686.rpm eb270282119149cb802de3133d8488223a8c6d7687377d24851da8a5ce57070f bluez-alsa-4.66-2.el6_9.x86_64.rpm 15d223dc36cb1556f92185614e1866daf2990a4019340e37d41ac98f1a09c781 bluez-compat-4.66-2.el6_9.x86_64.rpm ab1440290aba968f127578e02645f5b86affbf633101e07e334b94c6265de289 bluez-cups-4.66-2.el6_9.x86_64.rpm 3706f759e384c00379bb3619118e8d576a141ebbdcad34e830fadf28885021ad bluez-gstreamer-4.66-2.el6_9.i686.rpm 4d244850c245e50f8a65f8ce9306f2d2025997663797870a4c93adbf6a9ad597 bluez-gstreamer-4.66-2.el6_9.x86_64.rpm 26062fdd3ef719101c7c6c1be8069f74e7844fae8efeff18ab2b77e7b23c2e6e bluez-libs-4.66-2.el6_9.i686.rpm ff261867f68c7348b635d3b1fc962991b1405b5d48b9e5e97cd47a1606333f84 bluez-libs-4.66-2.el6_9.x86_64.rpm 381ed986c23d2fcd177e9020131a1c29f2906505bb735c79b8a491da930dd457 bluez-libs-devel-4.66-2.el6_9.i686.rpm 7c61988835262d896c3fcdbbc853f7b45b5972f6f7bfe9352142fd94f31f346d bluez-libs-devel-4.66-2.el6_9.x86_64.rpm Source: 07ac1e159666835719637d8a17ea9083951925377f7affbd8d18c315b5dfda84 bluez-4.66-2.el6_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 151, Issue 2 ***********************************************

1 0

Xen PV DomU's and the 3.10.0-693.el7 Kernel
by Johnny Hughes 12 Sep '17

12 Sep '17

If you are running CentOS Linux 7 inside a Xen DomU (VM) in PV mode, you can not upgrade to the standard 7.4.1708 kernel that is currently in the CR repo and that will be soon released in our file 7.4.1708 tree (3.10.0-693.*el7) The CentOS Plus kernel will be available when we release the 7.4.1708 tree and it does boot inside a Xen DomU PV, so you can either upgrade to the CentOS Plus kernel in PV mode .. or you can shift your DomU to either HVM or PVHVM modes. PVHVM is more like PV mode, and is usually much better than HVM mode. More info on PVHVM here: https://wiki.xen.org/wiki/PV_on_HVM https://wiki.xen.org/wiki/Xen_Linux_PV_on_HVM_drivers The anaconda installer and pxe booting from the standard tree 7.4.1708 tree will also not work in PV mode for new installs, only PVHVM or HVM installs can be done with the 7.4.1708 tree. Note: This is an upstream source code issue and will not be fixed in the main CentOS Linux 7 kernel unless it is fixed upstream in the RHEL source code. We are sorry for any inconvenience this issue may cause. Thanks, Johnny Hughes

1 0

bind named fails after logrotate
by Götz Reinicke 12 Sep '17

12 Sep '17

Hi, on our centos 7.3.1611 server the named dies after the log rotates script is executed. systemctl status named ● named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Di 2017-09-12 14:27:57 CEST; 2s ago Process: 20714 ExecStop=/bin/sh -c /usr/sbin/rndc stop > /dev/null 2>&1 || /bin/kill -TERM $MAINPID (code=exited, status=1/FAILURE) Process: 20684 ExecReload=/bin/sh -c /usr/sbin/rndc reload > /dev/null 2>&1 || /bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Main PID: 14496 (code=killed, signal=ABRT) Any suggestions or hints or is that a known problem? logrotate-3.8.6 bind-9.9.4 Thanks and regards . Götz

1 0

Missing CentOS 7 Updates
by Ken Gramm 12 Sep '17

12 Sep '17

I must be missing something, because I can't believe that there haven't been any updates since July 27 9fa12aadcd2ea45fdcb91bd125b619545993defa2032cf99b8a89cf6099723e8-primary.xml.gz 27-Jul-2017 15:12 4.0M [ ] 23b0e14a9667597b69a8719f0eea709721cc32f9f3b6c8202da0f5a36b9f1759-other.xml.gz 27-Jul-2017 15:12 137M [ ] 33fdce604445f67a26ce5ddc354ea0c835ed119ac8cb7404cc2b565bf80722a1-primary.sqlite.bz2 27-Jul-2017 15:16 7.8M [ ] 732f62a4c48e764e2ebe276eef7e6bf25eaf477452260a03805512a6a7a6ce80-filelists.sqlite.bz2 27-Jul-2017 15:16 4.4M [ ] 36288cdc93433b594aed022edabca28fe92c3497e23da598c59f890c0ddd7255-other.sqlite.bz2 27-Jul-2017 15:16 93M [ ] a6fd2af929647636c10531913d7c0b3a4277732a694d9aff9093dbb7890c4094-prestodelta.xml.gz 27-Jul-2017 15:14 954K [ ] bab46e0e0fd6233a1d50ad0cebcc6bae42c43fb85bf143f6ec415fd3458e882d-filelists.xml.gz 27-Jul-2017 15:12 4.8M [TXT] repomd.xml 27-Jul-2017 15:16 3.4K [TXT] repomd.xml.asc 27-Jul-2017 15:21 811

3 4

Corosync on a home network
by J Martin Rushton 11 Sep '17

11 Sep '17

I've been trying to build a model cluster using three virtual machines on my home server. Each VM boots off its own dedicated partition (CentOS 7.3). One partition is designated to be the common /home partition for the VMs, (on the real machine it will mount as /cluster). I'm intending to run GFS2 on the shared partition, so I need to configure DLM and corosync. That's where I'm getting bogged down. The VMs and the real machine are bridged onto one ethernet. There is another ethernet in the main machine on a different network, but that is not used for clustering. The ethernet port is connected to a switch which in turn connects to a BT Home Hub 6. All four adresses are static, Network Manager is off, ssh works across the nodes without a password and ping gives sensible times. --------------%<------------------- # brctl show bridge name bridge id STP enabled interfaces br3 XXXXXXXXX no enp3s0 vnet0 vnet1 vnet2 virbr0 XXXXXXXXX yes virbr0-nic --------------%<------------------- When I start corosync each node starts up but does not see the others. For instance I see: --------------%<---------------------- # corosync-quorumtool Quorum information ------------------ Date: Sun Sep 10 12:56:56 2017 Quorum provider: corosync_votequorum Nodes: 1 Node ID: 3 Ring ID: 3/28648 Quorate: No Votequorum information ---------------------- Expected votes: 4 Highest expected: 4 Total votes: 1 Quorum: 3 Activity blocked Flags: Membership information ---------------------- Nodeid Votes Name 3 1 192.168.1.52 (local) ----------------%<------------------- All four nodes are similar, but with different node IDs, IP addresses and Ring IDs. The documentation warns that not all routers will handle multicast datagrams correctly. I therefore attempted to force unicast communication by making the following changes from the distributed corosync.conf: transport: updu cluster_name: <set to the same as the domain> # crypto_cipher: none # crypto_hash: none # mcastaddr: 239.255.1.1 # mcastport: 5405 # ttl: 1 The following are unchanged: version: 2 secauth: off ringnumber: 0 bindnetaddr: 192.168.1.0 The nodelist is: ---------%<---------------- nodelist { node { ring0_addr: 192.168.1.2 nodeid: 1 } node { ring0_addr: 192.168.1.51 nodeid: 2 } node { ring0_addr: 192.168.1.52 nodeid: 3 } node { ring0_addr: 192.168.1.53 nodeid: 4 } } --------%<------------------ logging and quorum are as supplied. Any help will be gratefully received. Regards, Martin

4 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