Discuss

discuss@lists.centos.org

34753 discussions

Avago (LSI) SAS-3 controller, poor performance on CentOS 7
by Gordon Messmer 18 Jan '17

18 Jan '17

I have a handful of new systems where I've seen unexpectedly low disk performance on an Avago SAS controller, when using CentOS 7. It looked like a regression, so I installed CentOS 6 on one of them and reloaded CentOS 7 on the other. Immediately after install, a difference is apparent in the RAID rebuild speed. The CentOS 6 system is initializing its software RAID5 array at somewhere around 120MB/s, while the CentOS 7 system is rebuilding at around 55MB/s. It took a while to get an older system installed, and I wasn't able to boot CentOS 6 under UEFI, to that's one difference between the systems. I also set the elevator on CentOS 7 to cfq, to match the CentOS 6 system. That didn't have any apparent effect. Other than that, the kernel reports "MSI-X vectors supported: 96" on C6, but "MSI-X vectors supported: 8" on C7. I don't know if that's a difference that would affect performance. Does anyone have experience with these controllers? Any pointers while I continue tracking this down? Output from lspci follows, as well as dmesg output regarding the MPT controller and the RAID array status on C6 and C7. 01:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02) Subsystem: LSI Logic / Symbios Logic Device 30e0 Physical Slot: 1 Flags: bus master, fast devsel, latency 0, IRQ 24 I/O ports at e000 [size=256] Memory at fb240000 (64-bit, non-prefetchable) [size=64K] Memory at fb200000 (64-bit, non-prefetchable) [size=256K] Expansion ROM at fb100000 [disabled] [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [68] Express Endpoint, MSI 00 Capabilities: [d0] Vital Product Data Capabilities: [a8] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=96 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [1e0] #19 Capabilities: [1c0] Power Budgeting <?> Capabilities: [190] #16 Capabilities: [148] Alternative Routing-ID Interpretation (ARI) Kernel driver in use: mpt3sas CentOS 6: # dmesg | grep -i mpt mpt3sas version 09.102.00.00-rh loaded mpt3sas 0000:01:00.0: PCI INT A -> GSI 26 (level, low) -> IRQ 26 mpt3sas 0000:01:00.0: setting latency timer to 64 mpt3sas_cm0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (32772632 kB) mpt3sas_cm0: MSI-X vectors supported: 96, no of cores: 12, max_msix_vectors: -1 mpt3sas 0000:01:00.0: irq 60 for MSI/MSI-X mpt3sas 0000:01:00.0: irq 61 for MSI/MSI-X mpt3sas 0000:01:00.0: irq 62 for MSI/MSI-X mpt3sas 0000:01:00.0: irq 63 for MSI/MSI-X mpt3sas 0000:01:00.0: irq 64 for MSI/MSI-X mpt3sas 0000:01:00.0: irq 65 for MSI/MSI-X mpt3sas 0000:01:00.0: irq 66 for MSI/MSI-X mpt3sas 0000:01:00.0: irq 67 for MSI/MSI-X mpt3sas 0000:01:00.0: irq 68 for MSI/MSI-X mpt3sas 0000:01:00.0: irq 69 for MSI/MSI-X mpt3sas 0000:01:00.0: irq 70 for MSI/MSI-X mpt3sas 0000:01:00.0: irq 71 for MSI/MSI-X mpt3sas0-msix0: PCI-MSI-X enabled: IRQ 60 mpt3sas0-msix1: PCI-MSI-X enabled: IRQ 61 mpt3sas0-msix2: PCI-MSI-X enabled: IRQ 62 mpt3sas0-msix3: PCI-MSI-X enabled: IRQ 63 mpt3sas0-msix4: PCI-MSI-X enabled: IRQ 64 mpt3sas0-msix5: PCI-MSI-X enabled: IRQ 65 mpt3sas0-msix6: PCI-MSI-X enabled: IRQ 66 mpt3sas0-msix7: PCI-MSI-X enabled: IRQ 67 mpt3sas0-msix8: PCI-MSI-X enabled: IRQ 68 mpt3sas0-msix9: PCI-MSI-X enabled: IRQ 69 mpt3sas0-msix10: PCI-MSI-X enabled: IRQ 70 mpt3sas0-msix11: PCI-MSI-X enabled: IRQ 71 mpt3sas_cm0: iomem(0x00000000fb240000), mapped(0xffffc90013ee0000), size(65536) mpt3sas_cm0: ioport(0x000000000000e000), size(256) mpt3sas_cm0: sending message unit reset !! mpt3sas_cm0: message unit reset: SUCCESS mpt3sas_cm0: Allocated physical memory: size(17971 kB) mpt3sas_cm0: Current Controller Queue Depth(9979),Max Controller Queue Depth(10240) mpt3sas_cm0: Scatter Gather Elements per IO(128) mpt3sas_cm0: LSISAS3008: FWVersion(10.00.00.00), ChipRevision(0x02), BiosVersion(08.25.00.00) mpt3sas_cm0: Protocol=( scsi0 : Fusion MPT SAS Host mpt3sas_cm0: sending port enable !! mpt3sas_cm0: host_add: handle(0x0001), sas_addr(0x500605b00aee5510), phys(8) mpt3sas_cm0: port enable: SUCCESS # cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] [raid1] md0 : active raid1 sda2[0] sdb2[1] 999360 blocks super 1.0 [2/2] [UU] md1 : active raid5 sdf3[6] sde3[4] sdd3[3] sdc3[2] sda3[0] sdb3[1] 19528458240 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/5] [UUUUU_] [====>................] recovery = 22.1% (864374932/3905691648) finish=417.0min speed=121538K/sec bitmap: 1/30 pages [4KB], 65536KB chunk unused devices: <none> CentOS 7: # dmesg | grep -i mpt mpt3sas version 04.100.00.00 loaded mpt3sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (32674176 kB) mpt3sas0: MSI-X vectors supported: 8, no of cores: 12, max_msix_vectors: 8 mpt3sas 0000:01:00.0: irq 45 for MSI/MSI-X mpt3sas 0000:01:00.0: irq 46 for MSI/MSI-X mpt3sas 0000:01:00.0: irq 47 for MSI/MSI-X mpt3sas 0000:01:00.0: irq 49 for MSI/MSI-X mpt3sas 0000:01:00.0: irq 50 for MSI/MSI-X mpt3sas 0000:01:00.0: irq 51 for MSI/MSI-X mpt3sas 0000:01:00.0: irq 52 for MSI/MSI-X mpt3sas 0000:01:00.0: irq 53 for MSI/MSI-X mpt3sas0-msix0: PCI-MSI-X enabled: IRQ 45 mpt3sas0-msix1: PCI-MSI-X enabled: IRQ 46 mpt3sas0-msix2: PCI-MSI-X enabled: IRQ 47 mpt3sas0-msix3: PCI-MSI-X enabled: IRQ 49 mpt3sas0-msix4: PCI-MSI-X enabled: IRQ 50 mpt3sas0-msix5: PCI-MSI-X enabled: IRQ 51 mpt3sas0-msix6: PCI-MSI-X enabled: IRQ 52 mpt3sas0-msix7: PCI-MSI-X enabled: IRQ 53 mpt3sas0: iomem(0x00000000fb240000), mapped(0xffffc90013180000), size(65536) mpt3sas0: ioport(0x000000000000e000), size(256) mpt3sas0: sending message unit reset !! mpt3sas0: message unit reset: SUCCESS mpt3sas0: Allocated physical memory: size(17329 kB) mpt3sas0: Current Controller Queue Depth(9979),Max Controller Queue Depth(10240) mpt3sas0: Scatter Gather Elements per IO(128) mpt3sas0: LSISAS3008: FWVersion(10.00.00.00), ChipRevision(0x02), BiosVersion(08.25.00.00) mpt3sas0: Protocol=( scsi host0: Fusion MPT SAS Host mpt3sas0: sending port enable !! mpt3sas0: host_add: handle(0x0001), sas_addr(0x500605b00aee5ca0), phys(8) mpt3sas0: port enable: SUCCESS # cat /proc/mdstat Personalities : [raid1] [raid6] [raid5] [raid4] md125 : active raid1 sda1[0] sdb1[1] 194496 blocks super 1.0 [2/2] [UU] md126 : active raid5 sdf3[6] sda3[0] sde3[4] sdd3[3] sdc3[2] sdb3[1] 19528458240 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/5] [UUUUU_] [=========>...........] recovery = 47.6% (1862704880/3905691648) finish=569.6min speed=59772K/sec bitmap: 2/30 pages [8KB], 65536KB chunk md127 : active raid1 sda2[0] sdb2[1] 999360 blocks super 1.0 [2/2] [UU] unused devices: <none>

3 5

Centos 7 dhcpd failure to allow a 2nd network over same interal nic
by Gregory P. Ennis 18 Jan '17

18 Jan '17

Everyone, I am trying to set up a second internal network (192.168.0.0/24) and have not been able to get dhcp to start when I have the following in my dhcpd.conf file : subnet 192.168.0.0 netmask 255.255.255.0 { range 192.168.0.110 192.168.0.130; option subnet-mask 255.255.255.0; option broadcast-address 192.168.0.255; option routers 192.168.0.1; option domain-name-servers 192.168.0.1; } When i remove the above from dhcpd.conf dhcpd works perfectly I have my internal nic card set with two ip addresses one of which is 192.168.0.1. the other address is my standard internal network address. I have also set up the domain server to allow access from 192.168.0.0/24, and the firewall allows internal access to the same subnet. The error that I get is the following : Job for dhcpd.service failed because the control process exited with error code. See "systemctl status dhcpd.service" and "journalctl -xe" for details. When I evaluate journalctl -xe the following is obtained : dhcpd[18763]: Internet Systems Consortium DHCP Server 4.2.5 dhcpd[18763]: Copyright 2004-2013 Internet Systems Consortium. dhcpd[18763]: All rights reserved. dhcpd[18763]: For info, please visit https://www.isc.org/software/dhcp/ dhcpd[18763]: Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file dhcpd[18763]: Internet Systems Consortium DHCP Server 4.2.5 dhcpd[18763]: Copyright 2004-2013 Internet Systems Consortium. dhcpd[18763]: All rights reserved. dhcpd[18763]: For info, please visit https://www.isc.org/software/dhcp/ dhcpd[18763]: Wrote 0 deleted host decls to leases file. dhcpd[18763]: Wrote 0 new dynamic host decls to leases file. dhcpd[18763]: Wrote 2 leases to leases file. dhcpd[18763]: Interface enp0s29u1u2 matches multiple shared networks dhcpd[18763]: dhcpd[18763]: This version of ISC DHCP is based on the release available dhcpd[18763]: on ftp.isc.org. Features have been added and other changes dhcpd[18763]: have been made to the base software release in order to make dhcpd[18763]: it work better with this distribution. dhcpd[18763]: dhcpd[18763]: Please report for this software via the CentOS Bugs Database: dhcpd[18763]: http://bugs.centos.org/ dhcpd.service: main process exited, code=exited, status=1/FAILURE dhcpd[18763]: systemd[1]: Failed to start DHCPv4 Server Daemon. When I review the information about dhcpd it appears that it can manage the ip addresses for two networks on different nic cards, but is there a problem in having it manage two networks on the same nic card? Does anyone have any ideas? Would sure appreciate your help. Greg Ennis -- Greg Ennis PoMec Corporation www.PoMec.Net

8 16

Centos7: disable hot-corner
by johan.vermeulen7＠telenet.be 18 Jan '17

18 Jan '17

Hello All, I switched some laptops over from Mate to Gnome. Now I would like to disable the hot -switch-to-gnome3- corner. When googling this, I see a lot of posts referring to /usr/share/gnome-shell/js /...... but the js dir is not there on my system. I also see posts referring to gnome-extensions, but I need to do it remotely from the cli. Can anyone help with this? Greetings, J.

1 0

PI3
by Jerry Geis 18 Jan '17

18 Jan '17

Hi All, I downloaded: http://mirror.centos.org/altarch/7/isos/armhfp/ for the PI3 This article says the PI3 runs X. http://news.softpedia.com/news/centos-7-linux-officially-released-for-raspb… When I groupinstall Gnome desktop and reboot, then run startx I get an error about no screens found. Whats the trick to get X on the PI3? Thanks, Jerry

3 3

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

18 Jan '17

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2017:0063 Important CentOS 5 bind Security Update (Johnny Hughes) 2. CESA-2017:0064 Important CentOS 5 bind97 Security Update (Johnny Hughes) 3. CESA-2017:0062 Important CentOS 7 bind Security Update (Johnny Hughes) 4. CESA-2017:0063 Important CentOS 6 bind Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 17 Jan 2017 13:00:14 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:0063 Important CentOS 5 bind Security Update Message-ID: <20170117130014.GA12460(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:0063 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0063.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 476cd5104692bcf026b6db800aeecff31c5600f3d64fac08084c3d61853f0645 bind-9.3.6-25.P1.el5_11.12.i386.rpm d526c2176aed4fee687f110fe8d892bcc553bcb1a756fb0cafd8b90643723a92 bind-chroot-9.3.6-25.P1.el5_11.12.i386.rpm f021b8dcca512def5daf9030caa562d29d25722c9537880d57cb2810dfb2e18b bind-devel-9.3.6-25.P1.el5_11.12.i386.rpm 4ed7fef04663dd5698df65b8330f761f8b3baf4d6f0d9724dc805c490f99a075 bind-libbind-devel-9.3.6-25.P1.el5_11.12.i386.rpm 355bc4519a8e4407a58c6ff57f9f73aa0f0e58a5c387ddebb2b501d203d717fd bind-libs-9.3.6-25.P1.el5_11.12.i386.rpm c39fde90b9dae40891146c07e22fa86efa67b1b7c3398342a02e3f4e8a00efd7 bind-sdb-9.3.6-25.P1.el5_11.12.i386.rpm 1a0aac18b38c02f92d46679e1bf597c34736ebb52babe608db6a027cd33dbfa2 bind-utils-9.3.6-25.P1.el5_11.12.i386.rpm a0e4df6c9c9a8e71ba271a273499f89ad8711f526e6e3f96d12cc3f975916802 caching-nameserver-9.3.6-25.P1.el5_11.12.i386.rpm x86_64: e82197a8f8b22b38fc714a1d11ef84cea29dfefef9eb54ad294922f720b8c3ef bind-9.3.6-25.P1.el5_11.12.x86_64.rpm ad683a24813a69d495ae71e5894b85de01414773b793ed916b36bb522b7c2342 bind-chroot-9.3.6-25.P1.el5_11.12.x86_64.rpm f021b8dcca512def5daf9030caa562d29d25722c9537880d57cb2810dfb2e18b bind-devel-9.3.6-25.P1.el5_11.12.i386.rpm a2870ab0a9bafe00d644546d951804d9953534de6a236253585367d512122fbf bind-devel-9.3.6-25.P1.el5_11.12.x86_64.rpm 4ed7fef04663dd5698df65b8330f761f8b3baf4d6f0d9724dc805c490f99a075 bind-libbind-devel-9.3.6-25.P1.el5_11.12.i386.rpm 7a2b25aa3226c64f5f454da3e3d52672a0e8da89fd38b7c614384266097d576c bind-libbind-devel-9.3.6-25.P1.el5_11.12.x86_64.rpm 355bc4519a8e4407a58c6ff57f9f73aa0f0e58a5c387ddebb2b501d203d717fd bind-libs-9.3.6-25.P1.el5_11.12.i386.rpm 0e1b85f2a746ce8a8548c3d22aa78a559cc75c7ff790a0169b2692a0132809b8 bind-libs-9.3.6-25.P1.el5_11.12.x86_64.rpm 1b15168ef3f4846baded7033e5184b6abfd24ed88bf5591d54b52b583bfcdb2e bind-sdb-9.3.6-25.P1.el5_11.12.x86_64.rpm 0f02b6e4925d97a6451bf2c4edc99b0d9d4f4c1757cd7403c9986fb2bfd61f7d bind-utils-9.3.6-25.P1.el5_11.12.x86_64.rpm 77ed878e16195d8314c9c2f95a4ba84a6d87254813d1abe517233f36b6b637cf caching-nameserver-9.3.6-25.P1.el5_11.12.x86_64.rpm Source: 897436d4f721c68e17038d55daac3947493f08a294a15a92cb211ac16c9a1605 bind-9.3.6-25.P1.el5_11.12.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ Message: 2 Date: Tue, 17 Jan 2017 13:00:47 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:0064 Important CentOS 5 bind97 Security Update Message-ID: <20170117130047.GA12610(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:0064 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0064.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 15901c27eb18339d100c822e229763b20a1c17442bc12394bf98d14b534f50db bind97-9.7.0-21.P2.el5_11.10.i386.rpm e628be5d4849b82e978989c405e4f3248f59d3bdeeb0ecc61216138a00f1061a bind97-chroot-9.7.0-21.P2.el5_11.10.i386.rpm ed3e8c4ef3105c25788a7a9f030f3992264d0a026d4dc56185cb3d8501dd3aff bind97-devel-9.7.0-21.P2.el5_11.10.i386.rpm 6621f2186190dca0b182539e7a6dc7fcb9be0e8ce08b157a9952209b17538e25 bind97-libs-9.7.0-21.P2.el5_11.10.i386.rpm 1e6dc63437f48c256ce341138759faf635b79afbb5fbc0cb1ca0b7e92828b530 bind97-utils-9.7.0-21.P2.el5_11.10.i386.rpm x86_64: f2c9671bbd0e1060fb57646a7095869fa6fd4d53b92422403c2ebf75899088b6 bind97-9.7.0-21.P2.el5_11.10.x86_64.rpm c459368a91c11712682af9cad9e4211d7a400f845981878eb36631087773d468 bind97-chroot-9.7.0-21.P2.el5_11.10.x86_64.rpm ed3e8c4ef3105c25788a7a9f030f3992264d0a026d4dc56185cb3d8501dd3aff bind97-devel-9.7.0-21.P2.el5_11.10.i386.rpm d1447bac46b92250da988fbba14372fdfd8e50b496630d220e2b3b7146d93b10 bind97-devel-9.7.0-21.P2.el5_11.10.x86_64.rpm 6621f2186190dca0b182539e7a6dc7fcb9be0e8ce08b157a9952209b17538e25 bind97-libs-9.7.0-21.P2.el5_11.10.i386.rpm 4ca5c353ee4caffccd0eb04ea239c30db06ff857020df3ed03eab8e0b68f7865 bind97-libs-9.7.0-21.P2.el5_11.10.x86_64.rpm 5b81957e075bb723933dbe8df9cbab893cffa8512d2ffaae0a9e2ec78c893da8 bind97-utils-9.7.0-21.P2.el5_11.10.x86_64.rpm Source: 258485f13396e50e1d83ca27fd2e4da0c96c0b8bc1ea3f54eca79006e6ca0c60 bind97-9.7.0-21.P2.el5_11.10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ Message: 3 Date: Tue, 17 Jan 2017 13:12:56 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:0062 Important CentOS 7 bind Security Update Message-ID: <20170117131256.GA36308(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:0062 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0062.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 922e6d7db809f86fb353cf2635724692c169f81b8f306372400e810dfcc7dd21 bind-9.9.4-38.el7_3.1.x86_64.rpm d7521bfd2279313d0ca6d92c2ca9f724c25a343cc3f7bf104d6bafdfe6c1baea bind-chroot-9.9.4-38.el7_3.1.x86_64.rpm 6745e01a27f6f2b0ee43040254f4737b455d6ed66ae161bf9c6b116572b3962f bind-devel-9.9.4-38.el7_3.1.i686.rpm 35898e81da63115180e390304796010f06b175f99598461efe2937e6b05dd17b bind-devel-9.9.4-38.el7_3.1.x86_64.rpm 8ba46f89c530972d8f7e60e25864437f265e76516bc3d51c949c3c85a65c6e75 bind-libs-9.9.4-38.el7_3.1.i686.rpm 5cfe528a1c12d5e97949cc56e89817c9156f5d46a674c2d1de2e21df5d441fe9 bind-libs-9.9.4-38.el7_3.1.x86_64.rpm 3e92363d65aa194ace31e76814279e88f64ed59921da6098189bb4e577c2a220 bind-libs-lite-9.9.4-38.el7_3.1.i686.rpm fcccb3dbd7846be233881a8c525d4515210c9d431921333ce4fc94697dd314c5 bind-libs-lite-9.9.4-38.el7_3.1.x86_64.rpm 07549f43dac929ba85a7e1123e4d8c3149a75947e8e88716588cd07f02cc7a2d bind-license-9.9.4-38.el7_3.1.noarch.rpm 85adc57e21acf71af69b06b17f236c3f8cdbfb2db660e97ef62d2332fbcbb41c bind-lite-devel-9.9.4-38.el7_3.1.i686.rpm 7c7bb26f5860bceacdb4884172daf16f04aee1e45bd61b1369448c6d9a08c6bd bind-lite-devel-9.9.4-38.el7_3.1.x86_64.rpm 533e77ad5b75b00ff4dc30640cb597f4d9471fbe8dec20ae0c537bb27c1f27a5 bind-pkcs11-9.9.4-38.el7_3.1.x86_64.rpm e81e12e30f217e052c830be848978e6aaf1792d49b5b790bfb740e66b9dc180f bind-pkcs11-devel-9.9.4-38.el7_3.1.i686.rpm 623b00adb0a66786faf9b7e7afe603534092cd4e0674eec44132b555af0c9077 bind-pkcs11-devel-9.9.4-38.el7_3.1.x86_64.rpm 6fee761a9ffde4503bb94a45b4480630801c30c8815c0b7153f9c2665ba4ab2d bind-pkcs11-libs-9.9.4-38.el7_3.1.i686.rpm 1c9cbe6497dcaa0fc9a54021a43f29df8648083e16934258f6c0fe68a32908de bind-pkcs11-libs-9.9.4-38.el7_3.1.x86_64.rpm 5e5b779edaa5ba9d19149ea28cb31a491ab14e2298c8b3fbc206c8133799d336 bind-pkcs11-utils-9.9.4-38.el7_3.1.x86_64.rpm 4678bbf2437150632e574f371e0719ceb36a8f5e3d8998c54a5a3ac64e414d9e bind-sdb-9.9.4-38.el7_3.1.x86_64.rpm 3c23783b1a42f0af013f38a698c25275425fe2fc0bd5483a104b3c0415fc28d4 bind-sdb-chroot-9.9.4-38.el7_3.1.x86_64.rpm 356da572ddae5297282284bae84be7df83daf6f28239d5f3768e72d7f24427ec bind-utils-9.9.4-38.el7_3.1.x86_64.rpm Source: 878bbd8d211b55b559f825892c3f2b57f2188fd5377e69e6bd36d861c068caae bind-9.9.4-38.el7_3.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Tue, 17 Jan 2017 13:14:25 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:0063 Important CentOS 6 bind Security Update Message-ID: <20170117131425.GA36634(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:0063 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0063.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: a5e9d904f5d3b760438b3d50e40a99abf24f2a83ac43333072a1362c0f61186a bind-9.8.2-0.47.rc1.el6_8.4.i686.rpm c88b96127401b4a73d7fb4260d284bcfe50cec45215e4b3b97a50e27db5a8742 bind-chroot-9.8.2-0.47.rc1.el6_8.4.i686.rpm e24be65343576a042a8a0b567f35bcf7a68314ceaa9698c045a9aeb226043c29 bind-devel-9.8.2-0.47.rc1.el6_8.4.i686.rpm 21ba0901191dee2ca1764921a0932245005edb3fab4b12d47c21dffabe8124ba bind-libs-9.8.2-0.47.rc1.el6_8.4.i686.rpm fe720e84cf035fed2e6bc1dff1f81a57e1f77d65aa0cc99428a282518cceabbc bind-sdb-9.8.2-0.47.rc1.el6_8.4.i686.rpm 04b878f0bd69fc813a575b48d268480e1ec8230a0e78fdc14e44ae312a777e54 bind-utils-9.8.2-0.47.rc1.el6_8.4.i686.rpm x86_64: 135d88035e507920bc4d63a49af67cc28fba5d59b15851652e67a5e4771b27b6 bind-9.8.2-0.47.rc1.el6_8.4.x86_64.rpm 6b173a9d942a21163cfd200bcf2687660d00201a5af79bfa5a48f8951e9381f4 bind-chroot-9.8.2-0.47.rc1.el6_8.4.x86_64.rpm e24be65343576a042a8a0b567f35bcf7a68314ceaa9698c045a9aeb226043c29 bind-devel-9.8.2-0.47.rc1.el6_8.4.i686.rpm ec3b537c771895846e6046ccefe92ef6342fca039ce7a58a5e0a6df40ed9b472 bind-devel-9.8.2-0.47.rc1.el6_8.4.x86_64.rpm 21ba0901191dee2ca1764921a0932245005edb3fab4b12d47c21dffabe8124ba bind-libs-9.8.2-0.47.rc1.el6_8.4.i686.rpm cbc4ec06b260f3201e0ff37718fd618cf2053f107f94d2206be41e1782961b0c bind-libs-9.8.2-0.47.rc1.el6_8.4.x86_64.rpm 7c171bfb67e8e22ab4bbff74032892ec381e5936191633f75af8534734966b47 bind-sdb-9.8.2-0.47.rc1.el6_8.4.x86_64.rpm 38fbafe72a6c6bc0acf4f1ddbfe648227e2bd05d558fc8adb848f8a3b2ab76f9 bind-utils-9.8.2-0.47.rc1.el6_8.4.x86_64.rpm Source: a48d7e57f50030bad2b2574c73e1060decb61eb2d11abf917876ac792efce6da bind-9.8.2-0.47.rc1.el6_8.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 143, Issue 6 ***********************************************

1 0

disable/mask NetworkManager leads to unit startup fails
by Oberdorfer Patrick 17 Jan '17

17 Jan '17

Hello! For me it was best practice to disable "NetworkManager" on headless installations. Now suddenly I ran into an problem with several programs not starting correctly upon boot anymore. The problem seems to be that their unit files contain "After=network.target" but network.target wont wait till network is up and working, just waits for some low level network stuff. Now I read that it would be good practice to edit this and use "After=network-online.target" instead. But I don't want to touch several systemd unit files shipped via rpm packages. Software like unbound, postfix and so on which needs to bind to ip+port on startup fails on my systems now since I disabled NetworkManager. What solved the problem for me was to install "systemd-networkd" instead and enable it upon boot. It's system unit file pulls in "network.target" as "Wants" this way software that says "After=network.target" will start after network cards are configured. Why there is this behavior I haven't found out yet. Whats your best practice to archieve stable networking upon reboot? Do you use NetworkManager or systemd-networkd or maybe something exotic anyway? PS: I have already filed an Bugzilla report here: https://bugzilla.redhat.com/show_bug.cgi?id=1412570 Thanks!

2 3

NetworkManager vs. Firewalld vs. /etc/sysconfig/network-scripts/ifcfg-*****
by Mike 17 Jan '17

17 Jan '17

I've made 3 CentOS 7 installation attempts to configure a simple firewall/router box with 2 nics. I got myself into a circular scenario where NetworkManager and firewalld and /etc/sysconfig/network-scrpts/ifcfg-***** were interfering or overwriting each other. Needed to perform ifdown enp3s7 on the internal LAN nic in order to make the external internet enp2s0 reach websites and ping nameservers. After completing firewall-cmd --complete-reload the internal LAN nic would still provide private ip addresses via dhcpd server but LAN clients could not access the internet. So far these steps work to enable both nics to provide router and firewall services: 1. sysctemctl stop NetworkManager 2. systemctl disable NetworkManager 3. Create dhcp ifcfg-***** for external interface. It must include a “ZONE=external” statement even though firewalld service will overwrite and erase it like this “ZONE=” Example (external/internet nic): Code: TYPE=Ethernet BOOTPROTO=dhcp NM_CONTROLLED=no DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no NAME=enp2s0 UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx DEVICE=enp2s0 ONBOOT=yes PEERDNS=yes PEERROUTES=yes IPV6_PEERDNS=yes IPV6_PEERROUTES=yes ZONE=external 4. Create static ip address ifcfg-enp3s7 for internal interface. Example (internal/LAN nic): Code: TYPE=Ethernet BOOTPROTO=static NM_CONTROLLED=no DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no NAME=enp3s7 UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx DEVICE=enp3s7 ONBOOT=yes HWADDR=xx:xx:xx:xx:xx:xx DNS1=75.75.75.75 DNS2=75.75.76.76 IPADDR=10.10.1.1 NETMASK=255.255.255.0 PREFIX=24 GATEWAY=10.10.1.1 IPV6_PEERDNS=yes IPV6_PEERROUTES=yes IPV6_PRIVACY=no ZONE=internal 5. As said in #3, firewalld will erase the ZONE setting on the external nic configured for dhcp. The only way I've found to deal with this overwriting is to make the intended external ethernet device associated with the default zone in firewalld. When firewalld reads the empty zone reference "ZONE=____" it will revert and assign the default zone I set like this --- Code: firewall-cmd --change-interface=enp2s0 --zone=external --permanent firewall-cmd --set-default-zone=external firewall-cmd --complete-reload 6. The external ethernet device won’t work (cannot ping any internet host) until you manually Deactivate it and then Reactivate it. ~# ifdown enp2s0 ~# ifup enp2s0 I didn't include my dhcpd server settings or firewalld settings for brevity. Please let me know if those would be helpful. Although the steps above work, it's definitely not ideal. If I need to reboot the routerbox remotely, I won't be able to access it again to perform the necessary ifdown/ifup routine to enable input/output/forward through the external interface. Any guidance on how to make this work is greatly appreciated. Kind regards.

3 3

BackupPC
by TE Dukes 15 Jan '17

15 Jan '17

Hello, Been working on this for a couple days and I am stuck! Followed the CentOS WIKI on BackupPC to the letter. It may be outdated, not sure. I also looked at the tutorial on HowToForge. I'm trying to get a windows client to backup via smb. I created the user 'backuppc' on the windows client with admin priviledges. I can map the drive/share from my CentOS Samba server using 'backuppc' credentials. Here's the error: full backup started for directory / Running: /usr/bin/ssh -q -x -l root hp8200 /usr/bin/rsync --server --sender --numeric-ids --perms --owner --group -D --links --hard-links --times --block-size=2048 --recursive --ignore-times . / Xfer PIDs are now 27000 Read EOF: Connection reset by peer Tried again: got 0 bytes Done: 0 files, 0 bytes Got fatal error during xfer (Unable to read 4 bytes) Backup aborted (Unable to read 4 bytes) Not saving this as a partial backup since it has fewer files than the prior one (got 0 and 0 files versus 0) /etc/BackupPC/hp8200.pl $Conf{XferMethod} = 'smb'; $Conf{SmbShareUserName} = 'backuppc'; $Conf{SmbSharePasswd} = 'xxxxxxxx'; $Conf{SmbShareName} = 'C'; Looking at the -l option it appears 'root' is trying to login. Windows doesn't use a root account per se. Do I need to change something in the config.pl? TIA

3 5

how to troubleshoot GUI issue?
by Dave Burns 14 Jan '17

14 Jan '17

Hello, I'm using a recent install of centos 7, no GUI customizations that I recall. When I log in using the GUI it accepts my password and the mouse appears on a black screen, like it is preparing the desktop, but the desktop never appears. If I hit control-alt-f4 and log in using the command line, and then execute startx, Everything seems to work perfectly. What sort of troubleshooting should I do to figure out what is stalling? I'm not at all familiar with this aspect of things. thanks, Dave

4 3

Re: [CentOS] Unable to edit resolv.conf - SOLVED
by TE Dukes 14 Jan '17

14 Jan '17

> -----Original Message----- > From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Gordon > Messmer > Sent: Friday, January 13, 2017 10:42 AM > To: CentOS mailing list > Subject: Re: [CentOS] Unable to edit resolv.conf > > On 01/13/2017 07:07 AM, TE Dukes wrote: > > I may have. If so, is there a way to undo it? > > > You can determine whether you've set the file's immutable attribute using > "lsattr". You can remove it using "chattr -i" > I found that I had done a chattr -i /etc/resolv.conf some time ago. Its now corrected. Thanks for all the help!!

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss