- Discuss - lists.centos.org

CentOS 7.4 fails to boot as Xen PV guest: resurfaces (now also) with centosplus kernel 693.11.6.el7
by David Groep 08 Jan '18

08 Jan '18

Dear all, Maybe I'm the only one - so before filing it as a bug: it appears that the latest set of kernel patches in 3.10.0-693.11.6.el7 makes issue 0013763 "CentOS 7.4 kernel (3.10.0-693*) fails to boot as Xen PV guest" re-surface *also* with the CentOS PLUS kernel. But maybe in a different way ... Thanks to the (great!) quick work on making the plus kernel available (in #14330, thanks for that!) I was able to test the following combinations: - 3.10.0-693.11.6.el7.centos.plus works fine on XenServer 7 HVM guests - 3.10.0-693.11.1.el7.centos.plus works fine on XenServer 7 XenPV guests - 3.10.0-693.11.6.el7.centos.plus crashes on boot for XS7 XenPV guests immediately after the boot stage where the PS/2 drivers are loaded Crashing does not depend on the amount of VM memory or #cores/sockets. Also, the tell-tale "mm/vmalloc.c" failure output is no longer present. The system 'just' crashes (with the kernel log lines as below) around the time of the i8042 controller probing. Obviously the stock upstream 3.10.0-693.11.6.el7 crashes as well for XS7 XenPV guests, but that was to be expected as per 0013763. It crashes in the same way, around the time of the i8042 probes. Can anyone (maybe bill_mcgonigle?) reproduce the issue? Did the KPTI patches break the XenPV fixes in CentOS Plus per 13763? Or is this a new XenPV issue? Interestingly, the crash is now sudden and (even at loglevel=7) without further information. The crash after the i8042/mousedev is (I think) unrelated to these devices, since the system crashes in the same way even with "i8042.debug i8042.nokbd i8042.noaux i8042.dumbkbd i8042.nomux i8042.noloop i8042.nopnp psmouse.proto=bare" added to the kernel command line (and then you don't see any PS/2 and mousedev). So something immediately after the mousy things triggers the crash: 0.2293541 io scheduler cfq registered 0.2295071 pci_hotplug: PCI Hot Plug PCI Core version: 0.5 0.2295241 pciehp: PCI Express Hot Plug Controller Driver version: 0.4 0.2301241 Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled 0.2306111 Non-volatile memory driver u1.3 0.2306601 Linux agpgart interface u0.103 0.2307641 crash memory driver: version 1.1 0.2308301 rdac: device handler registered 0.2308741 hp_sw: device handler registered 0.2308851 emc: device handler registered 0.2308941 alua: device handler registered 0.2309491 libphy: Fixed MDIO Bus: probed 0.2310301 ehci_hcd: USB 2.0 'Enhanced' Host Controller CEHCI) Driver 0.2310471 ehci-pci: EHCI PCI platform driver 0.2310671 ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver 0.2310791 ohci-pci: OHCI PCI platform driver 0.2310951 uhci_hcd: USB Universal Host Controller Interface driver 0.2311581 usbcore: registered new interface driver usbserial 0.2311741 usbcore: registered new interface driver usbserial_generic 0.2311941 usbserial: USB Serial support registered for generic 0.2312291 i8042: PNP: No PS/2 controller found. Probing ports directly. 1.2427071 i8042: No controller found 1.2428571 mousedev: PS/2 mouse device common for all mice [HANG - VM shuts down] although sometimes the boot stops at "i8042: PNP: No PS/2 controller found. Probing ports directly." and does not make it to the "mouse" bit. Anyone found similar behaviour? Thanks a lot! DavidG. -- David Groep ** Nikhef, Dutch National Institute for Subatomic Physics, PDP programme ** ** Room: H1.50 Phone: +31 20 5922179, PObox 41882, NL-1009DB Amsterdam NL ** ** PGP: 0xD80134C2 308E076A FP: 2facebea12803ba145685a21d80134c2308e076a **

3 2

CVE-2017-5715, CVE-2017-5753 and CVE-2017-5754
by Walter H. 07 Jan '18

07 Jan '18

Hello, will there be updates for these CVEs for CentOS 6? Thanks, Walter

6 5

Bug in gnome-control-center and network edit module in Centos 7.4
by Gregory P. Ennis 07 Jan '18

07 Jan '18

Everyone, I have been having a problem in setting up gateway/routers with Centos 7.4 machine and finally figured out the problem today. I am not sure if this bug occurred first in 7.3 but it is definitely in 7.4. I have other gateway routers that were created at the beginning of the Centos 7 that have been working perfectly even through the upgrades to 7.3 and 7.4, but the new gateways I have created would not work. It seems simple now that I have the solution, but it took me an embarrassingly too long a time to debug and resolves the problem. The problem appears to me to be a bug in the new gnome-command-center when using the network module to add or edit network interfaces. The problem that I identified is that the network module requires the user to enter a gateway ip address even on the internal networks. Normally the gateway ip address is left blank on the internal interfaces, and is only filled in on the external interface. I was never able to get the gui using the network editor within the gnome-control-center to be able to remove the gateway ip address from the; internal interfaces; I was forced to enter something, and I entered the external gateway ip address. However, to bypass and fix this problem, the gateway ip address is easily removed by editing the appropriate file or files in : /etc/sysconfig/network-scripts/ifcfg-emp3s0 /etc/sysconfig/network-scripts/ifcfg-emp4s0 The network editor in the gnome-control-center module required the entry of a gateway ip address. I had entered the gateway for the external ip address in this field, and all I did to solve the problem is to delete "GATEWAY=x.x.x.x" from both of the above files. This allowed both of the new gateway machines I have recently created to work like they should. Hope this saves someone else some time. Greg

1 0

Intel Flaw
by Chris Olson 05 Jan '18

05 Jan '18

How does the latest Intel flaw relate to CentOS 6.x systems that run under VirtualBox hosted on Windows 7 computers? Given the virtual machine degree of separation from the hardware, can this issue actually be detected and exploited in the operating systems that run virtually? If there is a slow down associated with the fix, how much might it impact the virtual systems?

3 2

CentOS-announce Digest, Vol 155, Issue 1
by centos-announce-request＠centos.org 05 Jan '18

05 Jan '18

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-2018:0007 Important CentOS 7 kernel Security Update (Karanbir Singh) 2. CESA-2018:0012 Important CentOS 7 microcode_ctl Security Update (Karanbir Singh) 3. CESA-2018:0014 Important CentOS 7 linux-firmware Security Update (Karanbir Singh) 4. [Infra] - planned outage : All services (Fabian Arrotin) 5. CESA-2018:0013 Important CentOS 6 microcode_ctl Security Update (Johnny Hughes) 6. CESA-2018:0008 Important CentOS 6 kernel Security Update (Johnny Hughes) 7. CESA-RHSA-2018:0024 Important CentOS 6 qemu-kvm Security Update (Johnny Hughes) 8. CESA-2018:0030 Important CentOS 6 libvirt Security Update (Johnny Hughes) 9. CESA-2018:0029 Important CentOS 7 libvirt Security Update (Johnny Hughes) 10. CESA-2018:0023 Important CentOS 7 qemu-kvm Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 4 Jan 2018 11:36:27 +0000 From: Karanbir Singh <kbsingh(a)centos.org> To: CentOS Announcements List <centos-announce(a)centos.org> Subject: [CentOS-announce] CESA-2018:0007 Important CentOS 7 kernel Security Update Message-ID: <d07d0b4b-cc89-329a-f517-08b3cd1bae7d(a)centos.org> Content-Type: text/plain; charset=utf-8 CentOS Errata and Security Advisory 2018:0007 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:0007 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 320ab3bd00bd1f051c69f65f2d4cd6ab64585f977d9cd7a52e64e8f8147894fc kernel-3.10.0-693.11.6.el7.x86_64.rpm 0eefdec5447d3ed2781f30d093e22f4654e8af201e1e8058a57876d1baf2ee64 kernel-abi-whitelists-3.10.0-693.11.6.el7.noarch.rpm 5137d0db8632342edfb355ce5bb0a4b4b80d5ffd4b9950bb8dcfcd78e4b8a9dc kernel-debug-3.10.0-693.11.6.el7.x86_64.rpm 882a6522bdafaa697173ff7adedd2cd6ceee5c4a6aa0cd1cb4cf042789420c78 kernel-debug-devel-3.10.0-693.11.6.el7.x86_64.rpm 9c0d7753c649d68cd25b212ee573cec37dc2211891444224e502128fcffdf301 kernel-devel-3.10.0-693.11.6.el7.x86_64.rpm d2005d6a85f2ddd627290dd4cd4d2084215ef45cd8b3f66077b68fe2b0cce61e kernel-doc-3.10.0-693.11.6.el7.noarch.rpm 34d8682b2df1e47c9675f913fbfb129420cce219beaf7985c607a69ccdb3e064 kernel-headers-3.10.0-693.11.6.el7.x86_64.rpm fd3eaf598546bcb502e5e7293d0301b48774c9358dd320b7e53bd042dfae7094 kernel-tools-3.10.0-693.11.6.el7.x86_64.rpm 3c53034adc4c942a02f1dd72f0adf688f558867caf086b5b239169262b75f570 kernel-tools-libs-3.10.0-693.11.6.el7.x86_64.rpm 91153ae59d0acf585201b9a5b453ed8e6504651bf114e3c21c725ce42c8675c5 kernel-tools-libs-devel-3.10.0-693.11.6.el7.x86_64.rpm 8ef1d6c1ef77af60bbb680fa58b1d15f7901c21220c7e5db05edbbbb56f7b17c perf-3.10.0-693.11.6.el7.x86_64.rpm b1f7bf92063bce0cec6286845686bc6ef96db126bdaa8987703b21a736a1a509 python-perf-3.10.0-693.11.6.el7.x86_64.rpm Source: b7756ceda51a35942e03d553f0ec6049ba2520c89e0d66e8e2cdae88f6db0d6a kernel-3.10.0-693.11.6.el7.src.rpm Note: 1) This is a widespread issue with potentially huge impact, we appreciate any help in spreading the word around so maximum number of users are able to find out, and patch their systems. 2) Upstream is curating information around this issue at https://access.redhat.com/security/vulnerabilities/speculativeexecution - information on that page would be helpful for most people on CentOS Linux as well. 3) Please reach out to us at #centos on irc.freenode.net for any feedback, comments, questions or concerns. -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc ------------------------------ Message: 2 Date: Thu, 4 Jan 2018 11:40:52 +0000 From: Karanbir Singh <kbsingh(a)centos.org> To: CentOS Announcements List <centos-announce(a)centos.org> Subject: [CentOS-announce] CESA-2018:0012 Important CentOS 7 microcode_ctl Security Update Message-ID: <ebbc916f-bc12-0a57-4228-cffde1956cdd(a)centos.org> Content-Type: text/plain; charset=utf-8 CentOS Errata and Security Advisory 2018:0012 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:0012 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: ccb96b47da6ce420c39a38d09e57adcc7ab3696c721d081fee94298f19fc6cab microcode_ctl-2.1-22.2.el7.x86_64.rpm Source: 589fe27443e43fd6549f56e39968cf515d1cd2448dc922bf0cc980fc651f880d microcode_ctl-2.1-22.2.el7.src.rpm -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc ------------------------------ Message: 3 Date: Thu, 4 Jan 2018 11:47:37 +0000 From: Karanbir Singh <kbsingh(a)centos.org> To: CentOS Announcements List <centos-announce(a)centos.org> Subject: [CentOS-announce] CESA-2018:0014 Important CentOS 7 linux-firmware Security Update Message-ID: <d1551ccd-4d12-3bc1-b1d9-9d9bcac949ae(a)centos.org> Content-Type: text/plain; charset=utf-8 CentOS Errata and Security Advisory 2018:0014 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:0014 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: dad80246e21277864476614560cae38820cc147b9ceb44dd0d1776e3935b05df iwl1000-firmware-39.31.5.1-57.el7.noarch.rpm dbb0a9095b11d9af2b8db8f160e1004ead7f5b07add216df63c843e2ac470259 iwl100-firmware-39.31.5.1-57.el7.noarch.rpm 1ff7d3347a2759b15818d71817d5055643bcc4a9f7b091d186006948cf75a3f0 iwl105-firmware-18.168.6.1-57.el7.noarch.rpm e807e3cc6faa0be6df4675d9810db6292a534bc0c3f9c714dcc7c92fed0ba4fd iwl135-firmware-18.168.6.1-57.el7.noarch.rpm d24d6225079ec7d7870ca022226686c67d70f9d034af1167b36570e8506fdf02 iwl2000-firmware-18.168.6.1-57.el7.noarch.rpm 2eebc03a19e54f4b072f21886f02e43bdac41ff5e8290d9eb7c62e3ef1ed7352 iwl2030-firmware-18.168.6.1-57.el7.noarch.rpm d154f7ddb5ccca2772604f907d7a3c06e1b2f95b35665e81363226c98a9115c4 iwl3160-firmware-22.0.7.0-57.el7.noarch.rpm aaba72a90838c5dee3373004ee00530e3f43fbd0b9cd634223d02ea500c3cd6d iwl3945-firmware-15.32.2.9-57.el7.noarch.rpm f18caaca13e3ed06f43483870ecdc57ff6c8796bf3cb8375822519d0ced3b659 iwl4965-firmware-228.61.2.24-57.el7.noarch.rpm 257fe78f77c4e1c5c9bea3873421411c77020c12d907b1d7c511e7e96eaa3190 iwl5000-firmware-8.83.5.1_1-57.el7.noarch.rpm e9edf8b527e94302b0572ce1e3f0e91d62e9d11f74cf3ad1c0350c8e23684acc iwl5150-firmware-8.24.2.2-57.el7.noarch.rpm b63dc1829cca0afbb4a6e5681cebf54509cc4c507ab0bad6553856c4063616ed iwl6000-firmware-9.221.4.1-57.el7.noarch.rpm 8abb25db6c0dcedfa0c11f87028521f5098a88374dcb99376f485bda4596a567 iwl6000g2a-firmware-17.168.5.3-57.el7.noarch.rpm d35951cc21bfccae24e6611ad03901ac1fe0183614add09b2b04528a72d3ea4b iwl6000g2b-firmware-17.168.5.2-57.el7.noarch.rpm 8a2cd4dbabdbdcc36ed46a2529c07b9873716981610082db5b40ae134e12ee3d iwl6050-firmware-41.28.5.1-57.el7.noarch.rpm 357388ce0000543ce9714ebffbadc15ab1e3969c4f1256d6f1132f619c82afdc iwl7260-firmware-22.0.7.0-57.el7.noarch.rpm 75a235701d30e685ca87945e0dd583bda08e254f9078d50b3d466af4d5e3cfe6 iwl7265-firmware-22.0.7.0-57.el7.noarch.rpm 16164fc1c681f5a04a14879041e66855aa434c9c9c30d722a273519896b0f7b7 linux-firmware-20170606-57.gitc990aae.el7.noarch.rpm Source: ffa8541e30f72d79d88740d418943668d1da9535ebbee0df3c61ad4d7d576cdc linux-firmware-20170606-57.gitc990aae.el7.src.rpm -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc ------------------------------ Message: 4 Date: Thu, 4 Jan 2018 14:21:49 +0100 From: Fabian Arrotin <arrfab(a)centos.org> To: "The CentOS developers mailing list." <centos-devel(a)centos.org>, centos-announce(a)centos.org Subject: [CentOS-announce] [Infra] - planned outage : All services Message-ID: <eb940deb-7311-381d-c2f4-ede324e9ffe4(a)centos.org> Content-Type: text/plain; charset="utf-8" Due to important security updates that we need to apply within the whole CentOS infra, please be aware that some nodes/services will be unresponsive during that maintenance window. As it targets both CentOS 6 and CentOS 7, we'll probably apply those updates ASAP but we'll not notify for each impacted service, so this announce will cover all impacted services during the next hours/days. Thanks for your comprehending and patience. on behalf of the Infra team, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 0

possible issue with nvidia and new patches?
by Zube 04 Jan '18

04 Jan '18

Twitter user stintel, in this thread: https://twitter.com/stintel/status/948499157282623488 mentions a possible problem with the new patches and the nvidia driver: "As if the @Intel bug isn't bad enough, #KPTI renders @nvidia driver incompatible due to GPL-only symbol 'cpu_tlbstate'. #epicfail" Also: https://twitter.com/tomasz_gwozdz/status/948590364679655429 https://twitter.com/BitsAndChipsEng/status/948578609761054721 Cheers, Zube

3 2

Issues with qt-creator from EPEL 7
by Toralf Lund 04 Jan '18

04 Jan '18

Hi, Is anyone here using the "EPEL" package for qt-creator on CentOS 7? I'm having a few issues with it, and I though I'd run them by the list before I try Qt Forums or whatever (since they could be specific to the above mentioned build.) Most notably, 1. If I click on an error message in the "Issues" list after compilation (to display source code related to the error), I sometimes get a "File not found" message *if the file in question is already open*. If I close the file and repeat, the same file opens just fine. 2. There is something slightly odd about the icons in the display. In particular, when I open the search panes, I sometimes get buttons with labels "Find Previous" and "Find Next", but at other times, those same buttons have arrow icons. Has anyone else seen something like this? - Toralf

1 0

Gtkcdlabel + cdlabelgen on CentOS 7 ?
by Nicolas Kovacs 03 Jan '18

03 Jan '18

Hi, I've been using the nifty little application Gtkcdlabel for making CD and DVD covers since 2005, if I remember correctly. Later versions are written in Python, and it's a graphical frontend to the cdlabelgen utility. The application doesn't look very well maintained, since the 1.15 release dates back to 2011. Nevertheless, I've been successfully running it on Slackware Linux until the latest 14.2 release. I'm currently trying to install it on CentOS 7, and I'm only having a partial success, with a showstopper. Here's what I could manage so far. The 'cdlabelgen' command line utility is available on EPEL, so I installed that. I downloaded Gtkcdlabel on the project site: http://gtkcdlabel.sourceforge.net/ The installation process takes you back 25 years, since it amounts to this: # tar xvjf gtkcdlabel-1.15.tar.bz2 -C / This installs the application in /usr/bin/gtkcdlabel.py along with a new desktop entry (and the ugliest icon on the planet). The application shows OK when running it, but PostScript file generation fails. I launched it from a terminal by invoking gtkcdlabel.py, filled out a few fields like Title and Subtitle and then clicked on Preview. Normally this is supposed to launch the PDF viewer (/usr/bin/evince in the default configuration). And it launches, except it gets stuck here, since nothing is generated. Under the hood, in my terminal, I get the following string of error messages: (libspectre) ghostscript reports: invalidfont -10 (libspectre) ghostscript reports: invalidfont -10 (libspectre) ghostscript reports: invalidfont -10 (libspectre) ghostscript reports: invalidfont -10 (libspectre) ghostscript reports: invalidfont -10 I checked, and ghostscript as well as ghostscript-fonts are installed. Which leaves me clueless. Any help would be greatly appreciated, since I've been using this application for years on a daily basis. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

3 8

Identifying Official CentOS AWS AMIs
by Paul Heinlein 02 Jan '18

02 Jan '18

I'm trying to automate identification of CentOS AWS images. It appears that official CentOS AMIs have an OwnerID value of 410186602215, but I'm not sure if that value is transient or specific to one or more AWS regions. Is there a maintainer lurking here that can confirm or deny? Here's the base query I'm testing: aws ec2 describe-images \ --owners 410186602215 \ --output text \ --query 'reverse(sort_by(Images, &CreationDate))[?starts_with(Description, `CentOS Linux 7`)].[ImageId, CreationDate, Description]' -- Paul Heinlein heinlein(a)madboa.com 45°38' N, 122°6' W

1 0

DHCP timeout and mysteriously dropping IP address
by Jason Edgecombe 02 Jan '18

02 Jan '18

Hi everyone, I'me having trouble with a CentOS 7 guest running on a Hyper-V host. For some reason, the CentOS guest randomly drops its IP address. Running "systemctl restart NetworkManager" on the console will restore IP connectivity without a reboot. I think that DHCP is timing out, but I'm not sure what to do about it. Is there a way to tell NetworkManager to keep trying after a timeout? Here are the versions of the kernel and NetworkManager: Kernel: 3.10.0-693.11.1.el7.x86_64 NetworkManager: 1.8.0-11.el7_4.x86_64 Here are some pertinent logs: Dec 23 03:30:26 myhost kernel: hv_utils: Using TimeSync version 3.0 Dec 23 03:30:27 myhost systemd: Time has been changed Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.3750] device (eth0): link connected Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.3762] device (eth0): DHCPv4 lease renewal requested Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.3889] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 7936 Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.3890] dhcp4 (eth0): state changed bound -> done Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.3899] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.4487] dhcp4 (eth0): dhclient started with pid 33165 Dec 23 03:30:33 myhost dhclient[33165]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 (xid=0x5cb111f1) Dec 23 03:30:33 myhost dhclient[33165]: DHCPACK from xxx.xxx.36.1 (xid=0x5cb111f1) Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5824] dhcp4 (eth0): address xxx.xxx.37.53 Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5825] dhcp4 (eth0): plen 23 (255.255.254.0) Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5826] dhcp4 (eth0): gateway xxx.xxx.36.1 Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5826] dhcp4 (eth0): lease time 7200 Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5826] dhcp4 (eth0): nameserver 'xxx.xxx.0.20' Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5826] dhcp4 (eth0): nameserver 'xxx.xxx.0.30' Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5826] dhcp4 (eth0): domain name 'example.com' Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5826] dhcp (eth0): domain search 'example.com.' Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5827] dhcp (eth0): domain search 'foo.example.com.' Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5827] dhcp (eth0): domain search 'dyn.example.com.' Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5827] dhcp4 (eth0): state changed unknown -> bound Dec 23 03:30:33 myhost dhclient[33165]: bound to xxx.xxx.37.53 -- renewal in 3368 seconds. Dec 23 03:30:33 myhost dbus-daemon: dbus[726]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Dec 23 03:30:33 myhost dbus[726]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Dec 23 03:30:33 myhost systemd: Starting Network Manager Script Dispatcher Service... Dec 23 03:30:33 myhost dbus[726]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Dec 23 03:30:33 myhost dbus-daemon: dbus[726]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Dec 23 03:30:33 myhost systemd: Started Network Manager Script Dispatcher Service. Dec 23 03:30:33 myhost nm-dispatcher: req:1 'dhcp4-change' [eth0]: new request (4 scripts) Dec 23 03:30:33 myhost nm-dispatcher: req:1 'dhcp4-change' [eth0]: start running ordered scripts... Dec 23 03:40:42 myhost kernel: hv_utils: Using TimeSync version 3.0 Dec 23 03:40:43 myhost systemd: Time has been changed Dec 23 03:40:49 myhost NetworkManager[788]: <info> [1514018449.4566] device (eth0): link connected Dec 23 03:40:49 myhost NetworkManager[788]: <info> [1514018449.4583] device (eth0): DHCPv4 lease renewal requested Dec 23 03:40:49 myhost NetworkManager[788]: <info> [1514018449.4693] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 33165 Dec 23 03:40:49 myhost NetworkManager[788]: <info> [1514018449.4694] dhcp4 (eth0): state changed bound -> done Dec 23 03:40:49 myhost NetworkManager[788]: <info> [1514018449.4703] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Dec 23 03:40:49 myhost NetworkManager[788]: <info> [1514018449.4781] dhcp4 (eth0): dhclient started with pid 33440 Dec 23 03:40:49 myhost dhclient[33440]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 (xid=0x2f112c1) Dec 23 03:40:52 myhost dhclient[33440]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 (xid=0x2f112c1) Dec 23 03:40:57 myhost dhclient[33440]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 (xid=0x2f112c1) Dec 23 03:41:02 myhost dhclient[33440]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 (xid=0xe5feb70) Dec 23 03:41:08 myhost dhclient[33440]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 (xid=0xe5feb70) Dec 23 03:41:18 myhost dhclient[33440]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 (xid=0xe5feb70) Dec 23 03:41:30 myhost dhclient[33440]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16 (xid=0xe5feb70) Dec 23 03:41:34 myhost NetworkManager[788]: <warn> [1514018494.9605] dhcp4 (eth0): request timed out Dec 23 03:41:34 myhost NetworkManager[788]: <info> [1514018494.9612] dhcp4 (eth0): state changed unknown -> timeout Dec 23 03:41:34 myhost NetworkManager[788]: <info> [1514018494.9713] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 33440 Dec 23 03:41:34 myhost NetworkManager[788]: <info> [1514018494.9714] dhcp4 (eth0): state changed timeout -> done Thanks, Jason --------------------------------------------------------------------------- Jason Edgecombe | Linux Administrator UNC Charlotte | The William States Lee College of Engineering 9201 University City Blvd. | Charlotte, NC 28223-0001 Phone: 704-687-1943 jwedgeco(a)uncc.edu | http://engr.uncc.edu | Facebook --------------------------------------------------------------------------- If you are not the intended recipient of this transmission or a person responsible for delivering it to the intended recipient, any disclosure, copying, distribution, or other use of any of the information in this transmission is strictly prohibited. If you have received this transmission in error, please notify me immediately by reply e-mail or by telephone at 704-687-1943. Thank you.

1 0

Re: [CentOS] OpenVPN server and firewalld
by Gianluca Cecchi 30 Dec '17

30 Dec '17

On Fri, Dec 29, 2017 at 10:32 AM, Kenneth Porter <shiva(a)sewingwitch.com> wrote: > How do I insert the iptables rule below using firewalld? > > I'm moving up from CentOS 6 to 7 on an office gateway and I'm trying to > get OpenVPN working to allow home workers to access PCs at the office. I've > got it all working but only by manually inserting an ACCEPT rule in the > FORWARD iptables chain: > > iptables -I FORWARD 3 -i tun+ -j ACCEPT > > This rule was extracted from my iptables firewall under CentOS6. The 3 > puts it after the accepts for established connections and loopback > connections, but before any firewalld sub-chains. With this I can connect > to an internal Windows 10 system with Remote Desktop. > > How can I inject this rule using firewalld, either as a direct rule or as > some more firewalld-approved kind of rule? > > Hello, in case your need is not covered by the "--add-service" and/or the "--add-port" you can still use a direct rule for it. I think it should be something like this to test: firewall-cmd --direct --add-rule ipv4 filter FORWARD 0 -i tun+ -j ACCEPT Manual page and some examples with man firewalld.direct The "iptables like" rule will be added into the pre-built chain named FORWARD_direct The 0 above means it is put at top of FORWARD_direct chain. In your example appears "3" and it is not clear what are lines 1 and 2. With iptables -L command you will see: # iptables -v -L FORWARD_direct Chain FORWARD_direct (1 references) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- tun+ any anywhere anywhere # With firewall-cmd you can see with # firewall-cmd --direct --get-all-rules ipv4 filter FORWARD 0 -i tun+ -j ACCEPT # If it works ok as expected, you can make it permanent with firewall-cmd --permanent --direct --add-rule ipv4 filter FORWARD 0 -i tun+ -j ACCEPT firewall-cmd --reload HIH digging into, Gianluca

2 1

CentOS 7 + KDE : post-installation script
by Nicolas Kovacs 29 Dec '17

29 Dec '17

Hi, I just spent two rainy days writing and fine-tuning a post-installation script for CentOS 7 and KDE. https://github.com/kikinovak/centos-7-desktop-kde I've just tested it on three different machines here, and it works quite nicely. Feel free to give it a spin and make some suggestions. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

2 3

Centos 7 and btrfs
by Matt 28 Dec '17

28 Dec '17

I am setting up a new test server. Doing a fresh install from CD onto a couple 4TB drives. Would like to try btrfs in a RAID 1 format. Are there any how to's on how to do that?

4 4

An rpmbuild spec question
by m.roth＠5-cent.us 28 Dec '17

28 Dec '17

I'm trying to build a package to create a directory and install some files. My rpmbuild keeps failing, unable to cd into the directory, "no such". Now, in the tmpfile, I *see* it cd'ing into BUILD/opt, and the source was unzipped and untared into BUILD/opt/smipmicfg-1.27.0. In the spec file, I've even added a cd $RPM_BUILD_ROOT/opt, and I see it cd to there... and then it says it fails cd'ing into the directory under it. I've been doing a lot of googling, but nothing seems to fix this. Anyone got a clue? mark

5 9

Can't see register value in crash vmcore
by wuzhouhui 28 Dec '17

28 Dec '17

OS: CentOS 6.5 Crash: crash-7.1.0-6.el6.x86_64 Kdump: kexec-tools-2.0.0-273.el6.x86_64 GDB: gdb-7.2-60.el6_4.1.x86_64 /etc/kdump.conf: core_collector makedumpfile -c --message-level 1 -d 31 Kernel crashed by panic("string"), but I can't see any register in vmcore: crash> bt PID: 53331 TASK: ffff880c523ed540 CPU: 2 COMMAND: "bw_sd-ar-7-0_2" #0 [ffff880c4f12f978] machine_kexec at ffffffff81038ed9 #1 [ffff880c4f12f9d8] crash_kexec at ffffffff810c5a82 #2 [ffff880c4f12faa8] panic at ffffffff815113b2 #3 [ffff880c4f12fb28] sd_submit_bio at ffffffffa0747a02 [sd] #4 [ffff880c4f12fb68] submit_clone_bio at ffffffffa0747d2b [sd] #5 [ffff880c4f12fb78] split_and_submit_bio_for_cbd at ffffffffa0747ec9 [sd] #6 [ffff880c4f12fbf8] sd_make_request at ffffffffa074c812 [sd] #7 [ffff880c4f12fc68] sdu_make_request at ffffffffa074ca41 [sd] #8 [ffff880c4f12fc88] generic_make_request at ffffffff81264d70 #9 [ffff880c4f12fd68] submit_bio at ffffffff81265140 #10 [ffff880c4f12fdb8] submit_area_bio at ffffffffa04ade20 [scst_vdisk] #11 [ffff880c4f12fde8] bwraid_submit_bio at ffffffffa04b03b2 [scst_vdisk] #12 [ffff880c4f12fe38] worker_thread at ffffffff81094c50 #13 [ffff880c4f12fee8] kthread at ffffffff8109ae26 #14 [ffff880c4f12ff48] kernel_thread at ffffffff8100c20a crash> Is it normal? Thanks.

1 0

(Dovecot) Package repository now available (fwd)
by Kenneth Porter 27 Dec '17

27 Dec '17

If you use CentOS as a mail server, you can now get the latest version of Dovecot (the IMAP and POP3 server) at the new Dovecot repo. ------------ Forwarded Message ------------ Date: Wednesday, December 27, 2017 5:00 PM +0200 From: aki.tuomi(a)dovecot.fi To: dovecot(a)dovecot.org, dovecot-news(a)dovecot.org Subject: Package repository now available Dovecot now has package repository for Debian, CentOS and Ubuntu available at https://repo.dovecot.org/ Packages are provided for 2.3 series and forward. Please let us know if you run into any trouble with these. --- Aki Tuomi Dovecot oy ---------- End Forwarded Message ----------

1 0

CentOS-announce Digest, Vol 154, Issue 4
by centos-announce-request＠centos.org 22 Dec '17

22 Dec '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. CEEA-2017:3489 CentOS 7 kmod-redhat-qed Enhancement Update (Johnny Hughes) 2. CEBA-2017:3488 CentOS 7 java-1.8.0-openjdk BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 21 Dec 2017 19:26:02 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2017:3489 CentOS 7 kmod-redhat-qed Enhancement Update Message-ID: <20171221192602.GA28969(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2017:3489 Upstream details at : https://access.redhat.com/errata/RHEA-2017:3489 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 9683e58225c1778e171043227dc376241a55ba74aec9f4579cf30f4fa4090dbf kmod-redhat-qed-8.10.10.21_dup7.4-2.el7_4.x86_64.rpm 6c962b2d384c8bf7dd7e8b92e24fa1c1235bbe6212f7be70665ab3f13b66ebf6 kmod-redhat-qede-8.10.10.21_dup7.4-2.el7_4.x86_64.rpm ed6c9515bcfa965d45397f017418f568594046d85a2075316593989275a8b2af kmod-redhat-qedf-8.10.7.0_dup7.4-2.el7_4.x86_64.rpm 01f8ae75160adfac3d286b1c410bd38bca5a2afd99ad2e70536b30dc20f18fdb kmod-redhat-qedi-8.10.4.0_dup7.4-3.el7_4.x86_64.rpm 96ebbaffa522fee78b45e1e4d7ac461314d2d87e585eb1670617808843f9f1ed kmod-redhat-qedr-8.10.10.0_dup7.4-2.el7_4.x86_64.rpm Source: a42ac424ad1fa43269d891ac23bc276cef7bcdd25e7660c9ecf29788f691229c kmod-redhat-qed-8.10.10.21_dup7.4-2.el7_4.src.rpm 25130fca8c3dc270affb3c1d43df0b12e8161924a204edd8db273842ad50f369 kmod-redhat-qede-8.10.10.21_dup7.4-2.el7_4.src.rpm 43bae084122db338174961b0a6b4a7265504f8be486a77db70838f00cc30ded9 kmod-redhat-qedf-8.10.7.0_dup7.4-2.el7_4.src.rpm cc3cbeb63ed45f2598b3ccf8c04344135e5785a0b9be1c84ba8dd0e5ecae559f kmod-redhat-qedi-8.10.4.0_dup7.4-3.el7_4.src.rpm f9c105b0f845d0722618d3eb867e94e26d3b1ae4164522a8727d677a7e998be7 kmod-redhat-qedr-8.10.10.0_dup7.4-2.el7_4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Thu, 21 Dec 2017 19:29:47 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2017:3488 CentOS 7 java-1.8.0-openjdk BugFix Update Message-ID: <20171221192947.GA29174(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2017:3488 Upstream details at : https://access.redhat.com/errata/RHBA-2017:3488 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 88b9407e3fa3e414d3f5c58054436d913a684f2418243d1a80f62360d490b3e1 java-1.8.0-openjdk-1.8.0.151-5.b12.el7_4.i686.rpm 05149beeef9d964630c315fb1f1ef789e6a13f91650b9a5f15512ed7932ce405 java-1.8.0-openjdk-1.8.0.151-5.b12.el7_4.x86_64.rpm fd3402a60e2655776a4f1397a27d0dabe9b6fe1a091a8bd9e26d44904ff95030 java-1.8.0-openjdk-accessibility-1.8.0.151-5.b12.el7_4.i686.rpm 831d088e4c4376526b8fe2b898b640d7d5cc9343ed445a81f63de3a9a73c927f java-1.8.0-openjdk-accessibility-1.8.0.151-5.b12.el7_4.x86_64.rpm 5465474e5f28a5a827559cf1e1d1f50f4c34e786c1d9674e132325cde996dc9d java-1.8.0-openjdk-accessibility-debug-1.8.0.151-5.b12.el7_4.i686.rpm 6e98a2aa798a8d947ce79330ae3d76e17818e88c7387049e3c962f9894c05b6c java-1.8.0-openjdk-accessibility-debug-1.8.0.151-5.b12.el7_4.x86_64.rpm fa0e91cd0ffbe8063798267db48b7539bfd538949f658340c08423b4cd46e3ac java-1.8.0-openjdk-debug-1.8.0.151-5.b12.el7_4.i686.rpm 3abc411f2ef77dff9d4dd9029ba73f2388bc1615b48e36c58fdceef70c27f715 java-1.8.0-openjdk-debug-1.8.0.151-5.b12.el7_4.x86_64.rpm 66a38fbcdd258f4476a763ab78a2521ba8b16bdefac4092c895ffe06a89750ca java-1.8.0-openjdk-demo-1.8.0.151-5.b12.el7_4.i686.rpm fc6f2ad0b5b0cc9f8006b0563318e67ee3b5d946c77164aad7804232e373291a java-1.8.0-openjdk-demo-1.8.0.151-5.b12.el7_4.x86_64.rpm 5ef918b503b2157b884a67afd008a5305318e252763025127aa4f88dbc97dfed java-1.8.0-openjdk-demo-debug-1.8.0.151-5.b12.el7_4.i686.rpm 53b8ae44f13c7a301aec5a86d615d7fe456a1a8b885eeb725f93d859d83a0d01 java-1.8.0-openjdk-demo-debug-1.8.0.151-5.b12.el7_4.x86_64.rpm 69309f73b87778acefd461386e0ec3e38789072062df5d86b948e2002e3fa735 java-1.8.0-openjdk-devel-1.8.0.151-5.b12.el7_4.i686.rpm e000185c393464cef260cf2ad09006dbec57a5d0af3ab07ddf660e63d85d8dcf java-1.8.0-openjdk-devel-1.8.0.151-5.b12.el7_4.x86_64.rpm 8cc915795a1e2c1e5360fb7dee840e1ee313e54ab8478da0b17febb1a8e0223f java-1.8.0-openjdk-devel-debug-1.8.0.151-5.b12.el7_4.i686.rpm 7cf96429bc9ace0baa790e39515a0caa62879d90f1a2c434b559ea91f56ea427 java-1.8.0-openjdk-devel-debug-1.8.0.151-5.b12.el7_4.x86_64.rpm 966737cdc9dbfc16a7ea4fdff949778d166f011b326c86bad319dfd3daf0b200 java-1.8.0-openjdk-headless-1.8.0.151-5.b12.el7_4.i686.rpm 2901045d49e3d933b17ad111999fdbf16b72824f0e56fe99789d944da054a1ac java-1.8.0-openjdk-headless-1.8.0.151-5.b12.el7_4.x86_64.rpm c7efb4aa1a5e2a9011bc943f94a5b4989488436292222dfb6613eafbfe712b1b java-1.8.0-openjdk-headless-debug-1.8.0.151-5.b12.el7_4.i686.rpm 29a773df8073a7f388e6d598c7ca0b7b6373be48b5954b7598bf88d4c4cd6eb9 java-1.8.0-openjdk-headless-debug-1.8.0.151-5.b12.el7_4.x86_64.rpm 2660fdc8dd1ef01bdaef92042cdeff1e9ffb973aae07b1560d72c395eec4c3f4 java-1.8.0-openjdk-javadoc-1.8.0.151-5.b12.el7_4.noarch.rpm 6bf58e3312f317b05b104410814cd75b596a1399d5289dba2c49af3cce8bb89e java-1.8.0-openjdk-javadoc-debug-1.8.0.151-5.b12.el7_4.noarch.rpm e5f9c92f82916404e3755a074a28362ab1504d4b021d259f6b4edc953f9d6926 java-1.8.0-openjdk-javadoc-zip-1.8.0.151-5.b12.el7_4.noarch.rpm fce1b975ec219f230047c87c0bf23262d9065b3a0b9a3c8e6072317c4ec70fc4 java-1.8.0-openjdk-javadoc-zip-debug-1.8.0.151-5.b12.el7_4.noarch.rpm 2e41900e72c7e6740f8a68a5292530473fdc42b820a9c72fc2b889ec55d0e27e java-1.8.0-openjdk-src-1.8.0.151-5.b12.el7_4.i686.rpm f644bf21f724dfe4865a33941710ef78d790bd55710254cce2572b3b35e1f4e8 java-1.8.0-openjdk-src-1.8.0.151-5.b12.el7_4.x86_64.rpm de5140dfbccb73bba874a7c1895f4657e3aac5e5c9c1bbb03e638470eedfafb3 java-1.8.0-openjdk-src-debug-1.8.0.151-5.b12.el7_4.i686.rpm 863b8b64536c0d8ea90367901097d46c3e94fee36c034cca52fb2e1801e2dc02 java-1.8.0-openjdk-src-debug-1.8.0.151-5.b12.el7_4.x86_64.rpm Source: 8439a79f2aa0f8c64fc9dda350fba575c3bb8119e56a2db8b1afcc2f04e4b597 java-1.8.0-openjdk-1.8.0.151-5.b12.el7_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 154, Issue 4 ***********************************************

1 0

Does anyone know how to get clipboard and mouse integration in Centos vm?
by Manish Jain 20 Dec '17

20 Dec '17

Hi, I am running a Centos 7 vm under FreeBSD, and it works very well now, with KDE installed from DVD iso. But there's a couple of things missing, which happens only with Centos vm (Virtualbox): 1) Despite clipboard sharing enabled, copy-paste just does not work between host and guest 2) Mouse integration does not work. So I have to repeatedly capture mouse manually both in the host and in the guest. If anyone could provide me tips how to tweak the above, it shall help me a lot. -- Thanks & Regards, Manish Jain

2 2

broadcom and centos 7
by Keith Keller 20 Dec '17

20 Dec '17

Hi all, A year or two ago, I installed CentOS 7.0 (or 7.1) on an old MacBook Pro, and compiled the Broadcom drivers as documented here: https://wiki.centos.org/HowTos/Laptops/Wireless/Broadcom After not using it for a while, I recently resurrected it, and updated to 7.4. Unfortunately that page has not been updated in a while, so only documents compiling for 7.3. When I try the patch, it fails on one of the hunks (I don't have the exact error, I can grab it later if important). Has anyone had success with this on CentOS 7.4, either with this compile, or the one documented by ELRepo (which I haven't tried yet)? https://elrepo.org/tiki/wl-kmod --keith -- kkeller(a)wombat.san-francisco.ca.us

2 4

Fwd: httpd24 Package Question
by Tyler Waldo 20 Dec '17

20 Dec '17

Hello everybody I am looking to push out httpd24-httpd-2.4.25-9.el7 to my organization, but I do not see it as being available on the mirror.centos.org site. I see a git commit for this package in April and was wondering how long it takes an rpm to become available once the commit has been completed. Also, I don't see the following CVEs addressed in any httpd24 changelogs and wanted to know if they were ever planning on being addressed in an httpd24 rpm? - CVE-2016-0736 - CVE-2016-2161 - CVE-2016-8743 - CVE-2016-1546 - CVE-2016-8740 -- Thanks, Tyler

2 3

firewalld
by Emmett Culley 20 Dec '17

20 Dec '17

I have two VMs, both with firewalld installed. One on machine It this in the IN_public chain: Chain IN_public (2 references) pkts bytes target prot opt in out source destination 81 3423 IN_public_log all -- * * 0.0.0.0/0 0.0.0.0/0 81 3423 IN_public_deny all -- * * 0.0.0.0/0 0.0.0.0/0 81 3423 IN_public_allow all -- * * 0.0.0.0/0 0.0.0.0/0 79 3335 REJECT all -- * * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited On the other I see: Chain IN_public (2 references) pkts bytes target prot opt in out source destination 101 4232 IN_public_log all -- * * 0.0.0.0/0 0.0.0.0/0 101 4232 IN_public_deny all -- * * 0.0.0.0/0 0.0.0.0/0 101 4232 IN_public_allow all -- * * 0.0.0.0/0 0.0.0.0/0 1 84 ACCEPT icmp -- * * 0.0.0.0/0 0.0.0.0/0 As might be expected, pinging the first VM fails. That is the ping is rejected with: [emmett@ws1 ~]$ ping 96.92.106.4 PING 96.92.106.4 (96.92.106.4) 56(84) bytes of data. >From 96.92.106.4 icmp_seq=1 Destination Host Prohibited >From 96.92.106.4 icmp_seq=2 Destination Host Prohibited And pinging the second works as expected. I've searche the firewalld configuration files in /usr/lib/firewalld and /etc/firewalld and can find no reference to any icmp rule. The two machines were cloned originally from the same VM. Why are they different? How can I remove the reject-with icmp rule using firewalld. I can remove it using "iptables -D [IN_public | FWDO_public | FWDI_public ] 4" and I can then ping that machine. But of course the rule is returned whenever firewalld is restarted. Emmett

3 3

Re: [CentOS] Unable to run TeamViewer 13 under Centos 7 (amd64)
by Manish Jain 20 Dec '17

20 Dec '17

On 12/19/17 22:11, Manish Jain wrote: > On 12/19/17 22:07, Jonathan Billings wrote: >> On Tue, Dec 19, 2017 at 02:54:36PM +0000, Manish Jain wrote: >>> I uninstalled the old TV, and installed the version you indicated, but I >>> get nothing at all: >>> >>> /home/bourne # teamviewer >>> >>> Init... >>> CheckCPU: SSE2 support: yes >>> Checking setup... >>> Launching TeamViewer ... >>> Launching TeamViewer GUI ... >>> /home/bourne # >>> >>> I deleted ~/.config/teamviewer* and ~/.local/share/teamviewer*, but >>> still no luck. >>> >>> Is it possible that this has something to do with Centos 7 running as a >>> vm (under VirtualBox) in my box ? (But then, Manjaro vm works fine). >> >> Maybe you have a customized $PS1 (or other shell) but with a shell >> prompt that includes '#', it makes me wonder if you're running this as >> the logged-into-X user or as root? >> > > Hi Jonathan, > > Thanks for joining the thread. > > I am doing this as a normal user (bourne), logged in with xfce4. I recreated the vm - this time letting the TV rpm pull in all its deps. But the situation remains the same - No TV window from teamviewer. Thanks & Regards, Manish Jain

5 9

Re: [CentOS] Strange dots on monitor
by vychytraly . 19 Dec '17

19 Dec '17

I forgot to write that the dots start to appear only inside "Desktop Environment" (in my case Gnome), not for example in grub/bios. Today I tried to install ubuntu 16.04 and the green dots appeared there too (in Unity). On Sun, Dec 17, 2017 at 12:50 AM, vychytraly . <vychytraly(a)gmail.com> wrote: > Hello friends, > > about 2 days ago, unexpected strange green dots started to appear on > monitor of my laptop running centos 7.4 with nvidia card. I enclose photo > of the problem. Before it was running perfectly fine, I did not do any > updates of the system / drivers last few weeks, so I am not sure what can > it be related to. When I try to do screenshot. The screenshot captures > screen without the dots. But now comes the strange thing: when i am in the > running system already and i do "systemctl restart gdm", X restarts and the > green dots disappear, everything looks perfect after that. > > Please could you give me some advice how can I resolve this problem? I > suspect that X could have some problems to properly "indetify" the monitor > and therefore it creates this artifacts? Or do you think it could be > hardware bug of gpu/monitor? > > Thank you very much for any advice > Have a nice day > > Vych >

3 6

Unable to run TeamViewer 13 under Centos 7 (amd64)
by Manish Jain 19 Dec '17

19 Dec '17

Hi, I am writing a book about Unix (Linux / FreeBSD) and my book needs documentation for TeamViewer13 running under Centos 7 (64-bit). Unfortunately, running TeamViewer does not get me a GUI -- the install went smoothly and teamviewerd daemon is running. This happens only under Centos. Under Manjaro, the same tarball (teamviewer_13.0.5494_amd64.tar.xz) gets me a nice TeamViewer window. But I need documentation for Centos. I have tried reinstalling via rpm (teamviewer_13.0.5693.x86_64.rpm), but that does not improve things. With the teamviewer command, I just get "Launching TeamViewer GUI" - but nothing actually happens after that. Can anyone please help me fix the issue ? -- Thanks & Regards, Manish Jain

4 6

CentOS-announce Digest, Vol 154, Issue 3
by centos-announce-request＠centos.org 19 Dec '17

19 Dec '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.13 on CentOS Linux 7 x86_64 (Niels de Vos) 2. Announcing the release for Gluster 3.13 on CentOS Linux 6 x86_64 (Niels de Vos) ---------------------------------------------------------------------- Message: 1 Date: Thu, 14 Dec 2017 09:24:10 +0530 From: Niels de Vos <ndevos(a)redhat.com> To: centos-announce(a)centos.org Subject: [CentOS-announce] Announcing the release for Gluster 3.13 on CentOS Linux 7 x86_64 Message-ID: <20171214035410.GA11272@ndevos-x270> Content-Type: text/plain; charset="us-ascii" I am happy to announce the General Availability of Gluster 3.13 for CentOS 7 on x86_64. These packages are following the upstream Gluster Community releases, and will receive monthly bugfix updates. Gluster 3.13 is a Short-Term-Maintenance release, and will only receive updates until the next version (4.0) 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.13 with only these two commands: # yum install centos-release-gluster313 # yum install glusterfs-server The centos-release-gluster313 package is delivered via CentOS Extras repos. This contains all the metadata and dependancy information, needed to install Gluster 3.13. Note that the standard centos-release-gluster (virtual) package is still available and points to the 3.12 version. This is intentional because 3.12 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-gluster313 to fullfill dependencies for other projects (possibly for oVirt, there may be others). 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

kernel: blk_cloned_rq_check_limits: over max segments limit., Device Mapper Multipath, iBFT, iSCSI COMSTAR
by Tom Robinson 19 Dec '17

19 Dec '17

Hi, WARNING: Long post ahead I have an issue when starting multipathd. The kernel complains about "blk_cloned_rq_check_limits: over max segments limit". The server in question is configured for KVM hosting. It boots via iBFT to an iSCSI volume. Target is COMSTAR and underlying that is a ZFS volume (100GB). The server also has two infiniband cards providing four (4) more paths over SRP (SCSI RDMA Protocol). With multipathd in the initramfs and enabled at boot, I get five paths (but also now the blk_cloned_req_check_limits error) on boot. I/O on the boot volume also causes the multipaths to fail one after the other until only one path remains, issuing the kernel message "blk_cloned_rq_check_limits: over max segments limit" for each failed path. The paths then recover one after the other but have also 'frozen' the system (final path did not recover!) at which point all I can do is reset the power. (I/O can be KVM Guest read/write, running "dracut -f", copying an ISO to /var/lib/libvirt/images or 'dd'ing a 1GB file to /tmp). I have read: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/pd… I have read: https://access.redhat.com/solutions/2437991 I don't use GPFS: http://www-01.ibm.com/support/docview.wss?uid=ssg1S1009622 I actually have two servers with the exact same hardware configuration. Originally they were both CentOS 7 with the default install LVM partitioning structure. For the above host, I have re-installed and removed LVM as it complicated the issue further. It does appear to be somewhat more stable but results on I/O testing are now inconsistent. Things that have changed are: Not using LVM on the host. Freed up some storage reservations (removed snapshots) on the SAN. ENVIRONMENT: CentOS 7.4 System is iBFT boot (boots from iSCSI on 10G card to COMSTAR zfs volume) System also has Infiniband which provide another four (4) paths multipath is initialised in initramfs Kernel is 3.10.0-693.11.1.el7.x86_64 With respect to https://access.redhat.com/solutions/2437991 there is a recommendation to adjust the 'max_sectors_kb' for devices when seeing the kernel error I am encountering. To that end I have queried the /sys/block area for that information the below. For debugging, at boot, I have disabled multipathd service I wrote the below script to query /sys/block for block device information: # cat bin/max_sectors_kb #!/bin/bash printf "%-18s: %-37s %-15s %-18s\n" $sysblk "Sys Block Node" "Device" "max_sectors_kb" "max_hw_sectors_kb" for b in `ls /sys/block/` do sysblk=/sys/block/$b ls $sysblk/dm/name > /dev/null 2>&1 if [ $? -ne 0 ]; then vendor=`cat $sysblk/device/vendor` model=`cat $sysblk/device/model` name="$vendor $model" else name=`cat $sysblk/dm/name` fi max_sectors_kb=`cat $sysblk/queue/max_sectors_kb` max_hw_sectors_kb=`cat $sysblk/queue/max_hw_sectors_kb` printf "%-18s: %-37s %-15s %-18s\n" $sysblk "$name" $max_sectors_kb $max_hw_sectors_kb done The boot volume is identified by the multipath wwid 3600144f00000000000005a2769c70001. It's underlying device nodes are: sda, sdd, sde, sdk and sdj. Running the script after boot for the boot device I get this: # max_sectors_kb | grep -e 3600144f00000000000005a2769c70001 -e sda -e sdd -e sde -e sdk -e sdj -e max Sys Block Node : Device max_sectors_kb max_hw_sectors_kb /sys/block/dm-1 : 3600144f00000000000005a2769c70001 512 32767 /sys/block/dm-5 : 3600144f00000000000005a2769c70001p1 512 32767 /sys/block/dm-6 : 3600144f00000000000005a2769c70001p2 512 32767 /sys/block/dm-7 : 3600144f00000000000005a2769c70001p3 512 32767 /sys/block/sda : SUN COMSTAR 512 32767 /sys/block/sdd : SUN COMSTAR 512 512 /sys/block/sde : SUN COMSTAR 512 512 /sys/block/sdj : SUN COMSTAR 512 512 /sys/block/sdk : SUN COMSTAR 512 512 On starting multipathd service manually I get: Dec 18 12:46:41 lemans systemd: Starting Availability of block devices... Dec 18 12:46:41 lemans systemd: Starting Device-Mapper Multipath Device Controller... Dec 18 12:46:41 lemans systemd: Started Availability of block devices. Dec 18 12:46:41 lemans systemd: Started Device-Mapper Multipath Device Controller. Dec 18 12:46:41 lemans multipathd: 3600144f00000000000005a2769c70001: load table [0 209715200 multipath 1 queue_if_no_path 0 1 1 service-time 0 5 1 8:64 1 8:144 1 8:48 1 8:160 1 8:0 1] Dec 18 12:46:41 lemans multipathd: 3600144f0000000000000524a93b80002: load table [0 41943040 multipath 1 queue_if_no_path 0 1 1 service-time 0 5 1 8:80 1 8:176 1 8:96 1 8:192 1 8:16 1] Dec 18 12:46:41 lemans multipathd: 3600144f0000000000000524a94510003: load table [0 41943040 multipath 1 queue_if_no_path 0 1 1 service-time 0 5 1 8:112 1 8:208 1 8:128 1 8:224 1 8:32 1] Dec 18 12:46:41 lemans kernel: blk_cloned_rq_check_limits: over max segments limit. Dec 18 12:46:41 lemans kernel: device-mapper: multipath: Failing path 8:48. Dec 18 12:46:41 lemans kernel: device-mapper: multipath: Reinstating path 8:48. Dec 18 12:46:41 lemans multipathd: 3600144f00000000000005a2769c70001: event checker started Dec 18 12:46:41 lemans multipathd: 3600144f0000000000000524a93b80002: event checker started Dec 18 12:46:41 lemans multipathd: 3600144f0000000000000524a94510003: event checker started Dec 18 12:46:41 lemans multipathd: path checkers start up Dec 18 12:46:41 lemans kernel: blk_cloned_rq_check_limits: over max segments limit. Dec 18 12:46:41 lemans kernel: device-mapper: multipath: Failing path 8:64. Dec 18 12:46:41 lemans kernel: blk_cloned_rq_check_limits: over max segments limit. Dec 18 12:46:41 lemans kernel: device-mapper: multipath: Failing path 8:160. Dec 18 12:46:41 lemans multipathd: sde: mark as failed Dec 18 12:46:41 lemans multipathd: 3600144f00000000000005a2769c70001: remaining active paths: 4 Dec 18 12:46:41 lemans multipathd: sdk: mark as failed Dec 18 12:46:41 lemans multipathd: 3600144f00000000000005a2769c70001: remaining active paths: 3 Dec 18 12:46:42 lemans multipathd: 3600144f00000000000005a2769c70001: sde - directio checker reports path is up Dec 18 12:46:42 lemans kernel: device-mapper: multipath: Reinstating path 8:64. Dec 18 12:46:42 lemans multipathd: 8:64: reinstated Dec 18 12:46:42 lemans multipathd: 3600144f00000000000005a2769c70001: remaining active paths: 4 Dec 18 12:46:42 lemans multipathd: 3600144f00000000000005a2769c70001: sdk - directio checker reports path is up Dec 18 12:46:42 lemans kernel: device-mapper: multipath: Reinstating path 8:160. Dec 18 12:46:42 lemans multipathd: 8:160: reinstated Dec 18 12:46:42 lemans multipathd: 3600144f00000000000005a2769c70001: remaining active paths: 5 AND also the max_hw_sectors_kb is reduced to 512 for all but one device: # max_sectors_kb | grep -e 3600144f00000000000005a2769c70001 -e sda -e sdd -e sde -e sdk -e sdj -e max Sys Block Node : Device max_sectors_kb max_hw_sectors_kb /sys/block/dm-1 : 3600144f00000000000005a2769c70001 512 512 /sys/block/dm-5 : 3600144f00000000000005a2769c70001p1 512 512 /sys/block/dm-6 : 3600144f00000000000005a2769c70001p2 512 512 /sys/block/dm-7 : 3600144f00000000000005a2769c70001p3 512 512 /sys/block/sda : SUN COMSTAR 512 32767 /sys/block/sdd : SUN COMSTAR 512 512 /sys/block/sde : SUN COMSTAR 512 512 /sys/block/sdj : SUN COMSTAR 512 512 /sys/block/sdk : SUN COMSTAR 512 512 I don't understand the inconsistent manipulation of the max_hw_sectors_kb... ENABLING multipathd AT BOOT: Enabling the multipathd service at boot, I get lots of path failures and the blk_cloned_rq_check_limits error. From dmesg: [ 48.486407] sd 4:0:0:7: [sdo] Attached SCSI disk [ 49.460048] blk_cloned_rq_check_limits: over max segments limit. [ 49.461199] device-mapper: multipath: Failing path 8:48. [ 49.462284] blk_cloned_rq_check_limits: over max segments limit. [ 49.463392] device-mapper: multipath: Failing path 8:144. [ 49.469282] blk_cloned_rq_check_limits: over max segments limit. [ 49.470886] device-mapper: multipath: Failing path 8:176. [ 49.472560] blk_cloned_rq_check_limits: over max segments limit. [ 49.473893] device-mapper: multipath: Failing path 8:64. [ 49.847469] device-mapper: multipath: Reinstating path 8:48. [ 49.850403] device-mapper: multipath: Reinstating path 8:144. [ 49.853143] device-mapper: multipath: Reinstating path 8:176. [ 50.626291] blk_cloned_rq_check_limits: over max segments limit. [ 50.627539] device-mapper: multipath: Failing path 8:144. [ 50.628533] blk_cloned_rq_check_limits: over max segments limit. [ 50.629467] device-mapper: multipath: Failing path 8:176. [ 50.630441] blk_cloned_rq_check_limits: over max segments limit. [ 50.631379] device-mapper: multipath: Failing path 8:48. [ 54.859526] device-mapper: multipath: Reinstating path 8:64. [ 54.860050] device-mapper: multipath: Reinstating path 8:144. [ 54.860463] device-mapper: multipath: Reinstating path 8:176. [ 55.861034] device-mapper: multipath: Reinstating path 8:48. [ 59.811712] UDP: bad checksum. From 192.168.0.124:55913 to 255.255.255.255:15000 ulen 58 [ 59.999563] blk_cloned_rq_check_limits: over max segments limit. [ 59.999591] device-mapper: multipath: Failing path 8:48. [ 59.999650] blk_cloned_rq_check_limits: over max segments limit. [ 59.999675] device-mapper: multipath: Failing path 8:144. [ 59.999711] blk_cloned_rq_check_limits: over max segments limit. [ 59.999736] device-mapper: multipath: Failing path 8:64. [ 59.999773] blk_cloned_rq_check_limits: over max segments limit. [ 59.999798] device-mapper: multipath: Failing path 8:176. [ 61.055033] device-mapper: multipath: Reinstating path 8:64. [ 61.087458] blk_cloned_rq_check_limits: over max segments limit. [ 61.087495] device-mapper: multipath: Failing path 8:64. [ 62.077462] device-mapper: multipath: Reinstating path 8:48. [ 66.078675] device-mapper: multipath: Reinstating path 8:144. [ 66.079036] device-mapper: multipath: Reinstating path 8:176. [ 67.079827] device-mapper: multipath: Reinstating path 8:64. [ 115.197811] blk_cloned_rq_check_limits: over max segments limit. [ 115.197876] device-mapper: multipath: Failing path 8:176. [ 115.197952] blk_cloned_rq_check_limits: over max segments limit. [ 115.198007] device-mapper: multipath: Failing path 8:48. [ 115.198063] blk_cloned_rq_check_limits: over max segments limit. [ 115.198117] device-mapper: multipath: Failing path 8:144. [ 121.101670] device-mapper: multipath: Reinstating path 8:48. [ 121.102270] device-mapper: multipath: Reinstating path 8:144. [ 121.102645] device-mapper: multipath: Reinstating path 8:176. [ 205.275512] blk_cloned_rq_check_limits: over max segments limit. [ 205.275577] device-mapper: multipath: Failing path 8:48. [ 205.275695] blk_cloned_rq_check_limits: over max segments limit. [ 205.275752] device-mapper: multipath: Failing path 8:176. [ 205.277268] blk_cloned_rq_check_limits: over max segments limit. [ 205.277333] device-mapper: multipath: Failing path 8:144. Other information at this boot point: Multipath # multipath -ll 3600144f00000000000005a2769c70001 3600144f00000000000005a2769c70001 dm-1 SUN ,COMSTAR size=100G features='3 queue_if_no_path queue_mode mq' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active |- 0:0:0:0 sda 8:0 active ready running |- 2:0:0:0 sdd 8:48 active ready running |- 1:0:0:0 sde 8:64 active ready running |- 3:0:0:0 sdj 8:144 active ready running `- 4:0:0:0 sdl 8:176 active ready running Other information at this boot point: /sys/block info: # max_sectors_kb | grep -e 3600144f00000000000005a2769c70001 -e sda -e sdd -e sde -e sdk -e sdj -e max Sys Block Node : Device max_sectors_kb max_hw_sectors_kb /sys/block/dm-1 : 3600144f00000000000005a2769c70001 512 512 /sys/block/dm-7 : 3600144f00000000000005a2769c70001p1 512 32767 /sys/block/dm-8 : 3600144f00000000000005a2769c70001p2 512 32767 /sys/block/dm-9 : 3600144f00000000000005a2769c70001p3 512 32767 /sys/block/sda : SUN COMSTAR 512 32767 /sys/block/sdd : SUN COMSTAR 512 512 /sys/block/sde : SUN COMSTAR 512 512 /sys/block/sdj : SUN COMSTAR 512 512 /sys/block/sdk : SUN COMSTAR 512 512 AND when I restart multipathd the max_hw_sectors_kb resets to 512 on all but one device: # max_sectors_kb | grep -e 3600144f00000000000005a2769c70001 -e sda -e sdd -e sde -e sdk -e sdj -e max Sys Block Node : Device max_sectors_kb max_hw_sectors_kb /sys/block/dm-1 : 3600144f00000000000005a2769c70001 512 512 /sys/block/dm-7 : 3600144f00000000000005a2769c70001p1 512 512 /sys/block/dm-8 : 3600144f00000000000005a2769c70001p2 512 512 /sys/block/dm-9 : 3600144f00000000000005a2769c70001p3 512 512 /sys/block/sda : SUN COMSTAR 512 32767 /sys/block/sdd : SUN COMSTAR 512 512 /sys/block/sde : SUN COMSTAR 512 512 /sys/block/sdj : SUN COMSTAR 512 512 /sys/block/sdk : SUN COMSTAR 512 512 Setting max_sectors_kb in /etc/multipath.conf gives very inconsistent results. It's not actually possible to increase the setting past 512 consistently across all available paths as they are established with different hardware maximums (by kernel? driver?) on boot. And starting multipathd seems to change the (read only) value of max_hw_sectors_kb. I get alignment issues and unmountable volumes. Having removed LVM and tidying up SAN storage looks to have solved some issues. I still get the errors on boot. The inconsistencies in max_hw_sectors_kb for each path before and after starting multipathd (both in initramfs and during/after boot) still baffle me. All comments welcome. Any clues appreciated. Kind regards, Tom -- Tom Robinson IT Manager/System Administrator MoTeC Pty Ltd 121 Merrindale Drive Croydon South 3136 Victoria Australia T: +61 3 9761 5050 F: +61 3 9761 5051 E: tom.robinson(a)motec.com.au

1 0

Centos7: backup with rsync problem: "rsync: rsync_xal_set: lremovexattr(""/tmp/test/etc/fstab"", "security.selinux") failed: Permission denied (13)"
by Dario Lesca 18 Dec '17

18 Dec '17

If I run this command in order to backup /etc from remote server to local dir I get a lot of this message: [root@s-virt tmp]# rsync -a --delete --numeric-ids --relative --delete-excluded --compress --acls --xattrs rsync://server-dati/root/etc/ /tmp/test/ -v receiving incremental file list rsync: rsync_xal_set: lremovexattr(""/tmp/test/etc/fstab"","security.selinux") failed: Permission denied (13) rsync: rsync_xal_set: lremovexattr(""/tmp/test/etc/resolv.conf"","security.selinux") failed: Permission denied (13) rsync: rsync_xal_set: lremovexattr(""/tmp/test/etc/rsyncd.conf"","security.selinux") failed: Permission denied (13) rsync: rsync_xal_set: lremovexattr(""/tmp/test/etc/rsyncd.secrets"","security.selinux") failed: Permission denied (13) rsync: rsync_xal_set: lremovexattr(""/tmp/test/etc/lvm/archive/dati_00001-728488062.vg"","security.selinux") failed: Permission denied (13) rsync: rsync_xal_set: lremovexattr(""/tmp/test/etc/lvm/backup/dati"","security.selinux") failed: Permission denied (13) rsync: rsync_xal_set: lremovexattr(""/tmp/test/etc/samba/.smb.conf.swp"","security.selinux") failed: Permission denied (13) rsync: rsync_xal_set: lremovexattr(""/tmp/test/etc/samba/smb.conf"","security.selinux") failed: Permission denied (13) rsync: rsync_xal_set: lremovexattr(""/tmp/test/etc/systemd/system/multi-user.target.wants/rsyncd.service"","security.selinux") failed: Permission denied (13) sent 671 bytes received 49804 bytes 100950.00 bytes/sec total size is 30375007 speedup is 601.78 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1518) [generator=3.0.9] I have also try to "setenforce 0" but the result is the same It's possible to do a full backup of remote /etc with SElinux attrs to a local dir? Many thanks -- Dario Lesca (inviato dal mio Linux Fedora 27 Workstation)

1 0

Offsite hosted backup solutions
by Joseph L. Casale 18 Dec '17

18 Dec '17

Given all the vendors that provide this service with both Windows and Linux clients, Code42 is the only one I am aware of that supports sets. For me, this was essential to prioritize urgent data over low risk changes in the event a disaster occurs while a large directory is taking days to upload. I would use sets with priorities and any changed data that was important would interrupt data of negligible importance. This worked well, however Code42 always bothered me as the software delivery was low quality on Linux, it was a tar file and only implemented sysv scripts and they did not have a cli interface. I worked around this as long as I could until they retooled the app based on electron and as bad as the ui was, it got worse. At this point I would rather switch vendors. Anyone know of another that meets the criteria, from what I can see it doesn't look like any support sets? Thanks, jlc

5 5

Centos 7: avc: denied { reload } for auid=0 uid=0 gid=0 cmdline="/usr/bin/systemctl reload named-chroot.service" ....
by Dario Lesca 17 Dec '17

17 Dec '17

How to resolve this SElinux problem? type=USER_AVC msg=audit(1513478641.700:1920): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='avc: denied { reload } for auid=0 uid=0 gid=0 cmdline="/usr/bin/systemctl reload named-chroot.service" scontext=system_u:system_r:logrotate_t:s0-s0:c0.c1023 tcontext=system_u:system_r:init_t:s0 tclass=service exe="/usr/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?' type=USER_AVC msg=audit(1513478641.702:1921): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='avc: denied { reload } for auid=0 uid=0 gid=0 cmdline="/usr/bin/systemctl reload named-sdb.service" scontext=system_u:system_r:logrotate_t:s0-s0:c0.c1023 tcontext=system_u:system_r:init_t:s0 tclass=service exe="/usr/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?' type=USER_AVC msg=audit(1513478641.703:1922): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='avc: denied { reload } for auid=0 uid=0 gid=0 cmdline="/usr/bin/systemctl reload named-sdb-chroot.service" scontext=system_u:system_r:logrotate_t:s0-s0:c0.c1023 tcontext=system_u:system_r:init_t:s0 tclass=service exe="/usr/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?' type=USER_AVC msg=audit(1513478641.704:1923): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='avc: denied { reload } for auid=0 uid=0 gid=0 cmdline="/usr/bin/systemctl reload named-pkcs11.service" scontext=system_u:system_r:logrotate_t:s0-s0:c0.c1023 tcontext=system_u:system_r:init_t:s0 tclass=service exe="/usr/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?' Many thanks -- Dario Lesca (inviato dal mio Linux Fedora 27 Workstation)

1 0

GUI/X11 login and shells other than bash?
by Valeri Galtsev 16 Dec '17

16 Dec '17

Dear Experts, After one of updates that was released some time ago (a Month ago or maybe even earlier) I have noticed the following. On the machines with default runlevel 5 (sorry about old terminology, the new one is still confusing for me ;-) GUI/X11 login (display manager) lists only users whose default shell is bash. Or, at least users whose default shell is tcsh are not listed at all, and if they attempt to log in just by giving their UNIX username, their X11 session "crashes", meaning that after attempting to start, it just trows one back to GUI/X11 login screen. I really do not want to start this shell vs that shell flame war (especially that I myself prefer not tcsh but sh and/or bash for scripting...). But I respect my user's freedom of choosing default shell, so this is really big issue IMHO. I just wonder: does RedHat (CentOS's upstream vendor) dislike and is willing to eradicate all shells except for bash, or what I see is just my own pilot's error? Thanks in advance for all your answers. Valeri ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++

3 4

Traffic shaping on CentOS
by Kenneth Porter 16 Dec '17

16 Dec '17

I'm deploying a CentOS 7 box as a gateway and I'm trying to figure out how to set up traffic shaping. Historically I've used the Wondershaper script but apparently it's not deprecated in favor of superior queue management. I haven't yet found a packaged solution and I'm wondering what others do to configure this kind of thing. Apparently the new modules are available in many appliance router products (eg. OpenWrt and Streamboost). Perhaps someone here knows of an RPM that wraps this up for RH-based distros? <https://www.bufferbloat.net/projects/cerowrt/wiki/Smart_Queue_Management/> Here's an article arguing why Wondershaper was great in its day but is now bad for modern traffic flows. <https://www.bufferbloat.net/projects/bloat/wiki/Wondershaper_Must_Die/>

3 4

Question on CentoS 7.4 on nvidia
by Jerry Geis 15 Dec '17

15 Dec '17

I installed the elrepo kmod-nvidia and also the nvidia-detect and modules (see below). I had X working with the 3.10 from Centos - but video was freezing. SO I thought I would try the elrepo kernel. I installed that and X does not come up? How do I re-make the nvidia module for 4.14.5 kernel? I want to make sure the kmod kernel did it. I 'm thinking it did not. lspci | grep VGA says GT218 Or what do I look at now to see why X is not coming up? Thanks, Jerry uname -r 4.14.5-1.el7.elrepo.x86_64 grep EE /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 136.998] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 136.998] (EE) NVIDIA: system's kernel log for additional error messages and [ 136.998] (EE) NVIDIA: consult the NVIDIA README for details. [ 136.998] (EE) No devices detected. [ 136.998] (EE) [ 136.998] (EE) no screens found(EE) [ 136.998] (EE) [ 136.998] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 136.998] (EE) [ 137.004] (EE) Server terminated with error (1). Closing log file. uname -a rpm -qa | grep kernel kernel-3.10.0-693.el7.x86_64 kernel-tools-3.10.0-693.5.2.el7.x86_64 abrt-addon-kerneloops-2.1.11-48.el7.centos.x86_64 kernel-headers-3.10.0-693.5.2.el7.x86_64 kernel-ml-devel-4.14.5-1.el7.elrepo.x86_64 kernel-devel-3.10.0-693.el7.x86_64 kernel-3.10.0-693.5.2.el7.x86_64 kernel-ml-4.14.5-1.el7.elrepo.x86_64 kernel-tools-libs-3.10.0-693.5.2.el7.x86_64 kernel-devel-3.10.0-693.5.2.el7.x86_64 [root@mediaport14 ~]# rpm -qa | grep kernel-ml kernel-ml-devel-4.14.5-1.el7.elrepo.x86_64 kernel-ml-4.14.5-1.el7.elrepo.x86_64 # rpm -qa | grep nvidia kmod-nvidia-340xx-340.102-4.el7_4.elrepo.x86_64 nvidia-detect-384.90-1.el7.elrepo.x86_64 yum-plugin-nvidia-1.0.2-1.el7.elrepo.noarch nvidia-x11-drv-340xx-340.102-1.el7.elrepo.x86_64

7 8

Accessing crashed disk
by martin.wagner＠mailbit.io 15 Dec '17

15 Dec '17

Hi I have a Centos server that crashed, it would no longer boot. I thought it was the disk with the OS that was the problem so I bought a new one and did a fresh install and now the computer is again up and running. But I'm having problems with accessing the old failed disk. I can see it with gnome-disk-utility and it says that the disk is OK but has 8 bad sectors. I can mount the boot partition from it and I can decrypt the main partition. But then I can see no way to mount the main partition. It is a LVM physical volume. Any advice?

6 6

Problems with dnscrypt's package from EPEL
by C. L. Martinez 14 Dec '17

14 Dec '17

Hi all, I have installed dnscrypt's rpm package from EPEL repo under a CentOS 7.4 and using unbound as a resolver. But, I see constant timeouts and responses are very slow ... Using same config in a Debian 9 virtual machine, all works ok. I think the problem is with dnscrypt's rpm package provided by EPEL. Anyone have seen similar problems? Thanks. -- Greetings, C. L. Martinez

2 6

Spamassassin vs. SELinux trouble
by Nicolas Kovacs 14 Dec '17

14 Dec '17

Hi, Spamassassin has been working nicely on my main server running CentOS 7 and Postfix. SELinux is activated (Enforcing). Since the most recent update (don't know if it's related to it though) I'm getting the following SELinux error. --8<----------------------------------------------------------------- SELinux is preventing /usr/bin/perl from 'read, write' accesses on the file /var/log/spamassassin/.spamassassin/bayes_toks. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that perl should be allowed read write access on the bayes_toks file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c '7370616D64206368696C64' --raw | audit2allow -M my-7370616D64206368696C64 # semodule -i my-7370616D64206368696C64.pp Additional Information: Source Context system_u:system_r:spamd_t:s0 Target Context system_u:object_r:var_log_t:s0 Target Objects /var/log/spamassassin/.spamassassin/bayes_toks [ file ] Source 7370616D64206368696C64 Source Path /usr/bin/perl Port <Unknown> Host <Unknown> Source RPM Packages perl-5.16.3-292.el7.x86_64 Target RPM Packages Policy RPM selinux-policy-3.13.1-166.el7_4.7.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing ... --8<----------------------------------------------------------------- Unfortunately the suggested solution does not work, e. g. the following command returns nothing: # ausearch -c '7370616D64206368696C64' --raw Now I'm clueless. Any suggestions? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

4 4

Broadcom BCM4352 on Centos 7
by Gary Stainburn 14 Dec '17

14 Dec '17

Hi Folks I'm trying to get my internal WiFi working and I'm following the instructions here: https://wiki.centos.org/HowTos/Laptops/Wireless/Broadcom My adaptor is: [gary@gary ~]$ lspci|grep Broad 08:00.0 Network controller: Broadcom Limited BCM4352 802.11ac Wireless Network Adapter (rev 03) [gary@gary ~]$ However, I've failed at step 2 as I cannot find any Linux / STA / WL drivers when I search the support page linked. Can anyone suggest how I can fix this, or suggest another web page I can follow? Cheers

3 7

Some problemas working with network namespaces
by C. L. Martinez 13 Dec '17

13 Dec '17

Hi all, I am trying to virtually connect two bridges on different network namespaces inside a CentOS KVM host. I have tried different configs, but this is the most closer than I can test: ip netns add pubnet ip netns exec pubnet ip link set dev lo up ip netns exec pubnet ifup pubif2 ip link add dev vethpubif1 type veth peer name vethpubif2 ovs-vsctl add-port pubif1 vethpubif1 ip link set vethpubif2 netns pubnet ip netns exec pubnet brctl addif pubif2 vethpubif2 ip link set dev vethpubif1 up ip netns exec pubnet ip link set dev vethpubif2 up Bridge in the root host network namespace is openvswitch based, and bridge inside pubnet's network namespace is brctl based. Using this config, vms attached to pubif1 openvswitch based can't ping to vms connected to vms in pubif2 bridge. What am i doing wrong? Thanks. -- Greetings, C. L. Martinez

1 0

Centos 6 Samba 4 specific question
by Kienker, Fred 13 Dec '17

13 Dec '17

I am setting up a Samba 4 installation on CentOS 6.9. I have installed the samba4, samba4-common, and samba4-libs with all of the dependencies using YUM which appear to be all of the samba4 packages which are available. In the /usr/bin directory I can find smbcontrol and smbstatus but the smbpasswd command is missing. Checking on a current CentOS 7 all three of these commands are found. Of course with this command missing it’s quite hard to set up standard Samba users in the .tdb file used in the Classic mode. Can someone enlighten me as to what I have done wrong? Best regards, Fred

2 1

LUKS question
by Wells, Roger K. 13 Dec '17

13 Dec '17

I have existing systems with un-encrypted disks. I have tried unsuccessfully to encrypt them using LUKS. Has anyone out there been able to encrypt an existing system (after the fact, so to speak)? TIA -- Roger Wells, P.E. leidos 221 Third St Newport, RI 02840 401-847-4210 (voice) 401-849-1585 (fax) roger.k.wells(a)leidos.com

8 7

Mate desktop configuration question
by me＠tdiehl.org 12 Dec '17

12 Dec '17

Hi, I am using Mate Desktop from EPEL on a C7.4 system with multiple desktops enabled. Does anyone know how to force alt tab to only switch between applications on the current desktop? Currently it seems that it picks some random app from another desktop that I was on previously (most time the browser). I only want it to chose from apps on the current desktop. It used to work they way that I want but when I upgraded to 7.4 it broke. I seem to remember when I built this machine there was a check box somewhere to control that behavior but I cannot find it. Regards, -- Tom me(a)tdiehl.org

1 0

upgrading python
by Larry Martell 12 Dec '17

12 Dec '17

I am running CentOS 7 and I have python version: Python 2.7.5 (default, Sep 15 2016, 22:37:39) I need a newer version of 2.7 to pick up a bug fix. How can I do that (without breaking anything in CentOS)?

10 23

CentOS-announce Digest, Vol 154, Issue 2
by centos-announce-request＠centos.org 09 Dec '17

09 Dec '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:3402 Moderate CentOS 7 postgresql Security Update (Johnny Hughes) 2. CEBA-2017:3397 CentOS 7 libvirt BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Sat, 9 Dec 2017 01:12:18 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:3402 Moderate CentOS 7 postgresql Security Update Message-ID: <20171209011218.GA60295(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:3402 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2017:3402 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: ebc21ceabf8beed3b7b9579cf28e90e0205cac9cacbea2591790f63399523f43 postgresql-9.2.23-3.el7_4.i686.rpm f055cc78d37e04f70a3db95623c2ca7471d5aae086b1e8136093aaa7121f714b postgresql-9.2.23-3.el7_4.x86_64.rpm da812088b757536335128c97674a268514aa2b6bc533465a469099fcc3117575 postgresql-contrib-9.2.23-3.el7_4.x86_64.rpm a574a2fa6ae283484bd48314ab6955e865225d8d5412d3cbbac382f6d48be7cd postgresql-devel-9.2.23-3.el7_4.i686.rpm 82ad0b17b461bd6217602bd7e3cb7865be09476aa9ace9ccf7da912d008d6073 postgresql-devel-9.2.23-3.el7_4.x86_64.rpm 54bb78b193ef24688c22ba2cc0ce3b0fd61f9766b6c813985322a594728c93c1 postgresql-docs-9.2.23-3.el7_4.x86_64.rpm d3f52343b02ead5afab52f019be4ce2edcabd2ba515bfe31ef76a1ea6b06bb82 postgresql-libs-9.2.23-3.el7_4.i686.rpm 050337bfc9d3b15c2776c8c31479019058e54e1ce2fa9656033ebb2fc0a49230 postgresql-libs-9.2.23-3.el7_4.x86_64.rpm 48c69f5753bf40227e50a46876796361accfa630970c8e93f126557e125b1931 postgresql-plperl-9.2.23-3.el7_4.x86_64.rpm e311b9ce20ad0fcd0390e6f509db91039c8c3fe20f5970a0fff836b9764a6d2b postgresql-plpython-9.2.23-3.el7_4.x86_64.rpm 89a290c184e62234310ca82b81055c2dd37b23a42eba08e9c0ada3a04c814bc1 postgresql-pltcl-9.2.23-3.el7_4.x86_64.rpm 799b62b93262b3882ab506ba80cca06fc81bad801a5daddd39366428edf771ee postgresql-server-9.2.23-3.el7_4.x86_64.rpm e0a687fc8c5d74ab396f0abb472d28d0ace98d51eccb31a0a9ec697ca2e67d00 postgresql-static-9.2.23-3.el7_4.i686.rpm 7322db0298b80fb21ce6ca635599ec6bdde2becbf9d62c3b292acb472330bc7f postgresql-static-9.2.23-3.el7_4.x86_64.rpm c63eef7396500d519a0187dba754c4f2bb6491cee0eeb7971a6734e81cbb84ed postgresql-test-9.2.23-3.el7_4.x86_64.rpm f5eb93288be8de28eb1f9161fd6e0e5aff20dad18124e4ec1e3bb8a5bc69a246 postgresql-upgrade-9.2.23-3.el7_4.x86_64.rpm Source: d4fc6f4b8c74daa73bdb2522b5aeaa538df42e09b5b31265bc7766a955875feb postgresql-9.2.23-3.el7_4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Sat, 9 Dec 2017 01:13:48 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2017:3397 CentOS 7 libvirt BugFix Update Message-ID: <20171209011348.GA60533(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2017:3397 Upstream details at : https://access.redhat.com/errata/RHBA-2017:3397 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: b4e03f352b03e9c9cedc94895fe58258e1443080a35ca6182f89453e24c121cf libvirt-3.2.0-14.el7_4.5.x86_64.rpm 5df47e144d7bc868697a96743e4856deb9bebe1895de9a7f04345fa91cb1919d libvirt-admin-3.2.0-14.el7_4.5.x86_64.rpm cb038daa2efb8bcefc3a3f6691513da39209125b5d1ce6fc1c3622e64441b7e9 libvirt-client-3.2.0-14.el7_4.5.i686.rpm f4996e90fdc4b416414f5659b1a1331b2126267b944108f964eed2144b998abc libvirt-client-3.2.0-14.el7_4.5.x86_64.rpm 69a0abb8a4b52ac232340009030504c6a81405e94cee2c325aaa698f3523e2fc libvirt-daemon-3.2.0-14.el7_4.5.x86_64.rpm 115d6b75bccbb080f7e2249266abafe72b70fe608fba5733540217433040065b libvirt-daemon-config-network-3.2.0-14.el7_4.5.x86_64.rpm 45afc89baa336a5c9b91d40e029b827dd716f0f4e4e291be4632b2198341819c libvirt-daemon-config-nwfilter-3.2.0-14.el7_4.5.x86_64.rpm 3b15cfcf1eefa808957d03e5ec51162535d87cabdb9c09630deb06a095097229 libvirt-daemon-driver-interface-3.2.0-14.el7_4.5.x86_64.rpm aed20b0e7e8d250e6c30656cf3fc99efc686b8559333fc9303c53e1fee672af1 libvirt-daemon-driver-lxc-3.2.0-14.el7_4.5.x86_64.rpm d30a76e8e51af36ed6a706d1795f8992f70e17be7b407ebc0f7f3e5679b26671 libvirt-daemon-driver-network-3.2.0-14.el7_4.5.x86_64.rpm b599a46ab37e2f076aada87ea13b1f74ec422c0e9db1a4c0107711948485e1ae libvirt-daemon-driver-nodedev-3.2.0-14.el7_4.5.x86_64.rpm 78a580d9d11ded1cc70481f6029f1e68cb42dd2c3a9817d65d41d6a57dbe5b4d libvirt-daemon-driver-nwfilter-3.2.0-14.el7_4.5.x86_64.rpm 1989e56a3271b0a9c79e2764743c19bbb65078852f60df1a36e0a433efd679ce libvirt-daemon-driver-qemu-3.2.0-14.el7_4.5.x86_64.rpm a0df66fb35c43a72cf33640abe0ae216ad1a1ec28f8fcc4b1c9b9cbebf056ee0 libvirt-daemon-driver-secret-3.2.0-14.el7_4.5.x86_64.rpm cd4f8548912bafb69a1e68200044668da5a6bd7f50bb710deaca9cc953ae41b3 libvirt-daemon-driver-storage-3.2.0-14.el7_4.5.x86_64.rpm f101e598269cd0032daf284c3b7abf7e4941b7abf7fb4a794fae57aafbc52dbb libvirt-daemon-driver-storage-core-3.2.0-14.el7_4.5.x86_64.rpm 8f4c34fd5072197ec6032bcda8f79d0a627161fffee75f8a2243a1cc44806517 libvirt-daemon-driver-storage-disk-3.2.0-14.el7_4.5.x86_64.rpm 3108a2e17d78bd48163b0bf08f5e42dff3bdd364e8e9a6a44146894f63ed0cac libvirt-daemon-driver-storage-gluster-3.2.0-14.el7_4.5.x86_64.rpm 271e3458e66e34234f9a1f0156e0b328ef585b41e6e1a231d4acc9e92f0db22a libvirt-daemon-driver-storage-iscsi-3.2.0-14.el7_4.5.x86_64.rpm 2a69a2142f54e43889ef8d56b0179b029211671e18fffaa39dea360226a339c4 libvirt-daemon-driver-storage-logical-3.2.0-14.el7_4.5.x86_64.rpm a691cc37c6a62c8a936977f3a51d48d171ec29a5b88de77c783b3172ef7b820f libvirt-daemon-driver-storage-mpath-3.2.0-14.el7_4.5.x86_64.rpm ce1423980ed2fe2e7aed7af287d9dc6ab184d45bee0a2f9093178f483b55f2bf libvirt-daemon-driver-storage-rbd-3.2.0-14.el7_4.5.x86_64.rpm 0081eee188acf10e4573dd60a3a7500bd8ec17c5cf56506c0f49f426056604b9 libvirt-daemon-driver-storage-scsi-3.2.0-14.el7_4.5.x86_64.rpm af5a65e5b83c6b33b4f533d6822e5851ab4bfec541bd102a64af18c09d252b07 libvirt-daemon-kvm-3.2.0-14.el7_4.5.x86_64.rpm 7283e0ba5f9cfcc0bb447ca98e0af91caae0611de4b7b53dfe6fd376251a9a95 libvirt-daemon-lxc-3.2.0-14.el7_4.5.x86_64.rpm 33b34721c4c7354c0d79c27d3dd8ba3ec64058030b001851b4e629ce41bd798a libvirt-devel-3.2.0-14.el7_4.5.i686.rpm 28c058c41a4ae95af03831c67fdd5d46a29e5f8e44138da696bbcb865c84bf79 libvirt-devel-3.2.0-14.el7_4.5.x86_64.rpm bdbd9652f0d1d650561189758b319206c308d978202e17c55ed85d950009090d libvirt-docs-3.2.0-14.el7_4.5.x86_64.rpm cc5d61d7b7e121a9772a3a8cb6f749e4d93ff913c4663cdf231b29f9ef15dd06 libvirt-libs-3.2.0-14.el7_4.5.i686.rpm 6f97604af56cdffcb6ec95243ac38e0240de8efd88c54cca973b0a08d3f8b53a libvirt-libs-3.2.0-14.el7_4.5.x86_64.rpm f4ef14f544074e71e3b45bd01accca04f9669267abfba5e0d14680463334650f libvirt-lock-sanlock-3.2.0-14.el7_4.5.x86_64.rpm 3fe8c3c8e27de696ae6b434b8d8e4d54e82b731b5d37e963fa499832e8322f8a libvirt-login-shell-3.2.0-14.el7_4.5.x86_64.rpm c45f4089d983c25634f99a3635330b017712c2917ba78d5a857b650fc27606e0 libvirt-nss-3.2.0-14.el7_4.5.i686.rpm 9b7a2e3f0804be7370aa68ca61a6682736240b90dd1da08e552f6aa8dd8b97a6 libvirt-nss-3.2.0-14.el7_4.5.x86_64.rpm Source: c3b2d2110f4938d787177481c619d4b403e68dac442678578ced52d3ff5ed06a libvirt-3.2.0-14.el7_4.5.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 154, Issue 2 ***********************************************

1 0

CAA records using PowerDNS from EPEL
by MRob 08 Dec '17

08 Dec '17

PowerDNS supports CAA records beginning with version 4.0, but the pdns package in EPEL for most recent centos versions is stuck at around version 3.4 (3.4.11 is what I have). Do I have no other choice but to manually compile and maintain my own pdns installation? I prefer to avoid this but I need up-to-date features. Perhaps there is a PowerDNS specific work-around? Maybe the EPEL maintainers backported CAA record support? Thank you for any assistance.

2 2

Switch off laptop screen when docked with lid close - CentOS 7
by Toralf Lund 07 Dec '17

07 Dec '17

Hi, I'm using CentOS on a laptop that part of the time is connected to a docking station with two monitor connected to it. When the laptop lid is docked, its lid is closed, as the system is placed in a position where it's not convenient to keep it open, let alone look at the screen. Now in the past, with CentOS 5 (on a different laptop, but same physical config) and 6, the screen has automatically been switched off in this configuration - it's been as if it was no longer there after I docked the machine, which is of course exactly what I want. After I recently switched to CentOS 7, however, I no longer get this behaviour. Even thought I can't see the screen, it's obvious that it's on, or at least the system thinks so - it appears in display config, and xrandr mentions it as "connected". Any idea what's going on? Shouldn't the screen just switch of automatically? What part of the system is supposed to handle this anyway? And what's the best way around my problem? I've already disabled the screen in Display preferences, of course, but it seems like the situation should ideally be handled at a more global level, and also, *my* display config obviously has no effect on the login manager. Which means I can't really log in while the machine is locked, as the monitor is then still on, and guess where the login window appears... Thanks, - Toralf

2 2

yum files in /tmp
by Jerry Geis 07 Dec '17

07 Dec '17

I am getting /tmp/yum_save_tx.2017-12..... files in /tmp one every hour. What process is making these files ??? I have stopped PackageKit so its not running. I am running CentOS 7.4. With GNOME desktop. Thanks Jerry

4 5

Linux IO Performance Monitor
by Ali Mumcu 06 Dec '17

06 Dec '17

Hello Friends, I wanna to ask how to learn disk (read,write) latency on linux server I use "iostat -kx 5" command to learn latency. But i cant understand which field show latency, svctm or iowait ? And if value svctm is gerater than 15 ms can we say there is a slowly io performance ? And i wanna to learn can we list io latency and utilization for per process? Thanks.

2 1

Migrating From CentOS-6 To CentOS-7
by Eugene Poole 05 Dec '17

05 Dec '17

I asked this in Vol 154, Issue 29: I've a system that has been running CentOS 6 64-bit for almost 4-years and I want to start the move to CentOS 7 64-bit. I run software RAID-1 with LVM everywhere except /boot which is a standard partition RAID-1. There are 2 areas that concern me greatly about this migration: 1. How do I duplicate my current grub configuration file that supports a failure of /dev/sda to grub2? 2. How do I install CentOS 7 but use my existing hard drive layout so I only format specific OS file systems. My drive layout goes back to the original proposed FHS layout. The separate partitions related to the operating system are: /boot 1GB (standard boot as defined in fstab is /dev/md0) The following file systems are all defined in volume group vg_jpdopsys (size is 64 GB) / (root) 6GB /home 4GB /opt 4GB /tmp 2GB /usr 12GB /usr/local 2GB /var 8GB The following file system is defined in volume group vg_jpdswap (size is 24 GB) swap 16GB Plus many other file system dedicated to specific applications and data all using logical volume management. When I moved from CentOS 5 to CentOS 6 all of the OS partitions were formatted except /home. All went extremely well then. But I don't see a way to do that with CentOS 7 retaining the existing disk configuration. Is there some detailed installation instructions showing some advanced methods? TIA Gene If you saw the original post you will see that I did clean it up a bit. I'm starting this move now understanding that I have until 2020 to do it. Any suggestions? TIA Gene -- Eugene Poole Woodstock, Georgia

1 0

Run as root w/o terminal/gksu-polkit uses 100 % CPU
by Toralf Lund 05 Dec '17

05 Dec '17

Hi, On CentOS 7, what's the best way to start a GUI program as root without a terminal? I mean, from a launcher or similar where you can't provide terminal input to "sudo". I'm talking about applications that aren't configured to switch to root out-of-the box, of course. I just tried gksu-polkit from EPEL, and it kind of did the job but: 1. It consumed *a lot* of resources - CPU usage was reported at a constant 100 %, more or less. 2. The process did not go away after I closed the application. Which means it's practically unusable, unless someone can provide a way to fix these problems. Thanks, - Toralf

1 0

Re: [CentOS] Broadcom BCM4360
by galtsev＠kicp.uchicago.edu 05 Dec '17

05 Dec '17

On Mon, December 4, 2017 1:40 am, Alice Wonder wrote: > On 12/03/2017 11:10 PM, Phil Perry wrote: >> On 04/12/17 00:38, John R Pierce wrote: >>> On 12/3/2017 4:22 PM, Gregory P. Ennis wrote: >>>> I have not been able to get it to work Centos 7.4 machine. Some of >>>> the >>>> centos user posts had indicated the nux repsitory had a Centos 7 >>>> kmod- >>>> wl, but it is not present when I tried to search or or install it at >>>> this time. >>> >>> this looks potentionally helpful >>> >>> http://elrepo.org/tiki/wl-kmod >>> >>> it appears those are closed source drivers with funky licenses, so >>> they can't just be redistributed without assumption of liability. >>> >>> >> >> Correct, elrepo isn't able to freely redistribute the drivers due >> Broadcom's licensing, but does provide instructions and a SRPM (minus >> tarball) for you to build yourself. Every time I encounter big enough trouble about some chipset to have to learn a bit about its internals, I usually learn about its engineering flaw. BCM43xx has the following one: the chip internally is 32 bit, though it sits on 64 bit bus. (Take that with a grain of salt, it's been long time since I looked into that crap). Once I discover the flaw, I add particular hardware in my black list and do my best to not buy anything containing it. Broadcom as a whole is not in my black list, they have great hardware, but their BCM43XX is, even if they corrected their design flaws since. I would replace that if possible (Intel would be great candidate), or use USB adapters others suggest. Just my $0.02 Valeri > > That's what I have to do, and it can sometimes be a PITA because a > kernel update can break it and you have to build it again. > > With major updates (like 7.3 to 7.4) you sometimes have to download a > new nosrc rpm. > >> >> Alternatively, for $8 you can purchase an adaptor that is natively >> supported and will work out of the box: >> >> https://www.amazon.com/Edimax-EW-7811Un-150Mbps-Raspberry-Supports/dp/B003M… >> >> >> https://www.newegg.com/Product/Product.aspx?Item=N82E16833315091&cm_re=edim… >> >> >> The above adaptor is based on the Realtek RTL8188CUS chipset and uses >> the rtl8192cu kernel driver. > > At some point I will be replacing mine, but with a low-profile PCI-E > card. I've had bad luck with USB wifi adapters, sometimes for example > they lose connection when a microwave is turned on and when I was > visiting my parents, had one that lost connection whenever the AC unit > kicked on. > > My best wifi experience in Linux has been with my T series thinkpad, it > uses some kind of Intel wireless chipset that is in the kernel. > > I'm going to be looking for a low profile Intel PCI-E card, but for now > my broadcom PCI-E actually works quite well - with the exception of > needing to rebuild every now and then (last time was 7.3 to 7.4 update) > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos > ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++

3 2

problem with cloud-init-0.7.9-9.el7.centos.2.x86_64 setting up puppet.conf
by ybaumy＠lost-frequencies.cloud 04 Dec '17

04 Dec '17

When running cloud-init im getting the following error Cloud-init v. 0.7.9 running 'modules:config' at Mon, 04 Dec 2017 18:07:26 +0000. Up 2597.52 seconds. Loaded plugins: fastestmirror, product-id, search-disabled-repos, subscription-manager This system is not registered with an entitlement server. You can use subscription-manager to register. Loading mirror speeds from cached hostfile * base: mirror.yannic-bonenberger.com * extras: mirror.yannic-bonenberger.com * updates: centos.bio.lmu.de Package puppet-agent-1.10.9-1.el7.x86_64 already installed and latest version Nothing to do 2017-12-04 18:07:27,102 - util.py[WARNING]: Running module puppet (<module 'cloudinit.config.cc_puppet' from '/usr/lib/python2.7/site-packages/cloudinit/config/cc_puppet.pyc'>) failed This is from /var/log/cloud-init.log ------------------------- 2017-12-04 18:07:26,579 - stages.py[DEBUG]: Running module puppet (<module 'cloudinit.config.cc_puppet' from '/usr/lib/python2.7/site-packages/cloudinit/config/cc_puppet.pyc'>) with frequency once-per-instance 2017-12-04 18:07:26,579 - handlers.py[DEBUG]: start: modules-config/config-puppet: running config-puppet with frequency once-per-instance 2017-12-04 18:07:26,579 - util.py[DEBUG]: Writing to /var/lib/cloud/instances/nocloud/sem/config_puppet - wb: [420] 20 bytes 2017-12-04 18:07:26,580 - util.py[DEBUG]: Restoring selinux mode for /var/lib/cloud/instances/nocloud/sem/config_puppet (recursive=False) 2017-12-04 18:07:26,580 - util.py[DEBUG]: Restoring selinux mode for /var/lib/cloud/instances/nocloud/sem/config_puppet (recursive=False) 2017-12-04 18:07:26,581 - helpers.py[DEBUG]: Running config-puppet using lock (<FileLock using file '/var/lib/cloud/instances/nocloud/sem/config_puppet'>) 2017-12-04 18:07:26,581 - cc_puppet.py[DEBUG]: Attempting to install puppet latest, 2017-12-04 18:07:26,581 - util.py[DEBUG]: Running command ['yum', '-t', '-y', 'install', 'puppet'] with allowed return codes [0] (shell=False, capture=False) 2017-12-04 18:07:27,101 - util.py[DEBUG]: Reading from /etc/puppet/puppet.conf (quiet=False) 2017-12-04 18:07:27,102 - handlers.py[DEBUG]: finish: modules-config/config-puppet: FAIL: running config-puppet with frequency once-per-instance 2017-12-04 18:07:27,102 - util.py[WARNING]: Running module puppet (<module 'cloudinit.config.cc_puppet' from '/usr/lib/python2.7/site-packages/cloudinit/config/cc_puppet.pyc'>) failed 2017-12-04 18:07:27,102 - util.py[DEBUG]: Running module puppet (<module 'cloudinit.config.cc_puppet' from '/usr/lib/python2.7/site-packages/cloudinit/config/cc_puppet.pyc'>) failed Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/cloudinit/stages.py", line 777, in _run_modules freq=freq) File "/usr/lib/python2.7/site-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python2.7/site-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python2.7/site-packages/cloudinit/config/cc_puppet.py", line 107, in handle contents = util.load_file(PUPPET_CONF_PATH) File "/usr/lib/python2.7/site-packages/cloudinit/util.py", line 1278, in load_file with open(fname, 'rb') as ifh: IOError: [Errno 2] No such file or directory: '/etc/puppet/puppet.conf ------------------------ To get around this error with the missing /etc/puppet/puppet.conf I created a directory and link for the .conf since the original location is in /etc/puppetlabs/puppet/puppet.conf [root@kent-hanchett puppet]# pwd /etc/puppet [root@kent-hanchett puppet]# ls -la total 12 drwxr-xr-x. 2 root root 29 Dec 4 18:13 . drwxr-xr-x. 79 root root 8192 Dec 4 18:13 .. lrwxrwxrwx. 1 root root 34 Dec 4 18:13 puppet.conf.old -> /etc/puppetlabs/puppet/puppet.conf But after the run you can see that it was renamed to .old and the error appears again. So how can I set either to correct path to puppet.conf or how do I handle this situation? Any ideas would be appreciated. BR Christian

1 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss