- Discuss - lists.centos.org

Strange issue with CentOS7 on XenServer
by Todor Petkov 21 Sep '17

21 Sep '17

Hello, I stumbled upon a strange problem with CentOS upgrade on XenServer environment, and I would like to ask if someone has this issue as well: XenServer 7.1, the VM is CentOS7, with kernel 3.10.0-514.26.2.el7.x86_64 running in PV mode When I upgrade the kernel (running with yum update kernel), after reboot in the VM console it says "dracut-pre-udev[212]: modprobe: ERROR: could not insert 'dm-mod': Cannot allocate memory" and after a while it drops to dracut shell If I boot from from an old kernel with the updated kexec-tools/dracut, it's fine. Anyone experiencing this issue? Regards,

2 2

CentOS 7 yum Issue
by Chris Olson 21 Sep '17

21 Sep '17

We have been following the email list discussion regarding recent problems with yum and the upgrade to the most current CentOS 7. We have also tried some of the remedies suggested or recommended. None of these measures has yielded success, and it is not totally clear whether or not our most recent yum issues have the same root cause as those experienced by others. Fortunately, our yum execution after the most recent updates came available was on one of our virtual machines. This is a CentOS 7 system running on VirtualBox and hosted on a Windows 7 system. It is typically used for verifying system updates and applications before they are introduced to regular Intel-based systems. This virtual CentOS 7 system has also been faithfully updated for over a year by using yum and accepting all updates when they become available. The truly remarkable thing is that yum does not finish with any identifiable errors. In fact it does not finish at all and seems to be in a continuous loop of some kind that has run up to ten minutes, so far. Information scrolling by seems to repeat every few seconds with the names of a set of packages repeating over and over. Many of the messages indicate package conflicts or a dependency problem of some kind. This "loop" never allows progress to the point where one would answer yes or no the to the updates. With no end in sight, we chose to kill the yum process. Shut down and restart of the current CentOS system yields a system that appears to work well with no issues related to killing the yum process. Four separate yum update sessions have been attempted, and all have been killed. All data has been backed up properly and our application reload plan is in place, with the exception of some from epel which have caused previous problems, that others have noticed recently also. Our current plan is to remove the current CentOS 7 virtual system and install the newest CentOS 7 available. We have no plans to run yum update on any other CentOS 7 systems.

2 1

CentOS-announce Digest, Vol 151, Issue 5
by centos-announce-request＠centos.org 21 Sep '17

21 Sep '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:2771 Important CentOS 7 emacs Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 20 Sep 2017 12:06:23 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:2771 Important CentOS 7 emacs Security Update Message-ID: <20170920120623.GA19904(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:2771 Important Upstream details at : https://access.redhat.com/errata/RHSA-2017:2771 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 47619da497682c1d399f3e839774d98a579db4c15f1f0295cfd6cdcae070e408 emacs-24.3-20.el7_4.x86_64.rpm 31638172ec33046d69beebdbde23d7e5f5521c6fe3df1ca063a4f11900d38b65 emacs-common-24.3-20.el7_4.x86_64.rpm a494e7928ca31b88142e2762f88a934c94e8c8bc526d3a78bc58ab706f650c08 emacs-el-24.3-20.el7_4.noarch.rpm 2184386790f816e052c59b814ba9c5acb898161ad3cf12b5d3523536dc021bd0 emacs-filesystem-24.3-20.el7_4.noarch.rpm 1c43a83bfa035a29d4c04958292253931172a07d910972fcdf07fcec9b59b658 emacs-nox-24.3-20.el7_4.x86_64.rpm 2a974431e4ae960ddd2c31f9183a22b926ebcbefbb31e51f250687e8545a01ed emacs-terminal-24.3-20.el7_4.noarch.rpm Source: 6d52969eb35bae9d613ab2297b900c6241a96f4e8fd3a67225e6d94c69cb8b3c emacs-24.3-20.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 151, Issue 5 ***********************************************

1 0

Public mirror synchronization failing
by Unsub Shafiq 21 Sep '17

21 Sep '17

Hello, Our CentOS public mirror synchronization is failing since yesterday, with the log files showing the following "Permission denied" messages. It seems that my server is not able to access some of the files; any leads on to how to resolve it? rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.3PYmPD" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.7ryULv" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.8K1cYn" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.KoVhZw" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.NihJX5" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.O44pIw" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.O6PlFu" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.PFLTdf" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.PuBBXM" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.W4ppDL" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.brAhov" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.cuN3VQ" (in centos): Permission denied (13) rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.fAEi2g" (in centos): Permission denied (13) -- *Unsub Shafiq* Inara Technologies (Pvt) Ltd.

2 1

weird wordpress/php/pecl/ssh problem
by John R Pierce 21 Sep '17

21 Sep '17

So I'm running a centos 6 server which among other things hosts a website using wordpress. I'm using php56u from IUS on C6's native apache, and pecl + ssh because php-ssh2 is kinda broken. I ran smack dab into this exact problem: https://core.trac.wordpress.org/ticket/39746 In my case, wordpress 4.7.6 auto updated, and I notied that 4.8.2 was available, so I chose my standard update method of ssh2.sftp via the web interface, and it errored "couldn't find wordpress directories". error_log showed a php error: PHP Warning: file_put_contents(ssh2.sftp://Resource id #834/.maintenance): failed to open stream ... this had worked for me for several years of updates prior to this. if I understand what that guy posted on the wordpress TRAC, there's an upstream error in php 5.6.29+ (I was on .30 and now .31) and pecl ssh2. the wordpress folks on that thread think that its a php ssh problem and don't want to address it, while the poster thinks they could easily work around it. now, I realize none of this is directly a centos problem as its the IUS (Rackspace?) version of php I'm running, and pecl is way out of your bounds, but I'm wondering. anyone here at all plugged into the pecl world and familiar with the ssh extension want to comment ? or am I way out of bounds. the wordpress folks I've talked with say just don't USE the ssh2.sftp update method, use FTP (ugh!) or use 'direct' (php directly writes the .php files to update the app, eek). they think I should contain php in php-fpm, something thing I've not looked at before. -- john r pierce, recycling bits in santa cruz

1 0

KeePassX replacement
by H 21 Sep '17

21 Sep '17

I have been using the KeePassX password manager on CentOS 6 and 7 for some time and it works pretty well. On my Windows machine I use KeePass which offers a number of features missing from KeePassX, I also sync the database between several machines, including Android units where I use keepass2android. Database compatibility is thus required. KeePassX, however, does not seem to be maintained any more, the last update was just a bit less than a year ago. It also has some annoying bugs, including where switching keyboards on the computer corrupts the username and the password if they include any character outside the ASCII range. There seems to be a community fork called KeePassXC and I would like to ask if anyone is using this password manager? It is not in EPEL, nor in any other standard repository, only through an unofficial repository at https://copr.fedorainfracloud.org/coprs/bugzy/keepassxc/,

11 22

xfs not getting it right?
by hw 20 Sep '17

20 Sep '17

Hi, xfs is supposed to detect the layout of a md-RAID devices when creating the file system, but it doesn´t seem to do that: # cat /proc/mdstat Personalities : [raid1] md10 : active raid1 sde[1] sdd[0] 499976512 blocks super 1.2 [2/2] [UU] bitmap: 0/4 pages [0KB], 65536KB chunk # mkfs.xfs /dev/md10p2 meta-data=/dev/md10p2 isize=512 agcount=4, agsize=30199892 blks = sectsz=512 attr=2, projid32bit=1 = crc=1 finobt=0, sparse=0 data = bsize=4096 blocks=120799568, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=58984, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 # mkfs.xfs -f -d su=64m,sw=2 /dev/md10p2 meta-data=/dev/md10p2 isize=512 agcount=16, agsize=7553024 blks = sectsz=512 attr=2, projid32bit=1 = crc=1 finobt=0, sparse=0 data = bsize=4096 blocks=120799568, imaxpct=25 = sunit=16384 swidth=32768 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=58984, version=2 = sectsz=512 sunit=8 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 The 64MB chunk size was picked my mdadm automatically. The device is made from two disks, and xfs either doesn´t figure that out, or it decided to ignore the layout of the underlying RAID. Am I doing something wrong here, or is xfs in Centos somehow different? Do, or must, we always specify the apporpriate values for su and sw or did xfs ignore them because what it picked is better?

5 8

Join us at CERN, October 20th, 2017
by Rich Bowen 20 Sep '17

20 Sep '17

Please join us, one month from today, in Meyrin, Switzerland, at the amazing CERN facility, for a day of learning and sharing. http://cern.ch/centos Details, schedule, and registration are at the above link. While the event is free, you *must* register in order to gain access to the facility, due to security requirements. See you at CERN! -- Rich Bowen - rbowen(a)redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity

1 0

update to 7.4
by Jerry Geis 20 Sep '17

20 Sep '17

I was doing an update to 7.4 and somewhere in middle the machine died. If I drop back to a previous kernel the machine is alive. So how do I say "forget the previous yum update" and start all over and do it again. Booting into the new kernel I get a kernel fault. So going back one level on teh boot screen solves that - I just need to start the update again. How is that? Thanks, Jerry

6 8

glib update problems
by Jason Welsh 20 Sep '17

20 Sep '17

any idea how to get out of this pickle? [root@oem /home/jason]$yum update glibc Loaded plugins: product-id, rhnplugin, search-disabled-repos, security This system is receiving updates from RHN Classic or Red Hat Satellite. Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package glibc.x86_64 0:2.12-1.209.el6_9.1 will be updated ---> Package glibc.x86_64 0:2.12-1.209.el6_9.2 will be an update --> Processing Dependency: glibc-common = 2.12-1.209.el6_9.2 for package: glibc-2.12-1.209.el6_9.2.x86_64 --> Running transaction check ---> Package glibc-common.x86_64 0:2.12-1.209.el6_9.1 will be updated --> Processing Dependency: glibc-common = 2.12-1.209.el6_9.1 for package: glibc-2.12-1.209.el6_9.1.i686 ---> Package glibc-common.x86_64 0:2.12-1.209.el6_9.2 will be an update --> Finished Dependency Resolution Error: Package: glibc-2.12-1.209.el6_9.1.i686 (@rhel-6-server-rpms) Requires: glibc-common = 2.12-1.209.el6_9.1 Removing: glibc-common-2.12-1.209.el6_9.1.x86_64 (@rhel-6-server-rpms) glibc-common = 2.12-1.209.el6_9.1 Updated By: glibc-common-2.12-1.209.el6_9.2.x86_64 (rhel6xbase) glibc-common = 2.12-1.209.el6_9.2 Available: glibc-common-2.12-1.166.el6_7.8.x86_64 (rhel6xupdates) glibc-common = 2.12-1.166.el6_7.8 ********************************************************************** yum can be configured to try to resolve such errors by temporarily enabling disabled repos and searching for missing dependencies. To enable this functionality please set 'notify_only=0' in /etc/yum/pluginconf.d/search-disabled-repos.conf ********************************************************************** Error: Package: glibc-2.12-1.209.el6_9.1.i686 (@rhel-6-server-rpms) Requires: glibc-common = 2.12-1.209.el6_9.1 Removing: glibc-common-2.12-1.209.el6_9.1.x86_64 (@rhel-6-server-rpms) glibc-common = 2.12-1.209.el6_9.1 Updated By: glibc-common-2.12-1.209.el6_9.2.x86_64 (rhel6xbase) glibc-common = 2.12-1.209.el6_9.2 Available: glibc-common-2.12-1.166.el6_7.8.x86_64 (rhel6xupdates) glibc-common = 2.12-1.166.el6_7.8 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@oem /home/jason]$ Jason --

4 4

Re: [CentOS] Block internet access for some users on the LAN ?
by James B. Byrne 20 Sep '17

20 Sep '17

On Monday, September 18, 2017 1:04 PM, Nicolas Kovacs wrote" > > This year the school's director wants to completely block Internet > access for all the student's personal devices. > The silent premise in this request is that all student Internet access occurs through the school's gateway. Which is of course false. If the objective is to prevent misuse of school resources for non-education purposes then the premise, while faulty, is fine. If the objective is to restrict students' Internet access in its entirety then this is doomed to fail. Have you clarified with the director that only access through your gateway can be affected by this policy and that student devices with cellular data plans will still have access? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

CentOS, PHP & OwnCloud/Nextcloud: the version dilemma
by Nicolas Kovacs 20 Sep '17

20 Sep '17

Hi, I'm currently experimenting with OwnCloud and Nextcloud on a sandbox CentOS 7 server. I've been using OwnCloud for the last two years for my own purposes on a Slackware server, and I'm quite happy with it. In my humble opinion, every admin who wants to host OwnCloud or Nextcloud on a RHEL/CentOS server is confronted with a version dilemma. 1. CentOS 7 sports PHP 5.4, which has been officially EOL for quite some time, but Red Hat will provide security update backports until 2024. Which is fine. 2. Currently supported versions of Nextcloud (namely the 11.x and 12.x branch) require a minimum of PHP 5.6. Which seems reasonable. But if I pull in PHP 5.6 from Webtatic, for example, I only get the "official" PHP support, which will end in 2018 for the 5.6 branch. And no security backports. 3. The solution would be to go with Nextcloud 10, which only requires PHP 5.4, and which is also provided in package form by EPEL. 'yum info nextcloud' shows that the current EPEL version is 10.0.4... but a peek on the Nextcloud homepage shows me that this version is officially unsupported. Uh oh. 4. Some of the stuff I'm hosting on my CentOS 7 server (like CMSMS) is not compatible with PHP 7.x versions. So right now I don't see a solution for this. As far as I can see, the "least evil" solution would be to pull in PHP 5.6 from Webtatic and go for Nextcloud 11.x, and have an EOL for both around next summer. I'd be curious if some of you are familiar with this sort of dilemma (I guess so) and how you manage it. Cheers, Niki Kovacs -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

13 20

Block internet access for some users on the LAN ?
by Nicolas Kovacs 19 Sep '17

19 Sep '17

Hi, In our local school we have two servers and roughly 80 clients. The network is 192.168.10.0/255.255.255.0, and DHCP+DNS is managed by Dnsmasq. School PCs (teachers and management) are registered via MAC address and get an IP address in a specific range: 192.168.10.2 - 192.168.10.50 - management + teachers 192.168.10.201 - 192.168.10.220 - computer room 192.168.10.246 - 192.168.10.247 - printers 192.168.10.251 - 192.168.10.253 - wireless access points If a client (like a student's laptop, tablet or smartphone) is not registered, it gets an IP address in the range between 192.168.10.100 and 192.168.10.200. Up until recently I've been using a combination of Squid and Squidguard to filter Internet access. This year the school's director wants to completely block Internet access for all the student's personal devices. The Linux server acts as a transparent gateway. Unfortunately with Squid I can only filter/block HTTP connections, but not HTTPS (well, I could, but this is way too complicated to setup). The firewall is managed by a simple Iptables script. Now I *think* the easiest way to block a certain IP range from Internet access would be through Iptables (correct me if I'm wrong). If this is the case, what would that look like? Any suggestions? Niki Kovacs -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

9 11

KVM SSL with wget
by MOKRANI Rachid 19 Sep '17

19 Sep '17

Hi, I installed KVM on a CentOS 7.4 host. The guest is also installed in CentOS 7.4, the network works perfectly. Both Host and Guest machines have the same OS. I do not understand why I have an SSL error on the guest and not on the host while the two computers have the same OS installation. The firewalld, selinux, fail2ban services are not installed on host and guest. Is there an extra manipulation that I have forgotten to do? Many thanks. Below my log on Host and Guest. Host /usr/bin/wget --version GNU Wget 1.14 built on linux-gnu. wget https://www.google.com --2017-09-19 16:15:44-- https://www.google.com/ Resolving www.google.com<http://www.google.com> (www.google.com<http://www.google.com>)... 2a00:1450:4009:809::2004, 216.58.198.164 Connecting to www.google.com<http://www.google.com> (www.google.com<http://www.google.com>)|2a00:1450:4009:809::2004|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://www.google.fr/?gfe_rd=cr&dcr=0&ei=kCbBWe-fOMnU8gfBmLmABA [following] --2017-09-19 16:15:44-- https://www.google.fr/?gfe_rd=cr&dcr=0&ei=kCbBWe-fOMnU8gfBmLmABA Resolving www.google.fr<http://www.google.fr> (www.google.fr<http://www.google.fr>)... 2a00:1450:4009:814::2003, 216.58.204.3 Connecting to www.google.fr<http://www.google.fr> (www.google.fr<http://www.google.fr>)|2a00:1450:4009:814::2003|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: 'index.html.10' [ <=> ] 10,853 --.-K/s in 0s 2017-09-19 16:15:45 (41.9 MB/s) - 'index.html.10' saved [10853] Guest VM ping www.google.com<http://www.google.com> return OK /usr/bin/wget --version GNU Wget 1.14 built on linux-gnu. My Pb on the guest : wget https://www.google.com --2017-09-19 16:16:03-- https://www.google.com/ Resolving www.google.com<http://www.google.com> (www.google.com<http://www.google.com>)... 216.58.198.164, 2a00:1450:4009:809::2004 Connecting to www.google.com<http://www.google.com> (www.google.com<http://www.google.com>)|216.58.198.164|:443... connected. OpenSSL: error:1408D07B:SSL routines:ssl3_get_key_exchange:bad signature Unable to establish SSL connection. __________________________ Avant d'imprimer, pensez à l'environnement ! Please consider the environment before printing ! Ce message et toutes ses pièces jointes sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. IFP Energies nouvelles décline toute responsabilité au titre de ce message. This message and any attachments are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. IFP Energies nouvelles should not be liable for this message. __________________________

2 1

JRE 8.1 for CentOS6
by Larry Martell 18 Sep '17

18 Sep '17

I have some software that says it requires JRE 8.1 or higher. If I go to http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133… and install jre-8u144-linux-x64.rpm I get jrel.8.0_144. Anyone know where I can get 8.1?

9 31

Update from 7.3 to 7.4 failing because of architecture change from PPC64 to PPC
by Armin Kunaschik 18 Sep '17

18 Sep '17

Hello, I'm having problems updating from 7.3 to 7.4 on my ppc64 (IBM Power7 p770) installation. yum update stops with Error: Multilib version problems found. [..] Protected multilib versions: systemd-libs-219-42.el7.ppc != systemd-libs-219-42.el7_4.1.ppc64 When I scroll back through the transaction check I see various package dependencies for *.ppc instead of *.ppc64. First appearance in the check is glibc.ppc and then everything goes nuts: [..] --> Running transaction check ---> Package boost-date-time.ppc64 0:1.53.0-27.el7 will be installed ---> Package elfutils-default-yama-scope.noarch 0:0.168-8.el7 will be installed ---> Package glibc.ppc 0:2.17-196.el7 will be installed --> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.17-196.el7.ppc --> Processing Dependency: libfreebl3.so for package: glibc-2.17-196.el7.ppc ---> Package grub2-common.noarch 1:2.02-0.64.el7.centos will be installed ---> Package grub2-ppc64.ppc64 1:2.02-0.64.el7.centos will be installed --> Processing Dependency: grub2-ppc64-modules = 1:2.02-0.64.el7.centos for package: 1:grub2-ppc64-2.02-0.64.el7.centos.ppc64 ---> Package gtk-update-icon-cache.ppc64 0:3.22.10-4.el7 will be installed ---> Package libfastjson.ppc64 0:0.99.4-2.el7 will be installed ---> Package libseccomp.ppc64 0:2.3.1-3.el7 will be installed ---> Package nss-pem.ppc64 0:1.0.3-4.el7 will be installed ---> Package python-linux-procfs.noarch 0:0.4.9-3.el7 will be installed ---> Package python-schedutils.ppc64 0:0.4-6.el7 will be installed ---> Package stix-fonts.noarch 0:1.1.0-5.el7 will be installed ---> Package systemd-libs.ppc 0:219-42.el7 will be installed --> Processing Dependency: libselinux.so.1 for package: systemd-libs-219-42.el7.ppc --> Processing Dependency: libpam_misc.so.0(LIBPAM_MISC_1.0) for package: systemd-libs-219-42.el7.ppc --> Processing Dependency: libpam_misc.so.0 for package: systemd-libs-219-42.el7.ppc --> Processing Dependency: libpam.so.0(LIBPAM_MODUTIL_1.0) for package: systemd-libs-219-42.el7.ppc --> Processing Dependency: libpam.so.0(LIBPAM_EXTENSION_1.0) for package: systemd-libs-219-42.el7.ppc --> Processing Dependency: libpam.so.0(LIBPAM_1.0) for package: systemd-libs-219-42.el7.ppc --> Processing Dependency: libpam.so.0 for package: systemd-libs-219-42.el7.ppc --> Processing Dependency: liblzma.so.5(XZ_5.0) for package: systemd-libs-219-42.el7.ppc --> Processing Dependency: liblzma.so.5 for package: systemd-libs-219-42.el7.ppc --> Processing Dependency: libgpg-error.so.0 for package: systemd-libs-219-42.el7.ppc --> Processing Dependency: libgcrypt.so.11(GCRYPT_1.2) for package: systemd-libs-219-42.el7.ppc --> Processing Dependency: libgcrypt.so.11 for package: systemd-libs-219-42.el7.ppc --> Processing Dependency: libgcc_s.so.1(GCC_3.3.1) for package: systemd-libs-219-42.el7.ppc --> Processing Dependency: libgcc_s.so.1(GCC_3.0) for package: systemd-libs-219-42.el7.ppc --> Processing Dependency: libgcc_s.so.1 for package: systemd-libs-219-42.el7.ppc --> Processing Dependency: libdw.so.1 for package: systemd-libs-219-42.el7.ppc --> Processing Dependency: libcap.so.2 for package: systemd-libs-219-42.el7.ppc --> Running transaction check ---> Package elfutils-libs.ppc 0:0.168-8.el7 will be installed --> Processing Dependency: elfutils-libelf(ppc-32) = 0.168-8.el7 for package: elfutils-libs-0.168-8.el7.ppc --> Processing Dependency: libz.so.1(ZLIB_1.2.2.3) for package: elfutils-libs-0.168-8.el7.ppc --> Processing Dependency: libz.so.1 for package: elfutils-libs-0.168-8.el7.ppc --> Processing Dependency: libelf.so.1(ELFUTILS_1.7) for package: elfutils-libs-0.168-8.el7.ppc --> Processing Dependency: libelf.so.1(ELFUTILS_1.6) for package: elfutils-libs-0.168-8.el7.ppc --> Processing Dependency: libelf.so.1(ELFUTILS_1.5) for package: elfutils-libs-0.168-8.el7.ppc --> Processing Dependency: libelf.so.1(ELFUTILS_1.4) for package: elfutils-libs-0.168-8.el7.ppc --> Processing Dependency: libelf.so.1(ELFUTILS_1.3) for package: elfutils-libs-0.168-8.el7.ppc --> Processing Dependency: libelf.so.1(ELFUTILS_1.1.1) for package: elfutils-libs-0.168-8.el7.ppc --> Processing Dependency: libelf.so.1(ELFUTILS_1.0) for package: elfutils-libs-0.168-8.el7.ppc --> Processing Dependency: libelf.so.1 for package: elfutils-libs-0.168-8.el7.ppc --> Processing Dependency: libbz2.so.1 for package: elfutils-libs-0.168-8.el7.ppc [..] The current 7.3 has no .ppc at all installed. All filesets are ppc64 or noarch. Is it possible, that the repo is damaged somehow? How can I create additional info? Any idea how to fix it? Regards, Armin

3 6

audio flaky
by Michael Hennebry 18 Sep '17

18 Sep '17

I'm running CentOS 6. The audio goes in and out a lot. With vlc, I can sometimes get the audio back by turning the audio track off and on again. I have similar issues with a/v embedded in html. Any suggestions on how to diagnose this? -- Michael hennebry(a)web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards

4 7

Re: [CentOS] Centos 7.4.1708 dependency problems
by Lamar Owen 18 Sep '17

18 Sep '17

Greg, according to the release notes "Known Issues" section ( https://wiki.centos.org/Manuals/ReleaseNotes/CentOS7?action=show&redirect=M… ) you need to run "yum downgrade libgpod" first. I have updated a dozen or so machines to 7.4.1708, and several needed this.

2 1

keepalived segfault after upgrade to 7.4
by Phil Manuel 17 Sep '17

17 Sep '17

Prior to upgrading to CentOS 7.4 everything was fine, after upgrade I'm seeing /etc/keepalived# keepalived -f /etc/keepalived/keepalived.conf --dont-fork --log-console --log-detail --dump-conf -m -v Starting VRRP child process, pid=17224 Registering Kernel netlink reflector Registering Kernel netlink command channel Registering gratuitous ARP shared channel Opening file '/etc/keepalived/keepalived.conf'. VRRP_Instance(VI_1) removing protocol VIPs. Keepalived_vrrp exited due to segmentation fault (SIGSEGV). Please report a bug at https://github.com/acassen/keepalived/issues and include this log from when keepalived started, what happened immediately before the crash, and your configuration file. KLeepalived just respawns, segfaults, respawns ... Someone else has reported a similar issue, https://github.com/acassen/keepalived/issues/650 Regards Phil

1 0

workaround using CentOS Plus Kernel? -- for 7.4 does not support PV [Xen]
by centos＠trodman.com 17 Sep '17

17 Sep '17

Relates to: https://prgmr.com/blog/2017/09/14/centos-7-pv-unsupported.html I'm considering switching to the **CentOS Plus Kernel**. What are the downsides? In the link above, will the CentOS Plus Kernel get upgraded or will it be locked at a specific kernel? -- thanks!, Tom -- https://wiki.centos.org/AdditionalResources/Repositories/CentOSPlus

2 1

(no subject)
by centos＠trodman.com 17 Sep '17

17 Sep '17

1 0

sysconf and _SC_LEVEL1_DCACHE_LINESIZE returns 0?
by Jeffrey Walton 17 Sep '17

17 Sep '17

Hi Everyone, I'm working on GCC112, which is POWER System S822 (Power8) machine running CentOS 7 machine (https://gcc.gnu.org/wiki/CompileFarm) $ cat /etc/centos-release CentOS Linux release 7.3.1611 (AltArch) I'm trying to determine L1 data cache size. When the following code runs it returns 0. The man pages state -1 is an error, so I think its claiming to succeed. cacheLineSize = sysconf(_SC_LEVEL1_DCACHE_LINESIZE); GCC119, which is also a S822 Power8 running AIX, returns 128. Does anyone know what I might be doing wrong under Cent? Or maybe, how can I retrieve the L1 data cache line size? Thanks in advance.

1 0

Centos 7.4.1708 dependency problems
by Gregory P. Ennis 17 Sep '17

17 Sep '17

Everyone, I had four Centos 7.4 machines of which I did a manual yum update and ended up having the same problems on each machine. It looks like the packages below have dependency problems with the recent update to : CentOS Linux release 7.4.1708 (Core) Packages skipped because of dependency problems: gvfs-1.30.4-3.el7.x86_64 from base gvfs-afc-1.30.4-3.el7.x86_64 from base gvfs-afp-1.30.4-3.el7.x86_64 from base gvfs-archive-1.30.4-3.el7.x86_64 from base gvfs-client-1.30.4-3.el7.x86_64 from base gvfs-devel-1.30.4-3.el7.x86_64 from base gvfs-fuse-1.30.4-3.el7.x86_64 from base gvfs-goa-1.30.4-3.el7.x86_64 from base gvfs-gphoto2-1.30.4-3.el7.x86_64 from base gvfs-mtp-1.30.4-3.el7.x86_64 from base gvfs-smb-1.30.4-3.el7.x86_64 from base libimobiledevice-1.2.0-1.el7.x86_64 from base libplist-1.12-3.el7.x86_64 from base libusbmuxd-1.0.10-5.el7.x86_64 from base upower-0.99.4-2.el7.x86_64 from base usbmuxd-1.1.0-1.el7.x86_64 from base Greg Ennis

1 0

waitstates
by hw 16 Sep '17

16 Sep '17

Hi, are there other things than disk I/O that may cause waitstates (as shown by top, for example)? What about network traffic?

2 1

CentOS 6.4 apparent rpm problem
by Mark Haney 16 Sep '17

16 Sep '17

Well, after three days of beating my head against my desk, I'm waving the white flag. I've got a CentOS 6.4 box (yeah, I know) that I blew away the OpenLDAP client and installed the freeipa-client as we're transitioning off this terrible OpenLDAP implementation here. Everything installed fine, and while I'm still tweaking the ansible playbook for completely flushing PAM and OpenLDAP stuff off the box (we have more than 100 other C6 boxes to migrate), everything works fine with logging in using our IPA credentials. The only thing that /doesn't/ work is sudo. While debugging it, it was suggested (on the FreeIPA list) to update sudo. I've got a C6.4 box that I fully updated and sudo works fine on it. Unfortunately, I can't update this one fully, so I'm trying to update sudo only. The current version on this box is 1.8.6-7.el6.x86_64. Here's the head scratcher. I cannot, in any fashion get yum to update sudo, it says no packages are marked for update. I tried simply downloading the RPM and installing and I get this: [root@secure nnsops]# yum localinstall sudo-1.8.6p3-29.el6_9.x86_64.rpm Loaded plugins: changelog, fastestmirror Setting up Local Package Process Examining sudo-1.8.6p3-29.el6_9.x86_64.rpm: sudo-1.8.6p3-29.el6_9.x86_64 Nothing to do A couple of people on the IPA list suggested explictly using the 6.9 repo URL. Nothing. So, I ran a yum update to see what packages would update and sudo isn't one of them. I've rebuilt the RPM database with no change in result. I'm completely at a loss here, and I've been using RPM and Yum for two decades. Any other ideas? -- Mark Haney Network Engineer at NeoNova 919-460-3330 option 1 mark.haney(a)neonova.net www.neonova.net

2 2

libimoblidevice prevents updating to Centos7.4
by johan.vermeulen7＠telenet.be 16 Sep '17

16 Sep '17

Hello All, this problem occured both before the release with CR repo and now after the release. I have 150 laptops running Centos7 / MATe, including my own laptop. We have these repo's enabled: repo id repo naam status base/7/x86_64 CentOS-7 - Base 9.591 beid-release/7 Belgian eID package archive 68 epel/x86_64 Extra Packages for Enterprise Linux 7 - x86_64 11.904 extras/7/x86_64 CentOS-7 - Extras 196 google-talkplugin google-talkplugin 1 nux-dextop/x86_64 Nux.Ro RPMs for general desktop use 2.489 updates/7/x86_64 When updating I get EM: Fout: Pakket: libgpod-0.8.3-14.el7.x86_64 (@epel) Vereist: libusbmuxd.so.2()(64bit) Verwijderen: usbmuxd-1.0.8-11.el7.x86_64 (@base) libusbmuxd.so.2()(64bit) Nieuwer pakket is:: usbmuxd-1.1.0-1.el7.x86_64 (base) Niet gevonden Fout: Pakket: libgpod-0.8.3-14.el7.x86_64 (@epel) Vereist: libplist.so.1()(64bit) Verwijderen: libplist-1.10-4.el7.x86_64 (@base) libplist.so.1()(64bit) Bijgewerkt door: libplist-1.12-3.el7.x86_64 (base) ~libplist.so.3()(64bit) Fout: Pakket: libgpod-0.8.3-14.el7.x86_64 (@epel) Vereist: libimobiledevice.so.4()(64bit) Verwijderen: libimobiledevice-1.1.5-6.el7.x86_64 (@base) libimobiledevice.so.4()(64bit) Bijgewerkt door: libimobiledevice-1.2.0-1.el7.x86_64 (base) ~libimobiledevice.so.6()(64bit) Je zou kunnen proberen met behulp van --skip-broken het probleem te omzeilen Je zou kunnen proberen: rpm -Va --nofiles --nodigest What I've been doing for a few weeks when using CR repo is remove libimobiledevice and reinstall: brasero file-roller-nautilus gvfs-afc mate-applets mutter nautilus* tracker grilo-plugins libgpod mate-power-manager upower This worked but after that left-clicking NetworkManager icon doesn't display a normal window any more. And now that the problem persists after the actual release, I 'm wondering what to do. Greetings, J.

4 6

Cups driver
by H 16 Sep '17

16 Sep '17

I recently bought a Brother HL-L2360DW printer, a BW printer, and I was hoping the printer properties settings GUI could be used to adjust how colors are printed. There is a print-color-mode setting but it only has one selection: monochrome. I was wondering if tinkering with the cups driver parameters would make the above possible? I am looking for two alternative settings: - Forcing all colored text on a web page to black rather than various shades of gray which is very hard to read, background should be white. - Forcing e-mails in Thunderbird to print colored character background as some shade of gray, for some reason colored character backgrounds do not show at all, i.e. white. Are there any cups driver experts on this mailing list?

2 1

Geany markdown plugin
by H 16 Sep '17

16 Sep '17

I have not been able to find the markdown plugin for Geany for CentOS 7 on EPEL despite a number of other plugins being available. I filed a bug report some time ago so it may eventually be resolved. In the meantime, has anyone found it in a repository or should I compile all plugins from the Geany website?

1 0

zenity issue with latest Centos 7 update
by Frank Cox 15 Sep '17

15 Sep '17

zenity --width 800 --entry The window width comes out at 800 as expected, but the bar to type your entry into extends only about 1/4 of the way across the window, instead of all the way across like it did before I did the v1708 update. I'm using Centos 7 with Mate. -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

1 0

CentOS-announce Digest, Vol 151, Issue 4
by centos-announce-request＠centos.org 15 Sep '17

15 Sep '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:2728 Moderate CentOS 7 postgresql Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 14 Sep 2017 23:01:46 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:2728 Moderate CentOS 7 postgresql Security Update Message-ID: <20170914230146.GA49739(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:2728 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2017:2728 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 06772ccd2b8e77a3669d63a4d79842ad82c948d939d99425dca7c36f7108f91f postgresql-9.2.23-1.el7_4.i686.rpm 107eb14786c734223d1bf8703d955ddfacd0f80eb1719d14dd69b38925a75cff postgresql-9.2.23-1.el7_4.x86_64.rpm 480b527d4465414f789517d0b3d4f753801760fff2373199f9919ff96a6eb9dd postgresql-contrib-9.2.23-1.el7_4.x86_64.rpm 87f6520dd96840188fef128f1e8841fba1feda2c674219db38f52065dc9cb3b2 postgresql-devel-9.2.23-1.el7_4.i686.rpm 424770ca43eebaa79dc61670f21b92c7a0f4c064d84fd2f425b54ed743250d59 postgresql-devel-9.2.23-1.el7_4.x86_64.rpm 33d282ec674535b38c3fb2fb93135f2cd8130be9b0272cf4334e8d83b188e824 postgresql-docs-9.2.23-1.el7_4.x86_64.rpm 408447efea07e390d2b770feac0693254139c0d2cfcc62180129b60b1ffab761 postgresql-libs-9.2.23-1.el7_4.i686.rpm 34c713f21b9f5092bfda999d4651579791e41c37b925e561b6c18d7ecd08f079 postgresql-libs-9.2.23-1.el7_4.x86_64.rpm d9668df7d6146ed67efbfb6f2c6f26501b73300c6374c2c0420c23421ae51b2c postgresql-plperl-9.2.23-1.el7_4.x86_64.rpm 329b7c3c6c49abb0a2b5eefa00e68fd877967d1b848f934afd8019cee4e591e7 postgresql-plpython-9.2.23-1.el7_4.x86_64.rpm bc305537594d88ced0717a1479b46b877fa7478657ae92b74c302d49c459821c postgresql-pltcl-9.2.23-1.el7_4.x86_64.rpm b3018395a6c011a3f3f2a9bf94e046af73bd1caa7c925937a748a6fd4ac85a9e postgresql-server-9.2.23-1.el7_4.x86_64.rpm 8de006dc2d9295a27fe38a4815b74656f5245d7173d733c226b6c84b4ca4f788 postgresql-static-9.2.23-1.el7_4.i686.rpm 32161db990b33d6badac860e58611a9dd0d65bc64c6c841d438d0bf67f6977ef postgresql-static-9.2.23-1.el7_4.x86_64.rpm 8028f34f09288a2b6f6077a9cf702ab07a0f79483b97ddf6ea0183cd1611f54e postgresql-test-9.2.23-1.el7_4.x86_64.rpm f39a99c6bbd77710f733ef065b47062499ac76ed007b178218a28b23ce05cc3b postgresql-upgrade-9.2.23-1.el7_4.x86_64.rpm Source: 0af4d92fcbaf64e8c20dc23e05b2eb9939948ce898d0ce605cb275c0c43ff982 postgresql-9.2.23-1.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 151, Issue 4 ***********************************************

1 0

TCP Wrappers
by Nick Lekkas 15 Sep '17

15 Sep '17

Hello there to all ! I have issues to make work the spawn on hosts.allow on a CentOS 7 system ? Has anyone succeed with this ..? Thanks in advance Nick __________ Information from ESET Endpoint Antivirus, version of detection engine 16085 (20170914) __________ The message was checked by ESET Endpoint Antivirus. Email message - is OK http://www.eset.com

1 0

lighttpd and cgi error reporting
by hw 15 Sep '17

15 Sep '17

Hi, is there a way to get error messages created by CGI perl programs (not fastCGI) logged with lighttpd? Apache used to put all errors into its error log and lighttpd does not. That makes debugging rather difficult.

1 1

Spurious Segmentation Fault after upgrade to 7.4
by Gerhard Schneider 15 Sep '17

15 Sep '17

After upgrading approx. 50 machines to 7.4 we discovered a reproducible SegFault of one of our commercial programs we use. This SegFault does not occur on CentOS 7.3 and it occurs only on Xeon E3-1230 V3, Xeon E5-2690 and Xeon E5-2697 v2. It does NOT occur on Xeon E5-2697 v3 and Xeon E3-1231 v3, AMD Ryzen and older Core I7-9xx. It is not dependent of the kernel, we switched back to an CentOS 7.3 kernel and forward to an Linux 4.11 kernel without success. When we run CentOS 7.3 as a guest on CentOS 7.4 in VMWare on affected CPUs the Segmentation Fault does not occur. Is there any processor specific optimzation dependency on the 7.4 glibc or any libraries I don't know? And what to do against it? Thank you in advance! Gerhard Schneider -- Gerhard Schneider Institute of Lightweight Design and e-Mail: gs(a)ilsb.tuwien.ac.at Structural Biomechanics (E317) Tel.: +43 1 58801 31716 TU Wien / Vienna / Austria Fax: +43 1 58801 31799 A-1060 Wien, Getreidemarkt 9/BE02 http://www.ilsb.tuwien.ac.at/~gs/

1 0

Running COS 7.1708 on VirtualBox 5.1.28
by Ken Gramm 15 Sep '17

15 Sep '17

Anyone else having issues getting the VB drivers to load on 1708? I keep gettting an "Error: unable to find the sources of your current Linux kernel..." message. I do have kernel-devel installed and I had no issues running 1611 on the same host. Thanks

2 3

Update to 7.4 using DVD
by Jerry Geis 14 Sep '17

14 Sep '17

I am attempting to update to 7.4 using the DVD I get these errors(truncated list) Error: Package: libgpod-0.8.3-14.el7.x86_64 (@epel) Requires: libusbmuxd.so.2()(64bit) Removing: usbmuxd-1.0.8-11.el7.x86_64 (@anaconda) libusbmuxd.so.2()(64bit) Obsoleted By: usbmuxd-1.1.0-1.el7.x86_64 (c7-media) Not found Error: Package: network-manager-applet-1.4.0-2.el7.x86_64 (@base) Requires: libnma(x86-64) = 1.4.0-2.el7 Removing: libnma-1.4.0-2.el7.x86_64 (@base) libnma(x86-64) = 1.4.0-2.el7 Updated By: libnma-1.8.0-3.el7.x86_64 (c7-media) libnma(x86-64) = 1.8.0-3.el7 Error: Package: ipa-python-compat-4.4.0-14.el7.centos.7.noarch (@updates) Requires: ipa-common = 4.4.0-14.el7.centos.7 Removing: ipa-common-4.4.0-14.el7.centos.7.noarch (@updates) ipa-common = 4.4.0-14.el7.centos.7 Updated By: ipa-common-4.5.0-20.el7.centos.noarch (c7-media) ipa-common = 4.5.0-20.el7.centos Error: Package: jansson-devel-2.4-6.el7.x86_64 (@base) Requires: jansson = 2.4-6.el7 Removing: jansson-2.4-6.el7.x86_64 (@anaconda) jansson = 2.4-6.el7 Updated By: jansson-2.10-1.el7.x86_64 (c7-media) jansson = 2.10-1.el7 Error: Package: graphite2-devel-1.3.6-1.el7_2.x86_64 (c7-media) Requires: graphite2(x86-64) = 1.3.6-1.el7_2 Installed: graphite2-1.3.10-1.el7_3.x86_64 (@updates) graphite2(x86-64) = 1.3.10-1.el7_3 Available: graphite2-1.3.6-1.el7_2.x86_64 (c7-media) graphite2(x86-64) = 1.3.6-1.el7_2 Error: Package: ipa-python-compat-4.4.0-14.el7.centos.7.noarch (@updates) Requires: python2-ipalib = 4.4.0-14.el7.centos.7 Removing: python2-ipalib-4.4.0-14.el7.centos.7.noarch (@updates) python2-ipalib = 4.4.0-14.el7.centos.7 Updated By: python2-ipalib-4.5.0-20.el7.centos.noarch (c7-media) python2-ipalib = 4.5.0-20.el7.centos Error: Package: grilo-devel-0.2.12-2.el7.x86_64 (@base) Requires: libgrlnet-0.2.so.0()(64bit) Removing: grilo-0.2.12-2.el7.x86_64 (@anaconda) libgrlnet-0.2.so.0()(64bit) Updated By: grilo-0.3.3-1.el7.x86_64 (c7-media) ~libgrlnet-0.3.so.0()(64bit) Error: Package: mesa-libgbm-devel-11.2.2-2.20160614.el7.x86_64 (@base) Requires: mesa-libgbm(x86-64) = 11.2.2-2.20160614.el7 Removing: mesa-libgbm-11.2.2-2.20160614.el7.x86_64 (@base) mesa-libgbm(x86-64) = 11.2.2-2.20160614.el7 Updated By: mesa-libgbm-17.0.1-6.20170307.el7.x86_64 (c7-media) mesa-libgbm(x86-64) = 17.0.1-6.20170307.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest I have ran the rpm -Va --nofiles --nodigest did no help, I ran with the --skip-broken and then all these files are skipped, including new kernel. What else can I run to install these files ? I'm doing this from the mounted DVD yum --disablerepo=\* --enablerepo=c7-media update Thanks, Jerry

6 18

Re: [CentOS] Intel Skylake Server
by Mark (Netbook) 14 Sep '17

14 Sep '17

Hello, I have a pre-production Intel Skylake server using dual 8176 processors (28 core @2.1Ghz) I have loaded from the DVD distribution CentOS 7.3 and RHEL 7.4 with no problems. When I try and load CentOS 6.9 the boot process hangs just as the Anaconda graphics is started for CentOS configuration. If I use a secondary graphics card then the process completes with no problems and CentOS boots from the system disk error free. The server uses AST2500 graphics as standard. This seems to be the problem. What I need is an iso file that I can load during the initial boot process. I have tried various grub options and they don’t work. The reason that I am trying CentOS 6.9 is that many people have applications which will only run on CentOS 6.*. Regards, Mark Woolfson MW Consultancy Ltd Leeds LS18 4LY United Kingdom Tel: +44 113 259 1204 Mob: +44 786 065 2778 --- This email has been checked for viruses by AVG. http://www.avg.com

3 3

vmware player 12.5.7 with CentOS 7.4
by Jerry Geis 14 Sep '17

14 Sep '17

hi all - anyone find a way to get vmware player 12.5.7 working with 7.4? Thanks - everything good with the upgrade except that. Great job CentOS team! Jerry starting vmplayer I get the following: Note: adwaita is installed. canberra is installed No idea what pk is ? vmplayer (vmware-modconfig:12595): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", /usr/share/themes/Adwaita/gtk-2.0/main.rc:733: error: unexpected identifier `direction', expected character `}' (vmware-modconfig:12595): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", /usr/share/themes/Adwaita/gtk-2.0/hacks.rc:28: error: invalid string constant "normal_entry", expected valid string constant Gtk-Message: Failed to load module "pk-gtk-module": libpk-gtk-module.so: cannot open shared object file: No such file or directory Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory Stopping vmware (via systemctl): [ OK ] Using kernel build system. make: Entering directory `/tmp/modconfig-piDjEW/vmnet-only' /usr/bin/make -C /lib/modules/3.10.0-693.2.2.el7.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/kernels/3.10.0-693.2.2.el7.x86_64' CC [M] /tmp/modconfig-piDjEW/vmnet-only/driver.o CC [M] /tmp/modconfig-piDjEW/vmnet-only/hub.o CC [M] /tmp/modconfig-piDjEW/vmnet-only/userif.o CC [M] /tmp/modconfig-piDjEW/vmnet-only/netif.o CC [M] /tmp/modconfig-piDjEW/vmnet-only/bridge.o CC [M] /tmp/modconfig-piDjEW/vmnet-only/procfs.o CC [M] /tmp/modconfig-piDjEW/vmnet-only/smac.o CC [M] /tmp/modconfig-piDjEW/vmnet-only/smac_compat.o CC [M] /tmp/modconfig-piDjEW/vmnet-only/vnetEvent.o In file included from include/linux/pci.h:35:0, from /tmp/modconfig-piDjEW/vmnet-only/compat_netdevice.h:27, from /tmp/modconfig-piDjEW/vmnet-only/netif.c:43: include/linux/pci_ids.h:2251:0: warning: "PCI_VENDOR_ID_VMWARE" redefined [enabled by default] #define PCI_VENDOR_ID_VMWARE 0x15ad ^ In file included from /tmp/modconfig-piDjEW/vmnet-only/net.h:38:0, from /tmp/modconfig-piDjEW/vmnet-only/vnetInt.h:26, from /tmp/modconfig-piDjEW/vmnet-only/netif.c:42: /tmp/modconfig-piDjEW/vmnet-only/vm_device_version.h:56:0: note: this is the location of the previous definition #define PCI_VENDOR_ID_VMWARE 0x15AD ^ In file included from /tmp/modconfig-piDjEW/vmnet-only/netif.c:43:0: /tmp/modconfig-piDjEW/vmnet-only/netif.c: In function ‘VNetNetifStartXmit’: /tmp/modconfig-piDjEW/vmnet-only/compat_netdevice.h:343:46: error: ‘struct net_device’ has no member named ‘trans_start’ #define compat_netif_trans_update(d) do { (d)->trans_start = jiffies; } while (0) ^ /tmp/modconfig-piDjEW/vmnet-only/netif.c:468:4: note: in expansion of macro ‘compat_netif_trans_update’ compat_netif_trans_update(dev); ^ make[2]: *** [/tmp/modconfig-piDjEW/vmnet-only/netif.o] Error 1 make[2]: *** Waiting for unfinished jobs.... In file included from /tmp/modconfig-piDjEW/vmnet-only/net.h:38:0, from /tmp/modconfig-piDjEW/vmnet-only/vnetInt.h:26, from /tmp/modconfig-piDjEW/vmnet-only/bridge.c:52: /tmp/modconfig-piDjEW/vmnet-only/vm_device_version.h:56:0: warning: "PCI_VENDOR_ID_VMWARE" redefined [enabled by default] #define PCI_VENDOR_ID_VMWARE 0x15AD ^ In file included from include/linux/pci.h:35:0, from /tmp/modconfig-piDjEW/vmnet-only/compat_netdevice.h:27, from /tmp/modconfig-piDjEW/vmnet-only/bridge.c:51: include/linux/pci_ids.h:2251:0: note: this is the location of the previous definition #define PCI_VENDOR_ID_VMWARE 0x15ad ^ make[1]: *** [_module_/tmp/modconfig-piDjEW/vmnet-only] Error 2 make[1]: Leaving directory `/usr/src/kernels/3.10.0-693.2.2.el7.x86_64' make: *** [vmnet.ko] Error 2 make: Leaving directory `/tmp/modconfig-piDjEW/vmnet-only' Starting vmware (via systemctl): Job for vmware.service failed because the control process exited with error code. See "systemctl status vmware.service" and "journalctl -xe" for details. [FAILED]

2 1

Re: [CentOS] JRE 8.1 for CentOS6
by ejm 14 Sep '17

14 Sep '17

> When I put in http it changes it back to https That's common now that everyone puts re-directs in to force everyone to use https. Can you get to the Apache logs on the remote machine? They may have more info. The error about Java 1.8 might be a red-herring. If the remote machine uses Perl on the backend, you might try setting the shell env variable OPENSSL_PREFIX to point on your local CentOS6 box to a newer version of openssl that handles the TLS handshake. The CPAN module Net::SSLeay uses that variable (if set) to use the specified OpenSSL library. --Ed

3 2

CentOS-announce Digest, Vol 151, Issue 3
by centos-announce-request＠centos.org 14 Sep '17

14 Sep '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. Release for CentOS Linux 7 (1708) on x86_64 (Karanbir Singh) 2. Release for CentOS 7.4.1708 for AArch64/ARM64 (Jim Perrin) 3. Release for CentOS Linux 7 (1708) on armhfp (Fabian Arrotin) 4. CESA-2017:2685 Moderate CentOS 7 bluez Security Update (Johnny Hughes) 5. CESA-2017:2679 Important CentOS 7 kernel Security Update (Johnny Hughes) 6. Updates for CentOS Linux 7 (1708) through 9/11/2017 (Johnny Hughes) 7. Release for CentOS Linux 7 (1708) on ppc64le (James O'Connor) 8. Release for CentOS Linux 7 (1708) on ppc64 (James O'Connor) ---------------------------------------------------------------------- Message: 1 Date: Wed, 13 Sep 2017 20:48:27 +0100 From: Karanbir Singh <kbsingh(a)centos.org> To: CentOS Announcements List <centos-announce(a)centos.org> Subject: [CentOS-announce] Release for CentOS Linux 7 (1708) on x86_64 Message-ID: <93441a2b-09f1-3577-6f02-76cace36ba3f(a)centos.org> Content-Type: text/plain; charset="utf-8" I am pleased to announce the general availability of CentOS Linux 7 (1708) for 64 bit x86 compatible machines. Effectively immediately, this is the current release for CentOS Linux 7 and is tagged as 1708, derived from Red Hat Enterprise Linux 7.4 As always, read through the Release Notes at : http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 - these notes contain important information about the release and details about some of the content inside the release from the CentOS QA team. These notes are updated constantly to include issues and incorporate feedback from the users. ---------- Updates, Sources, and DebugInfos Updates released since we froze the iso and install media content are posted in the updates repo along with the release. This will include content from late Aug 2017 and Sept 2017, therefore anyone running a new install is highly encouraged to run a 'yum update' operation immediate on install completion. You can apply all updates, including the content released today, on your existing CentOS Linux 7/x86_64 machine by just running 'yum update'. As with all CentOS Linux 7 components, this release was built from sources hosted at git.centos.org. In addition, SRPMs that are a byproduct of the build (and also considered critical in the code and buildsys process) are being published to match every binary RPM we release. Sources will be available from vault.centos.org in their own dedicated directories to match the corresponding binary RPMs. Since there is far less traffic to the CentOS source RPMs compared with the binary RPMs, we are not putting this content on the main mirror network. If users wish to mirror this content they can do so using the reposync command available in the yum-utils package. All CentOS source RPMs are signed with the same key used to sign their binary counterparts. Developers and end users looking at inspecting and contributing patches to the CentOS Linux distro will find the code hosted at git.centos.org far simpler to work against. Details on how to best consume those are documented along with a quick start at : http://wiki.centos.org/Sources Debuginfo packages are also being signed and pushed. Yum configs shipped in the new release file will have all the context required for debuginfo to be available on every CentOS Linux install. This release supersedes all previously released content for CentOS Linux 7, and therefore we highly encourage all users to upgrade their machines. Information on different upgrade strategies and how to handle stale content is included in the Release Notes. Note that older content, obsoleted by newer versions of the same applications are trim'd off from repos like Extras/ and Plus/ However this time we have also extended this to the sIG content hosted at mirror.centos.org, and some older End of Life content has been dropped. Everything we ever release, is always available on the vault service for people still looking for and have a real need for it. ---------- Download In order to conserve donor bandwidth, and to make it possible to get the mirror content sync'd out as soon as possible, we recommend using torrents to get your initial installer images: Details on the images are available on the mirrors at http://mirror.centos.org/centos/7/isos/x86_64/0_README.txt - that file clearly highlights the difference in the images, and when one might be more suitable than the others. The sizes, sha256 sums for the ISO files: ec7500d4b006702af6af023b1f8f1b890b6c7ee54400bb98cef968b883cd6546 CentOS-7-x86_64-DVD-1708.iso ( 4.2G) 8593f5a1631ebfb7581193a7b4ef96d44f500d3ceb49cc4cfbfd71d5698e4173 CentOS-7-x86_64-Everything-1708.iso ( 8.1G) 9941f5e1257d74e763652ceae5096ed73ddc94a9703ae116931d8713b801fec0 CentOS-7-x86_64-LiveGNOME-1708.iso ( 1.2G) 4ba63634a8430d134d8a9535c62ff1341c33c898fb1c768a0c6e54fbc92a9133 CentOS-7-x86_64-LiveKDE-1708.iso ( 1.7G) bba314624956961a2ea31dd460cd860a77911c1e0a56e4820a12b9c5dad363f5 CentOS-7-x86_64-Minimal-1708.iso ( 792 M) fe3d960cce4d2c1c9f1b66817fe87cc0ee1a1c6c5dd126204cb5c33d51a45620 CentOS-7-x86_64-NetInstall-1708.iso ( 422 M) Information for the torrent files and sums are available at http://mirror.centos.org/centos/7/isos/x86_64 -------- Additional Images The container, Vagrant, Cloud and Atomic Host images are being prepared and will be released in the next few days. Look for an announcement posted to the centos-announce list for more information on availability for these in the coming days. ---------- Dojo We try and organise Dojos in various parts of the world as a one day event, to bring together people who use CentOS and others who are keen to learn about CentOS. The day's focus is on sharing technical knowledge and success stories. It's also a great place to meet and talk about upcoming technologies and learn how others are using them on CentOS Linux. The next Dojo coming up is on the 20th Oct hosted by CERN, in Switzerland. Details for this are available on https://indico.cern.ch/event/649159/ ( please note that you must register ahead of time to attend ) ---------- Getting Help The CentOS ecosystem is sustained by community driven help and guidance. The best place to start for new users is at http://wiki.centos.org/GettingHelp We are also on social media, you can find the project: on Twitter at : http://twitter.com/CentOSProject on Facebook at : https://www.facebook.com/groups/centosproject/ on LinkedIn at : https://www.linkedin.com/groups/22405 And you will find the core team and a majority of the contributors on irc, on freenode.net in #centos ; talking about the finer points of distribution engineering and platform enablement. ---------- Contributors This release was made possible due to the hard work of many people, foremost on that list are the Red Hat Engineers for producing a great distribution and the CentOS QA team, without them CentOS Linux would look very different. Many of the team went further and beyond expectations to bring this release to you, and I would like to thank everyone for their help. We are also looking for people to get involved with the QA process in CentOS, if you would like to join this please introduce yourself on the centos-devel list (http://lists.centos.org/mailman/listinfo/centos-devel ). As some people would have noticed there is no i686 build for 1708 as yet - we have run into a couple of build and dependency issues that could use help. So if you are keen to get involved this is a great opportunity. Finally, please join me in thanking the donors who all make this possible for us. Enjoy the fresh new release! -- 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

1 0

Update of cloud-init in CentOS 7 Extras
by Pierre Riteau 14 Sep '17

14 Sep '17

Hello, The version of cloud-init packaged in CentOS 7 Extras is rather old (0.7.5, which was released in 2014). It is missing some functionality that we would like to use, as well as important bug fixes. Before I tackle rebuilding the package myself, I would like to know if there is a plan to update extras to a newer cloud-init version, or if has anyone has already updated cloud-init and would be happy to share the spec? Many thanks, Pierre Riteau Chameleon Lead DevOps Engineer

2 4

Apache 2.2 EOL - what is Red Hat's story for RHEL6?
by Alan McKay 13 Sep '17

13 Sep '17

Hi folks, I have been googling for a few weeks now and not finding anything. Apache 2.2 is EOL at the end of this year. Has Red Hat announced a plan yet on what they are doing in RHEL6? I am assuming they will up-version from 6.9 to 6.10 and as part of that upgrade from Apache 2.2 to Apache 2.4 ? thanks, -Alan -- "You should sit in nature for 20 minutes a day. Unless you are busy, then you should sit for an hour" - Zen Proverb

7 9

cyrus spool on btrfs?
by hw 13 Sep '17

13 Sep '17

Hi, is there anything that speaks against putting a cyrus mail spool onto a btrfs subvolume?

12 45

[CentOS] https://ctan.org/tex-archive/graphics/pstricks/contrib/pst-barcode/
by hw 13 Sep '17

13 Sep '17

Hi, https://ctan.org/tex-archive/graphics/pstricks/contrib/pst-barcode/ says that pst-barcode is included in texlive. I installed texlive, and it can´t find pst-barcode.sty. Is that a bug in the packaging Centos does, or is texlive in Centos some derelict version?

3 3

system slowdown
by Larry Martell 13 Sep '17

13 Sep '17

I have a CentOS 6 system that has suddenly starting significantly slowing down. It runs a django app with an Apache server and MySQL server. There is plenty of disk space and no process seems to be hogging the memory or CPU. But operations that used to take 5 minutes are now taking hours and hours. Coinciding with this slow down I see these messages in /var/log/messages (this is hand typed, as I can't copy/paste or send email from this system, although for a change I do have remote access via 2 VPN hops): kernel: BUG: soft lockup - CPU#5 stuck for 67s! [khungtaskd] kernel: BUG: soft lockup - CPU#7 stuck for 67s! [khugepaged] These messages started appearing today around 7 AM, which is when users started reporting the slowdown. They are still occurring periodically and the system is still slow. Are these messages caused by the slowdown or are they the reason for it? Are they useful in tracking down the problem?

2 3

CentOS-announce Digest, Vol 151, Issue 2
by centos-announce-request＠centos.org 13 Sep '17

13 Sep '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:2681 Important CentOS 6 kernel Security Update (Johnny Hughes) 2. CESA-2017:2685 Moderate CentOS 6 bluez Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 12 Sep 2017 23:15:02 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:2681 Important CentOS 6 kernel Security Update Message-ID: <20170912231502.GA63829(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:2681 Important Upstream details at : https://access.redhat.com/errata/RHSA-2017:2681 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 7a7e756bdd778e6b552e95e51ec2b38f8492b755929fafd37ee80341a05a2fe0 kernel-2.6.32-696.10.2.el6.i686.rpm 6b2e9e78a22faba659b12ea2775604009bb6b41e243179df49ce5c187b4cd76b kernel-abi-whitelists-2.6.32-696.10.2.el6.noarch.rpm a79b93e88aa475510db88b2f0503b752c69ab0797a32b1a3b46e7ab455f52bfa kernel-debug-2.6.32-696.10.2.el6.i686.rpm 3f37d2c6befe9bd7d9d4afc1bb5024e589285e30e5a758ed3755764dfff0f5cd kernel-debug-devel-2.6.32-696.10.2.el6.i686.rpm fea84013ef28f95125c2a6175af0eaac4876e575a0a62e5d5c04f00898780844 kernel-devel-2.6.32-696.10.2.el6.i686.rpm ea414d9514476ed940bb33ad39b3ab9c58b2f7ac4e72fbb667a706ea8349bf56 kernel-doc-2.6.32-696.10.2.el6.noarch.rpm 5566fbb87f5c6f1a3d267487ea6ca417ca6ec60ff610d0421d40d30d5f8a1c98 kernel-firmware-2.6.32-696.10.2.el6.noarch.rpm 5ddf34e914c3a51d4b1887a44fd1e2eb70c7189be716b6c0906c101a303e17ee kernel-headers-2.6.32-696.10.2.el6.i686.rpm 133bd9bbe4b85cba6ce8153f20d83c9456abd755944384d597de556b200bff08 perf-2.6.32-696.10.2.el6.i686.rpm c0f48d37c0adeca7aa7847353288eecadbbafe8e5c4470679bd8425deb521d64 python-perf-2.6.32-696.10.2.el6.i686.rpm x86_64: 5a068ea731cace53bfce2ead23a15536f258424fab34f1213daea933e8966d78 kernel-2.6.32-696.10.2.el6.x86_64.rpm 6b2e9e78a22faba659b12ea2775604009bb6b41e243179df49ce5c187b4cd76b kernel-abi-whitelists-2.6.32-696.10.2.el6.noarch.rpm 6ee990b5ee67f5cefcee70ddeb7feeeccffc6457d18ff3c0f1a82c375535c0b7 kernel-debug-2.6.32-696.10.2.el6.x86_64.rpm 3f37d2c6befe9bd7d9d4afc1bb5024e589285e30e5a758ed3755764dfff0f5cd kernel-debug-devel-2.6.32-696.10.2.el6.i686.rpm 6027e42601a185c0f4bf6c290c971678922b1e31cad4c2aedbef8e1c80f2f922 kernel-debug-devel-2.6.32-696.10.2.el6.x86_64.rpm 709c68c776d8db6d03e08b4fb609e5f9c0b6b293531a8cb59bb1c5c4b2389b7b kernel-devel-2.6.32-696.10.2.el6.x86_64.rpm ea414d9514476ed940bb33ad39b3ab9c58b2f7ac4e72fbb667a706ea8349bf56 kernel-doc-2.6.32-696.10.2.el6.noarch.rpm 5566fbb87f5c6f1a3d267487ea6ca417ca6ec60ff610d0421d40d30d5f8a1c98 kernel-firmware-2.6.32-696.10.2.el6.noarch.rpm e412035e84b763214b8dd9f679ba6c7c4c22e07107c000fdd193b613c492d5af kernel-headers-2.6.32-696.10.2.el6.x86_64.rpm 0b4eeb2ac18fa4da9998621b5595a6492929b0258c936056e2a3e1c19e261eff perf-2.6.32-696.10.2.el6.x86_64.rpm 93163e180b9f2927220805b39b10b97e7b74bd202b0abb22d8ecb92bd213d60d python-perf-2.6.32-696.10.2.el6.x86_64.rpm Source: 187fa35692f8a9f2c294a3f9a20713e78351e6e662a9983ab65533aff437ecfc kernel-2.6.32-696.10.2.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Tue, 12 Sep 2017 23:15:38 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:2685 Moderate CentOS 6 bluez Security Update Message-ID: <20170912231538.GA64188(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:2685 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2017:2685 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: f55b99ac9aeb545e217b69fa3f9bf1570ec4c59f5c6d121c22c2af788345ae7d bluez-4.66-2.el6_9.i686.rpm 57b7082172ce050457c8767b0c71cb3ea1333b63d4c371b790e267b2d5fbb369 bluez-alsa-4.66-2.el6_9.i686.rpm 4c70d6a7409019bfc72d131abb0456715738f24e0a3da38d5f5fd69aeebebe16 bluez-compat-4.66-2.el6_9.i686.rpm 668e314d0f092255fab6d18627ee93ae0ee5ce583d0753f1a66c87efee26591f bluez-cups-4.66-2.el6_9.i686.rpm 3706f759e384c00379bb3619118e8d576a141ebbdcad34e830fadf28885021ad bluez-gstreamer-4.66-2.el6_9.i686.rpm 26062fdd3ef719101c7c6c1be8069f74e7844fae8efeff18ab2b77e7b23c2e6e bluez-libs-4.66-2.el6_9.i686.rpm 381ed986c23d2fcd177e9020131a1c29f2906505bb735c79b8a491da930dd457 bluez-libs-devel-4.66-2.el6_9.i686.rpm x86_64: 160a385295a5d3087a5001c08372c9273d6f31e03242f134de45a54548adb630 bluez-4.66-2.el6_9.x86_64.rpm 57b7082172ce050457c8767b0c71cb3ea1333b63d4c371b790e267b2d5fbb369 bluez-alsa-4.66-2.el6_9.i686.rpm eb270282119149cb802de3133d8488223a8c6d7687377d24851da8a5ce57070f bluez-alsa-4.66-2.el6_9.x86_64.rpm 15d223dc36cb1556f92185614e1866daf2990a4019340e37d41ac98f1a09c781 bluez-compat-4.66-2.el6_9.x86_64.rpm ab1440290aba968f127578e02645f5b86affbf633101e07e334b94c6265de289 bluez-cups-4.66-2.el6_9.x86_64.rpm 3706f759e384c00379bb3619118e8d576a141ebbdcad34e830fadf28885021ad bluez-gstreamer-4.66-2.el6_9.i686.rpm 4d244850c245e50f8a65f8ce9306f2d2025997663797870a4c93adbf6a9ad597 bluez-gstreamer-4.66-2.el6_9.x86_64.rpm 26062fdd3ef719101c7c6c1be8069f74e7844fae8efeff18ab2b77e7b23c2e6e bluez-libs-4.66-2.el6_9.i686.rpm ff261867f68c7348b635d3b1fc962991b1405b5d48b9e5e97cd47a1606333f84 bluez-libs-4.66-2.el6_9.x86_64.rpm 381ed986c23d2fcd177e9020131a1c29f2906505bb735c79b8a491da930dd457 bluez-libs-devel-4.66-2.el6_9.i686.rpm 7c61988835262d896c3fcdbbc853f7b45b5972f6f7bfe9352142fd94f31f346d bluez-libs-devel-4.66-2.el6_9.x86_64.rpm Source: 07ac1e159666835719637d8a17ea9083951925377f7affbd8d18c315b5dfda84 bluez-4.66-2.el6_9.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 151, Issue 2 ***********************************************

1 0

Xen PV DomU's and the 3.10.0-693.el7 Kernel
by Johnny Hughes 12 Sep '17

12 Sep '17

If you are running CentOS Linux 7 inside a Xen DomU (VM) in PV mode, you can not upgrade to the standard 7.4.1708 kernel that is currently in the CR repo and that will be soon released in our file 7.4.1708 tree (3.10.0-693.*el7) The CentOS Plus kernel will be available when we release the 7.4.1708 tree and it does boot inside a Xen DomU PV, so you can either upgrade to the CentOS Plus kernel in PV mode .. or you can shift your DomU to either HVM or PVHVM modes. PVHVM is more like PV mode, and is usually much better than HVM mode. More info on PVHVM here: https://wiki.xen.org/wiki/PV_on_HVM https://wiki.xen.org/wiki/Xen_Linux_PV_on_HVM_drivers The anaconda installer and pxe booting from the standard tree 7.4.1708 tree will also not work in PV mode for new installs, only PVHVM or HVM installs can be done with the 7.4.1708 tree. Note: This is an upstream source code issue and will not be fixed in the main CentOS Linux 7 kernel unless it is fixed upstream in the RHEL source code. We are sorry for any inconvenience this issue may cause. Thanks, Johnny Hughes

1 0

bind named fails after logrotate
by Götz Reinicke 12 Sep '17

12 Sep '17

Hi, on our centos 7.3.1611 server the named dies after the log rotates script is executed. systemctl status named ● named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Di 2017-09-12 14:27:57 CEST; 2s ago Process: 20714 ExecStop=/bin/sh -c /usr/sbin/rndc stop > /dev/null 2>&1 || /bin/kill -TERM $MAINPID (code=exited, status=1/FAILURE) Process: 20684 ExecReload=/bin/sh -c /usr/sbin/rndc reload > /dev/null 2>&1 || /bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Main PID: 14496 (code=killed, signal=ABRT) Any suggestions or hints or is that a known problem? logrotate-3.8.6 bind-9.9.4 Thanks and regards . Götz

1 0

Missing CentOS 7 Updates
by Ken Gramm 12 Sep '17

12 Sep '17

I must be missing something, because I can't believe that there haven't been any updates since July 27 9fa12aadcd2ea45fdcb91bd125b619545993defa2032cf99b8a89cf6099723e8-primary.xml.gz 27-Jul-2017 15:12 4.0M [ ] 23b0e14a9667597b69a8719f0eea709721cc32f9f3b6c8202da0f5a36b9f1759-other.xml.gz 27-Jul-2017 15:12 137M [ ] 33fdce604445f67a26ce5ddc354ea0c835ed119ac8cb7404cc2b565bf80722a1-primary.sqlite.bz2 27-Jul-2017 15:16 7.8M [ ] 732f62a4c48e764e2ebe276eef7e6bf25eaf477452260a03805512a6a7a6ce80-filelists.sqlite.bz2 27-Jul-2017 15:16 4.4M [ ] 36288cdc93433b594aed022edabca28fe92c3497e23da598c59f890c0ddd7255-other.sqlite.bz2 27-Jul-2017 15:16 93M [ ] a6fd2af929647636c10531913d7c0b3a4277732a694d9aff9093dbb7890c4094-prestodelta.xml.gz 27-Jul-2017 15:14 954K [ ] bab46e0e0fd6233a1d50ad0cebcc6bae42c43fb85bf143f6ec415fd3458e882d-filelists.xml.gz 27-Jul-2017 15:12 4.8M [TXT] repomd.xml 27-Jul-2017 15:16 3.4K [TXT] repomd.xml.asc 27-Jul-2017 15:21 811

3 4

Corosync on a home network
by J Martin Rushton 11 Sep '17

11 Sep '17

I've been trying to build a model cluster using three virtual machines on my home server. Each VM boots off its own dedicated partition (CentOS 7.3). One partition is designated to be the common /home partition for the VMs, (on the real machine it will mount as /cluster). I'm intending to run GFS2 on the shared partition, so I need to configure DLM and corosync. That's where I'm getting bogged down. The VMs and the real machine are bridged onto one ethernet. There is another ethernet in the main machine on a different network, but that is not used for clustering. The ethernet port is connected to a switch which in turn connects to a BT Home Hub 6. All four adresses are static, Network Manager is off, ssh works across the nodes without a password and ping gives sensible times. --------------%<------------------- # brctl show bridge name bridge id STP enabled interfaces br3 XXXXXXXXX no enp3s0 vnet0 vnet1 vnet2 virbr0 XXXXXXXXX yes virbr0-nic --------------%<------------------- When I start corosync each node starts up but does not see the others. For instance I see: --------------%<---------------------- # corosync-quorumtool Quorum information ------------------ Date: Sun Sep 10 12:56:56 2017 Quorum provider: corosync_votequorum Nodes: 1 Node ID: 3 Ring ID: 3/28648 Quorate: No Votequorum information ---------------------- Expected votes: 4 Highest expected: 4 Total votes: 1 Quorum: 3 Activity blocked Flags: Membership information ---------------------- Nodeid Votes Name 3 1 192.168.1.52 (local) ----------------%<------------------- All four nodes are similar, but with different node IDs, IP addresses and Ring IDs. The documentation warns that not all routers will handle multicast datagrams correctly. I therefore attempted to force unicast communication by making the following changes from the distributed corosync.conf: transport: updu cluster_name: <set to the same as the domain> # crypto_cipher: none # crypto_hash: none # mcastaddr: 239.255.1.1 # mcastport: 5405 # ttl: 1 The following are unchanged: version: 2 secauth: off ringnumber: 0 bindnetaddr: 192.168.1.0 The nodelist is: ---------%<---------------- nodelist { node { ring0_addr: 192.168.1.2 nodeid: 1 } node { ring0_addr: 192.168.1.51 nodeid: 2 } node { ring0_addr: 192.168.1.52 nodeid: 3 } node { ring0_addr: 192.168.1.53 nodeid: 4 } } --------%<------------------ logging and quorum are as supplied. Any help will be gratefully received. Regards, Martin

4 5

Kernel Updates
by Michael Rapuano 11 Sep '17

11 Sep '17

We are running kernel-3.10.0-514.26.2.el7 and need to update to kernel-3.10.0-693.el7. The new kernel is in the CR repo but not in the base/update repos. When will the updates in the CR repo be in the base/update repos? This is a high priority security issue for us. -- Michael Rapuano michael.rapuano(a)cloudlock.com

3 2

centos-7.4 elfutils
by Jack Bailey 11 Sep '17

11 Sep '17

Hello, I'm taking 7.4 for a spin. I did the minimal install, and ran into trouble with groupinstall base. The trouble seems to stem from elfutils. One command claims elfutils-libs-0.166-2.el7.x86_64 is missing, and another one claims it's installed. Not sure what's going on here. [root@ip-172-31-34-187 ~]# yum -y install elfutils.x86_64 Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirror.web-ster.com * extras: mirror.chpc.utah.edu * updates: mirrors.cat.pdx.edu Resolving Dependencies --> Running transaction check ---> Package elfutils.x86_64 0:0.166-2.el7 will be installed --> Processing Dependency: elfutils-libs(x86-64) = 0.166-2.el7 for package: elfutils-0.166-2.el7.x86_64 --> Processing Dependency: elfutils-libelf(x86-64) = 0.166-2.el7 for package: elfutils-0.166-2.el7.x86_64 --> Finished Dependency Resolution Error: Package: elfutils-0.166-2.el7.x86_64 (base) Requires: elfutils-libelf(x86-64) = 0.166-2.el7 Installed: elfutils-libelf-0.168-8.el7.x86_64 (@anaconda) elfutils-libelf(x86-64) = 0.168-8.el7 Available: elfutils-libelf-0.166-2.el7.x86_64 (base) elfutils-libelf(x86-64) = 0.166-2.el7 Error: Package: elfutils-0.166-2.el7.x86_64 (base) Requires: elfutils-libs(x86-64) = 0.166-2.el7 Installed: elfutils-libs-0.168-8.el7.x86_64 (@anaconda) elfutils-libs(x86-64) = 0.168-8.el7 Available: elfutils-libs-0.166-2.el7.x86_64 (base) elfutils-libs(x86-64) = 0.166-2.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@ip-172-31-34-187 ~]# yum -y install elfutils-libs.x86_64 Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirror.web-ster.com * extras: mirror.chpc.utah.edu * updates: mirrors.cat.pdx.edu Package matching elfutils-libs-0.166-2.el7.x86_64 already installed. Checking for update. Nothing to do

3 3

SNMP V3 libraries not found, SNMPV3 disabled.
by Alex Tang 11 Sep '17

11 Sep '17

Dear all, I have installed mrtg via yum on centos 7, and using cron job to load mrtg every 5 mins. Everything work fine but just snmp v3 graph no show up. I try to load the command LAND=C /usr/bin/mrtg /etc/mrtg/metg.cfg it will show an error "SNMP V3 libraries not found, SNMPV3 disabled.". so, i installed all the net-snmp but still showing the error. I can't find any suggestion on google. can anyone have the same problem ? Thanks Alex

1 0

systemctl poweroff
by Nicolas Kovacs 11 Sep '17

11 Sep '17

Hi, I've been using CentOS since versions 4.x, and I see a weird trend in recent Linux distributions. Under CentOS 4.x, 5.x and 6.x, shutting down a server (workstation, laptop) simply meant issuing 'shutdown -h now' (or choosing 'Shutdown' from the GUI menu), and the machine would simply shut down. Whatever crazy process went haywire, shutting down the system meant exactly that. No questions asked. Now with CentOS 7.x, sometimes the machine would simply hang during the shutdown process, or I would get a message like "a stop job is running", and I would end up having to hit the Reset button to stop the system, as I did when I used Microsoft Windows (before 2001). Cheers, Niki Kovacs -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

2 1

Flush memory on a server?
by Nicolas Kovacs 11 Sep '17

11 Sep '17

Hi, A few days ago I checked the health of my main public server running CentOS 7, a quad-core machine with 16 GB RAM. It had been running non-stop for 65 days, hosting only a handful of services (BIND, NTP, Apache, Postfix, Dovecot) for two domains. I was surprised to see that RAM consumption was relatively high, and apparently, the machine even had to swap at some time. I read up a bit on RAM consumption, and now I wonder if flushing the memory cache regularly is a good idea. https://tecadmin.net/flush-memory-cache-on-linux-server/ Any suggestions? Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

6 9

CentOS 7 on PPC64le booting from a MD RAID volume
by Tom Leach 08 Sep '17

08 Sep '17

I've been trying to install CentOS 7 AltArch ppc64le onto a new Power 8 system and I want to configure mdraid for the volumes. I can get everything working if I install to a single disk, but when I configure for RAID 1, the system fails to boot. So, is mdraid1 supported for booting a Power 8 system? Tom Leach leach(a)coas.oregonstate.edu

1 0

Re: [CentOS] login case sensitivity
by James B. Byrne 08 Sep '17

08 Sep '17

On Thu, September 7, 2017 14:07, hw wrote: > Gordon Messmer wrote: >> On 09/07/2017 08:11 AM, Stephen John Smoogen wrote: >>> This was always problematic because DNS hostnames and >>> email addresses in the RFC standards were case insensitive >> >> >> Not quite. SMTP is required to treat the "local-part" of the RCPT >> argument as case-sensitive, and to preserve case when relaying mail. >> The destination is allowed to treat addresses according to local >> policy, but in general SMTP is case sensitive with regard to the >> user identifier. > > Last time I checked, RFCs said that local parts *should not* be case > sensitive, and cyrus defaulted to treat them case sensitive, which > is a default that usually needs to be changed because senders of > messages tend to not pay any attention to the case sensitiveness > of recipient addresses at all, which then confuses them like any > other error. > > https://tools.ietf.org/html/rfc5321 Updated by: 7504 DRAFT STANDARD Errata Exist Network Working Group J. Klensin Request for Comments: 5321 October 2008 Obsoletes: 2821 Updates: 1123 Category: Standards Track . . . 2.4. General Syntax Principles and Transaction Model . . . Verbs and argument values (e.g., "TO:" or "to:" in the RCPT command and extension name keywords) are not case sensitive, with the sole exception in this specification of a mailbox local-part (SMTP Extensions may explicitly specify case-sensitive elements). That is, a command verb, an argument value other than a mailbox local-part, and free form text MAY be encoded in upper case, lower case, or any mixture of upper and lower case with no impact on its meaning. __The local-part of a mailbox MUST BE treated as case sensitive.__ Therefore, SMTP implementations MUST take care to preserve the case of mailbox local-parts. In particular, for some hosts, the user "smith" is different from the user "Smith". However, exploiting the case sensitivity of mailbox local-parts impedes interoperability and is discouraged. Mailbox domains follow normal DNS rules and are hence not case sensitive. . . . Case munging of the local part is handled by the local delivery agent in my experience. The Cyrus LMTP service can be, and often is, configured to force lower case munging (imapd.conf 'lmtp_downcase_rcpt: 1') of the local part. That decision is site specific. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

intel wireless 3165 and CentOS 7.3
by Jerry Geis 08 Sep '17

08 Sep '17

I am trying to get wireless working on CentOS 7.3 with intel wireless 3165 ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000 link/ether b8:ae:ed:77:b3:3a brd ff:ff:ff:ff:ff:ff 3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000 link/ether 34:02:86:cc:a0:79 brd ff:ff:ff:ff:ff:ff 4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT qlen 1000 link/ether 52:54:00:70:8f:48 brd ff:ff:ff:ff:ff:ff 5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue master virbr0 state DOWN mode DEFAULT qlen 500 link/ether 52:54:00:70:8f:48 brd ff:ff:ff:ff:ff:ff lspci 00:00.0 Host bridge: Intel Corporation Device 2280 (rev 21) 00:02.0 VGA compatible controller: Intel Corporation Device 22b1 (rev 21) 00:13.0 SATA controller: Intel Corporation Device 22a3 (rev 21) 00:14.0 USB controller: Intel Corporation Device 22b5 (rev 21) 00:1a.0 Encryption controller: Intel Corporation Device 2298 (rev 21) 00:1b.0 Audio device: Intel Corporation Device 2284 (rev 21) 00:1c.0 PCI bridge: Intel Corporation Device 22c8 (rev 21) 00:1c.1 PCI bridge: Intel Corporation Device 22ca (rev 21) 00:1c.2 PCI bridge: Intel Corporation Device 22cc (rev 21) 00:1f.0 ISA bridge: Intel Corporation Device 229c (rev 21) 00:1f.3 SMBus: Intel Corporation Device 2292 (rev 21) 02:00.0 Network controller: Intel Corporation Wireless 3165 (rev 81) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) I have created the ifcfg-ESSID and keys-ESSID files. but I dont even thing the wireless is loading. ifconfig does not report wlan0 or anything. What am I missing to get wireless going? Thanks, Jerry

1 0

login case sensitivity
by FHDATA 08 Sep '17

08 Sep '17

hello, some users' login fails since they type upper case for their user ids ,etc ... how can case sensitivity be disabled so they can login with mix of upper and lower case? this is what i tried: in /etc/sssd/sssd.conf i tested this below [domain/default] case_sensitive = false i stopped sssd, deleted all inside /var/sss/db and started sssd but that did not help .... thank you, F-

8 11

installing lxqt on CentOS-7
by Fred Smith 07 Sep '17

07 Sep '17

I see that epel has a bunch of lxqt packages,, but there doesn't seem to be a lxqt group. if I try to install lxqt-* it of course wants to install a whole shipload of stuff alongside it. does anyone here happen to know the correct incantation for getting lxqt onto a C7 system without unnecessary crap? thanks in advance! Fredex -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- "For him who is able to keep you from falling and to present you before his glorious presence without fault and with great joy--to the only God our Savior be glory, majesty, power and authority, through Jesus Christ our Lord, before all ages, now and forevermore! Amen." ----------------------------- Jude 1:24,25 (niv) -----------------------------

1 0

lightdm dependency
by Jon LaBadie 05 Sep '17

05 Sep '17

On a CentOS 7 system I'm trying to install lightdm. Yum says it requires "glib2(x86-64) >= 2.50.3". glib2 2.46 is installed but I have not found a 2.50 version. Have I overlooked it in some repo? -- Jon H. LaBadie jcu(a)labadie.us 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)

2 2

Network Interrogation
by Chris Olson 05 Sep '17

05 Sep '17

Small private networks are a necessary part of our business. We also run some small networks with Internet connectivity through firewall routers. The smallest of these networks has only a printer and a mix of five CentOS and Windows 7 machines. We use a commercial protection product on the W7 system. This product has worked well guarding against unwanted software on the system for about three and a half years. Scans are scheduled and performed routinely once a week or on demand at various times. A recent update to this protection product has caused it to start probing the network for other systems. There is sometimes a message following scans indicating that there are other systems on our network that are unprotected. It appears that the two systems it is naming are a CentOS 6 system and the HP printer. This network probing does not happen with every scan that is run by the protection software and we have not been able to determine what causes that probing to be initiated. We also do not know exactly what is happening over the network during the probing activity. The protection software support folks have been no help in figuring out what is going on. There seems to be no good reason for the probing message to name only these two systems. The available printer status shows no indication of network traffic associated with this probing activity. The CentOS 6 system also does not indicate any related network activity from the system that is running the protection software. We have tried unsuccessfully to capture the network probing activity using Wireshark. Any ideas regarding how to track down what is happening here would be greatly appreciated.

5 4

Kernel 4.12 and nVidia Driver
by Eugene Poole 05 Sep '17

05 Sep '17

I tried to move to the latest stable kernel (4.12) so I could take advantage of my newest custom system (Intel Core I7 6-core; 64 GB RAM; MSI nVidia graphics card; 2 - 120 GB SSD; 2 - 4TB WD Black) on a UEFI Asrock mother board. I've had the machine for 3-months but I couldn't get it to work until I found out that the Nouveau driver was causing me all the 'hardware' issues. I moved to the nVidia driver along with DKMS and all of my issues went away until I attempted to upgrade kernel 4.12 ... It seems that DKMS doesn't automatically upgrade when the kernel is upgraded. Will this issue go away if I change my graphics card to a AMD? -- Eugene Poole Woodstock, Georgia

4 3

Simple OCSP server ??
by Alice Wonder 05 Sep '17

05 Sep '17

Hello list, I'm contemplating running my own CA to implement the new proposed ISP for validation of S/MIME certificates via DANE. I already use self-signed for my MX servers (with 3 1 1 dane records on TCP port 25) but I don't want to use self-signed for S/MIME for user specific x.509 certs because A) That's potentially a lot of DNS records B) That requires a hash of the e-mail addresses in DNS Instead, I will be using a wildcard in DNS with an intermediary that signs the user x.509 certificates. Using an intermediary to sign their certificates though means I can't just revoke their certificates by removing the DNS certificate, I'll need to provide an OCSP server for when one of their private keys gets compromised. I found https://access.redhat.com/documentation/en-US/Red_Hat_Certificate_System/8.… but it looks like that is intended for enterprise, more complex than I need. Anyone know of a good simple script for providing OCSP ?? -=- Not relevant to question but just important for me to note, I will *not* be asking people to install my root certificate in their e-mail clients. I think it is a bad practice to get users in the habit of installing root certificates. I think the PKI system has way way way to many root certificates as it is. I want a world where DANE validates most certificates, and only a few root certificates are needed for things like banks where EV certificates are a must. DANE as a way to validate S/MIME I think will be a godsend to e-mail security, I hope clients implement it.

2 5

Problem with IPTABLES logging message to the screen/console
by Jobst Schmalenbach 05 Sep '17

05 Sep '17

Hi I am not sure how to solve this. I am constantly getting messages that should go into the kern/message log printed on screen - MOSTLY from iptables. The messages are ALSO logged to the syslog files. It still prints those message onto the console screen even if I am logged off (security issue). When logged in on the console its anoying as I constantly have to hit CTRL-L to refresh the screen to get rid of those messages. However it does NOT happen when I ssh into the machine. How can I solve this that those messages are NOT printed. thanks Jobst -- Share your knowledge. It's a way to achieve immortality. | |0| | Jobst Schmalenbach, jobst(a)barrett.com.au, General Manager | | |0| |0|0|0| +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia

2 2

selinux denial of cgi script with httpd using ssl
by Gregory P. Ennis 05 Sep '17

05 Sep '17

Everyone, I am trying to use a cgi perl script for a CentOs 7 website that works fine with selinux in permissive mode but fails with selinux in enforcing mode. The problem I have is that I can not find where the selinux error message is being recorded. It does not appear to be in the /var/log/messages or /var/log/audit/audit.log. I do not get any /var/log/httpd/ssl_error_log entries. I do get a successful entry into /var/log/httpd/ssl_access_log and ssl_request_log when selinux is in permissive mode, but not when selinux is in enforcing mode. The only place I can see that I am getting an error message is in the /var/log/httpd/error_log which is as follows : Mon Sep 04 11:40:24.216569 2017] [cgi:error] [pid 2290] [client x.x.x.x:55748] AH01215: (13)Permission denied: exec of '/var/www/cgi-bin/name.of.script.cgi' failed, referer: https://name.domain.com/ When selinux is in permissive mode the above error does not occur and the script works fine. When selinux is in enforcing mode the above error occurs, and the cgi script fails to execute. Is there a way to increase the sensitivity of selinux loging, or is there a different place to look for the error that prevents the execution of the script. Your help would be appreciated. Thanks, Greg Ennis

4 7

CentOS nDPI kmod avaliable for testing
by Eliezer Croitoru 04 Sep '17

04 Sep '17

I have been working for quite some time building nDPI iptables module from vel21ripn for many Linux distributions and I just finished couple basic tests on the module for CentOS 7 and I am quite satisfied. I am looking for other CentOS 7 admins who will want to test this iptables module. More details are at: https://github.com/vel21ripn/nDPI/issues/18 Thanks, Eliezer ---- Eliezer Croitoru Linux System Administrator Mobile: +972-5-28704261 Email: eliezer(a)ngtech.co.il

1 0

rkhunter and prelink
by m.roth＠5-cent.us 02 Sep '17

02 Sep '17

Can't remember if I posted this before... We're getting warnings from rkhunterWarning: Checking for prerequisites [ Warning ] All file hash checks will be skipped because: This system uses prelinking, but the hash function command does not look like SHA1 or MD5. Now, googling, I find people saying to rm /etc/prelink.cache, then run rkhunter --propupd. Works. And then, prelink runs in the middle of the night, via /etc/cron.daily, and when the cron job of rkhunter runs, it's back to complaining. Anyone have any ideas what's going on here? I don't see anything in the prelink.conf, or any options in the prelink manpage to tell is what hash to use. mark

5 7

share /var/spool/cups-pdf/SPOOL/?
by hw 02 Sep '17

02 Sep '17

Hi, is there a way to set multiple selinux attributes to files/directories? I would like to share /var/spool/cups-pdf/SPOOL/, which has 'system_u:object_r:print_spool_t:s0' and would also need 'system_u:object_r:samba_share_t:s0'. The point is that there will be files accumulating that only need to be deleted, and there might be files users may actually want access to. Sharing the directory (and a script that automatically deletes files from there which are too old) would be a way to achieve this.

1 0

spice client?
by hw 01 Sep '17

01 Sep '17

Hi, how do I connect to a VM running on a removte machine with some sort of spice client? There doesn´t seem to be any spice client available in Centos 7 that works.

3 7

CentOS-announce Digest, Vol 151, Issue 1
by centos-announce-request＠centos.org 01 Sep '17

01 Sep '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:2550 Moderate CentOS 6 poppler Security Update (Johnny Hughes) 2. CESA-2017:2534 Important CentOS 6 thunderbird Security Update (Johnny Hughes) 3. CESA-2017:2563 Moderate CentOS 6 openssh Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 31 Aug 2017 18:48:46 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:2550 Moderate CentOS 6 poppler Security Update Message-ID: <20170831184846.GA34711(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:2550 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2017:2550 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 5e00e48b8c0ac31de59d24deaa04247cc665a39827832cfac05df03c164c52c4 poppler-0.12.4-12.el6_9.i686.rpm d25cdcfbfc0bf8ef7f5e548984674c6ce2a8d6a2eaef784b1ea7767840690466 poppler-devel-0.12.4-12.el6_9.i686.rpm 94011927f19dd72b17214ea203338a17c4e75507543666097b0d7244860da132 poppler-glib-0.12.4-12.el6_9.i686.rpm 23425ddf68356964411efc36159173c6ae243d0eb237dce6361e582d2baa9e97 poppler-glib-devel-0.12.4-12.el6_9.i686.rpm f88d5fb1cb327fb9dacc48f2ab02cc12ac09ea043622e39b4eb34ec33088cd76 poppler-qt-0.12.4-12.el6_9.i686.rpm d201890924ed934ca293d1a88c1a7da78be176166099574c7858c60f3ee93c6e poppler-qt4-0.12.4-12.el6_9.i686.rpm 8d645831a8fac15e1c8e5a32fc9183e95713f9ef1ee561af2d1cc7d11bd705fc poppler-qt4-devel-0.12.4-12.el6_9.i686.rpm 5b88d65fe039f4b9f2ea41faeaa59c35ee0e10a6c24bbf1756f5a9ea6fb0a8f0 poppler-qt-devel-0.12.4-12.el6_9.i686.rpm 59ca913a180b4fd587d4479b64efa37f04c1ee5b6812d17319f69e9cc38d5807 poppler-utils-0.12.4-12.el6_9.i686.rpm x86_64: 5e00e48b8c0ac31de59d24deaa04247cc665a39827832cfac05df03c164c52c4 poppler-0.12.4-12.el6_9.i686.rpm 2a7c924303b93c19268086f7202cd4d147d54ba04b4d5e9c31f785c887d0f3ff poppler-0.12.4-12.el6_9.x86_64.rpm d25cdcfbfc0bf8ef7f5e548984674c6ce2a8d6a2eaef784b1ea7767840690466 poppler-devel-0.12.4-12.el6_9.i686.rpm df823b5d17233bc08e976918b1aeb8d16d88e40c8de95da56c6ad9d22cde0f03 poppler-devel-0.12.4-12.el6_9.x86_64.rpm 94011927f19dd72b17214ea203338a17c4e75507543666097b0d7244860da132 poppler-glib-0.12.4-12.el6_9.i686.rpm aaa7b0ad900a0f1b77a503bed3772ca8f8d5cc9299be07eba849d67fff67f21a poppler-glib-0.12.4-12.el6_9.x86_64.rpm 23425ddf68356964411efc36159173c6ae243d0eb237dce6361e582d2baa9e97 poppler-glib-devel-0.12.4-12.el6_9.i686.rpm 77a0cf7d64625bd9547bde17cee820eb1c12c4d153cc92dd1f3edd2afc5113bb poppler-glib-devel-0.12.4-12.el6_9.x86_64.rpm f88d5fb1cb327fb9dacc48f2ab02cc12ac09ea043622e39b4eb34ec33088cd76 poppler-qt-0.12.4-12.el6_9.i686.rpm 29d53b90f6ca5ba1ea401ae122c4ff987a20aa8accfa019f3a9afbb25bb24b46 poppler-qt-0.12.4-12.el6_9.x86_64.rpm d201890924ed934ca293d1a88c1a7da78be176166099574c7858c60f3ee93c6e poppler-qt4-0.12.4-12.el6_9.i686.rpm b411d564f12f72a171e5dfb7a15ed32b276afc23b86ce0799aebd2e3400006cf poppler-qt4-0.12.4-12.el6_9.x86_64.rpm 8d645831a8fac15e1c8e5a32fc9183e95713f9ef1ee561af2d1cc7d11bd705fc poppler-qt4-devel-0.12.4-12.el6_9.i686.rpm 6935fc562c03523283368b0ac587bbc9d98b8ec84006d4991d2e3b243157a134 poppler-qt4-devel-0.12.4-12.el6_9.x86_64.rpm 5b88d65fe039f4b9f2ea41faeaa59c35ee0e10a6c24bbf1756f5a9ea6fb0a8f0 poppler-qt-devel-0.12.4-12.el6_9.i686.rpm 2ce55815fe0011187173d93bba74e0f4fc0c01b5b2b4800081c27d54c659b654 poppler-qt-devel-0.12.4-12.el6_9.x86_64.rpm e75d1d7531bd8ff24932c7ed58fb34b24d9cb1913a3642887e42f441f1725b5d poppler-utils-0.12.4-12.el6_9.x86_64.rpm Source: 8f9a5f707bf29ee83b8e38b90cf211b01a841591e47fd5848061d37fddf66669 poppler-0.12.4-12.el6_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Thu, 31 Aug 2017 18:49:52 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:2534 Important CentOS 6 thunderbird Security Update Message-ID: <20170831184952.GA34820(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:2534 Important Upstream details at : https://access.redhat.com/errata/RHSA-2017:2534 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 96494a6bbf9295994238419e7b7e9d0f32bd34771f06b54f0f0d06439c72f95e thunderbird-52.3.0-1.el6.centos.i686.rpm x86_64: 6afe985ea385fb5549fcb8ed89fff3cb4ceacf121de067e809e88da57daa5c48 thunderbird-52.3.0-1.el6.centos.x86_64.rpm Source: 369ece0043d2781f548a3fe74c097d222f6e9afabd2e7f38a07c476f10dd9cb7 thunderbird-52.3.0-1.el6.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Thu, 31 Aug 2017 18:50:28 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:2563 Moderate CentOS 6 openssh Security Update Message-ID: <20170831185028.GA35127(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:2563 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2017:2563 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 7fcc14482bde0ffd56256a95d4e9fb1adde76ff3bd4e51bca62d991216637a41 openssh-5.3p1-123.el6_9.i686.rpm 0b7200aa9e46618664f5ce4418d8dc2a3536246ce4c05a8d49c87a91a2e65c4c openssh-askpass-5.3p1-123.el6_9.i686.rpm 38117542a8fbe8ed16604704c90009c0317759f67de4329b644f1741e72c98fb openssh-clients-5.3p1-123.el6_9.i686.rpm 9446db394224c7ad6b155386d690b5992115d1c0cc2a1e6c324f8db313faffa2 openssh-ldap-5.3p1-123.el6_9.i686.rpm 1b4954075f7f4364460e35cdd4c76c9bdd0f8a6ab5bb7e2ef04cbee9c1098aaa openssh-server-5.3p1-123.el6_9.i686.rpm 318fe5d62ad947c5090fd36310e6938a1f0de93bd2b9b9c490c2bbf2ba9bd65d pam_ssh_agent_auth-0.9.3-123.el6_9.i686.rpm x86_64: ca4e9591f2670255c532f2be9b229eff12799006d60aefd7decdf68ab555975c openssh-5.3p1-123.el6_9.x86_64.rpm 5a8b1a467d7836300f53b54e1e96bdaa93cf8df93cd730729f6d5e430f61a8f5 openssh-askpass-5.3p1-123.el6_9.x86_64.rpm 5c7ac733ef43bdd9169c9ba26d2e44d273496508649c30acf2c119c8ee4dd7d0 openssh-clients-5.3p1-123.el6_9.x86_64.rpm 1c4c57bb410082a30401cd68e492d13d3b58577afa604e9ae79114468f61b006 openssh-ldap-5.3p1-123.el6_9.x86_64.rpm 69b18041197c4be9a2812bbea1fc92f94b45d7adca0dd9c308f87dde7743ac06 openssh-server-5.3p1-123.el6_9.x86_64.rpm 318fe5d62ad947c5090fd36310e6938a1f0de93bd2b9b9c490c2bbf2ba9bd65d pam_ssh_agent_auth-0.9.3-123.el6_9.i686.rpm f87bed409bfde8b91268589a1c32da959cba0bae5a555bed2150c2a4667723f3 pam_ssh_agent_auth-0.9.3-123.el6_9.x86_64.rpm Source: 4c78bd24259d3604ffbf905642dbf44d209c3997696cfc443eae7885a8d9a53a openssh-5.3p1-123.el6_9.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 151, Issue 1 ***********************************************

1 0

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

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??

1 0

Odd switch of running MTA during update through CR to 7.4.1708
by Lamar Owen 27 Aug '17

27 Aug '17

Ok, had a real oddity here, and am working to track it down. I've done a few updates to 7(1708) via CR at this point, and hadn't had any real issues, so during a slack time today updated our email server. Now, prior to the update, I had our email server set up with postfix, but after the update the system had sendmail enabled and postfix disabled. Like I said, I'm still looking into it, but just a heads-up. A 'systemctl disable sendmail; systemctl stop sendmail' then 'systemctl enabled postfix; systemctl start postfix' seems to have restored things. I would probably be well-off to remove sendmail altogether, but I would have thought that the startup settings would have been honored anyway. -- Lamar Owen Chief Technology Officer Pisgah Astronomical Research Institute 1 PARI Drive Rosman, NC 28772 828-862-5554 www.pari.edu

1 0

Lenovo T460p post 7.4 CR possible problems
by Stephen John Smoogen 26 Aug '17

26 Aug '17

I have updated my laptop to 7.4 CR this morning and found that there have been a lot of logs on two fronts for the first time. 1. The kernel has indicated overheating: [Sat Aug 26 08:58:21 2017] CPU2: Core temperature above threshold, cpu clock throttled (total events = 1) [Sat Aug 26 08:58:21 2017] CPU4: Package temperature above threshold, cpu clock throttled (total events = 1) [Sat Aug 26 08:58:21 2017] CPU6: Core temperature above threshold, cpu clock throttled (total events = 1) [Sat Aug 26 08:58:21 2017] CPU0: Package temperature above threshold, cpu clock throttled (total events = 1) [Sat Aug 26 08:58:21 2017] CPU6: Package temperature above threshold, cpu clock throttled (total events = 1) [Sat Aug 26 08:58:21 2017] mce: [Hardware Error]: Machine check events logged [Sat Aug 26 08:58:21 2017] CPU2: Package temperature above threshold, cpu clock throttled (total events = 1) [Sat Aug 26 08:58:21 2017] mce: [Hardware Error]: Machine check events logged [Sat Aug 26 08:58:21 2017] CPU1: Package temperature above threshold, cpu clock throttled (total events = 1) [Sat Aug 26 08:58:21 2017] CPU5: Package temperature above threshold, cpu clock throttled (total events = 1) [Sat Aug 26 08:58:21 2017] CPU3: Package temperature above threshold, cpu clock throttled (total events = 1) [Sat Aug 26 08:58:21 2017] CPU7: Package temperature above threshold, cpu clock throttled (total events = 1) [Sat Aug 26 08:58:21 2017] CPU2: Core temperature/speed normal [Sat Aug 26 08:58:21 2017] CPU4: Package temperature/speed normal [Sat Aug 26 08:58:21 2017] CPU1: Package temperature/speed normal [Sat Aug 26 08:58:21 2017] CPU5: Package temperature/speed normal [Sat Aug 26 08:58:21 2017] CPU0: Package temperature/speed normal [Sat Aug 26 08:58:21 2017] CPU6: Core temperature/speed normal [Sat Aug 26 08:58:21 2017] CPU3: Package temperature/speed normal [Sat Aug 26 08:58:21 2017] CPU7: Package temperature/speed normal [Sat Aug 26 08:58:21 2017] CPU6: Package temperature/speed normal [Sat Aug 26 08:58:21 2017] CPU2: Package temperature/speed normal This happened when logging into a Cinnamon desktop. The desktop background would go black when this happened and the fans went to 100%. After two minutes it quieted down. Logging in again with Cinnamon repeated it. Using the default Gnome desktop does not have this problem so this is more of a "if you are using Cinnamon you may run into this." The second was that the new nouveau driver is very noisy on the hardware. The message repeats: Sat Aug 26 13:42:36 2017] nouveau 0000:02:00.0: priv: HUB0: 6013d4 00005700 (1f408200) [Sat Aug 26 13:42:37 2017] nouveau 0000:02:00.0: priv: HUB0: 10ecc0 ffffffff (1940822c) [Sat Aug 26 13:42:37 2017] nouveau 0000:02:00.0: DRM: resuming client object trees... [Sat Aug 26 13:42:44 2017] nouveau 0000:02:00.0: DRM: evicting buffers... [Sat Aug 26 13:42:44 2017] nouveau 0000:02:00.0: DRM: waiting for kernel channels to go idle... [Sat Aug 26 13:42:44 2017] nouveau 0000:02:00.0: DRM: suspending client object trees... [Sat Aug 26 13:42:44 2017] nouveau 0000:02:00.0: DRM: suspending kernel object tree... [Sat Aug 26 13:42:45 2017] nouveau 0000:02:00.0: DRM: resuming kernel object tree... [Sat Aug 26 13:42:45 2017] nouveau 0000:02:00.0: priv: HUB0: 6013d4 ffff57ff (18408200) [Sat Aug 26 13:42:45 2017] nouveau 0000:02:00.0: priv: HUB0: 10ecc0 ffffffff (1840822c) [Sat Aug 26 13:42:45 2017] nouveau 0000:02:00.0: DRM: resuming client object trees... fairly often. The system does seem to be running hotter with the fan going louder than what i remember it being with 7.3. At this point I am mostly reporting this as a "anyone else seeing this?" type report. -- Stephen J Smoogen.

3 5

more questions on setting up autofs on C7
by Fred Smith 26 Aug '17

26 Aug '17

Hi! Thanks to some of you I got autofs set up on my C7 netbook for mounting local cifs filesytems. Now I want to do something on my C7 desktop machine, that seems to me to be a little different, and I"m not sure how to do it. I have an external RAID1 box that attaches via USB. It is/will be nearly always /dev/sdc, but being USB I can't guarantee that it will always be found there. accordingly, in my /etc/fstab I have an entry that mounts it via its UUID: UUID=09bfc97a-8db2-46de-b4dd-427da19b114 /mnt/backup xfs defaults,noauto,users 0 2 and I'm wondering how to specify that in an autofs recipe instead... If doing cifs mounts, /etc/auto.master may contain this line: /mymount /etc/auto.mymount then there would be a file /etc/auto.mymount that contains a line similar to this: winbox -fstype=cifs,rw,noperm,user=sushi,pass=yummy ://winbox/getme so, in my case, the USB drive contains an xfs filesystem. would I do something like this: in /etc/auto.master: backup /etc/auto.backup and in /etc/auto.backup backup -fstype=xfs,defaults,noauto,users :UUID=09bfc97a-8db2-46de-b4dd-427da19b114 Would that be expected to work, or am I all overlooking something obvious? Thanks in advance for your advice! Fred -- ------------------------------------------------------------------------------- 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 -----------------------------

2 10

Thunderbird update without announcement?
by Leonard den Ottolander 25 Aug '17

25 Aug '17

Hi, I usually receive updates after the related announcement has hit my inbox. But today I see a thunderbird update, but no message on centos-announce yet, not even in the archives. Regards, Leonard. -- mount -t life -o ro /dev/dna /genetic/research

4 3

C7 and ebtables
by m.roth＠5-cent.us 24 Aug '17

24 Aug '17

I need to set ebtables up on a mini-firewall we've got. I'd like to just use ebtables-save to dump the rules from another firewall, and restore it to the new one. There is *no* manpage* for either ebtables-save or ebtables-restore. Usage - restore doesn't like -?, -h, or --help, and I have no clue as to what it will accept. Google is being egregiously useless. Has anyone used these commands, and/or have some examples of their use? Thanks in advance. mark

1 0

Updated Apache httpd packages?
by Erik Osterholm 24 Aug '17

24 Aug '17

I'm concerned about the vulnerability at https://access.redhat.com/ errata/RHSA-2017:2479 I see via https://lists.centos.org/pipermail/centos-announce/ 2017-August/022518.html that Centos 6 has received the fix for this. Is there a roadmap for when Centos 7 will receive the fix? Thanks!

5 9

CentOS-announce Digest, Vol 150, Issue 3
by centos-announce-request＠centos.org 24 Aug '17

24 Aug '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. CEBA-2017:2506 CentOS 6 dhcp BugFix Update (Johnny Hughes) 2. CEBA-2017:2504 CentOS 6 kernel BugFix Update (Johnny Hughes) 3. CEBA-2017:2501 CentOS 6 acl BugFix Update (Johnny Hughes) 4. CEBA-2017:2502 CentOS 6 java-1.8.0-openjdk BugFix Update (Johnny Hughes) 5. CEBA-2017:2503 CentOS 6 samba BugFix Update (Johnny Hughes) 6. CEEA-2017:2500 CentOS 6 unbound Enhancement Update (Johnny Hughes) 7. CEBA-2017:2505 CentOS 6 sssd BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 23 Aug 2017 18:00:06 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2017:2506 CentOS 6 dhcp BugFix Update Message-ID: <20170823180006.GA12741(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2017:2506 Upstream details at : https://access.redhat.com/errata/RHBA-2017:2506 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 31d4b1e77ecd473cfae41fbf4216158cc9b923d553556d412e637ff2fa8cec47 dhclient-4.1.1-53.P1.el6.centos.1.i686.rpm c35277ba2644e77feb9984275cd871a9e632e0392b9d332e0a85827e7906d1aa dhcp-4.1.1-53.P1.el6.centos.1.i686.rpm d35c82ff2e3d02889531fd6adb737c11890758c2252ad1cc85f11cd871a4e24a dhcp-common-4.1.1-53.P1.el6.centos.1.i686.rpm 9a0feab0407cb62c42d6e3d2488a0ec9a00c1812117bf9ff591742b3f578fc3c dhcp-devel-4.1.1-53.P1.el6.centos.1.i686.rpm x86_64: 1a5b9ef938292a1b272db6a52a341cb4cf470d78c9ee44b999b66837797a1c5c dhclient-4.1.1-53.P1.el6.centos.1.x86_64.rpm 069cbc470f4d064b759f1573f74102667aae852b3efc7c3999f5322f3f559e16 dhcp-4.1.1-53.P1.el6.centos.1.x86_64.rpm 6570ee68e9333cbf9698863b2ce4b90f3bd3135c27b537e78d0506b7673a4792 dhcp-common-4.1.1-53.P1.el6.centos.1.x86_64.rpm 9a0feab0407cb62c42d6e3d2488a0ec9a00c1812117bf9ff591742b3f578fc3c dhcp-devel-4.1.1-53.P1.el6.centos.1.i686.rpm 27b4ec55bae530671a45a52a54c84c175cb5d7d2169ac0a5b465ec9ea2b15f31 dhcp-devel-4.1.1-53.P1.el6.centos.1.x86_64.rpm Source: 904fbae9672602a5e167a228ea712b71460e2a1f705ef0922b5bbec9559dd9cf dhcp-4.1.1-53.P1.el6.centos.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Wed, 23 Aug 2017 18:01:56 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2017:2504 CentOS 6 kernel BugFix Update Message-ID: <20170823180156.GA13196(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2017:2504 Upstream details at : https://access.redhat.com/errata/RHBA-2017:2504 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 36f1caaa6c48a78430998ec9d682c77fc9df21d9a83304552120556ecd6422a4 kernel-2.6.32-696.10.1.el6.i686.rpm 8608dcfbc36435abd0c53888bf4cf42bef1d3b6db0d3a40c5f4d8deaf468f5be kernel-abi-whitelists-2.6.32-696.10.1.el6.noarch.rpm 045fb48f38b4cecf54daaa5592d9a02f69df0208cac0469c205649f2aa62969f kernel-debug-2.6.32-696.10.1.el6.i686.rpm 29f13703c00dbda98959ed95dea17d8af796b5b19a92b61c73c76def3cb73573 kernel-debug-devel-2.6.32-696.10.1.el6.i686.rpm d76cfa1de782160933f03fe983d9f65bf3c6d8a19ba3a493f17b503617c9fd91 kernel-devel-2.6.32-696.10.1.el6.i686.rpm b67a79c5f7f1ab3ee4901179c10a2ed752224ae8cc3372052bedef807993ce0a kernel-doc-2.6.32-696.10.1.el6.noarch.rpm 4fd75de3d8f4695b54c95fd530311ecec385197c7439312afb2f47562a63c18f kernel-firmware-2.6.32-696.10.1.el6.noarch.rpm b965f76a4170f1acd67eb026745c1cec18a05d7613059face9391081e2d9269b kernel-headers-2.6.32-696.10.1.el6.i686.rpm 575fb150297a97b200d17a562b87c117058c914162fb2e0065d05a0715f14a87 perf-2.6.32-696.10.1.el6.i686.rpm 45119a13d91a6e388f7a421c8b6608cfc5240c98de6d459a4c26b18d25960799 python-perf-2.6.32-696.10.1.el6.i686.rpm x86_64: c3354e273a4502253f6bb47dac4a6651c3248e62b3e367ddec7410115f146647 kernel-2.6.32-696.10.1.el6.x86_64.rpm 8608dcfbc36435abd0c53888bf4cf42bef1d3b6db0d3a40c5f4d8deaf468f5be kernel-abi-whitelists-2.6.32-696.10.1.el6.noarch.rpm a8d900bcedce07d2df857a9cf8fa2e9e1069d2e5c4b975ef711e0225448ac725 kernel-debug-2.6.32-696.10.1.el6.x86_64.rpm 29f13703c00dbda98959ed95dea17d8af796b5b19a92b61c73c76def3cb73573 kernel-debug-devel-2.6.32-696.10.1.el6.i686.rpm 09dbd4bd464ac4ef723b6cae81013bc40fccf8aecccdaff38e7a875ebc53a674 kernel-debug-devel-2.6.32-696.10.1.el6.x86_64.rpm af3867adb5216dbf71f3c9c126cf0de06996767ef65c05f0786c0210c9a0125e kernel-devel-2.6.32-696.10.1.el6.x86_64.rpm b67a79c5f7f1ab3ee4901179c10a2ed752224ae8cc3372052bedef807993ce0a kernel-doc-2.6.32-696.10.1.el6.noarch.rpm 4fd75de3d8f4695b54c95fd530311ecec385197c7439312afb2f47562a63c18f kernel-firmware-2.6.32-696.10.1.el6.noarch.rpm b496b65ca47516f47ea820c11ee7909f3147af4c1576cd0a06e8823c8d5e67e9 kernel-headers-2.6.32-696.10.1.el6.x86_64.rpm 19a1513d18dbbdafc6982b24b6346c77539b1cc1a8cdb2771b73808ee7e15293 perf-2.6.32-696.10.1.el6.x86_64.rpm f3f19f3b992692f8910046499b26773b025e8e0b5b501ceb39f6f91c6b4da9bf python-perf-2.6.32-696.10.1.el6.x86_64.rpm Source: 63c595b74270700871b44133cabae13243117cd858fddd66d0589d875eb1509f kernel-2.6.32-696.10.1.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Wed, 23 Aug 2017 18:02:41 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2017:2501 CentOS 6 acl BugFix Update Message-ID: <20170823180241.GA13450(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2017:2501 Upstream details at : https://access.redhat.com/errata/RHBA-2017:2501 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 56c8bd71d132223a86492533476fe9ff37c5ba7c09e21b5927a9efd5b2d717dd acl-2.2.49-7.el6_9.1.i686.rpm fdd9e75884a47e8ef4ebc8552e907cd27405f6e9efbb2be773dcae07c01fc294 libacl-2.2.49-7.el6_9.1.i686.rpm 48295e81557752bcce96dd7271fe5234560db841fe309a732a7e5810323e209c libacl-devel-2.2.49-7.el6_9.1.i686.rpm x86_64: 3afaabd15713abab6adc5033f35b9db225e792d651e42199d59c8444695893a5 acl-2.2.49-7.el6_9.1.x86_64.rpm fdd9e75884a47e8ef4ebc8552e907cd27405f6e9efbb2be773dcae07c01fc294 libacl-2.2.49-7.el6_9.1.i686.rpm 2d2bb216ec706020dd82ddb7f0971d799161d3e7fb35937e14eb1a77a8c183e0 libacl-2.2.49-7.el6_9.1.x86_64.rpm 48295e81557752bcce96dd7271fe5234560db841fe309a732a7e5810323e209c libacl-devel-2.2.49-7.el6_9.1.i686.rpm 32b91ef60f2813d8275e0b87dd8193efcc515f71a8fdc54f306ee334bc55ab95 libacl-devel-2.2.49-7.el6_9.1.x86_64.rpm Source: 5ce6a3887fb3a2026f08ba2dcfe43861c564fdcf2ba330d70701abb25f4a2a19 acl-2.2.49-7.el6_9.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Wed, 23 Aug 2017 18:03:38 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2017:2502 CentOS 6 java-1.8.0-openjdk BugFix Update Message-ID: <20170823180338.GA13875(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2017:2502 Upstream details at : https://access.redhat.com/errata/RHBA-2017:2502 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 29aa47221ed0af8e6682de084d4540d06c601a6c0de5c9b2cb4f0d7bbb218262 java-1.8.0-openjdk-1.8.0.141-3.b16.el6_9.i686.rpm 82e16e5070e31a9020997eba9b93b147edc625bd0de2e786f847297de1a3074a java-1.8.0-openjdk-debug-1.8.0.141-3.b16.el6_9.i686.rpm 62574067c088c23c6d955b6c633645b483e5d339d36c3da5c9a83e7a45316c22 java-1.8.0-openjdk-demo-1.8.0.141-3.b16.el6_9.i686.rpm efe75fdda3527e508b612992da6d4802f9da71eedc8ac16939f94b29082de8a1 java-1.8.0-openjdk-demo-debug-1.8.0.141-3.b16.el6_9.i686.rpm 9fdb6873649450892fda86320a97cfea4991ce997ece1968a058adead1305cee java-1.8.0-openjdk-devel-1.8.0.141-3.b16.el6_9.i686.rpm b6705809d914d7dfdb47de13e99924cfae3915b5f3857ea77d21323874361a44 java-1.8.0-openjdk-devel-debug-1.8.0.141-3.b16.el6_9.i686.rpm b5f2badc5bf4b10129a99a10a653e6abc4b2098fac4f5a6b5e521edd603d9eed java-1.8.0-openjdk-headless-1.8.0.141-3.b16.el6_9.i686.rpm 0a0663ac988035cf801a7446053555d09fbe4ced45e97152e0f9efd439323889 java-1.8.0-openjdk-headless-debug-1.8.0.141-3.b16.el6_9.i686.rpm 697147e970a7f210014853ad4a292c6ce00de1f09338d2cbb1bada2a1dea6aeb java-1.8.0-openjdk-javadoc-1.8.0.141-3.b16.el6_9.noarch.rpm ced0c9be3af069982b0bb2b491df0f12f90fe9230425f3150ac7974a35e09784 java-1.8.0-openjdk-javadoc-debug-1.8.0.141-3.b16.el6_9.noarch.rpm 1f3df35edddb81c4f8df5ed438cb8692d8a2395e3e8b9b198c4f7e76567c5cde java-1.8.0-openjdk-src-1.8.0.141-3.b16.el6_9.i686.rpm 36dd102f5166929c45675f3e0b4f44167e851663fb909ce2152d59813463bc33 java-1.8.0-openjdk-src-debug-1.8.0.141-3.b16.el6_9.i686.rpm x86_64: bcef0720030aa7686ac1d05487e4944ed75328f20e5e07af087fc6e9537b123f java-1.8.0-openjdk-1.8.0.141-3.b16.el6_9.x86_64.rpm 031f02121c2e2f5577e2124787f7df0465fe739ba622be843ee6df2299fc0ec7 java-1.8.0-openjdk-debug-1.8.0.141-3.b16.el6_9.x86_64.rpm eb17cf3738d447bedb2aa8fb839ba7060d6c65b261ef9ddb989df0146528e42b java-1.8.0-openjdk-demo-1.8.0.141-3.b16.el6_9.x86_64.rpm f97cc7d63f151e26b5e622094e744462d83fe0f390664bd8fa7b39bcaac4df56 java-1.8.0-openjdk-demo-debug-1.8.0.141-3.b16.el6_9.x86_64.rpm 4844af6c9421c0530f3339a3c41dcabad174297866993cb7e7db26ba776250e9 java-1.8.0-openjdk-devel-1.8.0.141-3.b16.el6_9.x86_64.rpm c1ee5081c1347aabab55c11df2af0d0c86302ce2b08fa0a712adbaa41481c00d java-1.8.0-openjdk-devel-debug-1.8.0.141-3.b16.el6_9.x86_64.rpm 3bc5f354c12f7b6cfb99a4744ba466aa9d734d994a6474538fa6adc29d25414e java-1.8.0-openjdk-headless-1.8.0.141-3.b16.el6_9.x86_64.rpm af993d0a3e481916d29a621549a87a05c8ce9b4ff800e20a2b3f0f17a3e4b05d java-1.8.0-openjdk-headless-debug-1.8.0.141-3.b16.el6_9.x86_64.rpm 697147e970a7f210014853ad4a292c6ce00de1f09338d2cbb1bada2a1dea6aeb java-1.8.0-openjdk-javadoc-1.8.0.141-3.b16.el6_9.noarch.rpm ced0c9be3af069982b0bb2b491df0f12f90fe9230425f3150ac7974a35e09784 java-1.8.0-openjdk-javadoc-debug-1.8.0.141-3.b16.el6_9.noarch.rpm 60e766a44b71709b81024f3449f9d0a58a28f57ef8a2478b66fd021bda4b3ca4 java-1.8.0-openjdk-src-1.8.0.141-3.b16.el6_9.x86_64.rpm 213d25f86aae1878a802e2281897d38f09624e4ef42dcf0aefbbaf056b1b37d3 java-1.8.0-openjdk-src-debug-1.8.0.141-3.b16.el6_9.x86_64.rpm Source: 2f5bf796b01b62d0f84d5f162ccd24689e6195379a761db829c176d292504d3f java-1.8.0-openjdk-1.8.0.141-3.b16.el6_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Wed, 23 Aug 2017 18:04:15 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2017:2503 CentOS 6 samba BugFix Update Message-ID: <20170823180415.GA14358(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2017:2503 Upstream details at : https://access.redhat.com/errata/RHBA-2017:2503 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 87269f714a65dd129fca8497dd8b037337fb99868de85c4a429b42d9f13bd0d2 libsmbclient-3.6.23-44.el6_9.i686.rpm 7010b7851ad11bf90b6c804f3ad163e148ebdce72e0ffa2707f5e47564398bc6 libsmbclient-devel-3.6.23-44.el6_9.i686.rpm e9c2f8f869542a0ad4aaacf1bb2ebd95ba1aeb2b9866ad204964b12f2d9a0915 samba-3.6.23-44.el6_9.i686.rpm 2e6d7682d23d823b2b791245497532f72fb07cc7f719eae622eb9542b60c8beb samba-client-3.6.23-44.el6_9.i686.rpm e61cd439e12710eb6af6a65bd0146716afed4be2f6da933ef36f54f584cbb146 samba-common-3.6.23-44.el6_9.i686.rpm 73eddc6e1b6d13601df165a93a60345057a8cf0442d172e51405533636db5795 samba-doc-3.6.23-44.el6_9.i686.rpm e8c2763e776470aa92d6fdfbf89fa24bceeaa4ea169967e343868765fcd570dd samba-domainjoin-gui-3.6.23-44.el6_9.i686.rpm 674c4f38741bb2c92a2fc99d7ec993fc65d787116b3e7b54bebbddf97dfa72a3 samba-swat-3.6.23-44.el6_9.i686.rpm 05fa3c1e498572c70a66c960330663843d127adfa2c8624e10e306e1f6c3862b samba-winbind-3.6.23-44.el6_9.i686.rpm b2bb5fa267c592a950d31987d493552f144894f66261ad7cb647a3ef78b544e4 samba-winbind-clients-3.6.23-44.el6_9.i686.rpm cc45242631859f54be41370195540ac2526d12b861dd338af94ee6329c01b50c samba-winbind-devel-3.6.23-44.el6_9.i686.rpm 17d40cdb7f23806604bd5808986bd5b4dfd883fb49aed3b3374e884cff4aec8c samba-winbind-krb5-locator-3.6.23-44.el6_9.i686.rpm x86_64: 87269f714a65dd129fca8497dd8b037337fb99868de85c4a429b42d9f13bd0d2 libsmbclient-3.6.23-44.el6_9.i686.rpm 9ba6b7253311bfed18bb3523849a92b31d755dfae228acaec53144079f491221 libsmbclient-3.6.23-44.el6_9.x86_64.rpm 7010b7851ad11bf90b6c804f3ad163e148ebdce72e0ffa2707f5e47564398bc6 libsmbclient-devel-3.6.23-44.el6_9.i686.rpm 77e46d8910bfceb778676cbba018cf2a40295321d592418202c5af269cb1b8cf libsmbclient-devel-3.6.23-44.el6_9.x86_64.rpm 21018e8fe062e1589d484cb208a6f90dc03e7e69c895af2e01a158879942a122 samba-3.6.23-44.el6_9.x86_64.rpm cd1277c4736080daf752f69651edab8aea20b49f1ed2dc93ab43558266f92c13 samba-client-3.6.23-44.el6_9.x86_64.rpm e61cd439e12710eb6af6a65bd0146716afed4be2f6da933ef36f54f584cbb146 samba-common-3.6.23-44.el6_9.i686.rpm 28c2dfe75c2b510abb31fd29c5f92878d878aab839ac7d7c3d77c286846d33cf samba-common-3.6.23-44.el6_9.x86_64.rpm 1bc5b16aa7f71146a4b523d3d1c0684287de5e1e9b539dff8b14b7573876d28a samba-doc-3.6.23-44.el6_9.x86_64.rpm 27189348fedd2b1be13f64f792c594ee1007f6c12dae96af4e47bfb33634f670 samba-domainjoin-gui-3.6.23-44.el6_9.x86_64.rpm e23a85368e28e90c1491aff86b9bffa0863ca7a30e9830c878f88432e68add28 samba-glusterfs-3.6.23-44.el6_9.x86_64.rpm f4755292e85ff60bb0b039b18fe193e69be40ad26d1b390629b95a48c48ca58b samba-swat-3.6.23-44.el6_9.x86_64.rpm 500229f658d887638590fb05c6bca7b43868f40cf7032538c92d211ac3aa5c5c samba-winbind-3.6.23-44.el6_9.x86_64.rpm b2bb5fa267c592a950d31987d493552f144894f66261ad7cb647a3ef78b544e4 samba-winbind-clients-3.6.23-44.el6_9.i686.rpm ff1deaa1f55f103d7f02d352cdc142bb5306bbb4ee821dcac95d45165431cfbb samba-winbind-clients-3.6.23-44.el6_9.x86_64.rpm cc45242631859f54be41370195540ac2526d12b861dd338af94ee6329c01b50c samba-winbind-devel-3.6.23-44.el6_9.i686.rpm 1488541aa150dd17c739144146acb975bd4f4565c1c9d424d6b02262d2e69d22 samba-winbind-devel-3.6.23-44.el6_9.x86_64.rpm ca71de881c47e6eb18d6742d698a38789d022e5b0624df21ed655dc8dd91aa36 samba-winbind-krb5-locator-3.6.23-44.el6_9.x86_64.rpm Source: 19c9c2264fc0813d95442abc9358c34387b4760204e1318487bb9919a1470756 samba-3.6.23-44.el6_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 6 Date: Wed, 23 Aug 2017 18:04:36 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2017:2500 CentOS 6 unbound Enhancement Update Message-ID: <20170823180436.GA14632(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2017:2500 Upstream details at : https://access.redhat.com/errata/RHEA-2017:2500 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 2fac524811e1dbf01a6cd6bd931d4628a5adba2d20d0cd97f0cb342ea064b8b3 unbound-1.4.20-23.el6_9.4.i686.rpm ed1ce6f7b787138dd29af1064ce5046fa6fa49c0849f6facf1cc683ec1c61cdb unbound-devel-1.4.20-23.el6_9.4.i686.rpm 929982cc3197d5bfa6b770bace24e395a14ec98ff4e4db3377da3a2c29db32cf unbound-libs-1.4.20-23.el6_9.4.i686.rpm 46e553a20ee09820c08415a89ad3a5be5c978c1794ca2419caf913737183dd02 unbound-python-1.4.20-23.el6_9.4.i686.rpm x86_64: b870310bbc3ed3d0386e25b3bf72be92d256032c2c272a5ac3e94d109fddb661 unbound-1.4.20-23.el6_9.4.x86_64.rpm ed1ce6f7b787138dd29af1064ce5046fa6fa49c0849f6facf1cc683ec1c61cdb unbound-devel-1.4.20-23.el6_9.4.i686.rpm cd93e772f13decfbcd5ee60ead21d04d7a734a22370b1c83e185f75ab2465d07 unbound-devel-1.4.20-23.el6_9.4.x86_64.rpm 929982cc3197d5bfa6b770bace24e395a14ec98ff4e4db3377da3a2c29db32cf unbound-libs-1.4.20-23.el6_9.4.i686.rpm b9991f293eddceba22b2cd66e15f451ddb4338fb3fcf1811f728fc640dcf4074 unbound-libs-1.4.20-23.el6_9.4.x86_64.rpm 46e553a20ee09820c08415a89ad3a5be5c978c1794ca2419caf913737183dd02 unbound-python-1.4.20-23.el6_9.4.i686.rpm 73f0e380f4a8e9e75439325e0ed9cb3371fecdbaaea6ae1fa6e4485f1f0d4797 unbound-python-1.4.20-23.el6_9.4.x86_64.rpm Source: 5e5a69b22ec6f36c6c3263d665855e11ee7c28cf339120ae15d16bcc45cf9eec unbound-1.4.20-23.el6_9.4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 7 Date: Wed, 23 Aug 2017 18:06:11 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2017:2505 CentOS 6 sssd BugFix Update Message-ID: <20170823180611.GA15460(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2017:2505 Upstream details at : https://access.redhat.com/errata/RHBA-2017:2505 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: a13401b5a68e93e194fa862f3502ad7c93976151e61df31543612279904316d4 libipa_hbac-1.13.3-57.el6_9.i686.rpm 7f12b9d12a0ea77382b0d3b776d77b04d5a2e4945ef022e33007074216de3dcb libipa_hbac-devel-1.13.3-57.el6_9.i686.rpm 5038172ca941498feae2da10afdd3c3196f2a7d9be0f1bac583fb38c085df10f libsss_idmap-1.13.3-57.el6_9.i686.rpm 5657074aafc12930b7c43e1221555cf76175052dfa5cf0b054d0ce6a0e27ce47 libsss_idmap-devel-1.13.3-57.el6_9.i686.rpm 701993ad8ce2dd85022d74a2ddc0c393b4f3675cd8635e5692f8bfd3214f0213 libsss_nss_idmap-1.13.3-57.el6_9.i686.rpm e33158734216b89323680ab4b23ed7ee51ca50ac9804cf34a1470fe04e50d1da libsss_nss_idmap-devel-1.13.3-57.el6_9.i686.rpm ad5ac6f7439d62997536b84755e20b7688913a3b4fd04afe622ba4f8c4fa8dd5 libsss_simpleifp-1.13.3-57.el6_9.i686.rpm 26a9d7d29a9c5bb89da20ac0774b8bb80cac735faddc44bd41e07baab8f0e1ed libsss_simpleifp-devel-1.13.3-57.el6_9.i686.rpm d5cc77c29545b83ff183425acd004c6149c0a60eacb0e811391d49c107602cd2 python-libipa_hbac-1.13.3-57.el6_9.i686.rpm e0c4ec8e31dd30b28079f628cab53e5f9940b067288c22c3f029e774829f09d4 python-libsss_nss_idmap-1.13.3-57.el6_9.i686.rpm 29f3a7938d5b30a99b6a8aee70499a1643a8a63dcca8c944b692947ece5c784e python-sss-1.13.3-57.el6_9.i686.rpm c7b8df5b47960010dcd0b9464e17f8df42205f739754816573d5c8d5f58a330d python-sssdconfig-1.13.3-57.el6_9.noarch.rpm d1d7f68a5b700a7599129c12f7c7aeae764536631cd988b211a9cf9521eaed2b python-sss-murmur-1.13.3-57.el6_9.i686.rpm d3b70d514a3e7a3c8b5ccb654718bd8ae829371ccf4dcb7f9d22a2a9b29bc45a sssd-1.13.3-57.el6_9.i686.rpm 2fe9180dc9ec9b552890a5ada4445e48353573e1b47b9db508125d5602a44383 sssd-ad-1.13.3-57.el6_9.i686.rpm 0e18519ce4ec99044ddfc9b2f16bbcba96057a078ebbd8c9544c06e351d36d66 sssd-client-1.13.3-57.el6_9.i686.rpm 532039b14de6f3b8fc11e516ea25810ed419acd28d4843bf842b9c219f1e82e5 sssd-common-1.13.3-57.el6_9.i686.rpm 9199a323b752c421afde17234ae1232a442ef4d49cb06033d8741995270d9ce4 sssd-common-pac-1.13.3-57.el6_9.i686.rpm c733c43f0a22930700bb0d46e4cd57293e9335f9bff49180edb43f4ec2c1c3ac sssd-dbus-1.13.3-57.el6_9.i686.rpm 6783419d96794196655edaa9171e8022cd052ef52062f494e712c741a358bb92 sssd-ipa-1.13.3-57.el6_9.i686.rpm 7bde1eb73e97da65079b7ea00f144b033ad7ad57b29d918db06913e2daea2ed7 sssd-krb5-1.13.3-57.el6_9.i686.rpm e1f422785b790cb6ff7278543799ab5518e6d3347c6d14688b0d13b30e52ddd2 sssd-krb5-common-1.13.3-57.el6_9.i686.rpm 4ed9ee3cf8b2bcd81bc638af7394b96686b9605949c2e2c0a42e20bee07759a5 sssd-ldap-1.13.3-57.el6_9.i686.rpm 8bcf5312b87932b4d7c2f6b8b45fe48faca924e90e1c244d81d410899d979c40 sssd-proxy-1.13.3-57.el6_9.i686.rpm 81bcb25b9f2ae1ed30456741db7df9a37c1a0405555614a7b5ae95a2bd44dd5e sssd-tools-1.13.3-57.el6_9.i686.rpm x86_64: a13401b5a68e93e194fa862f3502ad7c93976151e61df31543612279904316d4 libipa_hbac-1.13.3-57.el6_9.i686.rpm 9115fd0f410b9c54c12ef053717bc785c0a57c4e4c9142dd79215db39c7ef5b1 libipa_hbac-1.13.3-57.el6_9.x86_64.rpm 7f12b9d12a0ea77382b0d3b776d77b04d5a2e4945ef022e33007074216de3dcb libipa_hbac-devel-1.13.3-57.el6_9.i686.rpm cc15202f7287617ead9e33088307ca232d69205367bcfc48b629b4257be2bce2 libipa_hbac-devel-1.13.3-57.el6_9.x86_64.rpm 5038172ca941498feae2da10afdd3c3196f2a7d9be0f1bac583fb38c085df10f libsss_idmap-1.13.3-57.el6_9.i686.rpm 22509a00ea3a552a38a2fbe1fcd3d52aaf1fab61a88829529d0cdec4393991f9 libsss_idmap-1.13.3-57.el6_9.x86_64.rpm 5657074aafc12930b7c43e1221555cf76175052dfa5cf0b054d0ce6a0e27ce47 libsss_idmap-devel-1.13.3-57.el6_9.i686.rpm 8c5b2dbfe15941133e9dc6b9f04651f8fd6907a201a9321bc29a51f0a2ee06c6 libsss_idmap-devel-1.13.3-57.el6_9.x86_64.rpm 701993ad8ce2dd85022d74a2ddc0c393b4f3675cd8635e5692f8bfd3214f0213 libsss_nss_idmap-1.13.3-57.el6_9.i686.rpm a7077dc3b6b7a12044ee0b6788e182cb9a5ab48450c5127c7bb5ab62ce340ff4 libsss_nss_idmap-1.13.3-57.el6_9.x86_64.rpm e33158734216b89323680ab4b23ed7ee51ca50ac9804cf34a1470fe04e50d1da libsss_nss_idmap-devel-1.13.3-57.el6_9.i686.rpm 4d1a4f732ae27501bb013674f1b0b85028fc2d4a4ae061d1244db2bff8a477f5 libsss_nss_idmap-devel-1.13.3-57.el6_9.x86_64.rpm ad5ac6f7439d62997536b84755e20b7688913a3b4fd04afe622ba4f8c4fa8dd5 libsss_simpleifp-1.13.3-57.el6_9.i686.rpm 5629876de7fba52273539241f6cfbfb2c7ff1983fa02bc70eebb6bfa29a6b68d libsss_simpleifp-1.13.3-57.el6_9.x86_64.rpm 26a9d7d29a9c5bb89da20ac0774b8bb80cac735faddc44bd41e07baab8f0e1ed libsss_simpleifp-devel-1.13.3-57.el6_9.i686.rpm b1820d13dcd398ec17dcacc051ba6e81130fdca41e10b121968fbbbf5f5be456 libsss_simpleifp-devel-1.13.3-57.el6_9.x86_64.rpm 209f7352d918cb4adef50373529bdac4a5430e2379d7acd7a4724eb98bb13179 python-libipa_hbac-1.13.3-57.el6_9.x86_64.rpm 477897405d5762c897ce497069c6a7eac5b6c94a846956de9ca473049c18bc57 python-libsss_nss_idmap-1.13.3-57.el6_9.x86_64.rpm 2b95cc2a5bc3fbb2f64a25fc369a633701f61c28031f1583a81890ef6f234197 python-sss-1.13.3-57.el6_9.x86_64.rpm c7b8df5b47960010dcd0b9464e17f8df42205f739754816573d5c8d5f58a330d python-sssdconfig-1.13.3-57.el6_9.noarch.rpm 71c0760de386f0b713d147a11b0237801abfb3ce1db0befc729925e9149768d4 python-sss-murmur-1.13.3-57.el6_9.x86_64.rpm 1557f7ef5bb01a5b84a6a59a07e79add62c83545cd7b8f9d014e8a1fb699b3c3 sssd-1.13.3-57.el6_9.x86_64.rpm eba82b031016f13ea9721b946e084e918b2356f55da5b35be1cf011dc8760517 sssd-ad-1.13.3-57.el6_9.x86_64.rpm 0e18519ce4ec99044ddfc9b2f16bbcba96057a078ebbd8c9544c06e351d36d66 sssd-client-1.13.3-57.el6_9.i686.rpm 01f72a1a1e4bad08ff860a7fc7809d7a1c42e4f34cb4e774d8c6a81d618864d6 sssd-client-1.13.3-57.el6_9.x86_64.rpm d10d8155de1517c6bed677ee6dcfacd70b5bd9ff7d26c8fd832b7db6756e1c84 sssd-common-1.13.3-57.el6_9.x86_64.rpm b7aa3ad5384c6f917113f2ae28e15282bff563fcf533f7affbeb6a8af0582a2d sssd-common-pac-1.13.3-57.el6_9.x86_64.rpm 1ce45883ba5e42de2ba4b0f3d32ed518e0271065ca77cb4ab1e85af63e853d73 sssd-dbus-1.13.3-57.el6_9.x86_64.rpm c6016d578a734908687cb2a4e7c574b08bc8f77e197bf87ae7219b435b5b34e5 sssd-ipa-1.13.3-57.el6_9.x86_64.rpm 588fbde858c7d5f47e3f86dc0b54de543e01069338f6b313d9ea559e7281add3 sssd-krb5-1.13.3-57.el6_9.x86_64.rpm af20075ea6e142f484b4b6ffadc1f4480236835b162a0d708c65c75b869dc1ca sssd-krb5-common-1.13.3-57.el6_9.x86_64.rpm 70d654af09bd053d31546883d946bcb1c4a965006d344b48d84d47e0bce59b17 sssd-ldap-1.13.3-57.el6_9.x86_64.rpm 48928584868468445c42869789fadca83f09c62d2067727d4239504f08fd32ae sssd-proxy-1.13.3-57.el6_9.x86_64.rpm cfd0168886af56b426ad73a0085c4cc26a6450e067514049a7a5b5d6137db527 sssd-tools-1.13.3-57.el6_9.x86_64.rpm Source: 4d7f4a06ff19037727fce55eb84c8f8d8526abe2c6651c1ac809eeec21213b0b sssd-1.13.3-57.el6_9.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 150, Issue 3 ***********************************************

1 0

Centos and CVE-2017-1000117
by Herbert Chang 23 Aug '17

23 Aug '17

hi centos community, as many of you probably have been following along, a few days ago CVE 2017-1000117 <https://bugzilla.redhat.com/show_bug.cgi?id=1480386> was identified and redhat was prompt to release patches to fedora 25/26. I haven't seen any chatter thus far from CentOS, so was wondering if anyone knew the status of the patches landing in CentOS, and more specifically, for CentOS 6 and git 1.7.x that's currently latest in the repos. thanks! Herbert -- Herbert Chang clypd | engineer 781.540.1653 herbert(a)clypd.com <http://www.clypd.com/> Connect with us: Twitter <https://twitter.com/clypd> | LinkedIn <https://www.linkedin.com/company/clypd-inc-> | Facebook <https://www.facebook.com/clypd>

6 6

Installation on Knights Landing (KNL) machines failure
by Arif Ali 22 Aug '17

22 Aug '17

Hi all, We have a customer, where we are trying to install CentOS 7.3 on the new Intel Knights Landing nodes, unfortunately, we are unable to install then using PXE boot. Now, I have a lot of experience of installation of machines using PXE boot, so the setup of that is not the problem. Both myself and my colleagues have looked through the problem, and we are unable to get much diagnosis of the problem. When booting the machine via the network, it loads the ramdisk, and then we get no output, and then the machine reboots. Unfortunately, we have unable to get anything else on the screen. The machines don't have VGA, and monitor capable ports, so we are stuck with Serial Over Lan over IPMI. We have however, after some searching via search engines, we found some documentation suggesting that RHEL 7.2 and then with significant updates on 7.3 do work on these types of machines. We have then followed the same process to try installing the machines, and we have managed to get the machine up, and in a working order. However, we'd like to use CentOS 7.3, and would like to find the process of doing so, if it is any different I was wondering to see if anyone else has seen any similar issues, and if there is a problem here, that we haven't tackled? Any further debugging we can do? Any assistance on this would be much appreciated -- regards, Arif Ali

3 3

Where to start with making a CentOS-based distro
by Julian DeMille 22 Aug '17

22 Aug '17

I'm currently looking into making a distro based on CentOS; how would one do that? -- Julian DeMille CEO, demilleTech Flight Simulations, LLC. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

1 0

Problem with softwareraid
by Mr Typo 20 Aug '17

20 Aug '17

Hello all, i have already had a discussion on the software raid mailinglist and i want to switch to this one :) I am having a really strange problem with my md0 device running centos7. after a new start of my server the md0 was gone. now after trying to find the problem i detected the following: Booting any installed kernel gives me NO md0 device. (ls /dev/md* doesnt give anything). a 'cat /proc/partitions show me now /dev/sd[a-d]1 partition. partprobe and a mdadm assemble gives me "disk busy" [root@quad live]# cat mdstat Personalities : [raid6] [raid5] [raid4] [raid10] unused devices: <none> [root@quad ~]# partprobe device-mapper: remove ioctl on WDC_WD20EFRX-68AX9N0_WD-WMC301255087p1 failed: Device or resource busy Warning: parted was unable to re-read the partition table on /dev/mapper/WDC_WD20EFRX-68AX9N0_WD-WMC301255087 (Device or resource busy). This means Linux won't know anything about the modifications you made. .... .... [root@quad ~]# mdadm --assemble --force /dev/md0 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 mdadm: /dev/sda1 is busy - skipping mdadm: /dev/sdb1 is busy - skipping mdadm: /dev/sdc1 is busy - skipping mdadm: /dev/sdd1 is busy - skipping booting from a usb stick for rescue my centos everything works. the md0 device exists and is mounted. (rw). [root@quad usb-rescue]# cat mount | grep '/data' /dev/mapper/data-store on /mnt/sysimage/store type xfs (rw,noatime,seclabel,attr2,largeio,nobarrier,inode64,logbufs=8,logbsize=256k,sunit=256,swidth=768,noquota) /dev/mapper/data-tm on /mnt/sysimage/var/lib/vdr/video type xfs (rw,noatime,seclabel,attr2,largeio,nobarrier,inode64,logbufs=8,logbsize=256k,sunit=256,swidth=768,noquota) 3rd option: i am booting the installed rescue kernel from disk: i am getting a md0 device, but its not started. when i stop the md0 i cant assemble it anymore (disk busy) /dev/md0: Version : 1.2 Creation Time : Wed Aug 20 19:28:52 2014 Raid Level : raid5 Used Dev Size : 1953382272 (1862.89 GiB 2000.26 GB) Raid Devices : 4 Total Devices : 4 Persistence : Superblock is persistent Update Time : Thu Aug 17 22:38:14 2017 State : active, Not Started Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 128K Name : quad.core.sartori.at:0 (local to host quad.core.sartori.at) UUID : 9d020f27:c0542472:b95a18d2:5741114d Events : 25458 Number Major Minor RaidDevice State 0 8 1 0 active sync /dev/sda1 1 8 17 1 active sync /dev/sdb1 2 8 33 2 active sync /dev/sdc1 4 8 49 3 active sync /dev/sdd1 anyone got an idea, in which direction the problem could be? more logs needed? please help, i have no ideas anymore. regards Andy

3 6

Centos 7 Install
by Jerry Geis 20 Aug '17

20 Aug '17

I have a Centos 7 install that seems to be filling up disk space to 100% on the root partition. in /tmp I found files of names... systemd-private-XXXXXXXX-colord and rtkit I have never seen these files before. there were also files of XXXXXXXXXXXXX.tmp in the /tmp folder. Why are these files appearing? I have a number of installs and never came across this before. Thanks, Jerry

9 16

CentOS6, IP6tables, Routing, TPROXY (squid34 epel package)
by Walter H. 20 Aug '17

20 Aug '17

Hello, how do achieve this: how must files /etc/sysconfig/network-scripts/ look like to be the same as entering the following two commands ... ip -f inet6 rule add fwmark 1 lookup 100 ip -f inet6 route add local ::/0 dev lo table 100 is there the localhost device lo correct, or does it have to be br0? e.g. a file route-br0 with 192.168.1.0/24 via 10.10.10.1 dev br0 does the routing to the segment 192.168.1.0/24 via 10.10.10.1 /etc/sysconfig/ip6tables <BEGIN> *mangle :PREROUTING ACCEPT [0:0] :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :POSTROUTING ACCEPT [0:0] -N DIVERT -A DIVERT -j MARK --set-mark 1 -A DIVERT -j ACCEPT -A PREROUTING -i br0 -p tcp -m socket -j DIVERT -A PREROUTING -i br0 -p tcp -d 2a02:1788:2fd::b2ff:5302 --dport 80 -j TPROXY --tproxy-mark 0x1/0x1 --on-port 3129 COMMIT *filter :INPUT DROP [0:0] :FORWARD DROP [0:0] :OUTPUT DROP [0:0] -A INPUT -i br0 -m tcp -p tcp --dport 22 -m state --state NEW -j ACCEPT -A INPUT -i br0 -m tcp -p tcp --dport 80 -m state --state NEW -j ACCEPT -A INPUT -i br0 -m tcp -p tcp --dport 443 -m state --state NEW -j ACCEPT -A INPUT -i br0 -m tcp -p tcp --dport 3129 -m state --state NEW -j ACCEPT </END> the goal should be, that for specific IPv6 hosts (destination), the packets are redirected through the proxy running on the router box, other destinations should be just forwarded without proxy ... LAN port = br0 (dual stack), HE tunnel port = sit1 (ipv6 only), WAN port = eth1 (ipv4 only) Thanks, Walter

2 1

Problem with SNMP rpm
by Lucas Dutra 19 Aug '17

19 Aug '17

Hello everyone, Im trying to configure SNMP to use Kerberos authentication, but im having some trouble. The standard package of snmp dont have the kerberos module included, then i needed to create a new package. So i found the last centos snmp source rpm, version "net-snmp-5.7.2-24.el7_3.2.x86_64", and modified the .spec file to generate a new rpm with the kerberos module. But in the middle of compilation process, this happens: *checking for security modules to use... ksm usm* *checking for krb5-config... /bin/krb5-config* *checking for krb5... checking for krb5_init_context in -lkrb5... yes* *yes* *checking for heimdal... no* *checking to see which crypto API we need to use... checking for krb5_c_encrypt... yes* *(cached) old MIT crypto API* This "old MIT crypto API" dont happen if i use the same configuration with the standard snmp tar.gz And that is the problem, i need to receive "new MIT crypto API" to work. I have the Kerberos properly installed and running. Sorry if this looks confusing, but what im trying to say is that i guess this rpm is broken and need update. I used the same configuration with the rpm and the tar.gz . The tar.gz worked and the rpm didn't. This problem is for the ksm module, not the entire rpm is broken. Someone know who i cant contact to warn about this? Or if there is a new version out there. I searched for a new version but i didn't find anything. I used the 5.7.2 rpm and 5.7.3 tar.gz Thanks for the attention. Lucas.

1 0

CentOS 7 and Majordomo
by tslbai 19 Aug '17

19 Aug '17

Hi, i was running the latest ;-) Version of Majordomo (1.94.5) successful on CentOS 6.5 for years. Since i installed CentOS 7, majordomo isn't working any more (sendmail error). Is there anyone, who is running majordomo on CentOS 7 or has any hint? I know that Majordomo ist very old and greatcircle isn't supporting ist since years and the majordomo-Mailing-list ended 2003. I know about Mailman too, but i'd like to use majordomo as a small and tiny solution for a particular usecase. Thanks for any hint about running majordomo on CentOS 7. Bye, Florian

1 0

rsyslog stops logging on service reload?
by John Jasen 18 Aug '17

18 Aug '17

I have multiple servers running stock CentOS 7 rsyslog 7.4.7-16.el7, which are configured to log locally and over TCP to a remote logserver, also running stock CentOS 7 rsyslog. The remote server uses imptcp to receive, and pretty basic rules to parse and commit to disk. I have several systems that log prolifically, but periodically, they stop soon after the remote log server HUPs (daily logrotate). Very soon after they stop logging (completely, even to local files), the services on these systems block, and our monitoring system starts alerting. Restarting rsyslog on the clients proves ineffectual. The situation may clear itself without intervention after 90 minutes to several hours. However, this does not happen on all client systems in a similar situation (CentOS 7, large volume of constant log data); nor does it happen daily. Any ideas as to what's going on? Thanks in advance.

2 2

Power Fail Protection Update II
by Chris Olson 18 Aug '17

18 Aug '17

Many thanks once again to those that responded to my original posting (and my follow up message) with information about Network UPS Tools, other Linux-based tools like rtcwake, and commercial UPS products. We have quite a bit more evaluation and testing work to do before a power fail protection method is selected. I hope the discussion is as beneficial to others as it is to my organization. Along the way, one of our users pointed out that some of our CentOS 6 desktop/deskside machines actually throttle back power consumption in different ways than others. Instead of the yellow/amber LED display in the center of the power button, they flash green and then go solid green after the power button is pushed and the system wakes up. We have also noted that none of our CentOS 6 systems restart on their own when power is restored. This is the case whether power is lost during normal operation or when the systems are in a standby state when line power is lost. These two conditions or states (yellow/amber vs flashing green) have us wondering exactly what standby mode these systems are in and what settings may have been selected to send them to their standby state. Is there some sort of standard that applies to the standby states and are there BIOS settings or configuration files that control the what, how, and when standby is directed? Thanks to all and best regards.

1 0

fcitx-anthy request (for Japanese users)
by Scott Robbins 18 Aug '17

18 Aug '17

Apropos of the discussion this week with the person trying to get Chinese input going on CentOS, I filed a request for enhancement with Fedora's EPEL to add fcitx-anthy as a package. Currently, I'm able to get it working with the Fedora 20 rpm, but it would be nice to not have to search for it. It's been assigned (I'm not sure how meaningful that is, depending upon the assignee's free time), but anyone who would like to add their support to the request can view the bug at https://bugzilla.redhat.com/show_bug.cgi?id=1471924 -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

2 17

CentOS 7.x Russian certification
by Gorazd 18 Aug '17

18 Aug '17

Dear all, does anyone have any idea where to get a list of all CentOS 7.x versions that are certified to be used within Russia. My guess is that organizations, such as FSTEK, TR-CU declares those versions/distributions of CentOS that are certified to be used with commercial projects in Russia. Anyone with some information on this, plase advice, I would be very grateful. Regards, Gorazd

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss