Discuss January 2017

discuss@lists.centos.org

125 participants
118 discussions

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

20 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:0086 Important CentOS 7 kernel Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 19 Jan 2017 13:30:14 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:0086 Important CentOS 7 kernel Security Update Message-ID: <20170119133014.GA30129(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:0086 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0086.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: a301e9bd95957c5af03b85f8612aaf2053de837e1805e6e649312da8f49f952d kernel-3.10.0-514.6.1.el7.x86_64.rpm dad8a63d9c77bb941a0424b49ff21b6cc67f56e667258fbb3ae8fe9bf61a2812 kernel-abi-whitelists-3.10.0-514.6.1.el7.noarch.rpm c0f9f36cfe07a52320ac47449654f70400bf73707760037106be9563a1428d56 kernel-debug-3.10.0-514.6.1.el7.x86_64.rpm 09bdd98395b85932b2c73151ff6d025608e4fe874eb8b2a70190a5171bddeda3 kernel-debug-devel-3.10.0-514.6.1.el7.x86_64.rpm 628011a5e1958516519b9c65de9cbe9c17e37cd1d1ec26b123f5ddcfa52ef28c kernel-devel-3.10.0-514.6.1.el7.x86_64.rpm cfccc9265a4450544ef7fe783259517b9b0926e0982cccaa292781a82e6a9aa2 kernel-doc-3.10.0-514.6.1.el7.noarch.rpm 50decaf498dccec72c9925ef0c009158fd6cb298fcd5ed9e8dc688e0aeaf3b3e kernel-headers-3.10.0-514.6.1.el7.x86_64.rpm 389bc2f1b0999c01dbc57278a8a5fb45d353899c2fbc404f73e15ae7cecbb907 kernel-tools-3.10.0-514.6.1.el7.x86_64.rpm b2b363e82c863c73dafa895601bdd1fa9aea72bbd3325e1a63e8fbdec6290b35 kernel-tools-libs-3.10.0-514.6.1.el7.x86_64.rpm 5c32cfb66d0b0fc4c6aa6530b70c0d2a65dd6d2631ee68364c1843196ddcf35d kernel-tools-libs-devel-3.10.0-514.6.1.el7.x86_64.rpm 0e49420a74763b655ebf9b0dfbd3d8d9cb8fca551e7f4cd052667b253630b921 perf-3.10.0-514.6.1.el7.x86_64.rpm ea6b2f457ed461d2e1b1b451b834510dc8869be78d7aa3d59fc730c819f6edc0 python-perf-3.10.0-514.6.1.el7.x86_64.rpm Source: cb4cf328e79357f0d0884ee1c84ff4a014554b6e0c9094b6d616cab540c43289 kernel-3.10.0-514.6.1.el7.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 8 ***********************************************

1 0

[OT] VOIP
by TE Dukes 20 Jan '17

20 Jan '17

Hello, I changed ISPs a few weeks ago and now I'm on cable. In doing so, I lost the ability to use the DSL as a FAX line. So, I bought an OOMA. Turns out it uses a number of ports, three of which are reserved, 53 TCP/UDP, 110 TCP and 443 TCP. These ports have already been port forwarded from my cable modem/router to my server. I'm thinking this isn't going to work unless I change some ports on my server, which I'm not willing to do. I spent over 30 minutes with their support people last night. It appears the ports cannot be changed on the OOMA device. Are there any work arounds? TIA

3 4

SELinux upgrade
by Scott Robbins 19 Jan '17

19 Jan '17

Well, got hit by this too. Ironically, I don't use docker, I think I had it installed being pulled in for something else. So, tried the yum remove docker* but no go. When I do semanage port -a -t ssh_port_t -p tcp <port> I get an error Bad type declaration at /etc/selinux/targeted/tmp/modules/100/docker/cil:1 which is something that doesn't exist. Tried installing container-selinux, but so far, the only way to get SSH to work on a default port is to setenforce 0. This isn't a really important machine, but it is certainly annoying. -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

1 0

Increase CPU usage on HV after upgrade (7.2 -> 7.3)
by Subscriber 19 Jan '17

19 Jan '17

Hello , After upgrading the system from CentOS 7.2.1511 to CenOS 7.3.1611 I see that the average processing time has increased from 5-7% to 12-15% (doubled). Not critical but it is not pleasant. Server as KVM with 5 virtual machines. Someone noticed something similar? If so, how to fix that? Thx.

4 11

SELinux upgrade
by Marcin Trendota 19 Jan '17

19 Jan '17

Hello All After recent system upgrade (this night) i lost access to two servers through SSH, because of change in SELinux policy - i have ssh there on different port and now it's gone. Thanks to puppet i was able to change SSH port back to default and log in, but is this expected behavior? I thought minor upgrade shouldn't break up things? Or maybe "semanage port -a -t ssh_port_t -p tcp port" isn't enough to ensure persistency? -- Over And Out MoonWolf

6 7

Reliable way of having both LAN and WIFI on headless box
by Gary Stainburn 19 Jan '17

19 Jan '17

Once again I am building a headless Centos 7 box that needs to reliably be on both the LAN and WIFI network at all times. Amongst other things it's going to be an AirPrint bridge enabling IPads to print to printers on a different VLAN. I have asked about this before and got a solution working using nmtui to set up both the LAN and WIFI interface, and activate them. However, the WIFI link is unreliable. Sometimes it doesn't activate, or after a while de-activates. Sometimes it doesn't even appear in nmtui to enable me to activate it. Can anyone help me with how I can set up a more reliable server. Thanks Gary

9 15

Test
by TE Dukes 19 Jan '17

19 Jan '17

Is it working?

4 4

System Time Jumps During Boot on CentOS 7
by Peter Brady 19 Jan '17

19 Jan '17

Hi All, Just noticed a funny time jump on a testing CentOS 7 VM. Specifically the system time jumps around by a few hours during system boot. The below is a selection from /var/log/messages during boot: Jan 19 12:49:57 arr-data-dev chronyd[716]: Frequency -0.829 +/- 0.007 ppm read from /var/lib/chrony/drift Jan 19 12:49:57 arr-data-dev polkitd[720]: Started polkitd version 0.112 Jan 19 12:49:57 arr-data-dev systemd: Starting D-Bus System Message Bus... Jan 19 12:49:57 arr-data-dev systemd: Starting GSSAPI Proxy Daemon... Jan 19 12:49:57 arr-data-dev systemd: Started Dump dmesg to /var/log/dmesg. Jan 19 12:49:57 arr-data-dev kernel: NET: Registered protocol family 40 Jan 19 12:49:57 arr-data-dev sssd: Starting up Jan 19 12:49:57 arr-data-dev systemd: Started GSSAPI Proxy Daemon. Jan 19 12:49:57 arr-data-dev systemd: Reached target NFS client services. Jan 19 12:49:57 arr-data-dev systemd: Starting NFS client services. Jan 19 12:49:57 arr-data-dev systemd: Reached target Remote File Systems (Pre). Jan 19 12:49:57 arr-data-dev systemd: Starting Remote File Systems (Pre). Jan 19 12:49:57 arr-data-dev systemd: Started Authorization Manager. Jan 19 12:49:57 arr-data-dev systemd: Starting firewalld - dynamic firewall daemon... Jan 19 20:47:57 arr-data-dev systemd: Time has been changed Jan 19 20:47:57 arr-data-dev chronyd[716]: Forward time jump detected! Jan 19 20:47:57 arr-data-dev sssd[be[default]]: Starting up <snip> Jan 19 20:48:05 arr-data-dev systemd: Starting Multi-User System. Jan 19 20:48:05 arr-data-dev systemd: Starting Update UTMP about System Runlevel Changes... Jan 19 20:48:05 arr-data-dev systemd: Started Update UTMP about System Runlevel Changes. Jan 19 12:50:09 arr-data-dev chronyd[716]: Selected source IP-CHANGED Jan 19 12:50:09 arr-data-dev chronyd[716]: System clock wrong by -28676.126423 seconds, adjustment started Jan 19 12:50:09 arr-data-dev chronyd[716]: System clock was stepped by -28676.126423 seconds Jan 19 12:50:09 arr-data-dev systemd: Time has been changed Jan 19 12:50:09 arr-data-dev chronyd[716]: Selected source IP-CHANGED Jan 19 12:50:10 arr-data-dev chronyd[716]: Selected source IP-CHANGED Jan 19 12:50:11 arr-data-dev chronyd[716]: Selected source IP-CHANGED For reference the 12:49 -> 12:50 is the correct local time, I'm in the Australian Eastern Daylight Saving time zone and my hardware clock (from hwclock) is close to that time. The plus eight hours jump has me curious though as I think this is causing some trouble for SSSD and Network Manager that are starting up in interval when the time is stepped forward. Given I'm at +11 from UTC the system clock does not appear to be jumping to UTC. I'm running 3.10.0-514.2.2.el7.x86_64 with yum reporting no patches. This is a VM running on ESXi 5.6. According to /var/log/boot.log everything started up OK. Has anyone seen anything similar? Thanks in advance, -pete

1 1

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

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss January 2017