Discuss August 2017

discuss@lists.centos.org

94 participants
73 discussions

Syncronize systemctl status with reality?
by Leroy Tennison 30 Aug '17

30 Aug '17

The particular issue is with puppetmaster (which admittedly takes 4 minutes to actually start, setting TimeoutStartSec=300 in it's unit file stopped the false timeout report) but I have seen it one other time (don't remember the details). systemctl status puppetmaster ● puppetmaster.service - Puppet master Loaded: loaded (/lib/systemd/system/puppetmaster.service; enabled; vendor preset: enabled) Active: failed (Result: resources) since Tue 2017-08-29 11:24:36 CDT; 22min ago Process: 897 ExecStart=/usr/bin/puppet master (code=exited, status=0/SUCCESS) Aug 29 11:22:39 puppetmaster02 systemd[1]: Starting Puppet master... Aug 29 11:24:36 puppetmaster02 puppet-master[1233]: Reopening log files Aug 29 11:24:36 puppetmaster02 puppet-master[1233]: Starting Puppet master version 3.8.5 Aug 29 11:24:36 puppetmaster02 puppet-master[1233]: Could not run: Address already in use - listen(2) Aug 29 11:24:36 puppetmaster02 systemd[1]: puppetmaster.service: PID 1233 read from file /run/puppet/master.pid does not exist or is a zombie. Aug 29 11:24:36 puppetmaster02 systemd[1]: Failed to start Puppet master. Aug 29 11:24:36 puppetmaster02 systemd[1]: puppetmaster.service: Unit entered failed state. Aug 29 11:24:36 puppetmaster02 systemd[1]: puppetmaster.service: Failed with result 'resources'. However, ps -ef | grep puppet (run just after the above) returns puppet 1380 1 0 11:26 ? 00:00:08 Passenger RubyApp: /usr/share/puppet/rack/puppetmasterd root 2015 1341 0 11:48 pts/0 00:00:00 grep --color=auto puppet Earlier ps .. also reported puppet 1355 1166 3 11:26 ? 00:00:01 Passenger AppPreloader: /usr/share/puppet/rack/puppetmasterd And, the "bottom line", puppet agent -t on a client works. It reports finishing the catalog run and the client's yaml files on puppetmaster are up to date. Is there a command to tell systemd to re-scan running state and update its understanding on what it finds? I tried systemctl daemon-reload just to be sure that didn't solve the problem before posting this.

3 5

A potentially newbie question about vulnerability patching speed in CentOS 7.x's yum repository
by 知乎申诉处理 30 Aug '17

30 Aug '17

I've been dubbing with management of security vulnerabilities and their fixes for a while, recently I discovered there may be a delay in the process of software updates made available on CentOS yum repository. take CVE-2017-5335 for example: In redhat official notice board :https://access.redhat.com/security/cve/cve-2017-5335 we can see there is a link point to advisory for RHEL 7: https://access.redhat.com/errata/RHSA-2017:2292 . from there we can see that the fix happens at gnutls 3.3.26. But when trying to update with yum update from a CentOS 7.3 x64 machine. there is no 3.3.26 available. Only available rpm for CentOS 7.3.1611 for x86_64 is gnutls-3.3.24. This result can be verified using rpm finder: https://www.rpmfind.net/linux/rpm2html/search.php?query=gnutls Same problem happens to other software packages such as: glibc tcpdump libnl mariadb ... (and many others) Why is that? and are those software packages not going to get fixed? - p.s. please excuse me for any formating issues. :) Jeff

3 2

Centos 6 Airprint using CUPS/Avahi
by Gary Stainburn 29 Aug '17

29 Aug '17

I've set up another airprint server, but this time I've had to use Centos 6 because of the age of the kit I'm using - an old 1U rack server. I've configured CUPS and also Avahi. I've run airprint-generate.py and copied the .service files to /etc/avahi/services/ Everything looks fine until I try to print from my IPhone. I usually test by trying to print an email. As soon as I go to search / select a printer I get the following start to appear in /var/log/cups/error_log E [29/Aug/2017:15:24:07 +0100] Request from "10.1.103.237" using invalid Host: field "harpo.local:631" The printer list appears and I can select a printer and click on print. However nothing prints off, and I just keep getting the above error message. I've tried setting [server] host-name=harpo domain-name=ringways.co.uk in /etc/avahi/avahi-daemon.conf but that just prevents Avahi from starting. Can anyone suggest what I need to do to get Avahi and CUPS to be friendly? Gary -- https://fundraise.cancerresearchuk.org/page/garys-march-march

1 0

ALPN and Http/2, CentOS 7.4
by SternData 29 Aug '17

29 Aug '17

Now that 7.4 CR has delivered OpenSSL 1.0.2, I should be able to serve http/2 pages to Chrome, but I still see messages that ALPN is not enabled. OpenSSL 1.0.2 is installed: $ rpm -qa |grep openssl openssl-libs-1.0.2k-8.el7.x86_64 openssl-1.0.2k-8.el7.x86_64 But https://tools.keycdn.com/http2-test says "www.stevenstern.me" supports http 2 but ALPN is not supported. Ideas? Does anything need to be explicitly enabled for ALPN? As I mentioned, the http2 stuff seems to be working. -- -- Steve

3 2

Problem installing glibc-devel.i686 on CentOS 7
by Alfred von Campe 28 Aug '17

28 Aug '17

The following transcript should provide all the necessary details: # yum install glibc-devel-2.17-157.el7.i686 Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * base: mirrors.gigenet.com * epel: mirrors.xmission.com * extras: mirrors.gigenet.com * updates: ftp.osuosl.org Resolving Dependencies --> Running transaction check ---> Package glibc-devel.i686 0:2.17-157.el7 will be installed --> Processing Dependency: glibc-headers = 2.17-157.el7 for package: glibc-devel-2.17-157.el7.i686 --> Processing Dependency: glibc = 2.17-157.el7 for package: glibc-devel-2.17-157.el7.i686 --> Finished Dependency Resolution Error: Package: glibc-devel-2.17-157.el7.i686 (base) Requires: glibc-headers = 2.17-157.el7 Installed: glibc-headers-2.17-157.el7_3.5.x86_64 (@updates) glibc-headers = 2.17-157.el7_3.5 Available: glibc-headers-2.17-157.el7.x86_64 (base) glibc-headers = 2.17-157.el7 Available: glibc-headers-2.17-157.el7_3.1.x86_64 (updates) glibc-headers = 2.17-157.el7_3.1 Available: glibc-headers-2.17-157.el7_3.2.x86_64 (updates) glibc-headers = 2.17-157.el7_3.2 Available: glibc-headers-2.17-157.el7_3.4.x86_64 (updates) glibc-headers = 2.17-157.el7_3.4 Error: Package: glibc-devel-2.17-157.el7.i686 (base) Requires: glibc = 2.17-157.el7 Installed: glibc-2.17-157.el7_3.5.i686 (@updates) glibc = 2.17-157.el7_3.5 Available: glibc-2.17-157.el7.i686 (base) glibc = 2.17-157.el7 Available: glibc-2.17-157.el7_3.1.i686 (updates) glibc = 2.17-157.el7_3.1 Available: glibc-2.17-157.el7_3.2.i686 (updates) glibc = 2.17-157.el7_3.2 Available: glibc-2.17-157.el7_3.4.i686 (updates) glibc = 2.17-157.el7_3.4 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest I tried the two suggesting above to no avail. Has anyone else been able to install glib-devel.i686 successfully on CentOS 7? Alfred

2 2

CentOS 7 (1708) CR content
by Johnny Hughes 28 Aug '17

28 Aug '17

We have released the CR repo with what will be the CentOS 7 (1708) content. Please see this link for details: http://bit.ly/2w7eIe6 Release Notes: http://bit.ly/2is4Kku Announcements: http://bit.ly/2viRAIl Special thanks, as always, to our community based QA team. We could never get this stuff done without them. You guys and gals ROCK! Enjoy ! Thanks, Johnny Hughes

4 3

xorg-x11-drv-intel CR update breaks X server for Intel HD520
by milos.blazevic 28 Aug '17

28 Aug '17

Hi, As a consequence of rolling out CR updates on Latitude E7470 (Skylake chipset), X would no longer start until I rolled back all of the xorg-\* packages. And to be more precise, looks like the culprit is xorg-x11-drv-intel: https://bugzilla.redhat.com/show_bug.cgi?id=1445583 as the CR package release version matches the one mentioned in Comment #2, in the regression context. I've already submitted a bug report: https://bugs.centos.org/view.php?id=13717 so I just wanted to bring this issue to attention of anyone who's running this chipset/VGA. Thanks, Milos.

2 3

CentOS 7, nfs & autofs
by m.roth＠5-cent.us 28 Aug '17

28 Aug '17

Hi, folks, We've been seeing this almost since we started rolling out C7: for no apparent reason, it will automount *everyone* in /etc/auto.home, even though most of those folks not only have never logged onto that server or workstation, but are not allowed to. We distribute to all our systems the same auto.home, and we certainly don't want to customize it for nearly 200 systems, we like it under central control. Any clues as to why it does this? Note that kill -USR1 <autofs pid) makes the unused ones umount in a minute or two. mark

1 0

anybody else had this problem since the CR updates?
by Fred Smith 27 Aug '17

27 Aug '17

I'm running Mate on my C7 boxen, a desktop and a netbook.\ Mate comes from epel, so it's probably not a CentOS problem, but lemme ask here in case anybody else has seen it: some tools (nm, pavucontrol, and possibly others I haven't noted down) no longer have the correct formatting on screen. there are no backgrounds, i.e., backgrounds that define areas of the screen by shading or borders. clickable text tends to be jammed together. pavucontrol has no sliders for any of the level controls. an example, at the top of pavucontrol it has no visible tabs, just the text: PlaybackRecordingOutput DevicesInput DevicesConfiguration spaced as shown. they work when you click them, however. but since none of the sliders are visible (and I can't find 'em by randomly poking around with the mouse pointer) it's a little hard to use. :( If I can find a place to post some screenshots, I'll try the posting a note on the epel IRC. Thanks in advance! -- ------------------------------------------------------------------------------- Under no circumstances will I ever purchase anything offered to me as the result of an unsolicited e-mail message. Nor will I forward chain letters, petitions, mass mailings, or virus warnings to large numbers of others. This is my contribution to the survival of the online community. --Roger Ebert, December, 1996 ----------------------------- The Boulder Pledge -----------------------------

3 4

Re: [CentOS] Vmware No Longer Build on the New 693.1.1 kernel
by pro alias 27 Aug '17

27 Aug '17

>Build error "Failed to build vmnet. Failed to execute the build command." >when trying to compile vmnet.Not one other shred of data in the logs >telling me WHY it failed to build. >I have rolled back to the last 514 kernel to use vmware but I >don't want to recompile vmware because of the liability of not being able to >get it running again if the compilation problem is caused by one of the >other updates. >Anyone else found vmware problems after CR update?? The answer is to recompile the source tarball with a patch which appeared at: https://communities.vmware.com/message/2686431?tstart=0#2686431 generously provided by https://communities.vmware.com/people/dariusd . Tried it and it works swimmingly. Whew!

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss August 2017