Discuss January 2018

discuss@lists.centos.org

89 participants
72 discussions

Minor problem with yum-cron
by Bill Gee 18 Jan '18

18 Jan '18

Hello everyone - I have a minor problem with yum-cron. It has been doing this for a long time, and finally today I got annoyed enough to want to fix it. The problem: When yum-cron sends an email notification, the message is sent without a date field. Therefore it shows up in my inbox as "date: Unknown" and sorts to the opposite end of the list. The system is CentOS 7.4.1708 with all patches. Yum-cron is version 3.4.3-154. The email headers look like this: Return-Path: <root(a)campercaver.net> X-Original-To: bgee(a)campercaver.net Delivered-To: bgee(a)campercaver.net Received: from boinc01.billgee.local (unknown [192.168.17.131]) by campercaver.net (Postfix) with ESMTP id 94EA62C0C70 for <bgee(a)campercaver.net>; Thu, 18 Jan 2018 03:44:26 -0600 (CST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Yum: Updates installed on boinc01.billgee.local From: root(a)campercaver.net To: bgee(a)campercaver.net X-Spambayes-Classification: ham; 0.00 As you can see, there is no "Date:" field. I don't see anything in /etc/yum/yum-cron.conf that might affect this. I also see nothing in /etc/mail.rc,l though in this case it might not be using that file. The system does not have an smtp server on it. Yum-cron.conf specifies another server for smtp. It obviously works since I receive emails from it. Is this a bug in yum-cron? Am I missing something obvious? Thanks! -- Bill Gee

1 0

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

18 Jan '18

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2018:0093 Important CentOS 6 microcode_ctl Security Update (Johnny Hughes) 2. CESA-2018:0093 Important CentOS 7 microcode_ctl Security Update (Johnny Hughes) 3. CESA-2018:0094 Important CentOS 7 linux-firmware Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 17 Jan 2018 14:59:21 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:0093 Important CentOS 6 microcode_ctl Security Update Message-ID: <20180117145921.GA5351(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:0093 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:0093 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 54438c9b051c533a3b7c0eb4df3ee0b73f4bafcec4ea48428b2681e9a3aa3696 microcode_ctl-1.17-25.4.el6_9.i686.rpm x86_64: 5c2cc1670861c74c8ec14589d8cc9cb2b402ecb24fdb57a5472f4d213d727b37 microcode_ctl-1.17-25.4.el6_9.x86_64.rpm Source: 16e00d0102839f413217fd0616a7e5d204d9a9442495dccbed8e94e517096c41 microcode_ctl-1.17-25.4.el6_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Wed, 17 Jan 2018 16:50:17 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:0093 Important CentOS 7 microcode_ctl Security Update Message-ID: <20180117165017.GA16776(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:0093 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:0093 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 9ca51137ec96c3340b38bdbc8769d52b1640c38159b443e1228c681927ba1106 microcode_ctl-2.1-22.5.el7_4.x86_64.rpm Source: b7cb4af1f3498e147533df2523ebd1fe497ca9088cc26a207ecaf1b9d05a0a1e microcode_ctl-2.1-22.5.el7_4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Wed, 17 Jan 2018 16:51:32 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:0094 Important CentOS 7 linux-firmware Security Update Message-ID: <20180117165132.GA16930(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:0094 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:0094 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 477326f42dacde9755f0d662d0441e0f279225fbdb52c4f1557355bfe4ca0943 iwl1000-firmware-39.31.5.1-58.el7_4.noarch.rpm f4dcb45012ca1aaa758e9a31672d780270146a0070e0df6e0ed84b30824353f6 iwl100-firmware-39.31.5.1-58.el7_4.noarch.rpm 998665697fa54cbf485c3934e4bd17b69fbb7d62792480b9598a898407b8b6fd iwl105-firmware-18.168.6.1-58.el7_4.noarch.rpm 1cfe05c5f1fbd5d9d393a11b9c4fe90df4def61a240eaa38fc219a795b776b1d iwl135-firmware-18.168.6.1-58.el7_4.noarch.rpm ee01d9332220a7b91499180a83aae43abdfa14908f6f6139688bf017c609e68e iwl2000-firmware-18.168.6.1-58.el7_4.noarch.rpm 8429f035e10f57f4432929df9b218f597a368c84302cb5880d5e04fbc60395a4 iwl2030-firmware-18.168.6.1-58.el7_4.noarch.rpm 4c989c9c1f433055cfa94e4c0246209894d9c078ad0834455e110ed0e502b647 iwl3160-firmware-22.0.7.0-58.el7_4.noarch.rpm 8bc0c9de2f1f16da7cf7b0773809396e0f06147a3c199657fae4549c042358ec iwl3945-firmware-15.32.2.9-58.el7_4.noarch.rpm 52f1797d67c172b3326d152c0f0a7397b041c055fbf2e1878d596f685d8c35ee iwl4965-firmware-228.61.2.24-58.el7_4.noarch.rpm a314bbb5fb6d07d3a689dbb2896fc886847e0ad9527c7655da1718ac438b6656 iwl5000-firmware-8.83.5.1_1-58.el7_4.noarch.rpm eae7b5d69cecf1f6a047a41bbf1c56c0c41b3beedef594263e97734482f2dcb4 iwl5150-firmware-8.24.2.2-58.el7_4.noarch.rpm ba5a716bc1791e844990fc37f968fc040fd5456cdf95f7aff47cc7cf042dee00 iwl6000-firmware-9.221.4.1-58.el7_4.noarch.rpm 0b93b37d785647ca355adf71437b4d938b89aa7361bb6261937e670430ac93fb iwl6000g2a-firmware-17.168.5.3-58.el7_4.noarch.rpm 82dc7941f1865f2a3baeca035c017d1dea7f996840097e0feeb9203f9a579f4d iwl6000g2b-firmware-17.168.5.2-58.el7_4.noarch.rpm be1a9b0ea1d36fa539f9797ffaf150a1ce1137a4e79333514839f4741117c1b1 iwl6050-firmware-41.28.5.1-58.el7_4.noarch.rpm 4e456b537182b6418a6cabfd409cf755293443ee4e45b6f68c7ebb567b927644 iwl7260-firmware-22.0.7.0-58.el7_4.noarch.rpm ce6711788536b4dcb5cf85874ed4b86b9180f023ba3383b8dc5115434a751c69 iwl7265-firmware-22.0.7.0-58.el7_4.noarch.rpm 897d702e4f57affaee9afd069d8abe12cc1ae63d591bf535473af31ad1707c2d linux-firmware-20170606-58.gitc990aae.el7_4.noarch.rpm Source: 1d442fb1c99eb541aa36dd885a4963f0f2b7f16259275135d0d6f073324937d1 linux-firmware-20170606-58.gitc990aae.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 155, Issue 3 ***********************************************

1 0

sshfs mounting on Centos 6.9
by Miguel González 17 Jan '18

17 Jan '18

Hi all, I am trying to mount on boot a sshfs filesystem. I have tried this in /etc/fstab backup@myserver.com:/home/backup/myserver /backup fuse.sshfs nonempty,allow_other 0 2 but only works when network works. I have also tried this in my crontab: @reboot sshfs -o idmap=backup myserver.com:/home/backup/myserver /backup but doesn´t seem to work either. What else can I try? Thanks, Miguel --- This email has been checked for viruses by AVG. http://www.avg.com

2 1

Squid + wccp + firewalld
by Ranbir 16 Jan '18

16 Jan '18

Hi Everyone, I'm trying to get squid + wccp on a Centos 7 box working with a Cisco router. I've done this before several times using Centos 6 and iptables, but never on Centos 7 with firewalld. I've searched far and wide for clear, concise instructions on how to do what I want in Centos 7. I've pieced together what I've found to come up with what I thought should work. Unfortunately, squid simply refuses to respond. At the moment, it looks like squid isn't forwarding the requests it's receiving from the router over the GRE tunnel interface. The cisco router is showing the tunnel is up and active, which means wccp is working in that sense. I've edited sysctl.conf exactly as I would have on a Centos 6 box. Squid is configured like it would have been on a Centos 6 box, too. Here are the firewall rules: [root@s0989-stocac1 ~]# firewall-cmd --list-all public (active) target: default icmp-block-inversion: no interfaces: ens192 tun0 sources: services: ctc-custom dhcpv6-client ssh ports: 8081/tcp 3127/tcp 3128/tcp 8080/tcp protocols: masquerade: yes forward-ports: port=80:proto=tcp:toport=3127:toaddr=1.1.1.1 sourceports: icmp-blocks: rich rules: rule family="ipv4" source address="2.2.2.0/26" protocol value="gre" accept [root@s0989-stocac1 ~]# firewall-cmd --direct --get-all-rules ipv4 nat POSTROUTING 0 -j MASQUERADE ipv4 nat PREROUTING 0 -i tun0 -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 3127 Does anyone have any pointers/tips? I think I've messed up the firewalld rules somehow, but I'm not sure. Thanks in advance. -- Ranbir

1 0

Hello!
by Hideki Momokita. 16 Jan '18

16 Jan '18

To whom it may concern, Hello,I am Hideki Momokita,I joined last time. I work in IT Security at The MRC Foundation. I am Japanese. I was sending it from Osaka in Japan. Sorry,I am poor at English. Best regards, Hideki Momokita.

1 0

Re: [CentOS] lshw in centos 7 withdrawn
by david 15 Jan '18

15 Jan '18

John-- Thanks for the suggestion. I finally had a chance to get to the system in question, It was the only one of many that exhibited the USB hang. I tried a reboot with the two USB disks disconnected. Everything worked. I plugged them in, and then did both "lsusb -v" and "lshw", and again, everything worked. Continuing my test: Reboot with both drives plugged in: all worked. Power off, wait 1 minute for everything to quiet down, power on: all worked. So, I can't reproduce the problem. I guess I have to blame cosmic rays or those nasty gremlins that inhabit our IC's. :-) Or is it related to the annoying spin-down and spin-up delay of external USB disks. I have issues with the spin-up delay on other CentOS platforms, and have managed to find a kludge to avoid it most of the time. Windows 10 seems to handle the delay well. Thanks for your idea. At least it led me to "lsusb -v". David At 05:33 PM 1/11/2018, Stephen John Smoogen wrote: >On 11 January 2018 at 20:23, david <david(a)daku.org> wrote: > > Folks > > > > I've been running lshw for years in both Centos 6 and Centos 7, yet just > > recently it started hanging. Neither a Control^C nor a "kill" of the > > process cured the hang; only a reboot. > > > >Is this just one system or a range of boxes? I just ran it on 2 >different ones running CentOS 7 and it worked fine there. If it is >just one particular hardware then look through the lshw man page and >try the versions of something like > >lshw -disable usb > >to see if it still happens. [It might require other tests also.] > > > > When I run it by hand from the command line, it displays stuff on the next > > line overwriting it with things like PCI, USB. And USB is the last thing I > > see. A Control-C does not unlock it. > > > > I am running lshw-B.02.18-7.el7.x86_64. The CPU is an Intel I7-3770K, > > running CentOS 7.4.1708 > > > > Is there any idea? Is there some alternate program that could list the > > hardware? > > > > Thanks > > > > David > >

2 4

el7 systemd :: usage of AssertPathExists
by Adrian Sevcenco 15 Jan '18

15 Jan '18

Hi! I am trying to use AssertPathExists in a systemd unit but it seems it not working. Does anyone have problems with this? i have this in unit : AssertPathExists= AssertPathExists=/etc/mlsensor/mlsensor.properties but then when i start the service i get no errors : 26225 /usr/bin/java -Xms16m -Xmx32m -DMLSENSOR_HOME=/tmp -Djava.util.logging.config.class=lia.Monitor.monitor.LoggerConfigClass -Dlia.Monitor.ConfigURL=file:/etc/mlsensor/mlsensor.properties -jar /usr/share/java/mlsensor/MLSensor.jar i can't modify the java application, i am just doing an systemd unit for it... Anyone have any experience making systemd unit fail if the configuration file is not in place? Thank you! Adrian

2 2

CentOS Linux 7 (1708) AltArch i386 Kernel
by Johnny Hughes 13 Jan '18

13 Jan '18

Red Hat no longer maintains the i386 kernel for RHEL 7.4. We have been using a modified kernel until this latest meltdown / spectre release (*kernel-3.10.0-693.11.6.el7*). This latest release does not build on i386/i686 and we can't figure out how to make it work. Build try: https://buildlogs.centos.org/c7.1708.u.i386/kernel/20180109171431/3.10.0-69… SRPM: http://people.centos.org/hughesjr/kernel-3.10.0-693.11.6.el7.centos.plus.sr… In the mean time, people running the altarch i386 distribution can the latest i386 experimental kernel .. use the repo file from here (bottom of the page, 'CentOS-Experimental.repo' to '/etc/yum.repo.d/' ) to get it: https://wiki.centos.org/SpecialInterestGroup/AltArch/i386 We could use some community help in: 1. Making the 3.10.0-693.11.6.el7.centos.plus.i386 build. 2. Testing the 4.9.75.el7.centos.i686 kernel from the experimental repo on the i386 arch. Please post info on this thread in the mailing list. In the past the Springdale Linux distro has had i386 kernels as well, but they have not updated any since the 7.4 release (a couple behind us), so they haven't gotten it to build either. If we can not get a working backported kernel-3.10.0-693.11.6.el7, I'll push a newer 4.9.x LTS kernel from the experimental repo as an update to the i386 AltArch updates repository. Let's set a timeout of next Friday as the drop dead fix date for kernel-3.10.0-693.11.6.el7 .. if we can't get one to build, we'll push the latest LTS kernel from kernel.org it the i386 AltArch updates repo. Thanks, Johnny Hughes

3 3

update to Centos7.4: Failed to open \EFI\BOOT\grubx64.efi - Not Found
by johan.vermeulen7＠telenet.be 13 Jan '18

13 Jan '18

Hello All, updating from Centos7.3 to Centos7.4 rendered one of our laptops unbootable. EM: Failed to open \EFI\BOOT\grubx64.efi - Not Found Failed to load image \EFI\BOOT\grubx64.efi: Not Found start_image() returned Not Found How could this occur because of an update and how to fix this? What I tried is booting from centos usb, chroot to /mnt/sysimage and gave command: efibootmgr --create --label CentOS --disk /dev/sda1 --loader "\EFI\centos\shim.efi" This gave no EM, but booting remains impossible. I have to say I don't know whether to try grub2 of efibootmgr commands. Any help would be very much appreciated. Greetings, J.

3 3

FOSDEM Dojo update
by Rich Bowen 12 Jan '18

12 Jan '18

As you are no doubt aware, we are once again planning to hold a Dojo at the Marriott Grand Place on the Friday before FOSDEM starts - Friday, February 2, 2018. The schedule for the event may be found at https://wiki.centos.org/Events/Dojo/Brussels2018 and includes two tracks covering a wide variety of topics. Attendance at this event is free, but if you plan to attend please register - https://www.eventbrite.com/e/centos-dojo-at-fosdem-tickets-41309238043 - for planning and catering purposes. For those unable to attend, we will be recording (video) both tracks this year, and the sessions will be posted to YouTube as soon after the event as we can manage. See you in Brussels! -- Rich Bowen - rbowen(a)centosproject.org @RDOcommunity // @CentOSProject // @rbowen

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss January 2018