April 2019 - Discuss - lists.centos.org

Happy 15th Birthday, CentOS!
by Rich Bowen 15 Apr '19

15 Apr '19

CentOS is 15 years old today! Hear the story from some of our community members at https://blog.centos.org/2019/04/centos15-2/ Do you have your own story? Drop me a note - rbowen(a)centosproject.org - to tell me about it. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

3 2

Re: [CentOS] How to specify kernel version when restart kdump
by Benjamin Hauger 15 Apr '19

15 Apr '19

kdump operates by booting a fresh kernel to capture the context of a crashed kernel, and so the only way for kdump to dump a kernel is to crash it and cause kdump to invoke its post-crash kernel. You can manually force a running kernel to panic (and invoke a correctly-configured kdump) with the following command sequence: > echo 1 > /proc/sys/kernel/sysrq > echo c > /proc/sysrq-trigger Cheers, Ben On 3/25/19 7:19 PM, wuzhouhui wrote: > Hi, > > Is there a way to specify kernel version when (re)start kdump > service? Suppose I have install a new kernel and kdump will > generate kdump.img for new kernel in next boot. But I want kdump > to generate kdump.img for new kernel immediately, is it possible? > > Thanks. > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos > -- Benjamin Hauger SysAdmin/CSDC-DMO Rm. 94 x8371

3 7

Centos 7.6 & ether-wake
by Gregory P. Ennis 14 Apr '19

14 Apr '19

Everyone, I have not been able to get ether-wake to work waking up other centos 7.6 machines after the upgrade to Centos 7.6. Has anyone else had this problem, and if so any luck with a fix? Greg Ennis

4 5

Resource utilisation of processes on linux server.
by Kaushal Shriyan 14 Apr '19

14 Apr '19

Hi, I have around 6 processes running on CentOS Linux release 7.6.1810 (Core). Is there a way to find out which process is taking resources like memory, CPU, I/O and network. Process 1 : How much memory, CPU, I/O and network is currently consuming on linux server Process 2 : How much memory, CPU, I/O and network is currently consuming on linux server Process 3 : How much memory, CPU, I/O and network is currently consuming on linux server and so on and so forth. Thanks in Advance and i look forward to hearing from you. Best Regards, Kaushal

4 5

When should I reboot?
by Kenneth Porter 13 Apr '19

13 Apr '19

I reboot when I yum update to a new kernel or systemd, which seems to come out about once a month. Should I do it for this week's glibc? Is that "core" enough to justify a reboot or should I wait for the next kernel update? I know the glibc update was mainly to handle the new Japanese calendar, so that shouldn't affect my usage. So my question is more about how shared libraries work and whether anything bad would happen with different forks of running services (mainly the mail suite with dovecot and the various content scanners launched by sendmail) running different versions of the library based on when they were started.

6 5

When will CentOS 8 be available for download?
by Turritopsis Dohrnii Teo En Ming 13 Apr '19

13 Apr '19

Good morning from Singapore, When will CentOS 8 be available for download? Thank you. -----BEGIN EMAIL SIGNATURE----- The Gospel for all Targeted Individuals (TIs): [The New York Times] Microwave Weapons Are Prime Suspect in Ills of U.S. Embassy Workers Link: https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html ******************************************************************************************** Singaporean Mr. Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 14 Feb 2019 [1] https://tdtemcerts.wordpress.com/ [2] https://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming -----END EMAIL SIGNATURE-----

5 5

CentOS-announce Digest, Vol 170, Issue 2
by centos-announce-request＠centos.org 13 Apr '19

13 Apr '19

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-2019:0711 Low CentOS 6 openssh Security Update (Johnny Hughes) 2. CEBA-2019:0719 CentOS 6 nss-pam-ldapd BugFix Update (Johnny Hughes) 3. CEBA-2019:0718 CentOS 6 autofs BugFix Update (Johnny Hughes) 4. CEBA-2019:0716 CentOS 6 cups BugFix Update (Johnny Hughes) 5. CESA-2019:0717 Important CentOS 6 kernel Security Update (Johnny Hughes) 6. CEBA-2019:0726 CentOS 6 glibc BugFix Update (Johnny Hughes) 7. CESA-2019:0697 Important CentOS 7 freerdp Security Update (Johnny Hughes) 8. CESA-2019:0710 Important CentOS 7 python Security Update (Johnny Hughes) 9. CEBA-2019:0728 CentOS 7 glibc BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 12 Apr 2019 13:56:07 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:0711 Low CentOS 6 openssh Security Update Message-ID: <20190412135607.GA11086(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:0711 Low Upstream details at : https://access.redhat.com/errata/RHSA-2019:0711 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 27467ddad2dde0e5336bb110637544d01509babb3a38cb3b66fca633a3307b92 openssh-5.3p1-124.el6_10.i686.rpm 0a344afb6445c8a4e4a55ee60e24022b5dd122be55d2bb5bb2c36367ee2c1b87 openssh-askpass-5.3p1-124.el6_10.i686.rpm ec8ffff4c95ad5307e027ba29a8a76719091cbd99db9ebc14661847061d4d739 openssh-clients-5.3p1-124.el6_10.i686.rpm ec5b4e75a0d9ca6a95e5a27da7f1a3547c421abe5d800bf3e90ee0589e7e2a09 openssh-ldap-5.3p1-124.el6_10.i686.rpm cfe6c58e18bcc195aa651d0dd3880a9395d0f7c136b270affb6958a02b1b9aee openssh-server-5.3p1-124.el6_10.i686.rpm b1b2d05b83a4c572fb7e22a5d585c9aed08325f082beb6660cbcbb99e816c6bf pam_ssh_agent_auth-0.9.3-124.el6_10.i686.rpm x86_64: 28e005c819d15d4b7c6f73382dc398f63a38677e101d8cc7a12dfe394dbc3890 openssh-5.3p1-124.el6_10.x86_64.rpm 6cd3d4d49aa45e25644a4bd8454f508fe87e4516aabd7e498dedc85ff0de8e58 openssh-askpass-5.3p1-124.el6_10.x86_64.rpm 5a96e1673702b5d71960399560acc6736c5662c3fc1e6948bb471714096c2312 openssh-clients-5.3p1-124.el6_10.x86_64.rpm 46083180c9a143985a79092ef54fb2ae30a44f929cdef3957ec5fd1682bb6e64 openssh-ldap-5.3p1-124.el6_10.x86_64.rpm 84ce53f513cdfe22294012cd48fcbc65ac6393806289beb9c1f92fe60304735d openssh-server-5.3p1-124.el6_10.x86_64.rpm b1b2d05b83a4c572fb7e22a5d585c9aed08325f082beb6660cbcbb99e816c6bf pam_ssh_agent_auth-0.9.3-124.el6_10.i686.rpm fefd34490eb6bdc4439ea3a7bbb1bc841336d86b7f2d527ffa145722adff5a93 pam_ssh_agent_auth-0.9.3-124.el6_10.x86_64.rpm Source: da18c49ea13c0f0d373f7c0159da11381989f5616856f494a92f9ec03315ef56 openssh-5.3p1-124.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Fri, 12 Apr 2019 13:56:33 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2019:0719 CentOS 6 nss-pam-ldapd BugFix Update Message-ID: <20190412135633.GA11213(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2019:0719 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0719 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 7d1ac41ad83089a6818ad786cc653e188d8f5415d7d5d0a5a01cbde7cf4d241e nss-pam-ldapd-0.7.5-32.el6_10.1.i686.rpm x86_64: 7d1ac41ad83089a6818ad786cc653e188d8f5415d7d5d0a5a01cbde7cf4d241e nss-pam-ldapd-0.7.5-32.el6_10.1.i686.rpm 852f086132106925e09b24c11972d4bc87688aa4cca7a9d2265a0abe5dfd0678 nss-pam-ldapd-0.7.5-32.el6_10.1.x86_64.rpm Source: bac7e042f96facc1f627387551b731bdf771cce7c9d18c6109c9851dbdc30bbd nss-pam-ldapd-0.7.5-32.el6_10.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Fri, 12 Apr 2019 13:56:55 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2019:0718 CentOS 6 autofs BugFix Update Message-ID: <20190412135654.GA11322(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2019:0718 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0718 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: d3b83c312e415c0a0e0fed02a6fdf931689fb6d6938b21e35586f2851357f755 autofs-5.0.5-140.el6_10.1.i686.rpm x86_64: c5c5978538540e88487bad63741f6d22891137a50da652b3b1b6d6aff550d525 autofs-5.0.5-140.el6_10.1.x86_64.rpm Source: 4d44085945db75ab9fc10cd6692a29a0c9a784c281ca43a0dba3bd32aa19e63b autofs-5.0.5-140.el6_10.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Fri, 12 Apr 2019 13:57:40 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2019:0716 CentOS 6 cups BugFix Update Message-ID: <20190412135740.GA11521(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2019:0716 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0716 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 65e2297ff1ee5ec65e5a1a208134a440a9f4614331ca3b994c2a24cc69f542e1 cups-1.4.2-81.el6_10.i686.rpm a98976ee659eb2e3c10c51475c23d620b1b063f3cb0ac6475c4bf63fa0910f3e cups-devel-1.4.2-81.el6_10.i686.rpm e18fe7c6c2ceac124d33d36d3798c6728d44c66c53e372a390575bfb6f1cb3fc cups-libs-1.4.2-81.el6_10.i686.rpm 3cb1af04a63f6f5ed8f0ae9b4d60d478c3ff9ca3eb066bd6e23273a772484740 cups-lpd-1.4.2-81.el6_10.i686.rpm ce8deafb02a3a61ab72511e8180d0734fb40ec1150bdbddbedf669023cdf352b cups-php-1.4.2-81.el6_10.i686.rpm x86_64: fe9886d0d0a2e3dc1dbd131e0a0657a24c01fbab734722bb25a152a16cff0c3c cups-1.4.2-81.el6_10.x86_64.rpm a98976ee659eb2e3c10c51475c23d620b1b063f3cb0ac6475c4bf63fa0910f3e cups-devel-1.4.2-81.el6_10.i686.rpm 0c51ee1eb220bb794ae9d4236b768a1728171a67627521270c484fb477d4922d cups-devel-1.4.2-81.el6_10.x86_64.rpm e18fe7c6c2ceac124d33d36d3798c6728d44c66c53e372a390575bfb6f1cb3fc cups-libs-1.4.2-81.el6_10.i686.rpm e1253ae8c62c1d1f5fdb219efae54045e77ca75892f5c068f946250962837618 cups-libs-1.4.2-81.el6_10.x86_64.rpm 54640af413f3489548509bd665001c531904514f260cc7d294ffde74fbaa1de8 cups-lpd-1.4.2-81.el6_10.x86_64.rpm 8017a5a9052d0a94e0790bf0b1081c7fe183b0dbeb6d93bc33ab1de7be8f292e cups-php-1.4.2-81.el6_10.x86_64.rpm Source: f3122ab37e83fd2e4a21235d17b666c4ede19f6125f115a691094188cdc38d08 cups-1.4.2-81.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Fri, 12 Apr 2019 13:58:58 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:0717 Important CentOS 6 kernel Security Update Message-ID: <20190412135858.GA11805(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:0717 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:0717 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 8fb8e9240e878706f288c6f263e129edd8ecd88acb286f874bd51ddfd6747f9c kernel-2.6.32-754.12.1.el6.i686.rpm 3e3f4bec1c472f2b2646a24c2bc6f35e3f55e95781a1e2482093b3c979fe9e38 kernel-abi-whitelists-2.6.32-754.12.1.el6.noarch.rpm d9a95c7c30a222d7329070f43dfc5981a016143e05ef784ec5a334c216defbb3 kernel-debug-2.6.32-754.12.1.el6.i686.rpm 044e3595e00620e1fdf9da3110ed84f68ebd8a019caf9a639b6b8d577a90f54d kernel-debug-devel-2.6.32-754.12.1.el6.i686.rpm 2968d6b086bc827e4913c00d8952df9b3dfc1bc4f22f408423c3a0adef65bca3 kernel-devel-2.6.32-754.12.1.el6.i686.rpm be4cdf8355bb898f2a6348740384cc2c069235a7c1d07259e1ecb13423e0e63e kernel-doc-2.6.32-754.12.1.el6.noarch.rpm 89d6fac63d4fd562d45af15f9207fc999c0f30434a25661c8ddd32a57723955e kernel-firmware-2.6.32-754.12.1.el6.noarch.rpm 68b433532fca9e4a6ee4a2b01e73060fdfe60d8d749890a3f6742816acd62c09 kernel-headers-2.6.32-754.12.1.el6.i686.rpm ae1170c85ac135852596da0776d53edc0774f4957e0c670d4e77165d56a772d6 perf-2.6.32-754.12.1.el6.i686.rpm b67b15cbecc892986caa5cd30b8e0ecd8adf1f67b284d6fa0c59a01521633809 python-perf-2.6.32-754.12.1.el6.i686.rpm x86_64: 93a311db5315e13b3cde6aa0c561f8a5eee32e586f8c4d2103f3343781b62112 kernel-2.6.32-754.12.1.el6.x86_64.rpm 3e3f4bec1c472f2b2646a24c2bc6f35e3f55e95781a1e2482093b3c979fe9e38 kernel-abi-whitelists-2.6.32-754.12.1.el6.noarch.rpm 51b259b2c8c80e1090283acd4c7d6d684075aeab972b7d5cf2b1fb70742f35cc kernel-debug-2.6.32-754.12.1.el6.x86_64.rpm 044e3595e00620e1fdf9da3110ed84f68ebd8a019caf9a639b6b8d577a90f54d kernel-debug-devel-2.6.32-754.12.1.el6.i686.rpm fc62105dab75d76e19ce22135f750b86584eb196d0e0c30d25fccb8d10e60046 kernel-debug-devel-2.6.32-754.12.1.el6.x86_64.rpm c3a2da8bf2ed8e63462382305dd28a451b621265c9434bc813249c4d110c0a01 kernel-devel-2.6.32-754.12.1.el6.x86_64.rpm be4cdf8355bb898f2a6348740384cc2c069235a7c1d07259e1ecb13423e0e63e kernel-doc-2.6.32-754.12.1.el6.noarch.rpm 89d6fac63d4fd562d45af15f9207fc999c0f30434a25661c8ddd32a57723955e kernel-firmware-2.6.32-754.12.1.el6.noarch.rpm 8218f7ebda403674698cbc59a53e7071e954c3e7ea01d4680055015ffa2fc97c kernel-headers-2.6.32-754.12.1.el6.x86_64.rpm ae68e6024bfca466312961e2ec79ac86fc5a8312caac37e5e28e5ce8360776b7 perf-2.6.32-754.12.1.el6.x86_64.rpm 3e3d8e65b40201b70d0bdfe02e17780931889d62a3163ca5e3789a643a24176e python-perf-2.6.32-754.12.1.el6.x86_64.rpm Source: 2ea407f3f6366c4ee809ff41d1ac6aff6bdecba6a53149bbd0acf85047b4a090 kernel-2.6.32-754.12.1.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 6 Date: Fri, 12 Apr 2019 14:00:06 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2019:0726 CentOS 6 glibc BugFix Update Message-ID: <20190412140006.GA12101(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2019:0726 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0726 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 18a17790ec698ecce8da2d3bc72797341287d1693ff7280d825aa9a4b2bb3713 glibc-2.12-1.212.el6_10.3.i686.rpm 6bf91eda70d82e03f7ce027b12fbb30aa67123d24c31ede804d888ba8ddd585f glibc-common-2.12-1.212.el6_10.3.i686.rpm 03634dfff8f00d04043209deab8dde2a30e5092bd702e4ba9816b3876766f33d glibc-devel-2.12-1.212.el6_10.3.i686.rpm f84d11134f3771db1fed3e4b3d1ee3b6051e7ebe39af44d2e9411f844ab2b233 glibc-headers-2.12-1.212.el6_10.3.i686.rpm 2787c45140209d3aec02e2730b6b57ba1ab69048b72e6c26a02e9dd0d199a317 glibc-static-2.12-1.212.el6_10.3.i686.rpm e09c5b81cb742c802a2d39565dffbec467991560de9ff097d387ff4b24b04429 glibc-utils-2.12-1.212.el6_10.3.i686.rpm a2deec4793426e4f867956234f1a9e49947a938844bdf271ae4fb44625049d67 nscd-2.12-1.212.el6_10.3.i686.rpm x86_64: 18a17790ec698ecce8da2d3bc72797341287d1693ff7280d825aa9a4b2bb3713 glibc-2.12-1.212.el6_10.3.i686.rpm 0383c8ba8d870938a5a2ae252a2168e5a291a9b880e9c05537e4874acb8efc50 glibc-2.12-1.212.el6_10.3.x86_64.rpm 5eb095c1ed264f0459c81d13e741cd130d5b5ca37e5277371c5429d621f68434 glibc-common-2.12-1.212.el6_10.3.x86_64.rpm 03634dfff8f00d04043209deab8dde2a30e5092bd702e4ba9816b3876766f33d glibc-devel-2.12-1.212.el6_10.3.i686.rpm 29c18d7523c08746cb053c6682eedefb3029b6da97125b698208981d090dc168 glibc-devel-2.12-1.212.el6_10.3.x86_64.rpm 363274964801ba43b67ba265b303da4e5c26206b816bcc72ef7ac92f1b24f93d glibc-headers-2.12-1.212.el6_10.3.x86_64.rpm 2787c45140209d3aec02e2730b6b57ba1ab69048b72e6c26a02e9dd0d199a317 glibc-static-2.12-1.212.el6_10.3.i686.rpm 3304518a386ecb233b3cfa4d9b47ba7138080c78fc013f2f3e38ac245aab1505 glibc-static-2.12-1.212.el6_10.3.x86_64.rpm 492e9c62fb8175e9ec352ec11ac96c48629a5dd6f2c67406de6befaacfe4ad6e glibc-utils-2.12-1.212.el6_10.3.x86_64.rpm ebd50ddf69415c1e97d83e93b3245a4203fbb497fc5591084250417b5b325761 nscd-2.12-1.212.el6_10.3.x86_64.rpm Source: 343720baf52d494b96022005cace30033af4e71031b755df0c3c1dfca9f8824f glibc-2.12-1.212.el6_10.3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 7 Date: Fri, 12 Apr 2019 14:01:25 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:0697 Important CentOS 7 freerdp Security Update Message-ID: <20190412140125.GA12276(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:0697 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:0697 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: e6cd6480d1e1baa3be0b63afda63addcd363500bae95d18c38ab52160e2becfa freerdp-1.0.2-15.el7_6.1.x86_64.rpm 488bc577966d805f83d59fa7e4bae9ec856a5190880b4be23effa594cb0a38ba freerdp-devel-1.0.2-15.el7_6.1.i686.rpm 72b6ccc96220eae70c7f6b34337d707480e7101bed5425156426a9ac67c5ad06 freerdp-devel-1.0.2-15.el7_6.1.x86_64.rpm 9224b2e30a7550254d12ea709ad0d970a095c98c582df7e2bf20b311bcfa8c4e freerdp-libs-1.0.2-15.el7_6.1.i686.rpm f54a13fcb227f5d7bd7113b3056d1d9e6e8364e2c1785f5f65dd7ecadbe4005d freerdp-libs-1.0.2-15.el7_6.1.x86_64.rpm f42fa57dbb092aa129d33014975d4da3091b094047b65d97ba90d2c699954ade freerdp-plugins-1.0.2-15.el7_6.1.x86_64.rpm Source: 550cec9d827703215802648982627a7ea42496facaba89ba58f46d90f7d2320d freerdp-1.0.2-15.el7_6.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 8 Date: Fri, 12 Apr 2019 14:02:06 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:0710 Important CentOS 7 python Security Update Message-ID: <20190412140206.GA12437(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:0710 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:0710 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: e9b05ae45a0d656d4ff1ebc7b12b574e0173dae4bfb388ced32f0a02f7dfaec1 python-2.7.5-77.el7_6.x86_64.rpm a46e8bc336c27fce2c32081c42b3a6be1ac7ea10b2a19f2e8ab5795434106328 python-debug-2.7.5-77.el7_6.x86_64.rpm 9183d1b76d4e4f8bce7fd77047fe7d2c6721b0cd6a08cd92f2adcff5acabe551 python-devel-2.7.5-77.el7_6.x86_64.rpm 5d7c5abf5f28f83265df7892dc6dee1e7e8c7ea93c8d0c797775884075d3bc57 python-libs-2.7.5-77.el7_6.i686.rpm 310caf886a23c66b421939448da9dfb2ef4cfc10a06d2d99f598a3f4e2a7bce4 python-libs-2.7.5-77.el7_6.x86_64.rpm a6febbcdfdbd7190df0df350a6dc5341c16472c750d6915edbba2226c99be050 python-test-2.7.5-77.el7_6.x86_64.rpm 4d98ef6bcde7a158c2844c5297c160f40d13dc1402c0242a3fc1ca715f9a9ca1 python-tools-2.7.5-77.el7_6.x86_64.rpm daa4edb3eaf6b3f57dbb95ce2b2156ad0043ad372e38b05844b393c281a15ad2 tkinter-2.7.5-77.el7_6.x86_64.rpm Source: 9f73ef611c4a66d9f1f0c0dcee4789f16ef5d6c731053cacbbfb9a3637ddb501 python-2.7.5-77.el7_6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 9 Date: Fri, 12 Apr 2019 14:02:50 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2019:0728 CentOS 7 glibc BugFix Update Message-ID: <20190412140250.GA12616(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2019:0728 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0728 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 4f16e7220f0e26d3c6c894e9a7e5d3c3befcbc3bac574f82f441e57ff8de3d0b glibc-2.17-260.el7_6.4.i686.rpm 1a22e1abd98fe4209ae5bc1a70a83b25727e7a0ecc60f43255343fc995a1fa04 glibc-2.17-260.el7_6.4.x86_64.rpm 5849f67ff63d03859884569b54814e85dc71716bda08b86c61ad891e46827a16 glibc-common-2.17-260.el7_6.4.x86_64.rpm 6bef12b3942f054b6a2baf8b73f0bcbbdacbd4f31675a6a898c52ae6e1b51aaa glibc-devel-2.17-260.el7_6.4.i686.rpm f7bdbd7148e148dba970a0c4551e88619ae70b3036b36213100a21f0c5216f72 glibc-devel-2.17-260.el7_6.4.x86_64.rpm 98abcd028d9f3b74a6f215f09cf50dd5ba23908fbb2ba39f5113374e4e4ff58f glibc-headers-2.17-260.el7_6.4.x86_64.rpm afb153055817bbabb38696cdd83cec209ff23e5a5c257ad780d7dbcb83f238f3 glibc-static-2.17-260.el7_6.4.i686.rpm 5be8a3fc0704c5c013b98a03043c43b02ecb1b4660ed86827e376d54d40d8bdf glibc-static-2.17-260.el7_6.4.x86_64.rpm 6f3cd8dd90e40195a7db1dd8229a715758bffa68ba7ab7cf93981a87de7466fb glibc-utils-2.17-260.el7_6.4.x86_64.rpm 758f862e6d08250708cfa22218b9e3d394b64c3ea864f5f676cc7d8b084c41d2 nscd-2.17-260.el7_6.4.x86_64.rpm Source: 55d4ac8474ece84adb46e5c6cb7397cf89478441df9e816bc2a9a8f622ee0e17 glibc-2.17-260.el7_6.4.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 170, Issue 2 ***********************************************

1 0

rpmbuild how to know we are building kernel module package
by wuzhouhui 13 Apr '19

13 Apr '19

Hi, When I build a mpt3sas rpm package, I found something interesting: 1. package name is prefixed with kmod- automatically 2. so many requirements are added automatically, most of them are kabi So my question is rpmbuild how to know he is building kernel module package? Based on which condition? Here is mpt3sas.spec: Name: mpt3sas Version: 26.00.00.00 Release: 1 Summary: RHEL Driver Update Program package Group: System/Kernel License: GPLv2 URL: http://www.lsilogic.com Distribution: LSI Corporation Source0: %{name}-%{version}.tar.bz2 Source1: %{name}.files Source2: %{name}.conf BuildRoot: %(mktemp -ud %{_tmppath}/%{name}-%{version}-%{release}-XXXXXX) BuildRequires: %kernel_module_package_buildreqs %global kernel_version `uname -r` %kernel_module_package -f %{SOURCE1} default %description LSI MPT Fusion HBA drivers (12gb SAS) %prep %setup set -- * mkdir source mv "$@" source/ mkdir obj %build for flavor in %flavors_to_build; do rm -rf obj/$flavor cp -r source obj/$flavor make -C %{kernel_source $flavor} M=$PWD/obj/$flavor done %install export INSTALL_MOD_PATH=$RPM_BUILD_ROOT export INSTALL_MOD_DIR=extra/%{name} for flavor in %flavors_to_build ; do make -C %{kernel_source $flavor} modules_install \ M=$PWD/obj/$flavor # Cleanup unnecessary kernel-generated module dependency files. find $INSTALL_MOD_PATH/lib/modules -iname 'modules.*' -exec rm {} \; done sed -e s/this_weakupdate/`uname -r | cut -f1 -d-`/ \ ../../SOURCES/mpt3sas.conf > \ ../../SOURCES/mpt3sas.a mv ../../SOURCES/mpt3sas.a ../../SOURCES/mpt3sas.conf install -m 644 -D %{SOURCE2} $RPM_BUILD_ROOT/etc/depmod.d/%{name}.conf install -m 644 -D %{SOURCE2} $RPM_BUILD_ROOT/etc/modules-load.d/%{name}.conf %clean rm -rf $RPM_BUILD_ROOT %changelog

2 2

Cockpit within httpd
by david 12 Apr '19

12 Apr '19

Folks I'd love to use Cockpit, but I cannot open port 9090 for the access in all cases. I'd like to access it via my usual http port (such as 80) where I'm limited to a single HTTP port. I understand the security implications, and can deal with them later. My attempt was to allow the following URL to access the cockpit functionality: http://xxx.example.com/cockpit (not the real URL) where 'xxx.example.com' is one of the virtual web sites on my server. I tried as follows for the definition of the virtual server: <VirtualHost *:80> ServerName xxx.example.com ServerAdmin admin_xxx(a)example.com DocumentRoot /home/xxx/public_html Options +ExecCGI +Includes +FollowSymLinks LogFormat Combined TransferLog /var/log/httpd/u_xxx_access_log ErrorLog /var/log/httpd/u_xxx_error_log RewriteEngine on ProxyPreserveHost On RewriteCond %{HTTP:Upgrade} =websocket [NC] RewriteRule /cockpit/(.*) ws://127.0.0.1:9090/$1 [P,L] RewriteCond %{HTTP:Upgrade} !=websocket [NC] RewriteRule /cockpit/(.*) ws://127.0.0.1:9090/$1 [P,L] ProxyPass /cockpit/ http://127.0.0.1:9090/ ProxyPassReverse /cockpit/ http://127.0.0.1:9090/ </VirtualHost> All I get is a blank page displayed when I try to access the url. Testing Cockpit by accessing port 9090 works fine. Am I missing something? Thanks in advance David

2 1

dracut ipv6 fixed ip
by Natxo Asenjo 12 Apr '19

12 Apr '19

hi, we have successfully implemented at tang/clevis environment for automatically entering luks keys and booting hosts without operator intervention. Now we would like to use this as well on ipv6 networks, but I do not seem to get it to work. I have already posted this issue to the dracut devs github issue tracker ( https://github.com/dracutdevs/dracut/issues/554) but no response so far. Maybe here I will get an aswer. I have tried these combinations but none works (/etc/dracut.conf.d/1_static.conf) kernel_cmdline="ip=[fd0c:fc8a:xxxx:xx::2] netmask=64 gateway=[fd0c:fc8a:xxxx:xx::1] nameserver=[fd7a:f141:xxxx:xx::11]" omit_dracutmodules+="ifcfg" kernel_cmdline="ip=[fd0c:fc8a:xxxx:xx::2] netmask=/64 gateway=[fd0c:fc8a:xxxx:xx::1] nameserver=[fd7a:f141:xxxx:xx::11]" omit_dracutmodules+="ifcfg" kernel_cmdline="ip=[fd0c:fc8a:xxxx:xx::2]::[fd0c:fc8a:xxx:xx::1]:64:::none::[mac:address] nameserver=[fd7a:f141:xxxx:xx::11]" kernel_cmdline="ip=[fd0c:fc8a:xxxx:xx::2]::[fd0c:fc8a:xxxx:xx::1]:64::eno1:none nameserver=[fd7a:f141:xxxx:xxx::11]" With the first two I get an unbootable system (system halted) (sorry, I did not take a foto of the error), the latest two do boot but never contact the tang server so I need to manually enter the luks key. On the ipv6 gateway there comes no ipv6 traffic from the dracut client while on the luks password prompt. Once the system is booted, I can decrypt fine sing the clevis tools and ipv6 (no firewall issue). We are working arround the issue booting clevis in dracut with a ipv4 address and natting the http client to the tang servers on the gateway, but this is suboptimal and makes us maintain an ipv4 presence we neither need nor want. Am I missing something obvious in the dracut conf file maybe? Anyone experience with something similar? Thanks in advance. -- regards, Natxo

1 1

Nautilus and umask on CentOS 7 with Gnome3
by James Pearson 12 Apr '19

12 Apr '19

We have a problem whereby Nautilus is not using the umask setting defined by the user (e.g. when creating directories via the the 'Places' menu). The umask used by Nautilus is 022, but the shell umask (in our case) is set to 002 A quick search seems to suggest that this a common problem, and various methods are suggested to 'fix' this - the only way that appears to work on CentOS 7 is to add 'UMask 002' to the '[Service]' section via a unit file snippet in /etc/systemd/system/display-manager.service.d/ - this works OK - but it makes the umask a global setting for all users, when theoretically, different users may want to have different umask settings Does anyone know the 'proper' way to get Nautilus to use a user's own umask setting ? Thanks James Pearson

1 0

Short or long hostname ?
by Nicolas Kovacs 12 Apr '19

12 Apr '19

Hi, For the last ten years or so, I've defined the short hostname in /etc/hostname and the FQDN in /etc/hosts. Now I wanted to double-check this information, which eventually led me to this page: * https://serverfault.com/questions/331936/setting-the-hostname-fqdn-or-short… Now I admit I'm even more confused than before. Is there some reliable piece of information on this subject for CentOS ? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12

5 6

Re: [CentOS] Kernel panic after removing SW RAID1 partitions, setting up ZFS.
by Jyrki Tikka 11 Apr '19

11 Apr '19

On Wed, 10 Apr 2019 08:38:04 -0700, Benjamin Smith <lists(a)benjamindsmith.com> wrote >I drove to the site, picked up the machine, and last night found that the >problem wasn't anything to do with mdadm, but rather setting a partition to >GPT. For some reason, you *cannot* have a partition of type GPT and expect >Linux to boot. (WT F/H?!?) If you want to boot a BIOS based machine with a GPT boot disk you need to have a BIOS boot partition. Otherwise GRUB will have no place to write the necessary bootloader code. https://en.wikipedia.org/wiki/BIOS_boot_partition I found this out a few years ago when I replaced the 2 TiB MBR boot drives on my Fedora System with 3 TiB GPT disks (mdraid 1) <(*) Jyrki

2 1

postgis-2.0.7-2.el7 still in epel7-testing?
by Danny Smit 11 Apr '19

11 Apr '19

Hi all, I'm looking for a fix in postgis, which seems to be fixed already in postgis-2.0.7-2.el7. However that package seems to be 'stuck' in the epel7-testing repository: https://koji.fedoraproject.org/koji/buildinfo?buildID=750618 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-b6c229157e Is there a reason that the package is not pushed to stable yet? Or can it be pushed to stable? -- Kind regards, Danny

3 2

CVE-2019-0211 httpd24 / EL6
by Leon Fauster 11 Apr '19

11 Apr '19

It seems that httpd24-httpd from SCL is affected by CVE-2019-0211 [1]. Does the SIG has plans to update these rpms for EL6? [1] https://httpd.apache.org/security/vulnerabilities_24.html -- Thanks, LF

2 3

parallel not found!
by Nikos Gatsis - Qbit 11 Apr '19

11 Apr '19

Hello list. I'm trying to yum update my Centos 7 and have problem to update parallel. Is like file is missing: parallel-20190322-3.2.noarch.r FAILED http://download.opensuse.org/repositories/home%3A/tange/CentOS_7/noarch/par…: [Errno 14] HTTP Error 404 - Not Found-:-- ETA Trying other mirror. Did i miss something? Thank you in advance. Nikos.

3 3

WINE on CentOS 7
by Jerry Geis 10 Apr '19

10 Apr '19

Hi All - I have wine installed from EPEL on CentOS 7. My .exe is running except I dont seem to have network ? So I tried a ping command. wine ping 192.168.1.1 0009:err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions. Pinging 192.168.1.1 [192.168.1.1] with 32 bytes of data: PING: transmit failed. General failure. ^C0028:fixme:console:CONSOLE_DefaultHandler Terminating process 8 on event 0 wine ipconfig /all output looks all fine. Is there something special to do for network access under wine ??? Thanks, Jerry

2 1

Re: [CentOS] BhkMbpU
by mark 10 Apr '19

10 Apr '19

=?utf-8?Q?=E6=9C=8D=E5=8A=A1=E4=B8=9A=E6=99=AE=E9=80=9A=E7=99=BC=E7=A5=A8 =E9=9C=80=E8=A6=81=E8=81=94=E7=B3=BB =E7=94=B5+V=EF=BC=9A131289=E2=92=8F0961=E6=9D=A8=E7=94=9F?= wrote: > UsWbgnkbt Ah, yes, the joys of a plain text mailing list... where this garbage shows up as just garbage. Now, HTML email, or, as I often refer to it, malware-spreading email....

2 2

In place upgrade of RHEL 8 Beta to CentOS 8?
by Benjamin Smith 10 Apr '19

10 Apr '19

I'm about to rebuild a server, currently running CentOS 6. If I have to do an OS reinstall, my intention is to upgrade, as it's the oldest OS server under my purview. As this server is pretty low visibility, I'd like to see if I can start using EL 8 instead of 7.x. In the past, I was able to switch between different OS variants by simply changing out the yum.d files; EG: RHEL 6.x becomes CentOS 6.x by replacing a single RPM and doing a `yum -y clean all; yum -y update` without issue. How likely is it that similar functionality will exist switching from RHEL 8 Beta to CentOS 8 final? Google pounding provided little info. I couldn't even find useful information for the transition from RHEL 7 Beta. Ben

7 10

MegaRAID, and creating a RAID 1 while live
by mark 10 Apr '19

10 Apr '19

I've started searching, but if anyone here has a link.... I *just* discovered yesterday, to my dismay, that a previous admin built a box that has four hot-swap bays as two as RAID 1... and the other two as RAID 0. Honest, I thought I was pulling the failing drive out of a RAID 1, not that the RAID 0 contained all the websites for a production box.... So, what I want to do is this: it's a Dell, with a PERC 710. Let's call the two drives I'm dealing with sdb and sdc. With mdadm, what I'd do is 1. copy what's on the the RAID 0 of sdc to the RAID 0 of sdb, 2. create sdc as RAID 1, with a drive missing. 3. copy everything from sdb to sdc, and finally. 4. kill the RAID 0 of sdb, and add it as the missing drive to the new RAID 1. And, all with MegaCli64.... Links? mark

1 0

(no subject)
by Thusitha Kumara 10 Apr '19

10 Apr '19

FO Sent from Mobile App ------------------ This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0

Kernel panic after removing SW RAID1 partitions, setting up ZFS.
by Benjamin Smith 10 Apr '19

10 Apr '19

System is CentOS 6 all up to date, previously had two drives in MD RAID configuration. md0: sda1/sdb1, 20 GB, OS / Partition md1: sda2/sdb2, 1 TB, data mounted as /home Installed kmod ZFS via yum, reboot, zpool works fine. Backed up the /home data 2x, then stopped the sd[ab]2 partition with: mdadm --stop /dev/md1; mdadm --zero-superblock /dev/sd[ab]1; Removed /home in /etc/fstab. Used fdisk to set the partition type to gpt for sda2 and sdb2, then built *then destroyed* a ZFS mirror pool using the two partitions. Now the system won't boot, has a kernel panic. I'm remote, so I'll be going in tomorrow to see what's up. My assumption is that it has something to do with mdadm/RAID not being "fully removed". Any idea what I might have missed? Here's a screenshot of the panic http://effortlessis.com/images/IMG_0705.JPG

4 4

CentOS Dojo at DevConf.US: CFP and Registration open
by Rich Bowen 09 Apr '19

09 Apr '19

TL;DR: CentOS Dojo on August 14th at Boston University. CFP and Registration now available at https://wiki.centos.org/Events/Dojo/DevConfUS2019 Hello, folks. We will once again be holding the CentOS Dojo at Boston University, on the day before DevConf.US 2019. The details of DevConf.US are at https://devconf.us/ and the details of the CentOS Dojo are at https://wiki.centos.org/Events/Dojo/DevConfUS2019 The call for presentations is now open, and will close May 1st. Registration is now open. It's free to attend, but we need an attendee count for planning purposes. You can see last years schedule - https://wiki.centos.org/Events/Dojo/DevConfUS2018 - for an example of what kind of presentations we might have. And we'd love to hear from you - your stories of running your infra on CentOS, the projects that you're working on, and interesting challenges you've had. Please do submit your talk proposals! Based on requests last year, we expect to do a lightning talks session, with 5-minute impromptu talks for those who don't have a full presentation. Hope to see you in Boston! -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

Re: [CentOS] Issues when updating CentOS 7
by Jyrki Tikka 08 Apr '19

08 Apr '19

>I wanted to update my CentOS 7 install this morning and I started>getting the errors from below. >Any ideas on a fix? Certainly! >Error: Package: python34-xapps-overrides-1.0.4-13.el7.x86_64 (@epel) > Requires: xapps(x86-64) = 1.0.4-13.el7 > Removing: xapps-1.0.4-13.el7.x86_64 (@epel) > xapps(x86-64) = 1.0.4-13.el7 > Updated By: xapps-1.0.4-14.el7.x86_64 (epel) > xapps(x86-64) = 1.0.4-14.el7 > You could try using --skip-broken to work around the problem > You could try running: rpm -Va --nofiles --nodigest The package python34-xapps-overrides-1.0.4-13.el7.x86_64 has been replacedby python36-xapps-overrides-1.0.4-14.el7.x86_64 and yum can't handle it.Sometimes the problem will be solved within reasonable time but sometimes it'sjust simpler to remove and reinstall some offending package. Just remove xapps (yum remove xapps) and note which packages are removed with it.On my systems these packages were removed: Packages Altered: Erase python2-xapps-overrides-1.0.4- 13.el7.x86_64 @epel Erase python34-xapps-overrides-1.0.4- 13.el7.x86_64 @epel Erase xapps-1.0.4- 13.el7.x86_64 @epel Erase xed-1.6.2- 3.el7.x86_64 @epel Then reinstall xapps, xed, python2-xapps-overrides andinstall python36- xapps-overrides like so: Packages Altered: Install python2-xapps-overrides-1.0.4- 14.el7.x86_64 @epel Install python36-xapps-overrides-1.0.4- 14.el7.x86_64 @epel Install xapps-1.0.4- 14.el7.x86_64 @epel Install xed-1.6.2- 3.el7.x86_64 @epel <(*) Jyrki

3 2

Automatic updates applying after reboot
by Gestió Servidors 08 Apr '19

08 Apr '19

Hello, I have noticed something I consider "a bug". Running a CentOS-7-x86_64 with kernel 3.10.0-327.13.1 and Gnome 3.14.x, my systems detects some available updates, notifies me at top bar and, if I close session, Gnome ask me if I want to apply these "pending" updates and, then, execute "shutdown" or "restart". My questions/problems are two: * this automatic updates check runs in both root session and not a root session, so if a "normal" user login, that user could logout and APPLY updates (system reboots and, during boot, updates system). I consider these situation VERY DANGEROUS, because a normal user should not be able to apply updates * what daemon controls automatic updates? pakagekit? What RPM? gnome-packagekit-updater? I NEED to disable this feature. By the moment, the only solution I have found is disablinig packagekit daemon (systemctl disable packagekit) and remove RPM "gnome-packagekit-updater". Thanks.

1 0

Issues when updating CentOS 7
by Stelian Iancu 05 Apr '19

05 Apr '19

Hi all, I wanted to update my CentOS 7 install this morning and I started getting the errors from below. Any ideas on a fix? They seem to be related to cinnamon which I actually don't use at all (the machine was prepared by our IT at work and they install both Gnome and Cinnamon by default). Since I don't use it, I guess an option would be to remove it altogether and then I will probably not have the update issues anymore. But I would still try to find a proper way to solve this Thanks in advance! Here is the output from yum update: Resolving Dependencies --> Running transaction check ---> Package cinnamon-menus.x86_64 0:3.6.0-3.el7 will be updated ---> Package cinnamon-menus.x86_64 0:3.6.0-4.el7 will be an update ---> Package cinnamon-screensaver.x86_64 0:3.6.1-3.el7 will be updated ---> Package cinnamon-screensaver.x86_64 0:3.6.1-4.el7 will be an update --> Processing Dependency: python36-gobject(x86-64) for package: cinnamon-screensaver-3.6.1-4.el7.x86_64 --> Processing Dependency: python36-setproctitle(x86-64) for package: cinnamon-screensaver-3.6.1-4.el7.x86_64 --> Processing Dependency: python36-xapp for package: cinnamon-screensaver-3.6.1-4.el7.x86_64 --> Processing Dependency: python36-xapps-overrides(x86-64) for package: cinnamon-screensaver-3.6.1-4.el7.x86_64 ---> Package code.x86_64 0:1.32.3-1552607091.el7 will be updated ---> Package code.x86_64 0:1.33.0-1554390950.el7 will be an update ---> Package freerdp.x86_64 0:1.0.2-15.el7 will be updated ---> Package freerdp.x86_64 0:1.0.2-15.el7_6.1 will be an update ---> Package freerdp-libs.x86_64 0:1.0.2-15.el7 will be updated ---> Package freerdp-libs.x86_64 0:1.0.2-15.el7_6.1 will be an update ---> Package freerdp-plugins.x86_64 0:1.0.2-15.el7 will be updated ---> Package freerdp-plugins.x86_64 0:1.0.2-15.el7_6.1 will be an update ---> Package google-chrome-stable.x86_64 0:73.0.3683.86-1 will be updated ---> Package google-chrome-stable.x86_64 0:73.0.3683.103-1 will be an update ---> Package mint-y-theme.noarch 0:1.2.4-1.el7 will be updated ---> Package mint-y-theme.noarch 0:1.2.4-2.el7 will be an update ---> Package python2-crypto.x86_64 0:2.6.1-15.el7 will be updated ---> Package python2-crypto.x86_64 0:2.6.1-16.el7 will be an update ---> Package python2-pyxdg.noarch 0:0.25-6.el7 will be updated ---> Package python2-pyxdg.noarch 0:0.25-7.el7 will be an update ---> Package python2-xapps-overrides.x86_64 0:1.0.4-13.el7 will be updated ---> Package python2-xapps-overrides.x86_64 0:1.0.4-14.el7 will be an update ---> Package python34.x86_64 0:3.4.9-2.el7 will be obsoleted --> Processing Dependency: python(abi) = 3.4 for package: python34-gobject-base-3.22.0-4.el7.x86_64 --> Processing Dependency: python(abi) = 3.4 for package: python34-gobject-3.22.0-4.el7.x86_64 --> Processing Dependency: python(abi) = 3.4 for package: python34-xapp-1.0.1-8.el7.noarch --> Processing Dependency: python(abi) = 3.4 for package: python34-xapps-overrides-1.0.4-13.el7.x86_64 --> Processing Dependency: python(abi) = 3.4 for package: python34-setproctitle-1.1.6-2.el7.x86_64 --> Processing Dependency: python(abi) = 3.4 for package: python34-psutil-2.2.1-5.el7.x86_64 --> Processing Dependency: python(abi) = 3.4 for package: python34-cairo-1.10.0-24.el7.x86_64 ---> Package python34-libs.x86_64 0:3.4.9-2.el7 will be obsoleted --> Processing Dependency: libpython3.4m.so.1.0()(64bit) for package: python34-3.4.9-3.el7.x86_64 --> Processing Dependency: libpython3.4m.so.1.0()(64bit) for package: python34-setproctitle-1.1.6-2.el7.x86_64 --> Processing Dependency: libpython3.4m.so.1.0()(64bit) for package: python34-cairo-1.10.0-24.el7.x86_64 --> Processing Dependency: libpython3.4m.so.1.0()(64bit) for package: python34-psutil-2.2.1-5.el7.x86_64 ---> Package python34-psutil.x86_64 0:2.2.1-4.el7 will be updated ---> Package python34-psutil.x86_64 0:2.2.1-5.el7 will be an update ---> Package python36.x86_64 0:3.6.6-5.el7 will be obsoleting ---> Package python36-libs.x86_64 0:3.6.6-5.el7 will be obsoleting ---> Package xapps.x86_64 0:1.0.4-13.el7 will be updated --> Processing Dependency: xapps(x86-64) = 1.0.4-13.el7 for package: python34-xapps-overrides-1.0.4-13.el7.x86_64 ---> Package xapps.x86_64 0:1.0.4-14.el7 will be an update --> Running transaction check ---> Package python34.x86_64 0:3.4.9-2.el7 will be updated ---> Package python34.x86_64 0:3.4.9-3.el7 will be an update ---> Package python34-libs.x86_64 0:3.4.9-2.el7 will be updated ---> Package python34-libs.x86_64 0:3.4.9-3.el7 will be an update ---> Package python36-gobject.x86_64 0:3.22.0-6.el7 will be installed --> Processing Dependency: python36-gobject-base(x86-64) = 3.22.0-6.el7 for package: python36-gobject-3.22.0-6.el7.x86_64 --> Processing Dependency: python36-cairo(x86-64) for package: python36-gobject-3.22.0-6.el7.x86_64 ---> Package python36-setproctitle.x86_64 0:1.1.6-3.el7 will be installed ---> Package python36-xapp.noarch 0:1.0.1-9.el7 will be installed --> Processing Dependency: python36-psutil for package: python36-xapp-1.0.1-9.el7.noarch ---> Package python36-xapps-overrides.x86_64 0:1.0.4-14.el7 will be installed ---> Package xapps.x86_64 0:1.0.4-13.el7 will be updated --> Processing Dependency: xapps(x86-64) = 1.0.4-13.el7 for package: python34-xapps-overrides-1.0.4-13.el7.x86_64 --> Running transaction check ---> Package python36-cairo.x86_64 0:1.10.0-25.el7 will be installed ---> Package python36-gobject-base.x86_64 0:3.22.0-6.el7 will be installed ---> Package python36-psutil.x86_64 0:2.2.1-5.el7 will be installed ---> Package xapps.x86_64 0:1.0.4-13.el7 will be updated --> Processing Dependency: xapps(x86-64) = 1.0.4-13.el7 for package: python34-xapps-overrides-1.0.4-13.el7.x86_64 --> Finished Dependency Resolution Error: Package: python34-xapps-overrides-1.0.4-13.el7.x86_64 (@epel) Requires: xapps(x86-64) = 1.0.4-13.el7 Removing: xapps-1.0.4-13.el7.x86_64 (@epel) xapps(x86-64) = 1.0.4-13.el7 Updated By: xapps-1.0.4-14.el7.x86_64 (epel) xapps(x86-64) = 1.0.4-14.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest

2 1

Seek some help on operating system drivers. Thanks!
by JICHUN LIU 05 Apr '19

05 Apr '19

Hello, I am a user of CentOS 7.6. I came here for help. I recently bought a microserver called HPE Proliant MicroServer Gen10(X3216 APU). CentOS 7.6 was installed for it. I found that the fan of the machine would keep turning and the noise was very loud. I searched everywhere but I couldn't find any way out. Pardon my ignorance showing. I don’t know where to seek help. When I use sensors-detect: Sorry, no sensors were detected. Either your system has no sensors, or they are not supported, or they are connected to an I2C or SMBus adapter that is not supported. If you find out what chips are on your board, check http://www.lm-sensors.org/wiki/Devices for driver status. Some info about my microserver: [root@centos7 ~]# lsb_release -a LSB Version: :core-4.1-amd64:core-4.1-noarch Distributor ID: CentOS Description: CentOS Linux release 7.6.1810 (Core) Release: 7.6.1810 Codename: Core [root@centos7 ~]# lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] (rev 87) 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Host Bridge 00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Port 00:02.5 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Port 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Host Bridge 00:08.0 Encryption controller: Advanced Micro Devices, Inc. [AMD] Device 1578 00:09.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 157d 00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 20) 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 49) 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 49) 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 4a) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 5 01:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller (rev 11) 02:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe 02:00.1 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe

2 2

git.centos.org : Delayed migration
by Fabian Arrotin 05 Apr '19

05 Apr '19

Due to unexpected circumstances , we have to delay the git.centos.org migration. I'll post an update when we'll have all details, but it seems it would be only delayed for some days. Thanks for your comprehending, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 0

New post message
by Konstantin Msk 05 Apr '19

05 Apr '19

Hello! On my server PC i have Centos 7 installed. CentOS Linux release 7.6.1810. There are four arrays RAID1 (software RAID) md124 - /boot/efi md125 - /boot md126 - /bd md127 - / I have configured booting from both drives, everything works fine if both drives are connected. But if I disable any drive from which RAID1 is built the system crashes, there is a partial boot and as a result the Entering emergency mode. By all rules RAID1 in case of similar failure of one of disks the system has to recognize this moment at loading, analyze that from the array only one disk is available and forcibly assemble inactive RAID array in case it is degraded in the mode when the second disk is missing may be... In Debian system this problem does not occur, the initramfs runs the script /scripts/local-block/mdadm builds the array from one dostoinogo disc ( lack of drive is not important, it's either a drive failure or disconnection from power-random or not random). In this script You can see the following ...... if [ "$COUNT" = "$MAX" ] then # Poor man's mdadm-last-resort@.service for incremental devices mdadm -q --run /dev/md?* # And last try for all others mdadm -q --assemble --scan --run rm -f /run/count.mdadm.initrd .... Why in server Centos 7 this problem is still not solved? Will this be fixed in upcoming releases? Best Regards AndersonGH

3 6

Ark vs. RAR files under CentOS 7
by Nicolas Kovacs 05 Apr '19

05 Apr '19

Hi, Over the past weeks, I've configured and fine-tuned a bells-and-whistles desktop based on CentOS 7 and KDE, which I've documented in detail on my blog: * https://www.microlinux.fr/poste-de-travail-entreprise-centos-7-kde/ So far I have one single thing that's not working. It's a little detail, but I'm sure it will come bite me, since I know some of my users need this functionality. Ark (KDE's archive manager) can't handle RAR files, even though unrar is installed under the hood. It looks like I have to rebuild Ark to get this functionality. Before I do that, I thought I'd rather ask if there is a more straightforward solution to this. Some third-party repositories (like Nux-Dextop) offer rebuilt packages like k3b-freeworld or audacity-freeworld with extended functionality. Does anybody know of an ark-freeworld package that's out there somewhere? Cheers from the sunny South of France, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

1 0

Kickstart putting /boot on sda2 (anaconda partition enumeration)?
by Bryce Evans 04 Apr '19

04 Apr '19

Does anyone know how anaconda partitioning enumerates disk partitions when specified in kickstart? I quickly browsed through the anaconda installer source on github but didn't see the relevant bits. I'm using the centOS 6.10 anaconda installer. Somehow I am ending up with my swap partition on sda1, /boot on sda2, and root on sda3. for $REASONS I want /boot to be the partition #1 (sda1) My kickstart storage config looks like this: bootloader --location=mbr --driveorder=sda,sdb zerombr ignoredisk --only-use=sda,sdb clearpart --all --drives=sda,sdb part raid.boot0 --size 1000 --ondrive=sda part raid.swap0 --size 8192 --ondrive=sda part raid.root0 --size 8000 --grow --ondrive=sda part raid.boot1 --size 1000 --ondrive=sdb part raid.swap1 --size 8192 --ondrive=sdb part raid.root1 --size 8000 --grow --ondrive=sdb raid /boot --fstype ext4 --device md0 --level=RAID1 raid.boot1 raid.boot0 raid swap --fstype swap --device md1 --level=RAID1 raid.swap1 raid.swap0 raid / --fstype ext4 --device md2 --level=RAID1 raid.root1 raid.root0 The anaconda-ks.cfg file that gets written out to /root (after kickstart finishes) looks like this: #zerombr # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work #clearpart --all --drives=sda,sdb #ignoredisk --only-use=sda,sdb #raid /boot --fstype=ext4 --level=1 --device=md0 raid.008018 raid.008002 #raid swap --level=1 --device=md1 raid.008017 raid.008001 #raid / --fstype=ext4 --level=1 --device=md2 raid.008019 raid.008003 #part raid.008001 --size=8192 #part raid.008002 --size=1000 #part raid.008003 --grow --size=8000 #part raid.008017 --size=8192 #part raid.008018 --size=1000 #part raid.008019 --grow --size=8000 I'm assuming that my swap is being put on sda1 because for some reason that partition gets the lowest numeric value in the name (raid.008001) But I don't see why that is happening, nor am I sure how to tell anaconda that I want /boot on the first partition (other than doing it in %pre) I cannot specify the 'onpart=sda1' option because I use 'clearpart' in the script, and according to the docs: "If the clearpart command is used, then the --onpart command cannot be used on a logical partition." The partition table on disk ends up looking as such: bash-4.1# parted /dev/sda GNU Parted 2.1 Using /dev/sda Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) p Model: HP LOGICAL VOLUME (scsi) Disk /dev/sda: 480GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 8591MB 8590MB primary raid 2 8591MB 9640MB 1049MB primary ext4 boot, raid 3 9640MB 480GB 470GB primary raid Anyone know where I should be looking, or have a workaround besides doing my partitioning in %pre? Thanks

3 2

Re: [CentOS] nobody:nobody
by Mark LaPierre 03 Apr '19

03 Apr '19

On 4/3/19 6:43 AM, mark wrote: > On 04/02/19 20:21, Mark LaPierre wrote: >> Hey Y'all, >> >> For the last week or more I've been trying to get NFS and OpenLDAP to >> play nice with each other. I've pretty much worn the Google machine >> out trying to find a solution. I've found several that said "Solved" >> but none of those solutions solved my nobody:nobody problem. >> >> In the past I've used NFS in conjunction with NIS to share home >> directories from my NFS server but I read that NIS is deprecated in >> favor of LDAP so, being a sucker for new ideas, I decided I would use >> LDAP too like the big boys do. I think I'm regretting this decision. >> Now the question: >> >> Is there something I need to configure on the client side of the >> relationship that all the Google wisdom has failed to mention? All the > > I'd assume: have you edited /etc/idmapd.conf, and at least put in your > domain? Then started the imapd daemon? > > Btw, when you go to C 7, there's no imapd daemon, but you still need to > edit that file. > > mark >> guides/tutorial/etc... talk extensively about configuring the server, >> many giving conflicting information, but have nothing to say about the >> client. I've even found a couple that talk about configuring CentOS 6 >> but contain commands found only in CentOS 7. Makes one go hmmm? >> >> Here's the basic details: >> Server: >> CentOS 6 >> openldap-2.4.40-16.el6.i686 >> openldap-clients-2.4.40-16.el6.x86_64 >> perl-LDAP-0.40-3.el6.noarch >> sssd-ldap-1.13.3-60.el6_10.2.x86_64 >> openldap-2.4.40-16.el6.x86_64 >> openldap-servers-2.4.40-16.el6.x86_64 >> python-ldap-2.3.10-1.el6.x86_64 >> apr-util-ldap-1.3.9-3.el6_0.1.x86_64 >> smbldap-tools-0.9.6-4.el6.noarch >> nfs-utils-lib-1.1.5-13.el6.x86_64 >> nfs4-acl-tools-0.3.3-8.el6.x86_64 >> nfs-utils-1.2.3-78.el6_10.1.x86_64 >> >> Client: >> CentOS 7 KVM VM running on the server >> sssd-ldap-1.16.2-13.el7_6.5.x86_64 >> python-ldap-2.4.15-2.el7.x86_64 >> openldap-2.4.44-21.el7_6.x86_64 >> nfs4-acl-tools-0.3.3-19.el7.x86_64 >> nfs-utils-1.3.0-0.61.el7.x86_64 >> libnfsidmap-0.25-19.el7.x86_64 >> >> Both machines are fully updated. >> >> Would you like to see any of the myriad of configuration files for >> these applications? Just ask and you shall receive. Please be sure >> to tell me if you want the file from the server or the client hey. >> > > Content of idmapd.conf: Server: [General] #Verbosity = 0 # The following should be set to the local NFSv4 domain name # The default is the host's DNS domain name. #Domain = local.domain.edu Domain = peach.patch.mylan Client: [General] #Verbosity = 0 # The following should be set to the local NFSv4 domain name # The default is the host's DNS domain name. #Domain = local.domain.edu Domain = poppy.patch.mylan Now one more question. The imap daemon is a mail server. How is it that I need a mail server running to make LDAP and NFS work? Doesn't seem to make sense to me. -- _ °v° /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****

4 5

nobody:nobody
by Mark LaPierre 03 Apr '19

03 Apr '19

Hey Y'all, For the last week or more I've been trying to get NFS and OpenLDAP to play nice with each other. I've pretty much worn the Google machine out trying to find a solution. I've found several that said "Solved" but none of those solutions solved my nobody:nobody problem. In the past I've used NFS in conjunction with NIS to share home directories from my NFS server but I read that NIS is deprecated in favor of LDAP so, being a sucker for new ideas, I decided I would use LDAP too like the big boys do. I think I'm regretting this decision. Now the question: Is there something I need to configure on the client side of the relationship that all the Google wisdom has failed to mention? All the guides/tutorial/etc... talk extensively about configuring the server, many giving conflicting information, but have nothing to say about the client. I've even found a couple that talk about configuring CentOS 6 but contain commands found only in CentOS 7. Makes one go hmmm? Here's the basic details: Server: CentOS 6 openldap-2.4.40-16.el6.i686 openldap-clients-2.4.40-16.el6.x86_64 perl-LDAP-0.40-3.el6.noarch sssd-ldap-1.13.3-60.el6_10.2.x86_64 openldap-2.4.40-16.el6.x86_64 openldap-servers-2.4.40-16.el6.x86_64 python-ldap-2.3.10-1.el6.x86_64 apr-util-ldap-1.3.9-3.el6_0.1.x86_64 smbldap-tools-0.9.6-4.el6.noarch nfs-utils-lib-1.1.5-13.el6.x86_64 nfs4-acl-tools-0.3.3-8.el6.x86_64 nfs-utils-1.2.3-78.el6_10.1.x86_64 Client: CentOS 7 KVM VM running on the server sssd-ldap-1.16.2-13.el7_6.5.x86_64 python-ldap-2.4.15-2.el7.x86_64 openldap-2.4.44-21.el7_6.x86_64 nfs4-acl-tools-0.3.3-19.el7.x86_64 nfs-utils-1.3.0-0.61.el7.x86_64 libnfsidmap-0.25-19.el7.x86_64 Both machines are fully updated. Would you like to see any of the myriad of configuration files for these applications? Just ask and you shall receive. Please be sure to tell me if you want the file from the server or the client hey. -- _ °v° /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****

2 1

CentOS-announce Digest, Vol 170, Issue 1
by centos-announce-request＠centos.org 02 Apr '19

02 Apr '19

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 of Gluster 6 on CentOS Linux 7 x86_64 (Niels de Vos) 2. Announcing the release of Gluster 6 on CentOS Linux 6 x86_64 (Niels de Vos) 3. CEBA-2019:0689 CentOS 6 tzdata BugFix Update (Johnny Hughes) 4. CESA-2019:0672 Critical CentOS 6 firefox Security Update (Johnny Hughes) 5. CESA-2019:0680 Important CentOS 6 thunderbird Security Update (Johnny Hughes) 6. CESA-2019:0671 Critical CentOS 7 firefox Security Update (Johnny Hughes) 7. CESA-2019:0681 Important CentOS 7 thunderbird Security Update (Johnny Hughes) 8. CESA-2019:0679 Important CentOS 7 libssh2 Security Update (Johnny Hughes) 9. CEBA-2019:0689 CentOS 7 tzdata BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 28 Mar 2019 15:48:42 +0100 From: Niels de Vos <ndevos(a)redhat.com> To: centos-announce(a)centos.org Subject: [CentOS-announce] Announcing the release of Gluster 6 on CentOS Linux 7 x86_64 Message-ID: <20190328144842.GD2572(a)ndevos-x270.lan.nixpanic.net> Content-Type: text/plain; charset="us-ascii" I am happy to announce the General Availability of Gluster 6 for CentOS 7 on x86_64. These packages are following the upstream Gluster Community releases, and will receive monthly bugfix updates. Gluster 6 is expected to receive updates until the end of March 2020. The maintanance and release schedule can be found at: https://www.gluster.org/release-schedule/ Users of CentOS 7 can now simply install Gluster 6 with only these two commands: # yum install centos-release-gluster # yum install glusterfs-server The centos-release-gluster package is delivered via CentOS Extras repos. This contains all the metadata and dependency information, needed to install Gluster 6. The actual package that will get installed is centos-release-gluster6. Users of Gluster 4.1 can stay on that release until June 2019. 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 problems, 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

git.centos.org migration, please read
by Fabian Arrotin 02 Apr '19

02 Apr '19

As pre-announced a long time ago (see https://lists.centos.org/pipermail/centos-devel/2018-October/016997.html) , we'll migrate git.centos.org to a new host/platform (pagure/repospanner) The current migration is planned for : April 8th (more details later about the exact hour, as we need to have acknowledgement from all involved people). Instead of writing a long email, we instead decided to put focus on a dedicated page, that will , after migration, replace the current one. - current one : https://wiki.centos.org/Sources - new one : https://wiki.centos.org/Sources_new After migration, we'll rename/swap both pages, to reflect the changes that will go live next monday. As a reminder : we had https://git.stg.centos.org and https://src.stg.fedoraproject.org in "sync" since October, replicating to each other instance. We also got good feedback from CentOS contributors who started to use it to test the new features, including the automatic ACL for protected branches, and some pkgs from CentOS distro were even built through that staging instance , to validate that it was working the way it was designed. So please read that wiki page (https://wiki.centos.org/Sources_new) and we can also add/correct things in that page, based on future feedback. WRT existing repositories : they'll all be imported (already validated) but if you had access (RWC) to a specific project, you'll have *first* to login with your ACO account, and then ask to be added to the ACL, as well as changing the "git remote" url, to point to ssh (all pushes are going through ssh, as previous gitblit/git.centos.org allowed https pushes) PS: while the date is normally April 8th, if there is a chance that we'd need to change that date, we'll post an update in this thread PS2 : Fedora infra is in "freeze" mode , meaning that during our migration, we'll start with only the CentOS branches, and Fedora will import their repositories/branches in the existing repospanner cluster later, and so the Fedora/EPEL branches will then automatically appear on https://git.centos.org -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 0

udev rename NIC failed
by wuzhouhui 01 Apr '19

01 Apr '19

Hi, Sometimes, I found one of my Mellanox NIC renamed to rename6, instead of eth1. The right names of NICs in my system should be: eth0 Mellanox NIC eth1 Mellanox NIC eth2 Intel NIC eth3 Intel NIC eth4 Intel NIC eth5 Intel NIC eth0 and eth1 will combined as bond1 with mode 4. However, the current names are: eth0 Mellanox NIC rename6 Mellanox NIC eth1 Intel NIC eth2 Intel NIC eth4 Intel NIC eth5 Intel NIC And bond1 still consist of eth0 and eth1, but eth1 is Intel NIC, instead of Mellanox NIC. Following is selected log from /var/log/messages: ... kernel: [ 23.098148] i40e: Intel(R) 40-10 Gigabit Ethernet Connection Network Driver - version 2.2.4 kernel: [ 23.098554] i40e: Copyright(c) 2013 - 2017 Intel Corporation. kernel: [ 23.114270] i40e 0000:1a:00.0: fw 3.1.57069 api 1.5 nvm 3.33 0x80000f09 255.65535.255 kernel: [ 23.118320] i40e 0000:1a:00.0: MAC address: 28:41:c6:fb:c3:a2 kernel: [ 23.128007] i40e 0000:1a:00.0: MSI-X vector limit reached, attempting to redistribute vectors kernel: [ 23.133699] i40e 0000:1a:00.0: Added LAN device PF0 bus=0x1a dev=0x00 func=0x00 kernel: [ 23.134414] i40e 0000:1a:00.0: Features: PF-id[0] VFs: 32 VSIs: 34 QP: 56 RSS FD_ATR FD_SB NTUPLE CloudF DCB VxLAN NVGRE PTP VEPA kernel: [ 23.148085] i40e 0000:1a:00.1: fw 3.1.57069 api 1.5 nvm 3.33 0x80000f09 255.65535.255 kernel: [ 23.151729] i40e 0000:1a:00.1: MAC address: 28:41:c6:fb:c3:a3 kernel: [ 23.160694] i40e 0000:1a:00.1: MSI-X vector limit reached, attempting to redistribute vectors kernel: [ 23.166232] i40e 0000:1a:00.1: Added LAN device PF1 bus=0x1a dev=0x00 func=0x01 kernel: [ 23.167280] i40e 0000:1a:00.1: Features: PF-id[1] VFs: 32 VSIs: 34 QP: 56 RSS FD_ATR FD_SB NTUPLE CloudF DCB VxLAN NVGRE PTP VEPA kernel: [ 23.185771] i40e 0000:1a:00.2: fw 3.1.57069 api 1.5 nvm 3.33 0x80000f09 255.65535.255 kernel: [ 23.193232] i40e 0000:1a:00.2: MAC address: 28:41:c6:fb:c3:a4 kernel: [ 23.207420] i40e 0000:1a:00.2: MSI-X vector limit reached, attempting to redistribute vectors kernel: [ 23.217474] i40e 0000:1a:00.2: Added LAN device PF2 bus=0x1a dev=0x00 func=0x02 kernel: [ 23.219339] i40e 0000:1a:00.2: Features: PF-id[2] VFs: 32 VSIs: 34 QP: 56 RSS FD_ATR FD_SB NTUPLE CloudF DCB VxLAN NVGRE PTP VEPA kernel: [ 23.237958] i40e 0000:1a:00.3: fw 3.1.57069 api 1.5 nvm 3.33 0x80000f09 255.65535.255 kernel: [ 23.242039] i40e 0000:1a:00.3: MAC address: 28:41:c6:fb:c3:a5 kernel: [ 23.258645] i40e 0000:1a:00.3: MSI-X vector limit reached, attempting to redistribute vectors kernel: [ 23.270395] i40e 0000:1a:00.3: Added LAN device PF3 bus=0x1a dev=0x00 func=0x03 kernel: [ 23.271911] i40e 0000:1a:00.3: Features: PF-id[3] VFs: 32 VSIs: 34 QP: 56 RSS FD_ATR FD_SB NTUPLE CloudF DCB VxLAN NVGRE PTP ... kernel: [ 250.279739] Compat-mlnx-ofed backport release: f8de107 kernel: [ 250.280006] Backport based on mlnx_ofed/mlnx-ofa_kernel-4.0.git f8de107 kernel: [ 250.280261] compat.git: mlnx_ofed/mlnx-ofa_kernel-4.0.git kernel: [ 250.287865] mlx5_core 0000:3b:00.0: firmware version: 14.23.1020 kernel: [ 250.293492] tun: Universal TUN/TAP device driver, 1.6 kernel: [ 250.293731] tun: (C) 1999-2004 Max Krasnyansky <maxk(a)qualcomm.com> kernel: [ 250.360407] nbd: registered device at major 43 kernel: [ 250.367659] nf_conntrack version 0.5.0 (65536 buckets, 262144 max) kernel: [ 250.373103] VFIO - User Level meta-driver version: 0.3 kernel: [ 250.455352] EXT4-fs (sda2): re-mounted. Opts: (null) kernel: [ 250.489486] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) kernel: [ 251.202430] (0000:3b:00.0): E-Switch: Total vports 9, per vport: max uc(1024) max mc(16384) kernel: [ 251.343924] mlx5_core 0000:3b:00.1: firmware version: 14.23.1020 kernel: [ 252.273017] (0000:3b:00.1): E-Switch: Total vports 9, per vport: max uc(1024) max mc(16384) kernel: [ 252.411436] mlx5_core 0000:3b:00.0: MLX5E: StrdRq(1) RqSz(8) StrdSz(64) RxCqeCmprss(0) kernel: [ 252.575886] mlx5_core 0000:3b:00.1: MLX5E: StrdRq(1) RqSz(8) StrdSz(64) RxCqeCmprss(0) kernel: [ 252.814797] mlx5_ib: Mellanox Connect-IB Infiniband driver v4.2-1.2.0 kernel: [ 343.507623] Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) kernel: [ 343.508800] bonding: bond1 is being created... kernel: [ 343.525710] bond1: Setting MII monitoring interval to 100 kernel: [ 343.526101] bond1: Setting xmit hash policy to layer2+3 (2) kernel: [ 343.528088] IPv6: ADDRCONF(NETDEV_UP): bond1: link is not ready kernel: [ 343.543330] bond1: Adding slave eth0 kernel: [ 343.834246] mlx5_core 0000:3b:00.0 eth0: mlx5e_update_carrier:153: Link up kernel: [ 343.837195] bond1: Enslaving eth0 as a backup interface with an up link kernel: [ 343.852012] bond1: Adding slave eth1 kernel: [ 343.852264] i40e 0000:1a:00.1 eth1: set new mac address 98:03:9b:83:cd:5e kernel: [ 343.860085] bond1: Enslaving eth1 as a backup interface with a down link ... udevd-work[15328]: error changing netif name 'eth1' to 'eth3': Device or resource busy .... It seems that udevd failed to rename eth1 to eth3, because eth1 has been enslaved by bond1. Does anyone know how to handle this problem? i40e: 2.2.4 CentOS: 6.3 mlx5_core: 4.2 Thanks.

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss April 2019