- Discuss - lists.centos.org

Stuck on Loading CentOS
by Dhanasekaran Balakrishnan 29 Aug '18

29 Aug '18

Hello, I am currently using CentOS 7 and for the last two days GUI is not working in my computer and the operating system is not starting. Black Screen lists something like in Red Color [ ] Started show Plymouth Boot screen [ ] Reached target Paths [ ] Reached target Basic System . . . . . . [ ] Stopped Apply Kernel Variables [ ] Stopping Apply Kernel Variables [ ] Stopping udev Kernel Device Manager Please do let me know the way for starting the device properly. Thank you. Kind Regards, Dhana

2 1

OpenLDAP support in future versions of CentOS
by Alicia Smith 29 Aug '18

29 Aug '18

Hello! I just joined this mailing list, so I apologize in advance if this topic has already been covered. Red Hat and Suse announced they are no longer supporting OpenLDAP in future releases. https://www.ostechnix.com/redhat-and-suse-announced-to- withdraw-support-for-openldap/ However, we mainly use CentOS and while it's a RH derivative, I wanted to find out what CentOS plans on doing in this regard. Will you continue to include OpenLDAP or will it simply be removed? I wasn't able to find any CentOS related articles in response to this, and the only thing I did find that said CentOS hasn't released whether they will continue to support it or not is from two years ago? https://daasi.de/en/2017/09/25/red-hat-wont-continue-openldap-support-rhel-… Any updates/feedback/information is appreciated :) Thank you! -- Alicia Smith @phrozyn Information Security Engineer asmith(a)mozilla.com

8 8

Where are my /tmp and /var/tmp files?
by Kenneth Porter 28 Aug '18

28 Aug '18

I was pulling my hair out this morning trying to figure out why my PHP web script could see files in /var/tmp/scriptname but I couldn't see them with ls or my text editor. I was certain I'd gotten rootkitted. Then I thought maybe it was a new chroot in the latest Apache config. It turns out it's systemd's unit file for Apache, which containerizes /tmp and /var/tmp for selected apps. The httpd.service unit file includes the PrivateTmp setting. Here's some details for anyone else confused by this: https://access.redhat.com/blogs/766093/posts/1976243

1 0

Very odd: /proc/sys/net/ipv6/conf/all/disable_ipv6
by mark 27 Aug '18

27 Aug '18

CentOS 7.5, and on one system, I'm getting: setroubleshoot: SELinux is preventing /usr/sbin/sendmail.sendmail from read access on the file disable_ipv6 ll -Z shows -rw-r--r--. root root system_u:object_r:sysctl_net_t:s0 /proc/sys/net/ipv6/conf/all/disable_ipv6 I find this peculiar. Anyone have a resolution, or is this a bug? mark

1 0

Re: [CentOS] Mail has quit working
by TE Dukes 27 Aug '18

27 Aug '18

Third time trying respond! -------- Original Message -------- Subject: Re: [CentOS] Mail has quit working From: Gordon Messmer < <mailto:gordon.messmer@gmail.com> gordon.messmer(a)gmail.com> Date: Tue, July 24, 2018 10:31 am To: <mailto:centos@centos.org> centos(a)centos.org On 07/23/2018 03:39 PM, TE Dukes wrote: > Mail has come to an abrupt stop. Running C7, postfix and dovecot. > ... > Crond is no longer send mail. In one terminal: "tail -f /var/log/maillog" or "journalctl -f" In another, "echo test | mail -s test your(a)email.address" What do you see in the maillog at that time? What does the "df" command output? _______________________________________________ CentOS mailing list <mailto:CentOS@centos.org> CentOS(a)centos.org <https://lists.centos.org/mailman/listinfo/centos> https://lists.centos.org/mailman/listinfo/centos Thanks, Output from tail: Jul 24 10:05:02 ts130 clamd[3226]: SelfCheck: Database status OK. Jul 24 10:15:02 ts130 clamd[3226]: SelfCheck: Database status OK. Jul 24 10:25:02 ts130 clamd[3226]: SelfCheck: Database status OK. Jul 24 10:35:02 ts130 clamd[3226]: SelfCheck: Database status OK. Jul 24 10:35:59 ts130 postfix/qmgr[8283]: C33128410546: from=< <mailto:root@ts130.palmettodomains.com> root(a)ts130.palmettodomains.com>, size=949, nrcpt=1 (queue active) Jul 24 10:36:29 ts130 postfix/smtp[19763]: connect to <http://paalmettodomains.com> paalmettodomains.com[198.105.254.65]:25: Connection timed out Jul 24 10:36:59 ts130 postfix/smtp[19763]: connect to <http://paalmettodomains.com> paalmettodomains.com[104.239.198.84]:25: Connection timed out Jul 24 10:36:59 ts130 postfix/smtp[19763]: C33128410546: to=< <mailto:tdukes@paalmettodomains.com> tdukes(a)paalmettodomains.com>, relay=none, delay=13075, delays=13015/0.02/60/0, dsn=4.4.1, status=deferred (connect to <http://paalmettodomains.com> paalmettodomains.com[104.239.198.84]:25: Connection timed out) Jul 24 10:45:02 ts130 clamd[3226]: SelfCheck: Database status OK. Jul 24 10:55:02 ts130 clamd[3226]: SelfCheck: Database status OK. Jul 24 11:04:19 ts130 postfix/pickup[19912]: 55271840D734: uid=0 from=<root> Jul 24 11:04:19 ts130 postfix/cleanup[21840]: 55271840D734: message-id=< <mailto:20180724150419.55271840D734@ts130.palmettodomains.com> 20180724150419.55271840D734(a)ts130.palmettodomains.com> Jul 24 11:04:19 ts130 postfix/qmgr[8283]: 55271840D734: from=< <mailto:root@ts130.palmettodomains.com> root(a)ts130.palmettodomains.com>, size=466, nrcpt=1 (queue active) Jul 24 11:04:20 ts130 postfix/smtpd[21846]: connect from localhost[127.0.0.1] Jul 24 11:04:20 ts130 postfix/smtpd[21846]: 49161841ED92: client=localhost[127.0.0.1] Jul 24 11:04:20 ts130 postfix/cleanup[21840]: 49161841ED92: message-id=< <mailto:20180724150419.55271840D734@ts130.palmettodomains.com> 20180724150419.55271840D734(a)ts130.palmettodomains.com> Jul 24 11:04:20 ts130 postfix/qmgr[8283]: 49161841ED92: from=< <mailto:root@ts130.palmettodomains.com> root(a)ts130.palmettodomains.com>, size=951, nrcpt=1 (queue active) Jul 24 11:04:20 ts130 postfix/smtpd[21846]: disconnect from localhost[127.0.0.1] Jul 24 11:04:20 ts130 amavis[423]: (00423-03) Passed CLEAN {RelayedInbound}, [127.0.0.1] < <mailto:root@ts130.palmettodomains.com> root(a)ts130.palmettodomains.com> -> < <mailto:tdukes@palmettodomains.com> tdukes(a)palmettodomains.com>, Message-ID: < <mailto:20180724150419.55271840D734@ts130.palmettodomains.com> 20180724150419.55271840D734(a)ts130.palmettodomains.com>, mail_id: eYD2cL7fZ7rY, Hits: -0.001, size: 466, queued_as: 49161841ED92, 941 ms Jul 24 11:04:20 ts130 postfix/smtp[21842]: 55271840D734: to=< <mailto:tdukes@palmettodomains.com> tdukes(a)palmettodomains.com>, relay=127.0.0.1[127.0.0.1]:10024, delay=1, delays=0.07/0.01/0/0.94, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 49161841ED92) Jul 24 11:04:20 ts130 postfix/qmgr[8283]: 55271840D734: removed Jul 24 11:04:20 ts130 dovecot: lda(tdukes): msgid=< <mailto:20180724150419.55271840D734@ts130.palmettodomains.com> 20180724150419.55271840D734(a)ts130.palmettodomains.com>: saved mail to INBOX Jul 24 11:04:20 ts130 postfix/local[21847]: 49161841ED92: to=< <mailto:tdukes@palmettodomains.com> tdukes(a)palmettodomains.com>, relay=local, delay=0.09, delays=0.02/0.01/0/0.06, dsn=2.0.0, status=sent (delivered to command: /usr/libexec/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT") Jul 24 11:04:20 ts130 postfix/qmgr[8283]: 49161841ED92: removed >From df: Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/cl-root 97605056 12762640 84842416 14% / devtmpfs 8025676 0 8025676 0% /dev tmpfs 8043100 70176 7972924 1% /dev/shm tmpfs 8043100 59284 7983816 1% /run tmpfs 8043100 0 8043100 0% /sys/fs/cgroup tmpfs 262144 0 262144 0% /var/spool/MailScanner/incoming /dev/mapper/cl-home 97605056 34632 97570424 1% /home /dev/sda2 993004 391180 601824 40% /boot /dev/mapper/cl-data 3685467928 1205578432 2479889496 33% /data /dev/sdb1 3845548044 2677536044 972662756 74% /media tmpfs 1608620 56 1608564 1% /run/user/0

12 70

kernel-plus (plus 1?)
by lejeczek 24 Aug '18

24 Aug '18

hi guys did you notice, if you use kernel-plus on 7.5 this CentOS Linux (3.10.0-862.11.6.el7.centos.plus.1.x86_64) 7 (Core) CentOS Linux (3.10.0-862.11.6.el7.centos.plus.x86_64) 7 (Core) is that "plus.1" a new naming convention or just one off? regards, L

2 3

using lpadmin to add printers in CentOS 7 (v. CentOS 6)
by Zube 24 Aug '18

24 Aug '18

In CentOS 6, I could do: lpinfo -m then pick the model I want and put it as the option to -m in lpadmin (line wrapped): /usr/sbin/lpadmin -p printer -o printer-is-shared=false -o Duplex=None -o Resolution=600dpi -m 'gutenprint.5.2://pcl-g_5e/expert Generic PCL 5e Printer - CUPS+Gutenprint v5.2.5' -v 'socket://mydomain.edu' Alas, in CentOS 7, no matter what I do, I always get: Unable to copy PPD file! and the error in the cups error log: Returning IPP server-error-internal-error for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/printer) from localhost Bad ppd-name "gutenprint.5.2://pcl-g_5e/simple Generic PCL 5e Printer - CUPS+Gutenprint v5.2.9 Simplified" (-6)! copy_model: empty PPD file I assumed this was due to the newer version of cups. To make it work (kinda, sorta) the way it used to: 1) mkdir -p /usr/share/cups/model/gutenprint/5.2 2) cups-genppd.5.2 3) lpinfo -m, but choose one that is a file, not a gutenprint.5.2:// URL (?): /usr/sbin/lpadmin -p printer -o printer-is-shared=false -o Duplex=None -o Resolution=600dpi -m 'gutenprint/5.2/stp-hp-lj_4250.5.2.ppd.gz' -v 'socket://mydomain.edu' And this is fine, but I assume the other way should work as well. What am I missing? Thanks for any clues. Cheers, Zube

1 0

selinux question
by Nataraj 24 Aug '18

24 Aug '18

I have a web application which uses sudo to invoke python scripts as the user under which the application runs (NO root access). Is there any reason why sudo would would require sys_ptrace access for this? I only get this violation intermittenly, and not with every call to sudo. Here's the violation: Summary: SELinux is preventing sudo (httpd_t) "sys_ptrace" to <Unknown> (httpd_t). Detailed Description: SELinux denied access requested by sudo. It is not expected that this access is required by sudo and this access may signal an intrusion attempt. It is also possible that the specific version or configuration of the application is causing it to require additional access. Allowing Access: You can generate a local policy module to allow this access - see FAQ (http://fedora.redhat.com/docs/selinux-faq-fc5/#id2961385) Or you can disable SELinux protection altogether. Disabling SELinux protection is not recommended. Please file a bug report (http://bugzilla.redhat.com/bugzilla/enter_bug.cgi) against this package. Additional Information: Source Context system_u:system_r:httpd_t Target Context system_u:system_r:httpd_t Target Objects None [ capability ] Source sudo Source Path /usr/bin/sudo Port <Unknown> Host myhost.mydomain.com Source RPM Packages sudo-1.7.2p1-29.el5_10 Target RPM Packages Policy RPM selinux-policy-2.4.6-351.el5 Selinux Enabled True Policy Type targeted MLS Enabled True Enforcing Mode Enforcing Plugin Name catchall Host Name myhost.mydomain.com Platform Linux myhost.mydomain.com 2.6.18-419.el5 #1 SMP Fri Feb 24 22:06:09 UTC 2017 i686 i686 Alert Count 359 First Seen Tue Oct 8 09:24:50 2013 Last Seen Tue Aug 21 10:26:26 2018 Local ID 717eb9a4-cc7f-4ed1-b638-5db1a841abe4 Line Numbers Raw Audit Messages host=myhost.mydomain.com type=AVC msg=audit(1534872386.726:9642): avc: denied { sys_ptrace } for pid=8458 comm="sudo" capability=19 scontext=system_u:system_r:httpd_t:s0 tcontext=system_u:system_r:httpd_t:s0 tclass=capability host=myhost.mydomain.com type=SYSCALL msg=audit(1534872386.726:9642): arch=40000003 syscall=3 success=yes exit=166 a0=1a a1=b7ff4000 a2=400 a3=89cabf0 items=0 ppid=8979 pid=8458 auid=4294967295 uid=48 gid=48 euid=0 suid=0 fsuid=0 egid=48 sgid=48 fsgid=48 tty=(none) ses=4294967295 comm="sudo" exe="/usr/bin/sudo" subj=system_u:system_r:httpd_t:s0 key=(null) Thank You, Nataraj

4 7

How do I actaully get the current sources from centos-git?
by me＠tdiehl.org 21 Aug '18

21 Aug '18

Hi, I am trying to retrieve the srpm for the latest centos-release pacakge from centos-git by following the instructions @ https://wiki.centos.org/Sources. If I run the following commands: git clone https://git.centos.org/git/rpms/centos-release.git cd centos-release/ git checkout c7 ~/centos-git-common/get_sources.sh Everything completes without error. The problem is that the sources that get downloaded are not for 1804. (vgeppetto2 pts21) $ ll SOURCES/ SPECS/ SOURCES/: total 28 -rw-rw-r--. 1 mock mock 1584 Aug 6 08:19 1000-centos-release-cr.patch -rw-rw-r--. 1 mock mock 264 Aug 6 08:19 85-display-manager.preset -rw-rw-r--. 1 mock mock 2439 Aug 6 08:19 90-default.preset -rw-rw-r--. 1 mock mock 12799 Aug 6 08:20 centos-release-7-1.1503.tar.gz SPECS/: total 8 -rw-rw-r--. 1 mock mock 6471 Aug 6 08:19 centos-release.spec (vgeppetto2 pts21) $grep "define upstream_rel" SPECS/centos-release.spec %define upstream_rel 7.3 (vgeppetto2 pts21) $ So if I am reading things correctly, it looks like the SOURCES are for 1503 and the spec file is for 1611. Can someone please explain to me how to actually get the current SOURCES and SPEC for centos-release-7-5.1804.1 from centos git? To be clear I know I can get the srpm from vault but I would like to understand how to work centos git. Regards, -- Tom me(a)tdiehl.org

3 4

sssd logs
by Ian Diddams 21 Aug '18

21 Aug '18

We have sssd running on a centos 7 box... its logs of course (?!) go into /can't find any info on where this log directory is configured, or whether it is changeable. Anybody know differently? Cheers ian Disclaimer: This message is intended for the addressee only. It may contain information of a confidential or legally privileged nature. If you have received this message in error please notify the sender and destroy the message immediately. All attachments have been scanned for viruses. However D4t4 Solutions Plc cannot accept liability for any loss or damage you may incur as a result of virus infection.

2 1

Packaging a library for 64-bit or multilib
by Kenneth Porter 21 Aug '18

21 Aug '18

How does "make install" with autotools decide which directory libraries should go in? I haven't packaged anything since 32-bit (ie. a few years ago), and I now need to re-package a new version of a library I'd used before with CentOS 6 32-bit on CentOS 7 64-bit. The library is pxlib (http://pxlib.sourceforge.net/) which reads and writes old Borland Paradox database files. I've managed to fix 64-bit issues in the C sources. When I go to package the RPM, it runs configure and make and "make DESTDIR=${RPM_BUILD_ROOT} install". The install step puts the resulting libraries in /usr/lib, not /usr/lib64 where the %files step looks. I'm not familiar with autotools, so I don't know where to look to fix the install step to put the libraries in the correct directory. How does make/configure or whatever figure that out? Do I need to change the %prep step to run autotools to write the correct library directory for configure, or does configure need to be hacked to write the correct directory into the Makefiles? Maybe configure needs to be regenerated with a more recent autotools?

1 1

Using InstallAnywhere with CentOS? ... anyone
by KM 21 Aug '18

21 Aug '18

Hi All,I was wondering if anyone else uses InstallAnywhere to create a multi-platform installer for their products. My company does. However we have an official build server that is running CentOS, obviously because it is opensource and easy to update etc. However after we converted our build from an old RedHat 5 server to CentOS and were using InstallAnywhere we found out that it is not officially supported on CentOS but is officially supported on RedHat. This doesn't really make any sense to me since they are the same (or virtually the same). I guess it has to do with the amount of time a company wants to spend testing products on different platforms. All this being said, the main reason for this email is to encourage anyone using InstallAnywhere on CentOS for the designer and build functionality, to request that Flexera support CentOS officially. I only want this in case we have specific issues that arise due to the platform. Although it is true the RedHat users will most likely see the same results, it would be beneficial to have official support. Note that CentOS is support as a runtime or production execution platform. I am speaking mainly of the build and design functionality. Please also note that Flexera has not refused to help me with any of my issues so far. They have been great, but these issues are not OS related, they had to do with the use of their product. Thanks in advance for any help that you may give.KM

1 0

Unknown Error
by Eugene Poole 21 Aug '18

21 Aug '18

I've a HP 8000 Elite SFF machine with Intel Core 2 Duo Quad and 16 GB RAM. I wanted to create a LAB environment to try new things (like CentOS 7). I installed CentOS 6.10 64-bit with no problems and everything is running fine. I then went to Server World and followed the instructions to install Desktop and Virtualization. The install went fine but I had errors when I attempted to build my KVM virtual machines. I looked at dmesg and found a message stating that virtualization was turned off in the BIOS so I turned if on based on the output of lscpu: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 23 Model name: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz Stepping: 10 CPU MHz: 1998.000 BogoMIPS: 5652.96 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 6144K NUMA node0 CPU(s): 0-3 There were 2 parameters in the BIOS, VT-x and VT-x with Direct I/O. And as I was told, I powered the machine off. After restarting the machine I went to the instructions to build a virtual machine and that is where I've run into a problem I can't seem to solve. Using virt-manager and entering all of the requested parameters I clicked on the Finish button and immediately I get the Caps Lock and Scroll Lock keyboard lights blinking without stoping and everything locked up. Only the power button seems to work. Any ideas where I can possibly find the issue with this? -- Eugene Poole Woodstock, Georgia

1 0

Missing dependency
by Александр Кириллов 20 Aug '18

20 Aug '18

Hi. Can't install rh-ror42 on C6. Used to be working June 10th. Any ideas? TIA. # yum install rh-ror42 ... Resolving Dependencies --> Running transaction check ---> Package rh-ror42.x86_64 0:2.2-7.el6 will be installed ... --> Finished Dependency Resolution Error: Package: rh-ror42-2.2-7.el6.x86_64 (centos-sclo-rh) Requires: rh-nodejs4-nodejs You could try using --skip-broken to work around the problem ... # yum list rh-nodejs4-nodejs ... Error: No matching Packages to list # cat /etc/centos-release CentOS release 6.9 (Final)

1 1

GNOME lockscreen freeze on notification
by Nicolas Kovacs 18 Aug '18

18 Aug '18

Hi, I just installed CentOS 7 with GNOME on my new Dell Latitude E6230 laptop. So far, everything runs nicely. I just have one problem with the GNOME lockscreen. I launched the OwnCloud client and started to synchronize about 20 GB of data from my OwnCloud server. During the sync, I left the laptop unattended. After about 15 minutes, the desktop was replaced by the lockscreen, as it should. As soon as the OwnCloud sync was finished, there was a corresponding notification that displayed on the lockscreen. Usually I hit [Enter] to exit the lockscreen by providing my user password. Only this time nothing happened. The lockscreen seemed to have frozen with the notification in the center. To exit it, I had to hard reset my laptop. Anyone knows what could be the problem here? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

2 1

Re: [CentOS] CentOS Digest, Vol 163, Issue 13
by Ste Films- radio stream 17 Aug '18

17 Aug '18

oh sorry On Tue, Aug 14, 2018 at 7:00 AM, <centos-request(a)centos.org> wrote: > Send CentOS mailing list submissions to > centos(a)centos.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.centos.org/mailman/listinfo/centos > or, via email, send a message with subject or body 'help' to > centos-request(a)centos.org > > You can reach the person managing the list at > centos-owner(a)centos.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of CentOS digest..." > > > Today's Topics: > > 1. grub2 - add NVME to boot from - how? (lejeczek) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 14 Aug 2018 12:30:11 +0100 > From: lejeczek <peljasz(a)yahoo.co.uk> > To: CentOS mailing list <centos(a)centos.org> > Subject: [CentOS] grub2 - add NVME to boot from - how? > Message-ID: <a6ed224a-f80f-690d-5d86-f182ea5ba3ec(a)yahoo.co.uk> > Content-Type: text/plain; charset=utf-8; format=flowed > > hi guys, > > I thought I should ask before I start fiddling and break something - can > we tell grub2 to add nvme device as an option to boot from? > > And if yes then what do tell grub? > > many thanks, L. > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos > > > ------------------------------ > > End of CentOS Digest, Vol 163, Issue 13 > *************************************** >

1 0

CentOS-announce Digest, Vol 162, Issue 3
by centos-announce-request＠centos.org 16 Aug '18

16 Aug '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. CEBA-2018:2407 CentOS 6 389-ds-base BugFix Update (Johnny Hughes) 2. CEBA-2018:2406 CentOS 6 sos BugFix Update (Johnny Hughes) 3. Release for CentOS Linux 7 (1804) on POWER9 (ppc64le) (James O'Connor) ---------------------------------------------------------------------- Message: 1 Date: Wed, 15 Aug 2018 13:26:03 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2018:2407 CentOS 6 389-ds-base BugFix Update Message-ID: <20180815132603.GA40006(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2018:2407 Upstream details at : https://access.redhat.com/errata/RHBA-2018:2407 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: ae6efff96d69387264ef7f03b143c1719408036ed4da97436a7e639d0d11de7f 389-ds-base-1.2.11.15-97.el6_10.i686.rpm 562a895d4e0ee963ac0bfc8789e16a85a73a881cfc4305d444780b7dfa97e7a9 389-ds-base-devel-1.2.11.15-97.el6_10.i686.rpm d6d6925bc704747f207d592bcc2fef9acfcde8bf4b0669fc3c1b23599f43dbfa 389-ds-base-libs-1.2.11.15-97.el6_10.i686.rpm x86_64: 226125bf9c549430a6af2638c01fb797e4b2b26a8042725e28ba58e8a4317b3f 389-ds-base-1.2.11.15-97.el6_10.x86_64.rpm 562a895d4e0ee963ac0bfc8789e16a85a73a881cfc4305d444780b7dfa97e7a9 389-ds-base-devel-1.2.11.15-97.el6_10.i686.rpm 79a22fd167036159325d2fc44ba914ede2f12c1c163ee0e4f8f2f74dc0f6041b 389-ds-base-devel-1.2.11.15-97.el6_10.x86_64.rpm d6d6925bc704747f207d592bcc2fef9acfcde8bf4b0669fc3c1b23599f43dbfa 389-ds-base-libs-1.2.11.15-97.el6_10.i686.rpm 5423d51cfba1fa170c6f4c7b36ece4e51bb5ef1a26d5d0e20ec78b513825535f 389-ds-base-libs-1.2.11.15-97.el6_10.x86_64.rpm Source: 2dd39848c8d5b3dbf5efed94355f7a7cd230d7d22d36d3d0680b5dffd75c32ae 389-ds-base-1.2.11.15-97.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Wed, 15 Aug 2018 13:26:13 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2018:2406 CentOS 6 sos BugFix Update Message-ID: <20180815132613.GA40116(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2018:2406 Upstream details at : https://access.redhat.com/errata/RHBA-2018:2406 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 751a8137d6e283f8e83f9df970059a3b1b6691e092cb550dda709ae3b65b6e23 sos-3.2-63.el6.centos.2.noarch.rpm x86_64: 751a8137d6e283f8e83f9df970059a3b1b6691e092cb550dda709ae3b65b6e23 sos-3.2-63.el6.centos.2.noarch.rpm Source: 6c76c3ac69a92aada4b23cdf8a8ce64727efdc60b88baf25e5f787e2be09c3df sos-3.2-63.el6.centos.2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Wed, 15 Aug 2018 13:26:57 -0500 From: "James O'Connor" <jpoc(a)linux.vnet.ibm.com> To: centos-announce(a)centos.org Subject: [CentOS-announce] Release for CentOS Linux 7 (1804) on POWER9 (ppc64le) Message-ID: <8E062BA8-47A0-4243-B527-4FFCABF6E1D6(a)linux.vnet.ibm.com> Content-Type: text/plain; charset=utf-8 I am pleased to announce the general availability of CentOS Linux 7 (1804) for POWER9 processors (ppc64le - powerpc 64-bit little endian). This release is derived from Red Hat Enterprise Linux 7.5 ALT. Note this release is 99% equivalent to the existing CentOS 7 Linux 7 (1804) for POWER8 processors (ppc64le - powerpc 64-bit little endian). The key difference being that kernel-4.14.0 is used for POWER9 enablement and kernel-3.10.0 is used for POWER8 enablement. You will find the CentOS 7 (1804) Power9 installation images here: http://mirror.centos.org/altarch/7.5.1804/isos/power9/ sha256sum power9: 753c5b55c9ff681c925ec7d7c5295890284f40ec981f4da35b1f36f1ecbad95a CentOS-7-Power9-Everything-1804.iso 58d9af172656db71947b5db2d0d1f577217bbc1a86eada7ca3ce7bfcf7d7d9b4 CentOS-7-Power9-NetInstall-1804.iso CentOS 7 (1804) Power9 repositories: http://mirror.centos.org/altarch/7.5.1804/os/power9/ http://mirror.centos.org/altarch/7.5.1804/updates/power9/ http://mirror.centos.org/altarch/7.5.1804/extras/power9/ A special thank you to Johnny Hughes and Pablo Greco for their assistance making this release possible. -James O?Connor ------------------------------ 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 162, Issue 3 ***********************************************

1 0

Old kernel bug back in CentOS 6.10?
by Matthias Bethke 16 Aug '18

16 Aug '18

I updated a few hypervisors and their VMs to CentOS 6.10 on Monday; today I awoke to an alert saying all VMs are down. It looks like a very old bug crept back in. The machine is a ProLiant DL380 G7 with Xeon X5675 and 96 GB, running half a dozen smallish VMs. Hypervisor and all VMs have kernel 2.6.32-754.2.1.el6.x86_64. Around the time the VMs must have gone down, there are quite a few error messages like the following in the system log: Aug 16 03:10:13 hyper-7 kernel: [265397.382552] vmwrite error: reg 6000 value fffffffffffffff7 (err -9) Aug 16 03:10:13 hyper-7 kernel: [265397.421372] Pid: 9375, comm: qemu-kvm Not tainted 2.6.32-754.2.1.el6.x86_64 #1 Aug 16 03:10:13 hyper-7 kernel: [265397.464985] Call Trace: Aug 16 03:10:13 hyper-7 kernel: [265397.481530] [<ffffffffa0532a9c>] ? vmwrite_error+0x2c/0x30 [kvm_intel] Aug 16 03:10:13 hyper-7 kernel: [265397.520737] [<ffffffffa0532ac0>] ? vmcs_writel+0x20/0x30 [kvm_intel] Aug 16 03:10:13 hyper-7 kernel: [265397.560028] [<ffffffffa0535e63>] ? vmx_fpu_activate+0x93/0xc0 [kvm_intel] Aug 16 03:10:14 hyper-7 kernel: [265397.600072] [<ffffffffa04cd1e7>] ? kvm_arch_vcpu_create+0x37/0x50 [kvm] Aug 16 03:10:14 hyper-7 kernel: [265397.638183] [<ffffffffa04c72a1>] ? kvm_vm_ioctl+0x601/0x1050 [kvm] Aug 16 03:10:14 hyper-7 kernel: [265397.674367] [<ffffffff8113f461>] ? free_one_page+0x191/0x440 Aug 16 03:10:14 hyper-7 kernel: [265397.708101] [<ffffffff811b4159>] ? vfs_ioctl+0x29/0xc0 Aug 16 03:10:14 hyper-7 kernel: [265397.739124] [<ffffffff81142d86>] ? __free_pages+0x46/0xa0 Aug 16 03:10:14 hyper-7 kernel: [265397.773193] [<ffffffff811b463a>] ? do_vfs_ioctl+0x3aa/0x590 Aug 16 03:10:14 hyper-7 kernel: [265397.805774] [<ffffffff81142e29>] ? free_pages+0x49/0x50 Aug 16 03:10:14 hyper-7 kernel: [265397.839147] [<ffffffff811b48a1>] ? sys_ioctl+0x81/0xa0 Aug 16 03:10:14 hyper-7 kernel: [265397.870109] [<ffffffff810f1d0e>] ? __audit_syscall_exit+0x25e/0x290 Aug 16 03:10:14 hyper-7 kernel: [265397.909358] [<ffffffff81560351>] ? system_call_fastpath+0x2f/0x34 Curiously, the messages don't seem to indicate anything fatal in and of themselves; there are a two like this a minute after bootup and like a dozen more after about a day, none of which seems to have crashed anything. However, it's the only obvious anomaly I could find around the time and as it's VT-x related, I reckon there's a connection. The stack trace closely resembles this bug that turned up in 2015 and was fixed long ago: https://lkml.org/lkml/2015/7/3/288 Has anyone seen this recently and could confirm or refute any of my guesswork? Cheers, Matthias

1 0

grub2 - add NVME to boot from - how?
by lejeczek 15 Aug '18

15 Aug '18

hi guys, I thought I should ask before I start fiddling and break something - can we tell grub2 to add nvme device as an option to boot from? And if yes then what do tell grub? many thanks, L.

2 2

Re: [CentOS] CentOS Digest, Vol 163, Issue 10
by Ste Films- radio stream 15 Aug '18

15 Aug '18

the thread seams to have dead out or gone from rdadmin login prassword reset to user login on centos I dumped mysql to find the password but can't find it with this comand $mysql dump -u rduser -p Rivendell > resetpass.sql i am useing rduser to run airplay but I can't get into config part of rdadmin which rdadmin controls the paramiter to set the rduser program like rdairplay, rdlogedit, rdlibary...ect rdadmin is used to set default and setting all threwout the rd program.... for radio... On Fri, Aug 10, 2018 at 7:00 AM, <centos-request(a)centos.org> wrote: > Send CentOS mailing list submissions to > centos(a)centos.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.centos.org/mailman/listinfo/centos > or, via email, send a message with subject or body 'help' to > centos-request(a)centos.org > > You can reach the person managing the list at > centos-owner(a)centos.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of CentOS digest..." > > > Today's Topics: > > 1. Re: Can't boot into GUI: Centos 7 "Server with GUI" option > (James Pearson) > 2. bad udp cksum (Laszlo Danielisz) > 3. xfs quota question (mark) > 4. Re: xfs quota question (Valeri Galtsev) > 5. Re: xfs quota question (mark) > 6. Re: xfs quota question (Valeri Galtsev) > 7. Re: bad udp cksum (Simon Matter) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 9 Aug 2018 12:20:26 +0000 > From: James Pearson <james-p(a)moving-picture.com> > To: Jay Hart <jhart(a)kevla.org> > Cc: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] Can't boot into GUI: Centos 7 "Server with GUI" > option > Message-ID: <a7387fc9-ddcd-f827-cf07-76667a2a0b2e(a)moving-picture.com> > Content-Type: text/plain; charset="utf-8" > > Jay Hart wrote: > > > > A complete step by step would be appreciated. It will avoid further > back-n-forth. > > It's not that difficult - a quick google of 'centos 7 rebuild initramfs' > brings up (e.g.) > https://sites.google.com/site/syscookbook/rhel/rhel-kernel-rebuild > > James Pearson > > > > ------------------------------ > > Message: 2 > Date: Thu, 9 Aug 2018 14:53:17 -0400 > From: Laszlo Danielisz <lacibsd(a)gmail.com> > To: centos(a)centos.org > Subject: [CentOS] bad udp cksum > Message-ID: > <CABPYxKwuSPEeNxdAUu2p4h-oTibH-RJBnxntWbVO2NuBk0-zfA@ > mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hi, > > Recently I'm noticing an interesting issue. > My CentOS servers are trying to send logs to a logging server via 514/udp, > however I'm not receiving anything. > > I did the following on CentOS > *tcpdump -vvv -nn udp -i esn160 port 514* > > In another session on the same server: > *nc syslog-server -u 514* > > tcpdump started to show me messages like: > *[bad udp cksum 0x3ce9 -> 0xb0f5!] SYSLOG, length: 172* > > After some research I disabled TCO (ethtool -K ens160 tx off rx off), now > tcpdump shows: > *[udp sum ok] [|syslog]* > And I'm also receiving the logs. Yay! > > I have the same issue on multiple servers with CentOS versions 7.3.1611, > 7.4.1708 & 7.5.1804. I'm having the issue no matter if it is a physical or > virtual server (they also use different hardware and NIC's) > > Of course I could run ethtool every time a server starts but I think there > should be a better solution. Also I enjoy having TCO giving some rest to > the CPUs. > > Did anyone find a solution for this? > > Thanks! > Laszlo > > > ------------------------------ > > Message: 3 > Date: Thu, 9 Aug 2018 15:57:25 -0400 > From: "mark" <m.roth(a)5-cent.us> > To: "CentOS mailing list" <centos(a)centos.org> > Subject: [CentOS] xfs quota question > Message-ID: > <993f74e35fb023b2a49b9053dc3e5a3f.squirrel(a)host290.hostmonster.com > > > Content-Type: text/plain;charset=utf-8 > > Can I go to an existing xfs file system, and apply a soft quota to each > user on it? If I do, can I then run a report, and see who's using how > much, or does it only apply to files created after the quotas are applied? > > mark > > > > ------------------------------ > > Message: 4 > Date: Thu, 9 Aug 2018 15:22:30 -0500 > From: Valeri Galtsev <galtsev(a)kicp.uchicago.edu> > To: centos(a)centos.org > Subject: Re: [CentOS] xfs quota question > Message-ID: <6551c6c1-bbb6-ef43-eb3d-03de0fa58b8c(a)kicp.uchicago.edu> > Content-Type: text/plain; charset=utf-8; format=flowed > > > > On 08/09/18 14:57, mark wrote: > > Can I go to an existing xfs file system, and apply a soft quota to each > > user on it? If I do, can I then run a report, and see who's using how > > much, or does it only apply to files created after the quotas are > applied? > > > > After remounting XFS filesystem with option "usrquota" you can issue the > command similar to: > > xfs_quota -x -c "limit bsoft=8g bhard=10g -d" /home > > This command will enable the limits above for all users (-d flag), > except users who have their limits existing already (usually ones who > preformed fs operations). > > For those who already have some limits set you can still can change > these limits, but with individual command, say in the loop, like: > > for i in `cat user_list`; \ > do xfs_quota -x -c "limit bsoft=8g bhard=10g $i; \ > done > > I hope, this helps. > > Valeri > > > > mark > > > > _______________________________________________ > > CentOS mailing list > > CentOS(a)centos.org > > https://lists.centos.org/mailman/listinfo/centos > > > > -- > ++++++++++++++++++++++++++++++++++++++++ > Valeri Galtsev > Sr System Administrator > Department of Astronomy and Astrophysics > Kavli Institute for Cosmological Physics > University of Chicago > Phone: 773-702-4247 > ++++++++++++++++++++++++++++++++++++++++ > > > ------------------------------ > > Message: 5 > Date: Thu, 9 Aug 2018 17:24:09 -0400 > From: "mark" <m.roth(a)5-cent.us> > To: "CentOS mailing list" <centos(a)centos.org> > Subject: Re: [CentOS] xfs quota question > Message-ID: > <4e5e8e726f2df226bc9d6612a1a572c1.squirrel(a)host290.hostmonster.com > > > Content-Type: text/plain;charset=utf-8 > > Valeri Galtsev wrote: > > On 08/09/18 14:57, mark wrote: > > > >> Can I go to an existing xfs file system, and apply a soft quota to each > >> user on it? If I do, can I then run a report, and see who's using how > >> much, or does it only apply to files created after the quotas are > >> applied? > > > > After remounting XFS filesystem with option "usrquota" you can issue the > > command similar to: > > > > xfs_quota -x -c "limit bsoft=8g bhard=10g -d" /home > > > > This command will enable the limits above for all users (-d flag), > > except users who have their limits existing already (usually ones who > > preformed fs operations). > > > > For those who already have some limits set you can still can change > > these limits, but with individual command, say in the loop, like: > > > > for i in `cat user_list`; \ do xfs_quota -x -c "limit bsoft=8g bhard=10g > > $i; \ > > done > > > > I hope, this helps. > > Will that work if I do a mount -o remount? > > mark > > > > ------------------------------ > > Message: 6 > Date: Thu, 9 Aug 2018 16:57:06 -0500 (CDT) > From: "Valeri Galtsev" <galtsev(a)kicp.uchicago.edu> > To: "CentOS mailing list" <centos(a)centos.org> > Subject: Re: [CentOS] xfs quota question > Message-ID: > <54719.108.68.162.197.1533851826.squirrel(a)cosmo.uchicago.edu> > Content-Type: text/plain;charset=iso-8859-1 > > > On Thu, August 9, 2018 4:24 pm, mark wrote: > > Valeri Galtsev wrote: > >> On 08/09/18 14:57, mark wrote: > >> > >>> Can I go to an existing xfs file system, and apply a soft quota to each > >>> user on it? If I do, can I then run a report, and see who's using how > >>> much, or does it only apply to files created after the quotas are > >>> applied? > >> > >> After remounting XFS filesystem with option "usrquota" you can issue the > >> command similar to: > >> > >> xfs_quota -x -c "limit bsoft=8g bhard=10g -d" /home > >> > >> This command will enable the limits above for all users (-d flag), > >> except users who have their limits existing already (usually ones who > >> preformed fs operations). > >> > >> For those who already have some limits set you can still can change > >> these limits, but with individual command, say in the loop, like: > >> > >> for i in `cat user_list`; \ do xfs_quota -x -c "limit bsoft=8g bhard=10g > >> $i; \ > >> done > >> > >> I hope, this helps. > > > > Will that work if I do a mount -o remount? > > If you are able to execute > > mount -o remount -o usrquota /mountpoint > > then you are OK. Normally, you will not be able to do it if there is even > a single file open on the filesystem, Therefore if it is /home you do have > to kick all users off. Executing any command related to quota will make it > obvious if particular filesystem is mounted with quotas enabled or not. > > Good luck. > > Valeri > > > > > mark > > > > ++++++++++++++++++++++++++++++++++++++++ > Valeri Galtsev > Sr System Administrator > Department of Astronomy and Astrophysics > Kavli Institute for Cosmological Physics > University of Chicago > Phone: 773-702-4247 > ++++++++++++++++++++++++++++++++++++++++ > > > ------------------------------ > > Message: 7 > Date: Fri, 10 Aug 2018 09:34:24 +0200 > From: "Simon Matter" <simon.matter(a)invoca.ch> > To: "CentOS mailing list" <centos(a)centos.org> > Subject: Re: [CentOS] bad udp cksum > Message-ID: > <1c988b38e34d5ddc32177f921f7a6c6b.squirrel(a)webmail.bi.invoca.ch> > Content-Type: text/plain;charset=utf-8 > > > Hi, > > > > Recently I'm noticing an interesting issue. > > My CentOS servers are trying to send logs to a logging server via > 514/udp, > > however I'm not receiving anything. > > > > I did the following on CentOS > > *tcpdump -vvv -nn udp -i esn160 port 514* > > > > In another session on the same server: > > *nc syslog-server -u 514* > > > > tcpdump started to show me messages like: > > *[bad udp cksum 0x3ce9 -> 0xb0f5!] SYSLOG, length: 172* > > > > After some research I disabled TCO (ethtool -K ens160 tx off rx off), now > > tcpdump shows: > > *[udp sum ok] [|syslog]* > > And I'm also receiving the logs. Yay! > > > > I have the same issue on multiple servers with CentOS versions 7.3.1611, > > 7.4.1708 & 7.5.1804. I'm having the issue no matter if it is a physical > or > > virtual server (they also use different hardware and NIC's) > > > > Of course I could run ethtool every time a server starts but I think > there > > should be a better solution. Also I enjoy having TCO giving some rest to > > the CPUs. > > > > Did anyone find a solution for this? > > You can configure the ETHTOOL_OPTS option in the ifcfg files to > automatically assign settings on startup. > > Regards, > Simon > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos > > > ------------------------------ > > End of CentOS Digest, Vol 163, Issue 10 > *************************************** >

1 0

Docker + firewalld
by Todor Petkov 15 Aug '18

15 Aug '18

Hello, I am using Centos7 + Docker CE (docker-ce-18.03.1.ce-1.el7.centos.x86_64), in the following setup 1) On interface br-ee1ac3f6bbaf I have network 172.16.26/24 2) Network from (1) is routed via the IP address of eth0 of the CentOS machine 3) Access to machines in network (1) is direct, without port forwarding I want to be able to reach other machines in other subnet from the IP address of the Docker containers. I ran the following command: firewall-cmd --direct --permanent --add-rule ipv4 nat POSTROUTING 0 -i br+ -o eth0 -s 172.16.26.0/24 -j ACCEPT However, the firewall rules for NAT are: -A POSTROUTING -s 172.16.26.0/24 ! -o br-ee1ac3f6bbaf -j MASQUERADE -A POSTROUTING -j POSTROUTING_direct -A POSTROUTING_direct -s 172.16.26.0/24 -i br+ -o eth0 -j ACCEPT With this, it always goes via MASQUERADE first, without hitting the POSTROUTING_direct chain. Is there a way to add this rule on top of POSTROUTING? Regards,

1 0

USB disk IO
by Jerry Geis 15 Aug '18

15 Aug '18

Hello - frequently I turn on my external USB 3.0 disk and back. While my machine is copying and backing up my desktop becomes very sluggish. Is there a way to change that ? I am using CentOS 7.5 x86 with a very nice processor extra cores available and plenty of memory. There is no reason the "other" cores cannot keep the desktop going. Thanks, Jerry

2 2

CentOS-announce Digest, Vol 162, Issue 2
by centos-announce-request＠centos.org 15 Aug '18

15 Aug '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:2390 Important CentOS 6 kernel Security Update (Johnny Hughes) 2. CESA-2018:2384 Important CentOS 7 kernel Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 15 Aug 2018 01:59:55 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:2390 Important CentOS 6 kernel Security Update Message-ID: <20180815015955.GA24393(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:2390 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:2390 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 106a77192bd5329bcc3f7e388192dd6f180b0ab95f4680064d75f3c51d959702 kernel-2.6.32-754.3.5.el6.i686.rpm 62f7a798b08f065e936aa1f3d56a5c7fb4e9e41931a9d85f100f475517f7b017 kernel-abi-whitelists-2.6.32-754.3.5.el6.noarch.rpm 6e5987cd17220deecfa9e669c0be2ffcf42730dd99574c8e3a660e7f1ec7a6d5 kernel-debug-2.6.32-754.3.5.el6.i686.rpm bcab4f5115d1f298efc4894f2d38ebeffd75ae4ee6292146550bbbefdda6f036 kernel-debug-devel-2.6.32-754.3.5.el6.i686.rpm fda995f13c04b4f71fe7ecfb720266a0dade787c4f48b943581c6e75fcae5ef1 kernel-devel-2.6.32-754.3.5.el6.i686.rpm 83fbe21432b4cebf049ba18423bedb34f3f52ba72dd59c5609246d1a393cdb7f kernel-doc-2.6.32-754.3.5.el6.noarch.rpm 22a3605c9893c09958d7d691feec8819680b5117389fab7be28d52bc8f2f108d kernel-firmware-2.6.32-754.3.5.el6.noarch.rpm 17f99387f14bea201de0ef0fc9a117201a26595f9f1bde392504579c9ed71493 kernel-headers-2.6.32-754.3.5.el6.i686.rpm bad0c18a9fcebb72f6a08aac18787222e1c3b10f49ca8eea1a015029c4761515 perf-2.6.32-754.3.5.el6.i686.rpm fa8c69dafcb9bb4a209f8f2fae92a208389b3183a5a473608ef7d765601ec82a python-perf-2.6.32-754.3.5.el6.i686.rpm x86_64: a315d9824eba61490ec384774421d84baf2e853d12e031aaf9ea26f6459e4307 kernel-2.6.32-754.3.5.el6.x86_64.rpm 62f7a798b08f065e936aa1f3d56a5c7fb4e9e41931a9d85f100f475517f7b017 kernel-abi-whitelists-2.6.32-754.3.5.el6.noarch.rpm 67e08721326f15f1b4e9f2a062a45ef612c0d8a784d9f1e3e03f5bb677b56d34 kernel-debug-2.6.32-754.3.5.el6.x86_64.rpm bcab4f5115d1f298efc4894f2d38ebeffd75ae4ee6292146550bbbefdda6f036 kernel-debug-devel-2.6.32-754.3.5.el6.i686.rpm cc9f24337e23be4eeb20a1a87aa69dc91f9a765be4430c58e20ff31b782c75ba kernel-debug-devel-2.6.32-754.3.5.el6.x86_64.rpm 0c16e8f698561ed21e832431b402150f94fe0a0437c5c43a12b70c15306ebcf2 kernel-devel-2.6.32-754.3.5.el6.x86_64.rpm 83fbe21432b4cebf049ba18423bedb34f3f52ba72dd59c5609246d1a393cdb7f kernel-doc-2.6.32-754.3.5.el6.noarch.rpm 22a3605c9893c09958d7d691feec8819680b5117389fab7be28d52bc8f2f108d kernel-firmware-2.6.32-754.3.5.el6.noarch.rpm 0cd344a1d45d5d38e0b00cd2a966c4c6c5c436a830af589edc69ff43da620833 kernel-headers-2.6.32-754.3.5.el6.x86_64.rpm 8f0d34fb64a264cc1d345d3f929f4e0915b4eafab6516de5f32b2e11f4426e27 perf-2.6.32-754.3.5.el6.x86_64.rpm bb421ac56e0ebc227b240dcdccd0a724da33c07fc92d8106b7e4e71c52cb3918 python-perf-2.6.32-754.3.5.el6.x86_64.rpm Source: 4da720dc6cd3913aa9b54abb9d398295b74d5cfb64ea4c93f3eac61ac1070c08 kernel-2.6.32-754.3.5.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Wed, 15 Aug 2018 03:59:04 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:2384 Important CentOS 7 kernel Security Update Message-ID: <20180815035904.GA31375(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:2384 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:2384 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 4c81a12f0c1bab43e45a688035081b68bc17d4ccaf219ad92b8a8a7856282106 kernel-3.10.0-862.11.6.el7.x86_64.rpm 85b7bd8c17bea34630282c70fdcbadb1daafcb112b0a1396770753f90d220c29 kernel-abi-whitelists-3.10.0-862.11.6.el7.noarch.rpm 406fb8d4fe1a048955208a96288505e3c8c0d0d58252650c21f113532fc5b62b kernel-debug-3.10.0-862.11.6.el7.x86_64.rpm cc676de2fa76153f340ceb98d1f709314b404fb19c09f312266b53272f46f127 kernel-debug-devel-3.10.0-862.11.6.el7.x86_64.rpm f28bacde434bc5801b423172e75c932654d153d05bde710306b56323e5ba6b36 kernel-devel-3.10.0-862.11.6.el7.x86_64.rpm 7c45bf82de48d08ad52586c38980366e51e71ff84cb9661452df41484e44598f kernel-doc-3.10.0-862.11.6.el7.noarch.rpm 6c041e73dfa61237e70ecc9f7c201581175a26a88bc2cdcbb2337e19e386d905 kernel-headers-3.10.0-862.11.6.el7.x86_64.rpm e899bc77622146b49a47d58a04dffb8b22215fc8219f1dd8a5fb60dfdbaf9782 kernel-tools-3.10.0-862.11.6.el7.x86_64.rpm 69acbd5ba958c6f367edd0e484822134a325c7d1a97c6af7954d53c80fdb6457 kernel-tools-libs-3.10.0-862.11.6.el7.x86_64.rpm d619c0a7d84568240e05b30e45a207fdc7f8acd7a93643f7d66128c0cf9943e6 kernel-tools-libs-devel-3.10.0-862.11.6.el7.x86_64.rpm 203da784ce254e22df2a78021c5cc97f3a5948432d4d04c49ec44bf1d630ff1a perf-3.10.0-862.11.6.el7.x86_64.rpm 94abbe3057a41b29f89163e5bd838b8c11015182a91f9c58647418d18808282c python-perf-3.10.0-862.11.6.el7.x86_64.rpm Source: aabaa81106744323a084655078fcb93498357768315f53020135688ec03cd21f kernel-3.10.0-862.11.6.el7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 162, Issue 2 ***********************************************

1 0

Sending mail from CentOS7 VM to FX ApeosPort-IV C4475 problem
by マスターズ　イアン 15 Aug '18

15 Aug '18

Hi Folks I'm a long term Linux user but have never used CUPS until this week. I'm trying to print from a CentOS7 VM to a Fuji Xerox ApeosPort-IV C4475 printer which requires a user name to be specified but no password. CUPS reports jobs are complete but nothing appears at the printer. This is what I've tried: 1. I downloaded the linux printer driver from the Fuji Xerox website and installed it and its accompanying printer utility. 2. I've followed various guides for setting up the printer in CUPS as an LPR connection as that is what my Windows machine uses. 3. I used the print utility (fxlputil) to specify my user name as I have to with Windows. However I have a sneaky feeling that nothing is arriving at the printer (whose admin info I don't have access to). I know the connection is OK: /usr/lib/cups/backend/snmp 172.16.58.222 gives: network socket://172.16.58.222 "Unknown" "FUJI XEROX ApeosPort-IV C4475 v 34. 52. 0 Multifunction System" "MANUFACTURER:FUJI XEROX;MODEL:ApeosPort-IV C4475" "" But lpinfo -l -v gives alot of "make-and-model = Unknown" messages. What can I can try to get more information or to get this working? Sorry if my information is vague. As I said, I'm only just starting to dip my feet in the pond of CUPS and it hasn't been very successful so far. Thanks in advance for any assistance. Ian

1 0

Proxy rendering of 4K
by Phil Evans 14 Aug '18

14 Aug '18

Hi everyone. I have used cinelerra for several years and love the application, so thanks to all for the hard work. I recently started to edit 4K footage from a Canon 1DX Mk 2. This is obviously very slow even with a six core processor. So I am required to use proxy files to speed things up. This worked with fedora 28. However I have changed to Centos 7.5 and now have an issue, the proxy files when dropped into the viewer are very small only taking up a small part of the window. I cannot find a way to resize these to fill the viewer window. This did not happen on fedora 28. I set the >settins >format to the resolution of the original video, then the >settings >Proxy settings to use scaler, 1/3rd size, FFMPEG Mp4 and auto proxy/scale media loads. I then import the video and drag the newly created proxy file into the viewer where it sits at a third size in the centre of the viewer window. Any suggestions welcome. Cinelerra 5.1 built jul 31st 2018 06:59:29 Regards Phil Evans

1 0

TLS 1.3 and openSSL 1.1.1 support
by Robert Moskowitz 14 Aug '18

14 Aug '18

TLS 1.3 RFC has 'shipped': RFC 8446. Don't yet know all that will have to be updated to support it, but I am working on openSSL 1.1.1 beta which is available in the Fedora 29 beta. The openSSL team is looking at one more beta release (I had challenges with ED25519 certs, I will soon have an Internet Draft out on them). So general heads up. TLS 1.3 is claimed to be the cat's meow for security (I see it as a kitchen sink). There will be questions asking for when it will be available (wait until they start thinking about creating EDDSA pkis). Yet another thing for our hard working Centos team.

1 0

CentOS 7.5 x86_64 ISO with Kernel 4.x
by andreas.reschke＠mahle.com 14 Aug '18

14 Aug '18

Hi there, I can't boot my new Laptop (HP Elitebook 840 G) with CentOS-7-x86_64-LiveKDE-1804.iso. Boot proccess stops very quick with kernel panic. Is there a ISO-Image with more recent kernel, maybe 4.17 from elrepo? Mit freundlichen Grüßen / Kind regards Andreas Reschke

3 2

Why the new centos-release update?
by Greg Bailey 14 Aug '18

14 Aug '18

Just curious about this after seeing the following output of a typical "yum upgrade": Resolving Dependencies --> Running transaction check ---> Package centos-release.x86_64 0:7-5.1804.el7.centos.2 will be updated ---> Package centos-release.x86_64 0:7-5.1804.1.el7.centos will be an update ...etc... After downloading the 2 centos-release RPMs, the content appears identical. I was assuming there'd at least be differences with yum definitions, GPG keys, or something like that. Was it just to fix some naming inconsistency or something? -Greg

2 1

ligthdm shutdown without a mouse
by Frank Cox 12 Aug '18

12 Aug '18

I have set up a computer that's going to be hand-carried through several airports on the way to its final destination. This is the Lenovo laptop that I asked about earlier, where everything works well except for the touchpad that isn't recognized at all. (For the touchpad I'm just kind of hoping that a future kernel update will make it magically start working; for the time being the computer owner will live without the touchpad and just use an external mouse.) When carrying this though airport security the security guards will likely require that this laptop be turned on for them. How can it be turned off again properly after being checked without having to carry a mouse too? Is there a keyboard shortcut for shutdown with lightdm? -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

2 1

Re: [CentOS] CentOS Digest, Vol 163, Issue 10
by Ste Films- radio stream 10 Aug '18

10 Aug '18

I know there is already a thread going on...but.. I can't get into rdadmin (I set a password) I found out that I can dump mysql and it is in there but I am not sure how to find it in there (in mysql that I have copied or "dumped" it into home user....folder) can someone help me by chance.. thanks, Stephen Campbell On Fri, Aug 10, 2018 at 7:00 AM, <centos-request(a)centos.org> wrote: > Send CentOS mailing list submissions to > centos(a)centos.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.centos.org/mailman/listinfo/centos > or, via email, send a message with subject or body 'help' to > centos-request(a)centos.org > > You can reach the person managing the list at > centos-owner(a)centos.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of CentOS digest..." > > > Today's Topics: > > 1. Re: Can't boot into GUI: Centos 7 "Server with GUI" option > (James Pearson) > 2. bad udp cksum (Laszlo Danielisz) > 3. xfs quota question (mark) > 4. Re: xfs quota question (Valeri Galtsev) > 5. Re: xfs quota question (mark) > 6. Re: xfs quota question (Valeri Galtsev) > 7. Re: bad udp cksum (Simon Matter) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 9 Aug 2018 12:20:26 +0000 > From: James Pearson <james-p(a)moving-picture.com> > To: Jay Hart <jhart(a)kevla.org> > Cc: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] Can't boot into GUI: Centos 7 "Server with GUI" > option > Message-ID: <a7387fc9-ddcd-f827-cf07-76667a2a0b2e(a)moving-picture.com> > Content-Type: text/plain; charset="utf-8" > > Jay Hart wrote: > > > > A complete step by step would be appreciated. It will avoid further > back-n-forth. > > It's not that difficult - a quick google of 'centos 7 rebuild initramfs' > brings up (e.g.) > https://sites.google.com/site/syscookbook/rhel/rhel-kernel-rebuild > > James Pearson > > > > ------------------------------ > > Message: 2 > Date: Thu, 9 Aug 2018 14:53:17 -0400 > From: Laszlo Danielisz <lacibsd(a)gmail.com> > To: centos(a)centos.org > Subject: [CentOS] bad udp cksum > Message-ID: > <CABPYxKwuSPEeNxdAUu2p4h-oTibH-RJBnxntWbVO2NuBk0-zfA@ > mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hi, > > Recently I'm noticing an interesting issue. > My CentOS servers are trying to send logs to a logging server via 514/udp, > however I'm not receiving anything. > > I did the following on CentOS > *tcpdump -vvv -nn udp -i esn160 port 514* > > In another session on the same server: > *nc syslog-server -u 514* > > tcpdump started to show me messages like: > *[bad udp cksum 0x3ce9 -> 0xb0f5!] SYSLOG, length: 172* > > After some research I disabled TCO (ethtool -K ens160 tx off rx off), now > tcpdump shows: > *[udp sum ok] [|syslog]* > And I'm also receiving the logs. Yay! > > I have the same issue on multiple servers with CentOS versions 7.3.1611, > 7.4.1708 & 7.5.1804. I'm having the issue no matter if it is a physical or > virtual server (they also use different hardware and NIC's) > > Of course I could run ethtool every time a server starts but I think there > should be a better solution. Also I enjoy having TCO giving some rest to > the CPUs. > > Did anyone find a solution for this? > > Thanks! > Laszlo > > > ------------------------------ > > Message: 3 > Date: Thu, 9 Aug 2018 15:57:25 -0400 > From: "mark" <m.roth(a)5-cent.us> > To: "CentOS mailing list" <centos(a)centos.org> > Subject: [CentOS] xfs quota question > Message-ID: > <993f74e35fb023b2a49b9053dc3e5a3f.squirrel(a)host290.hostmonster.com > > > Content-Type: text/plain;charset=utf-8 > > Can I go to an existing xfs file system, and apply a soft quota to each > user on it? If I do, can I then run a report, and see who's using how > much, or does it only apply to files created after the quotas are applied? > > mark > > > > ------------------------------ > > Message: 4 > Date: Thu, 9 Aug 2018 15:22:30 -0500 > From: Valeri Galtsev <galtsev(a)kicp.uchicago.edu> > To: centos(a)centos.org > Subject: Re: [CentOS] xfs quota question > Message-ID: <6551c6c1-bbb6-ef43-eb3d-03de0fa58b8c(a)kicp.uchicago.edu> > Content-Type: text/plain; charset=utf-8; format=flowed > > > > On 08/09/18 14:57, mark wrote: > > Can I go to an existing xfs file system, and apply a soft quota to each > > user on it? If I do, can I then run a report, and see who's using how > > much, or does it only apply to files created after the quotas are > applied? > > > > After remounting XFS filesystem with option "usrquota" you can issue the > command similar to: > > xfs_quota -x -c "limit bsoft=8g bhard=10g -d" /home > > This command will enable the limits above for all users (-d flag), > except users who have their limits existing already (usually ones who > preformed fs operations). > > For those who already have some limits set you can still can change > these limits, but with individual command, say in the loop, like: > > for i in `cat user_list`; \ > do xfs_quota -x -c "limit bsoft=8g bhard=10g $i; \ > done > > I hope, this helps. > > Valeri > > > > mark > > > > _______________________________________________ > > CentOS mailing list > > CentOS(a)centos.org > > https://lists.centos.org/mailman/listinfo/centos > > > > -- > ++++++++++++++++++++++++++++++++++++++++ > Valeri Galtsev > Sr System Administrator > Department of Astronomy and Astrophysics > Kavli Institute for Cosmological Physics > University of Chicago > Phone: 773-702-4247 > ++++++++++++++++++++++++++++++++++++++++ > > > ------------------------------ > > Message: 5 > Date: Thu, 9 Aug 2018 17:24:09 -0400 > From: "mark" <m.roth(a)5-cent.us> > To: "CentOS mailing list" <centos(a)centos.org> > Subject: Re: [CentOS] xfs quota question > Message-ID: > <4e5e8e726f2df226bc9d6612a1a572c1.squirrel(a)host290.hostmonster.com > > > Content-Type: text/plain;charset=utf-8 > > Valeri Galtsev wrote: > > On 08/09/18 14:57, mark wrote: > > > >> Can I go to an existing xfs file system, and apply a soft quota to each > >> user on it? If I do, can I then run a report, and see who's using how > >> much, or does it only apply to files created after the quotas are > >> applied? > > > > After remounting XFS filesystem with option "usrquota" you can issue the > > command similar to: > > > > xfs_quota -x -c "limit bsoft=8g bhard=10g -d" /home > > > > This command will enable the limits above for all users (-d flag), > > except users who have their limits existing already (usually ones who > > preformed fs operations). > > > > For those who already have some limits set you can still can change > > these limits, but with individual command, say in the loop, like: > > > > for i in `cat user_list`; \ do xfs_quota -x -c "limit bsoft=8g bhard=10g > > $i; \ > > done > > > > I hope, this helps. > > Will that work if I do a mount -o remount? > > mark > > > > ------------------------------ > > Message: 6 > Date: Thu, 9 Aug 2018 16:57:06 -0500 (CDT) > From: "Valeri Galtsev" <galtsev(a)kicp.uchicago.edu> > To: "CentOS mailing list" <centos(a)centos.org> > Subject: Re: [CentOS] xfs quota question > Message-ID: > <54719.108.68.162.197.1533851826.squirrel(a)cosmo.uchicago.edu> > Content-Type: text/plain;charset=iso-8859-1 > > > On Thu, August 9, 2018 4:24 pm, mark wrote: > > Valeri Galtsev wrote: > >> On 08/09/18 14:57, mark wrote: > >> > >>> Can I go to an existing xfs file system, and apply a soft quota to each > >>> user on it? If I do, can I then run a report, and see who's using how > >>> much, or does it only apply to files created after the quotas are > >>> applied? > >> > >> After remounting XFS filesystem with option "usrquota" you can issue the > >> command similar to: > >> > >> xfs_quota -x -c "limit bsoft=8g bhard=10g -d" /home > >> > >> This command will enable the limits above for all users (-d flag), > >> except users who have their limits existing already (usually ones who > >> preformed fs operations). > >> > >> For those who already have some limits set you can still can change > >> these limits, but with individual command, say in the loop, like: > >> > >> for i in `cat user_list`; \ do xfs_quota -x -c "limit bsoft=8g bhard=10g > >> $i; \ > >> done > >> > >> I hope, this helps. > > > > Will that work if I do a mount -o remount? > > If you are able to execute > > mount -o remount -o usrquota /mountpoint > > then you are OK. Normally, you will not be able to do it if there is even > a single file open on the filesystem, Therefore if it is /home you do have > to kick all users off. Executing any command related to quota will make it > obvious if particular filesystem is mounted with quotas enabled or not. > > Good luck. > > Valeri > > > > > mark > > > > ++++++++++++++++++++++++++++++++++++++++ > Valeri Galtsev > Sr System Administrator > Department of Astronomy and Astrophysics > Kavli Institute for Cosmological Physics > University of Chicago > Phone: 773-702-4247 > ++++++++++++++++++++++++++++++++++++++++ > > > ------------------------------ > > Message: 7 > Date: Fri, 10 Aug 2018 09:34:24 +0200 > From: "Simon Matter" <simon.matter(a)invoca.ch> > To: "CentOS mailing list" <centos(a)centos.org> > Subject: Re: [CentOS] bad udp cksum > Message-ID: > <1c988b38e34d5ddc32177f921f7a6c6b.squirrel(a)webmail.bi.invoca.ch> > Content-Type: text/plain;charset=utf-8 > > > Hi, > > > > Recently I'm noticing an interesting issue. > > My CentOS servers are trying to send logs to a logging server via > 514/udp, > > however I'm not receiving anything. > > > > I did the following on CentOS > > *tcpdump -vvv -nn udp -i esn160 port 514* > > > > In another session on the same server: > > *nc syslog-server -u 514* > > > > tcpdump started to show me messages like: > > *[bad udp cksum 0x3ce9 -> 0xb0f5!] SYSLOG, length: 172* > > > > After some research I disabled TCO (ethtool -K ens160 tx off rx off), now > > tcpdump shows: > > *[udp sum ok] [|syslog]* > > And I'm also receiving the logs. Yay! > > > > I have the same issue on multiple servers with CentOS versions 7.3.1611, > > 7.4.1708 & 7.5.1804. I'm having the issue no matter if it is a physical > or > > virtual server (they also use different hardware and NIC's) > > > > Of course I could run ethtool every time a server starts but I think > there > > should be a better solution. Also I enjoy having TCO giving some rest to > > the CPUs. > > > > Did anyone find a solution for this? > > You can configure the ETHTOOL_OPTS option in the ifcfg files to > automatically assign settings on startup. > > Regards, > Simon > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos > > > ------------------------------ > > End of CentOS Digest, Vol 163, Issue 10 > *************************************** >

1 0

CentOS-announce Digest, Vol 162, Issue 1
by centos-announce-request＠centos.org 10 Aug '18

10 Aug '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:2284 Important CentOS 6 yum-utils Security Update (Johnny Hughes) 2. CESA-2018:2283 Moderate CentOS 6 java-1.7.0-openjdk Security Update (Johnny Hughes) 3. CEEA-2018:2300 CentOS 6 microcode_ctl Enhancement Update (Johnny Hughes) 4. CESA-2018:2308 Important CentOS 6 openslp Security Update (Johnny Hughes) 5. CESA-2018:2286 Moderate CentOS 7 java-1.7.0-openjdk Security Update (Johnny Hughes) 6. CESA-2018:2285 Important CentOS 7 yum-utils Security Update (Johnny Hughes) 7. CEEA-2018:2299 CentOS 7 microcode_ctl Enhancement Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 9 Aug 2018 15:06:44 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:2284 Important CentOS 6 yum-utils Security Update Message-ID: <20180809150644.GA48251(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:2284 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:2284 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 7bfcb55e8ee020fb90438be89a7e6c4659815a47a6a1dc84307ed097c610b164 yum-NetworkManager-dispatcher-1.1.30-42.el6_10.noarch.rpm 0cd10e34874133c0c0894eff1d558fd4a6fdb7cd67db4ef1ae54e47e17a8386d yum-plugin-aliases-1.1.30-42.el6_10.noarch.rpm b43fb8e9d706e3d163f98c085bee3772a2b95e213096ba7c2a7b5fe2d48e2071 yum-plugin-auto-update-debug-info-1.1.30-42.el6_10.noarch.rpm 81d8b7eb5bb4a008559fed431c1721184ce9519e027a7748f9058a1b16374e44 yum-plugin-changelog-1.1.30-42.el6_10.noarch.rpm f0b5012d5c108b231f10e7d79568fdf1382121aef1d51adffe40ab0c3a3eebf9 yum-plugin-fastestmirror-1.1.30-42.el6_10.noarch.rpm 87c1b2d68ff3cb75288f7954b865faefb5ea8a5788e61ca45188837a79bec5e3 yum-plugin-filter-data-1.1.30-42.el6_10.noarch.rpm ddaf9c4883f1b85612a7579025961988241a77733d616380da44a9dca835a771 yum-plugin-fs-snapshot-1.1.30-42.el6_10.noarch.rpm 5bf518b73d2dd00d2c8c183d5089839038fdd88e1da82102f19b5f0ecd4d62a2 yum-plugin-keys-1.1.30-42.el6_10.noarch.rpm 21b1d70c8b13b173479c0fd6df539755849dc966b9e20947bdf5b4bd1ffa667b yum-plugin-list-data-1.1.30-42.el6_10.noarch.rpm 13af558be264f80cd30e94640c6d14c6188c90f43e0d6988e473d704863cc96d yum-plugin-local-1.1.30-42.el6_10.noarch.rpm df05258dcf572fe8f834066715da11a9b0f4987e5529a02a8de8a46f2395dac7 yum-plugin-merge-conf-1.1.30-42.el6_10.noarch.rpm 161c5190e409c96b025eacec584a2ebb12bac6b0549917efe5747fe870f9eecd yum-plugin-ovl-1.1.30-42.el6_10.noarch.rpm 4140ac99eb793c08f4c83736a3524c9cfe6f0bce2e636163708b441787ae193b yum-plugin-post-transaction-actions-1.1.30-42.el6_10.noarch.rpm c49a097f2b6b141a5ddc3a6a0c4cb98b788b1cae17381e5dbb7da65817911ff7 yum-plugin-priorities-1.1.30-42.el6_10.noarch.rpm 7dc3c4cb2caae34b698eca89af931932abdd4570c3e14b5d7c9faa345ca4b369 yum-plugin-protectbase-1.1.30-42.el6_10.noarch.rpm 994f577a16671dc0c21df23ab92b97788dccf332819ee5bc50624845ec80cc82 yum-plugin-ps-1.1.30-42.el6_10.noarch.rpm 8a0291ddeb80f0df79e1c45b40ccd4f18ce67e52d4e814759300c9d86465f83a yum-plugin-remove-with-leaves-1.1.30-42.el6_10.noarch.rpm 67ca18b553619ecd7b8c4edf4930f289be25b8f17407c8bfab2da00c95291a79 yum-plugin-rpm-warm-cache-1.1.30-42.el6_10.noarch.rpm c7efb7d125e82a8fceeb865739d79621ef5c3d7a29063edf35af9761188cf6a8 yum-plugin-security-1.1.30-42.el6_10.noarch.rpm 28e93077b07e0a2b0d011d87cae99ba6a61369fd15678fd31e9ffbaa32046e56 yum-plugin-show-leaves-1.1.30-42.el6_10.noarch.rpm 9a7f57f4fa32b1b61a0458d0800a18496a4068e6dde6473d8c6705f9ce102162 yum-plugin-tmprepo-1.1.30-42.el6_10.noarch.rpm 5879369debc94ac2b1b715411c457d2ac68546d484588cd2a1de13692e99001a yum-plugin-tsflags-1.1.30-42.el6_10.noarch.rpm 601664907b5f6eb9508c445b1988b9fa708645e40311d3ad4a74e3b3417618bc yum-plugin-upgrade-helper-1.1.30-42.el6_10.noarch.rpm 11f428d2609b08188d2c8674bc434b59a942c01a2b8e2d7f417baa9572038cca yum-plugin-verify-1.1.30-42.el6_10.noarch.rpm b8df971607bb4e263d8e8501841f137f674f13df720d5ab44707c7f276092559 yum-plugin-versionlock-1.1.30-42.el6_10.noarch.rpm 6656d23a21732389cabd73c2405cd18f03195e082e797b7ece269cf4ae6194f5 yum-updateonboot-1.1.30-42.el6_10.noarch.rpm 9dd7d61ca036fbaae599ef356d452be2cfeca5bad926580d17998e9b6bab7428 yum-utils-1.1.30-42.el6_10.noarch.rpm x86_64: 7bfcb55e8ee020fb90438be89a7e6c4659815a47a6a1dc84307ed097c610b164 yum-NetworkManager-dispatcher-1.1.30-42.el6_10.noarch.rpm 0cd10e34874133c0c0894eff1d558fd4a6fdb7cd67db4ef1ae54e47e17a8386d yum-plugin-aliases-1.1.30-42.el6_10.noarch.rpm b43fb8e9d706e3d163f98c085bee3772a2b95e213096ba7c2a7b5fe2d48e2071 yum-plugin-auto-update-debug-info-1.1.30-42.el6_10.noarch.rpm 81d8b7eb5bb4a008559fed431c1721184ce9519e027a7748f9058a1b16374e44 yum-plugin-changelog-1.1.30-42.el6_10.noarch.rpm f0b5012d5c108b231f10e7d79568fdf1382121aef1d51adffe40ab0c3a3eebf9 yum-plugin-fastestmirror-1.1.30-42.el6_10.noarch.rpm 87c1b2d68ff3cb75288f7954b865faefb5ea8a5788e61ca45188837a79bec5e3 yum-plugin-filter-data-1.1.30-42.el6_10.noarch.rpm ddaf9c4883f1b85612a7579025961988241a77733d616380da44a9dca835a771 yum-plugin-fs-snapshot-1.1.30-42.el6_10.noarch.rpm 5bf518b73d2dd00d2c8c183d5089839038fdd88e1da82102f19b5f0ecd4d62a2 yum-plugin-keys-1.1.30-42.el6_10.noarch.rpm 21b1d70c8b13b173479c0fd6df539755849dc966b9e20947bdf5b4bd1ffa667b yum-plugin-list-data-1.1.30-42.el6_10.noarch.rpm 13af558be264f80cd30e94640c6d14c6188c90f43e0d6988e473d704863cc96d yum-plugin-local-1.1.30-42.el6_10.noarch.rpm df05258dcf572fe8f834066715da11a9b0f4987e5529a02a8de8a46f2395dac7 yum-plugin-merge-conf-1.1.30-42.el6_10.noarch.rpm 161c5190e409c96b025eacec584a2ebb12bac6b0549917efe5747fe870f9eecd yum-plugin-ovl-1.1.30-42.el6_10.noarch.rpm 4140ac99eb793c08f4c83736a3524c9cfe6f0bce2e636163708b441787ae193b yum-plugin-post-transaction-actions-1.1.30-42.el6_10.noarch.rpm c49a097f2b6b141a5ddc3a6a0c4cb98b788b1cae17381e5dbb7da65817911ff7 yum-plugin-priorities-1.1.30-42.el6_10.noarch.rpm 7dc3c4cb2caae34b698eca89af931932abdd4570c3e14b5d7c9faa345ca4b369 yum-plugin-protectbase-1.1.30-42.el6_10.noarch.rpm 994f577a16671dc0c21df23ab92b97788dccf332819ee5bc50624845ec80cc82 yum-plugin-ps-1.1.30-42.el6_10.noarch.rpm 8a0291ddeb80f0df79e1c45b40ccd4f18ce67e52d4e814759300c9d86465f83a yum-plugin-remove-with-leaves-1.1.30-42.el6_10.noarch.rpm 67ca18b553619ecd7b8c4edf4930f289be25b8f17407c8bfab2da00c95291a79 yum-plugin-rpm-warm-cache-1.1.30-42.el6_10.noarch.rpm c7efb7d125e82a8fceeb865739d79621ef5c3d7a29063edf35af9761188cf6a8 yum-plugin-security-1.1.30-42.el6_10.noarch.rpm 28e93077b07e0a2b0d011d87cae99ba6a61369fd15678fd31e9ffbaa32046e56 yum-plugin-show-leaves-1.1.30-42.el6_10.noarch.rpm 9a7f57f4fa32b1b61a0458d0800a18496a4068e6dde6473d8c6705f9ce102162 yum-plugin-tmprepo-1.1.30-42.el6_10.noarch.rpm 5879369debc94ac2b1b715411c457d2ac68546d484588cd2a1de13692e99001a yum-plugin-tsflags-1.1.30-42.el6_10.noarch.rpm 601664907b5f6eb9508c445b1988b9fa708645e40311d3ad4a74e3b3417618bc yum-plugin-upgrade-helper-1.1.30-42.el6_10.noarch.rpm 11f428d2609b08188d2c8674bc434b59a942c01a2b8e2d7f417baa9572038cca yum-plugin-verify-1.1.30-42.el6_10.noarch.rpm b8df971607bb4e263d8e8501841f137f674f13df720d5ab44707c7f276092559 yum-plugin-versionlock-1.1.30-42.el6_10.noarch.rpm 6656d23a21732389cabd73c2405cd18f03195e082e797b7ece269cf4ae6194f5 yum-updateonboot-1.1.30-42.el6_10.noarch.rpm 9dd7d61ca036fbaae599ef356d452be2cfeca5bad926580d17998e9b6bab7428 yum-utils-1.1.30-42.el6_10.noarch.rpm Source: 8db1cb822c4a45e97d602cfd3bce52ec5ffedb64cf85d0c9c01b7f6a9790a0c8 yum-utils-1.1.30-42.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Thu, 9 Aug 2018 15:07:41 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:2283 Moderate CentOS 6 java-1.7.0-openjdk Security Update Message-ID: <20180809150741.GA48537(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:2283 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2018:2283 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 5d7c23cc5f6490644f30cc874eff9b0376be8f5e5142d3000530457422a20257 java-1.7.0-openjdk-1.7.0.191-2.6.15.4.el6_10.i686.rpm 62bd98fda4c2d74b249097a2083dcf37ca36addf20a6668ab3e3f7a43bd66d66 java-1.7.0-openjdk-demo-1.7.0.191-2.6.15.4.el6_10.i686.rpm 3c2234d7f8a74105abf76e0c6ea66f385cf4083ac942063a25350f3cdabf4528 java-1.7.0-openjdk-devel-1.7.0.191-2.6.15.4.el6_10.i686.rpm f86b24613cb373d57bd9994321392d59455f9b951159d8d0d5a5a2cff4117923 java-1.7.0-openjdk-javadoc-1.7.0.191-2.6.15.4.el6_10.noarch.rpm a5833c2e102a05273e6306283d332cbee2f84b4e008aaaa60fda760cd5ab3535 java-1.7.0-openjdk-src-1.7.0.191-2.6.15.4.el6_10.i686.rpm x86_64: 1aa0cd7801ce78a765ec56e20af38882e540ca9c96d245ebc3ceb41636e1ef80 java-1.7.0-openjdk-1.7.0.191-2.6.15.4.el6_10.x86_64.rpm 74fad258b6a399f9cb9ad6eed044bff17d46ebfbb49631ee364af3695539fb66 java-1.7.0-openjdk-demo-1.7.0.191-2.6.15.4.el6_10.x86_64.rpm 7ce0a0c40b879461f0155bd5666c03bed02ac7da2a29a214d48bbcec7e59e9cd java-1.7.0-openjdk-devel-1.7.0.191-2.6.15.4.el6_10.x86_64.rpm f86b24613cb373d57bd9994321392d59455f9b951159d8d0d5a5a2cff4117923 java-1.7.0-openjdk-javadoc-1.7.0.191-2.6.15.4.el6_10.noarch.rpm c3440b525d7fc9a8aa20607b596e480104dfb1d6b8d78b5a862c9cf75051ef5e java-1.7.0-openjdk-src-1.7.0.191-2.6.15.4.el6_10.x86_64.rpm Source: 011b1cc84bde6a7a0652f63d63f20b9a05004b7ab91e61303e9d875e08f4c9c6 java-1.7.0-openjdk-1.7.0.191-2.6.15.4.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Thu, 9 Aug 2018 15:08:29 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2018:2300 CentOS 6 microcode_ctl Enhancement Update Message-ID: <20180809150829.GA48733(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2018:2300 Upstream details at : https://access.redhat.com/errata/RHEA-2018:2300 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 274d9da87e0ec117315739c978ed0e60b95dd537d16a009752382439cf5ecdd4 microcode_ctl-1.17-33.3.el6_10.i686.rpm x86_64: c2aea09a33502bab2a8d0868e004deeaf907ecc94fbfeb466b8959a56a27ed11 microcode_ctl-1.17-33.3.el6_10.x86_64.rpm Source: dfb669d88b46753646a51e83b76d40f2ae00e76233223c29feeee1064d331faa microcode_ctl-1.17-33.3.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Thu, 9 Aug 2018 15:08:57 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:2308 Important CentOS 6 openslp Security Update Message-ID: <20180809150857.GA48985(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:2308 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:2308 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 27b00ada4bec2125f2bdcbf4d2b4556d78c8dad7f3aa4db99719b11bdd14cbb8 openslp-2.0.0-3.el6.i686.rpm 878fc7adc5e540f49d9b1ad0f31cda8ecd537c0ebe6aa233f4fd77973d9101a7 openslp-devel-2.0.0-3.el6.i686.rpm 4946fa3327f713aeb9ed14f9fba166d4d615ded256a98acfa6f12beddc35927c openslp-server-2.0.0-3.el6.i686.rpm x86_64: 27b00ada4bec2125f2bdcbf4d2b4556d78c8dad7f3aa4db99719b11bdd14cbb8 openslp-2.0.0-3.el6.i686.rpm d52e73e63707e008192e0fa0b70ace0a78a939efeab3ba613a08e0d48ffe3246 openslp-2.0.0-3.el6.x86_64.rpm 878fc7adc5e540f49d9b1ad0f31cda8ecd537c0ebe6aa233f4fd77973d9101a7 openslp-devel-2.0.0-3.el6.i686.rpm 29ff71858aa6884d51a46c130509bf4c1f71fa86aecf035f06065aba3d251b74 openslp-devel-2.0.0-3.el6.x86_64.rpm 48503a61e53d510f77d42c664a5f1cb94a1d2941600c500daa721179522b474a openslp-server-2.0.0-3.el6.x86_64.rpm Source: a404790c3285eb34280ab96860e9638791232e1f7574288d054ba1fd786de5fa openslp-2.0.0-3.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Thu, 9 Aug 2018 15:11:54 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:2286 Moderate CentOS 7 java-1.7.0-openjdk Security Update Message-ID: <20180809151154.GA49144(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:2286 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2018:2286 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: eaf8b440d4d9616ec42e57ddf421871fa4f9a8e60f0c69446f2ec22e80c7b283 java-1.7.0-openjdk-1.7.0.191-2.6.15.4.el7_5.x86_64.rpm 63db95d992e429d779e8a1a0cd74173148b0da3f83025fe325ab802fba26aa35 java-1.7.0-openjdk-accessibility-1.7.0.191-2.6.15.4.el7_5.x86_64.rpm 479c06d62bf85cd7b18a82456d85288ce62f5fe17e30dab177710155f2bbc849 java-1.7.0-openjdk-demo-1.7.0.191-2.6.15.4.el7_5.x86_64.rpm ec352aae5f47c1b86d88b9572dd0b4de2aabc915c830924b318f34c1b7d1f6c7 java-1.7.0-openjdk-devel-1.7.0.191-2.6.15.4.el7_5.x86_64.rpm 13cf6c95028f06dc2c4f25040e0eb2b626ef4ddea1a3ab46c9fb788137b37596 java-1.7.0-openjdk-headless-1.7.0.191-2.6.15.4.el7_5.x86_64.rpm 2a6f4e573d7362e301cebc9efd96ffcb64849a04aecc6fd48161ddd50cdccc0a java-1.7.0-openjdk-javadoc-1.7.0.191-2.6.15.4.el7_5.noarch.rpm dad5d7f6805279dd705280e36aa3659a024543aed1308e052ed5cd6e5dfa8291 java-1.7.0-openjdk-src-1.7.0.191-2.6.15.4.el7_5.x86_64.rpm Source: 18786ff0a7eaf41146df9f010de77790c39f3f8e0b11bdf2e2b1a32bf744d07b java-1.7.0-openjdk-1.7.0.191-2.6.15.4.el7_5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 6 Date: Thu, 9 Aug 2018 15:12:08 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:2285 Important CentOS 7 yum-utils Security Update Message-ID: <20180809151208.GA49386(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:2285 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:2285 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 18ce4937fc4788db5136c8228b36e07e119c0383fe528fa345abc349db0b0f70 yum-NetworkManager-dispatcher-1.1.31-46.el7_5.noarch.rpm d9fe4dc03407e314e44b96cb727b3b0e115fabdb96c321318cf0f3eb05ec4226 yum-plugin-aliases-1.1.31-46.el7_5.noarch.rpm 78d0c9c4f8cc7f59a47163de6dc9b8c4aa7d41d9c4f8cdba2a90316de1063412 yum-plugin-auto-update-debug-info-1.1.31-46.el7_5.noarch.rpm df3834f742fa57866bb940399d8ff0835a9baf34b06d353d01062ce604616147 yum-plugin-changelog-1.1.31-46.el7_5.noarch.rpm a874364ad109e96d43cad1b112c499056454ec5797f4e9a4b7636f1b0b6229e4 yum-plugin-copr-1.1.31-46.el7_5.noarch.rpm 3b3f555a4e13e3f6e9ac9aaa829aa57384f7017eef7ee0b19b4210015b187cb1 yum-plugin-fastestmirror-1.1.31-46.el7_5.noarch.rpm fcc22adff5b4dd17458e3c398da88e0a90da1715222f86301a7a19e2c266378e yum-plugin-filter-data-1.1.31-46.el7_5.noarch.rpm 66423465c4a46128f5fdb625f7c94c212458442fb096f689819302f781f0605f yum-plugin-fs-snapshot-1.1.31-46.el7_5.noarch.rpm 39204f4413c69a11eb33aa7ec48a3096d207b7a1deb831ebf1e6e638224b79e6 yum-plugin-keys-1.1.31-46.el7_5.noarch.rpm 713bc86327e45601edf5d2c08f04192eb91fd438644b6b23e07ec0ba87d9fa62 yum-plugin-list-data-1.1.31-46.el7_5.noarch.rpm bef25112eafc8b14dbff4c44425f0943a437dce8799f432417faa2711afab441 yum-plugin-local-1.1.31-46.el7_5.noarch.rpm a845857ebd4e2362c1075944bcd5289b2e1265cfe88b7feb05f07305b69e631d yum-plugin-merge-conf-1.1.31-46.el7_5.noarch.rpm 8ea803d0d21eb0082c338e482c0bf8e54c802d01afa76338afe1a328c87ff92f yum-plugin-ovl-1.1.31-46.el7_5.noarch.rpm e76ebd6c80f6be2b0a2646d3212bb7e98015d8312d8ad393d50e724f6e7909a3 yum-plugin-post-transaction-actions-1.1.31-46.el7_5.noarch.rpm 12477d8716a34a84447405ad4dd1604c76e5c81e27ae8fd2bf3ab683e1373f04 yum-plugin-pre-transaction-actions-1.1.31-46.el7_5.noarch.rpm 379ab4fc7dd5c3239d43e606c509d87c7ab3fc5c72a2f1a507e01e76c5f04a38 yum-plugin-priorities-1.1.31-46.el7_5.noarch.rpm 9db52c94fcd48e42f472e8f43cb8c66689b809ad1fb0de44fbe037e622af6e4c yum-plugin-protectbase-1.1.31-46.el7_5.noarch.rpm 223497c43b3b7af69ac52ac5ba1d72236ee5876f09131856d8833484e469e21b yum-plugin-ps-1.1.31-46.el7_5.noarch.rpm a266281f256bad0137095207014b1477a2abf53a23db9a193fe1eec9e748b667 yum-plugin-remove-with-leaves-1.1.31-46.el7_5.noarch.rpm a0b9d9b0e933d821f3406e4249bae6f25421beecd077681583a40779935f1d69 yum-plugin-rpm-warm-cache-1.1.31-46.el7_5.noarch.rpm c46f2903e14ad4f1c888513466858d78026df782082603baead688a821351bc9 yum-plugin-show-leaves-1.1.31-46.el7_5.noarch.rpm 6d34fc2ca26fb8c011a2957b1265128b8878c2dab63c89bbe88e4cfe7f517f25 yum-plugin-tmprepo-1.1.31-46.el7_5.noarch.rpm 095f5aa724d5a45b902f3763ea8b20c0756ec1030a9cc46bbd6010e3bb2b2661 yum-plugin-tsflags-1.1.31-46.el7_5.noarch.rpm 55b3966a988b9b9d0921dc4f915e0cab354e6bac2df78fd87806a5d06fd53b6e yum-plugin-upgrade-helper-1.1.31-46.el7_5.noarch.rpm 51f92ef9387ee3e4e14172c6c3fba83c3f7e9fe30adac135616dd1a5056f908c yum-plugin-verify-1.1.31-46.el7_5.noarch.rpm 734dae165c6b300150d06e5c23b5619ced2fe282d8abfaad819acabc04baffd4 yum-plugin-versionlock-1.1.31-46.el7_5.noarch.rpm 91a924d61e3c92ea8a929ff0af4bfbfa1b12ee155f4cecbd279f1180704424ab yum-updateonboot-1.1.31-46.el7_5.noarch.rpm abc729a5ce64d9aeb89593ac092e6f16e7052a3b27f3f32be75c32cfaf4b47c1 yum-utils-1.1.31-46.el7_5.noarch.rpm Source: f07d0b15f192a60af822f5f05575abc2494003c4b2d2c9861138f33dcc4c202c yum-utils-1.1.31-46.el7_5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 7 Date: Thu, 9 Aug 2018 15:12:26 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2018:2299 CentOS 7 microcode_ctl Enhancement Update Message-ID: <20180809151226.GA49455(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2018:2299 Upstream details at : https://access.redhat.com/errata/RHEA-2018:2299 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 510816029f0bcdcf382be49e6ef6d5a85b4cdcdb3091714528f3572b94c0c78b microcode_ctl-2.1-29.10.el7_5.x86_64.rpm Source: 7b7b4c5af1d7b35fb76535b45341947602d0010f2cb72cb1a6e189c3c2f82820 microcode_ctl-2.1-29.10.el7_5.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 162, Issue 1 ***********************************************

1 0

xfs quota question
by mark 09 Aug '18

09 Aug '18

Can I go to an existing xfs file system, and apply a soft quota to each user on it? If I do, can I then run a report, and see who's using how much, or does it only apply to files created after the quotas are applied? mark

2 3

Re: [CentOS] Can't boot into GUI: Centos 7 "Server with GUI" option
by James Pearson 09 Aug '18

09 Aug '18

Jay Hart wrote: > > A complete step by step would be appreciated. It will avoid further back-n-forth. It's not that difficult - a quick google of 'centos 7 rebuild initramfs' brings up (e.g.) https://sites.google.com/site/syscookbook/rhel/rhel-kernel-rebuild James Pearson

1 0

Re: [CentOS] Can't boot into GUI: Centos 7 "Server with GUI" option
by James Pearson 09 Aug '18

09 Aug '18

Jay Hart wrote: > ** WARNING: This mail is from an external source ** > > >> Jay Hart wrote: >>> >>> I'm setting up a new server on Centos 7, running x86_64. Motherboard is a MITAC PD11BICC, >>> running >>> Indian Bay Trail, with a i915 chipset. >>> >>> I installed "Server with GUI", but when it boots I get the "blank screen with a cursor" issue. >>> >>> Decided to see about disabling the i915 driver, by blacklisting it. but I don't think I have >>> the >>> right commands, as when I did that, it appeared on the reboot the i915 driver was still active. >>> >>> vi /etc/modprobe.d/blacklist_i915.conf >>> added the following line to that file >>> blacklist i915 >>> Saved the file. Rebooted. >>> >>> The driver seemed to active upon the reboot. >>> >>> Can someone tell me if this is the correct and full procedure to get rid of this driver. >> >> It is probably being loaded by the initramfs image on boot >> >> If you rebuild the initramfs (which you can do by just running >> 'dracut'), it should honour the current 'blacklist' settings in >> /etc/modprobe.d/ >> >> James Pearson > > So, run 'dracut' and then reboot? Yes ... you should rename the existing initramfs first James Pearson

1 0

Can't boot into GUI: Centos 7 "Server with GUI" option
by Jay Hart 09 Aug '18

09 Aug '18

I'm setting up a new server on Centos 7, running x86_64. Motherboard is a MITAC PD11BICC, running Indian Bay Trail, with a i915 chipset. I installed "Server with GUI", but when it boots I get the "blank screen with a cursor" issue. Decided to see about disabling the i915 driver, by blacklisting it. but I don't think I have the right commands, as when I did that, it appeared on the reboot the i915 driver was still active. vi /etc/modprobe.d/blacklist_i915.conf added the following line to that file blacklist i915 Saved the file. Rebooted. The driver seemed to active upon the reboot. Can someone tell me if this is the correct and full procedure to get rid of this driver. Thanks, Jay

2 1

Okular
by mark 08 Aug '18

08 Aug '18

Does anyone know what Magical configuration file determines whether okular give measurements, in the properties of a .pdf, in millimeters, rather than, say, inches or cm or furlongs? mark -- Measurements will always be given in the least convenient units, such as the speed of light in furlongs per fortnight

2 1

systemd equivalent of xinetd 'only_from' and 'banner_fail' attributes
by James Pearson 08 Aug '18

08 Aug '18

I'm attempting to port an existing xinetd service from CentOS 6 to something equivalent with systemd for CentOS 7 The existing xinetd config uses the attributes 'only_from' to limit connections from a limited set of remote hosts and 'banner_fail' to print a suitable error message when access is denied However, I can't find suitable 'equivalents' with systemd socket/service files on CentOS 7 It appears later versions of systemd supports the option IPAddressAllow= (which is what I think I need ?) Does anyone know how to limit the remote hosts that can connect to a port with CentOS 7's systemd ? Also, how to implement the equivalent of 'banner_fail' ? (not absolutely required, but nice to have) Thanks James Pearson

2 2

SSSD and cache persistence
by Pete Biggs 08 Aug '18

08 Aug '18

I have a large number of CentOS machines (both 6 & 7) getting account information from an LDAP database using SSSD. It all works fine and is fairly reliable. However, I'm having problems with persuading the caching system to forget about users when they are deleted from LDAP. I know about sss_cache with either -E or -U options, but that doesn't delete anything, just invalidates the cache entry. If the cache is invalid SSS will, obviously, go back to the source and return the information there, however, bizarrely, if the original source doesn't have the information (like when a user is deleted) the cached information is still returned. That cached information is retained for ever it seems so my supposedly deleted user accounts still appear to be active on the machines. And it also seems you can't actually turn off caching - even though there are options in sssd.conf to do so. It looks like the "cache_credentials = False" option still caches things, but just acts like the entries are always invalid. I can of course do stop sssd delete the contents of /var/lib/sss/db start sssd and that's what I do when things become an issue. But surely there is a better way of SSSD actually realising that a user has been deleted from LDAP? Pete

4 5

Centos 7.5..and My GDM Greeter/GDM Don't Work Anymore
by Paul E. Virgo 07 Aug '18

07 Aug '18

So, we've updated to 7.5, and for two machines--A Dell Precision M4800, and a Dell Precision 7510..both running Radeon cards--we no longer get the GDM Greeter login box NOR can we switch to virtual text login terminals. It's been driving me nuts. The systems do allow for SSH logins, so that's how we get to them, but I've checked the Xorg.0.log and nothing stands out. Did a systemctl status gdm.service and got this: > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-shell[2023]: g_array_unref: > assertion 'array' failed > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-shell[2023]: g_array_unref: > assertion 'array' failed > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-shell[2023]: g_array_unref: > assertion 'array' failed > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-shell[2023]: g_array_unref: > assertion 'array' failed > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-shell[2023]: g_array_unref: > assertion 'array' failed > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-session-binary[1926]: > WARNING: Could not get session path for session. Check that logind is > properly installed and pam_systemd is getting used at login. > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-shell[2023]: g_array_unref: > assertion 'array' failed > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-session[1926]: > gnome-session-binary[1926]: WARNING: Could not get session path for > session. Check that logind is properly installed and pam_systemd > is...ed at login. > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-shell[2023]: g_array_unref: > assertion 'array' failed > Aug 07 16:23:32 gs6102dsclxpvirgo3 gnome-shell[2023]: JS ERROR: > Exception in callback for signal: reset: Gio.DBusError: > GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: No session available > LoginDialog<._resetGreeterProxy@resource:///org/gnome/shell/gdm/loginDialog.js:837:29 > wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22... Did the upgrade break something? Possibly. Any and all hints/ideas/etc. greatly welcomed. PEV -- Paul E Virgo Sr. System Administrator Code 610.2 SESDA III - DAAC/DISC Goddard Space Flight Ctr/NASA Greenbelt, MD Greenbelt, MD 20771 (301) 614-5751

1 0

Back to Xfce
by Robert Moskowitz 07 Aug '18

07 Aug '18

Now that the basic server is up and running. With Gnome via VNC (yuck), it is time to go back and figure out howto install Xfce without an Xfce group script. So I am asking those with X64 Centos for some pointers. Like where are the group scripts so maybe I can modify them for armhfp. I was reading: https://www.rootusers.com/how-to-install-xfce-gui-in-centos-7-linux/ Where the author talks about doing a minimal install then running: yum groupinstall "Server with GUI" But notes that this installs Gnome (which I don't want) and that instead to yum groupinstall “X Window System” But has concerns if this installs all needed followed up with yum groupinstall "Xfce" Thing is on armhfp, I do not have “X Window System” or "Xfce" I have come to understand that groups are scripts that install all the need rpms for the group. But I have not found where these scripts are so hopefully I can see them, figure out how to modify them for the armhfp rpms, and run them. So I am looking for pointers on where these are in tehx64 repos, and how to work with these scripts. thank you for your help..

3 8

rsync versioning problem
by Robert Moskowitz 06 Aug '18

06 Aug '18

I seem to have an rsync versioning problem. The sender is an old ClearOS6 server with rsynv 3.0.6 The receiver is a brand new Centos7-armv7 server with rsync 3.1.2 I am running rsync over ssh Got the error: rsync error: error in rsync protocol data stream (code 12) at io.c(600) [sender=3.0.6] And researching this it comes down to a versioning issue. But all I have found was to upgrade the 3.0.6 system! That will happen when I migrate to ClearOS7! Is there some option to specify to get this to work? rsync -ah --stats --delete -e "ssh" /var/flexshare/shares x.htt-consult.com:/media/backup/homebase/var/flexshare/shares/

2 6

Installing GCC 5.3.0 in CentOS 6 in Docker.
by Mohan Ganesalingam 06 Aug '18

06 Aug '18

I need to compile some C++ 11 with GCC 5.3.0 on CentOS 6. All of this is happening inside docker in CI using the centos:6 base image. (NB. It can't be GCC 6 or 7, because I have to send binaries to clients who won't install newer vs of libstdc++.so.) Until recently, I was installing devtoolset-4-gcc-c++ via yum, and then using RUN scl enable devtoolset-4 gcc to build the code. Unfortunately, devtoolset-4 is no longer supported, so this has stopped working. I've been trying to compile GCC from scratch, but it's been running for hours and hours – even if I get it working, I'll have to replicate the whole process inside Docker and I suspect it will be very brittle. Is there any easy way of downloading a precompiled version? E.g. -- Is there something that I can do to go back to the old v. of Software Collections? Or -- Is there somewhere I might find a precompiled gcc 5 package? Thanks very much, Mohan

1 0

Lenovo Ideapad 320 touchpad not recognized
by Frank Cox 05 Aug '18

05 Aug '18

I'm setting up a new Lenovo Ideapad 320 and everything shows up and works fine except for the touchpad. I did have to get into the bios and set Legacy for boot device and boot mode to get Centos 7 to finish installing. The default bios settings would load the Centos 7 Gnome Live image from a usb flash drive and work (except for the touchpad) but when I tried to install to the hard drive it would get to the end of the process and kernel panic when it was writing the bootloader. Setting Legacy Boot in the bios solved that problem. I have run yum update so everything is up to date. But the touchpad doesn't show up at all. [frankcox@localhost ~]$ cat list.txt ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ - Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ - Logitech USB Receiver id=8 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] - Virtual core XTEST keyboard id=5 [slave keyboard (3)] - Video Bus id=6 [slave keyboard (3)] - Power Button id=7 [slave keyboard (3)] - EasyCamera id=9 [slave keyboard (3)] - AT Translated Set 2 keyboard id=10 [slave keyboard (3)] - Ideapad extra buttons id=11 [slave keyboard (3)] The Logitech USB Receiver listed here is the wireless mouse that I'm using on it right now since the touchpad doesn't work. I've been reading everything I can find about this problem, tried a few different grub parameters that didn't help, and the most advanced solution that I've tried was this: https://superuser.com/questions/1156057/touchpad-not-working-on-centos-7-2 1. Add i8042.nopnp to grub command line in /etc/default/grub: # change this: GRUB_CMDLINE_LINUX_DEFAULT="... quiet splash" # to: GRUB_CMDLINE_LINUX_DEFAULT="... quiet splash i8042.nopnp" 2. Update your grub config (as root): # If you're using UEFI boot grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg # or legacy grub2-mkconfig -o /boot/grub2/grub.cfg 3. Blacklist module i2c_hid (as root): echo "blacklist i2c_hid" > /etc/modprobe.d/i2c-hid.conf 4. Regenerate your initramfs (as root): cp -v /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak dracut -f 5. Reboot! Unfortunately, that didn't change anything; xinput --list still doesn't show the touchpad. I have found references to some deb packages and fedora rpms that don't appear to exist for Centos 7: xorg-x11-drv-synaptics-legacy.x86_64 elantech-0608-dkms_0.2_all.deb I've pretty much run out of ideas. I checked the bios and don't see anything that appears to be related to the touchpad (not that I was really expecting to). -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

1 0

How to set macaddr with nmcli
by Robert Moskowitz 03 Aug '18

03 Aug '18

I see my problem. I mis-read what nmcli con mod eth0 mac "02:67:15:00:81:0B" does. It sets HWADDR; which interface to link to, not MACADDR, what MAC address you want for your interface. So I have read the nmcli pages and googled a bit. I cannot find a way to set MACADDR. I suppose I can set HWADDR then use sed to change it to MACADDR, but this seems a real hack. ARM boards do not have assigned MAC addresses. Uboot uses various information to generate a local MAC address. I want finer control of my MAC address for my servers. In the past, I just edited ifcfg-eth0. I am trying now to do it all with nmcli. I thought I had it, but I misread the manual. Any pointers? thanks BTW, I remember setting MAC addresses on 3COM 3C501C boards because the old board died and we had software licensed to specific MAC addresses. So you had to specify your MAC address in the config file. The DEC admin had to do a similar thing if he had to swap out his LAN card (related: read up on why Dr. Comer set ARP timeout to 10min). Then there was that counterfeit 3C503C from Malaysia, all with the same MAC address. Caused havoc on the networks. EVERYONE had to specify their MAC address with those. 3COM did find the plant making these clones and shut them down. But the damage was done to a lot of us.

2 2

How to set macaddr with nmcli
by Robert Moskowitz 03 Aug '18

03 Aug '18

I see my problem. I mis-read what nmcli con mod eth0 mac "02:67:15:00:81:0B" does. It sets HWADDR; which interface to link to, not MACADDR, what MAC address you want for your interface. So I have read the nmcli pages and googled a bit. I cannot find a way to set MACADDR. I suppose I can set HWADDR then use sed to change it to MACADDR, but this seems a real hack. ARM boards do not have assigned MAC addresses. Uboot uses various information to generate a local MAC address. I want finer control of my MAC address for my servers. In the past, I just edited ifcfg-eth0. I am trying now to do it all with nmcli. I thought I had it, but I misread the manual. Any pointers? thanks BTW, I remember setting MAC addresses on 3COM 3C501C boards because the old board died and we had software licensed to specific MAC addresses. So you had to specify your MAC address in the config file. The DEC admin had to do a similar thing if he had to swap out his LAN card (related: read up on why Dr. Comer set ARP timeout to 10min). Then there was that counterfeit 3C503C from Malaysia, all with the same MAC address. Caused havoc on the networks. EVERYONE had to specify their MAC address with those. 3COM did find the plant making these clones and shut them down. But the damage was done to a lot of us.

1 0

ifcfg-link?
by Robert Moskowitz 03 Aug '18

03 Aug '18

This is happening with the Centos7-armv7 image 1804, but I was wondering if it is a broader C7 issue. My image has only 2 ifcfg files: ifcfg-l0 and -link. 'ip a' is listing the ethernet as eth0. ifcfg-link has contains: DEVICE=link BOOTPROTO=dhcp ONBOOT=on I then used nmcli to create my ifcfg-eth0 nmcli con delete eth0 nmcli con add type ethernet con-name eth0 ifname eth0 ip4 192.168.129.11/25 gw4 192.168.129.1 nmcli con mod eth0 ipv4.dns "50.253.254.2 192.168.129.1" nmcli con mod eth0 mac "02:67:15:00:81:0B" I moved the cable to the 192.168.129.1 vlan (which does not have a dhcp server), and nmcli con up eth0 Error: Connection activation failed: No suitable device found for this connection. Oops. ? rebooting did not help. Came up with no address for interface eth0, yet no suitable device. Where would I look to find what may be happening here? I appreciate that this may be specific to armv7 and my Cubieboard2, but then again, it may be something known by other Centos people. Thanks for any help!

1 1

NFS/RDMA connection closed
by admin＠genome.arizona.edu 02 Aug '18

02 Aug '18

Hi, we are having a problem with NFS using RDMA protocol over our FDR10 Infiniband network. I previously wrote to NFS mailing list about this, so you may find our discussion there. I have taken some load off the server which was using NFS for backups, and converted it to use SSH, but we are still having critical problems with NFS clients losing connection to the server, causing the clients to hang and needing a reboot. I wanted to check in here before filing a bug with CentOS. Our setup is a cluster with one head node (NFS server) and 9 compute nodes (NFS clients). All the machines are running CentOS 6.9 2.6.32-696.30.1.el6.x86_64 and using the "Inbox"/CentOS RDMA implementation/drivers (not Mellanox OFED). (We also have other NFS clients but they are using 1GbE for NFS connection and, while they will still hang with messages like "NFS server not responding, retrying" or "timed out", they will eventually recover and don't need a reboot.) On the server (which is named pac) I will see messages like this: Jul 30 18:19:38 pac kernel: svcrdma: failed to send reply chunks, rc=-5 Jul 30 18:19:38 pac kernel: svcrdma: failed to send write chunks, rc=-5 Jul 31 15:03:05 pac kernel: svcrdma: failed to send write chunks, rc=-5 Jul 31 15:09:06 pac kernel: svcrdma: failed to send write chunks, rc=-5 Jul 31 15:16:09 pac kernel: svcrdma: failed to send write chunks, rc=-5 Jul 31 15:23:31 pac kernel: svcrdma: Error -107 posting RDMA_READ Jul 31 15:53:55 pac kernel: svcrdma: failed to send write chunks, rc=-5 Jul 31 16:09:19 pac kernel: svcrdma: failed to send reply chunks, rc=-5 Jul 31 16:09:19 pac kernel: svcrdma: failed to send reply chunks, rc=-5 Previously I had also seen messages like "Jul 11 21:09:56 pac kernel: nfsd: peername failed (err 107)!" however have not seen that in this latest hangup. And on the clients (named n001-n009) I will see messages like this: Jul 30 18:17:26 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff8810674024c0 (stale): WR flushed Jul 30 18:17:26 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff88106638a640 (stale): WR flushed Jul 30 18:19:26 n001 kernel: nfs: server 10.10.11.100 not responding, still trying Jul 30 18:19:36 n001 kernel: nfs: server 10.10.10.100 not responding, timed out Jul 30 18:19:38 n001 kernel: rpcrdma: connection to 10.10.11.100:20049 on mlx4_0, memreg 5 slots 32 ird 16 Jul 30 18:19:38 n001 kernel: nfs: server 10.10.11.100 OK Jul 31 14:42:08 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff8810671f02c0 (stale): WR flushed Jul 31 14:42:08 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff8810677bda40 (stale): WR flushed Jul 31 14:42:08 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff8810677bd940 (stale): WR flushed Jul 31 14:42:08 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff8810671f0240 (stale): WR flushed Jul 31 14:43:35 n001 kernel: rpcrdma: connection to 10.10.11.100:20049 on mlx4_0, memreg 5 slots 32 ird 16 Jul 31 15:01:53 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff881065133140 (stale): WR flushed Jul 31 15:01:53 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff8810666e3f00 (stale): WR flushed Jul 31 15:01:53 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff881063ea0dc0 (stale): WR flushed Jul 31 15:01:53 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff8810677bdb40 (stale): WR flushed Jul 31 15:03:05 n001 kernel: rpcrdma: connection to 10.10.11.100:20049 on mlx4_0, memreg 5 slots 32 ird 16 Jul 31 15:07:07 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff881060e59d40 (stale): WR flushed Jul 31 15:07:07 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff8810677efac0 (stale): WR flushed Jul 31 15:07:07 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff88106638a640 (stale): WR flushed Jul 31 15:07:07 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff8810671f03c0 (stale): WR flushed Jul 31 15:09:06 n001 kernel: rpcrdma: connection to 10.10.11.100:20049 on mlx4_0, memreg 5 slots 32 ird 16 Jul 31 15:16:09 n001 kernel: rpcrdma: connection to 10.10.11.100:20049 closed (-103) Jul 31 15:53:32 n001 kernel: nfs: server 10.10.10.100 not responding, timed out Jul 31 16:08:56 n001 kernel: nfs: server 10.10.10.100 not responding, timed out Jul 30 18:17:26 n002 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff881064461500 (stale): WR flushed Jul 30 18:17:26 n002 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff8810604b2600 (stale): WR flushed Jul 30 18:19:26 n002 kernel: nfs: server 10.10.11.100 not responding, still trying Jul 30 18:19:38 n002 kernel: rpcrdma: connection to 10.10.11.100:20049 on mlx4_0, memreg 5 slots 32 ird 16 Jul 30 18:19:38 n002 kernel: nfs: server 10.10.11.100 OK Jul 31 14:43:35 n002 kernel: rpcrdma: connection to 10.10.11.100:20049 closed (-103) Jul 31 16:08:56 n002 kernel: nfs: server 10.10.10.100 not responding, timed out Similar messages show up on the other clients n003-n009. After these messages on the clients, their load will continually go up (viewable through Ganglia) (I would guess since they are waiting for NFS mount to re-appear). They aren't reachable any longer through SSH and neither can root log in through console via IPMI web applet (just hangs after entering password, may get to prompt eventually but system load is so high), they need to be rebooted through IPMI interface. Here is /etc/fstab on the server, UUID=f15df051-ffb8-408c-8ad2-1987b6f082a2 / ext3 defaults 0 1 UUID=c854ee27-32cf-445d-8308-4e6f1a87d364 /boot ext3 defaults 0 2 UUID=b92a100f-2521-408b-9b15-93671c6ae056 swap swap defaults 0 0 UUID=a8a7b737-25ed-43a7-ae4b-391c71aa8c08 /data xfs defaults 0 2 UUID=d5692ec2-d5dc-4bb8-98d4-a4fb2ff54748 /projects xfs defaults 0 2 /dev/drbd0 /newwing xfs noauto 0 0 UUID=a305f309-d997-43ec-8e4f-78e26b07652f /working xfs defaults 0 2 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 I read that adding "inode64,nobarrier" for the xfs mount options may help? That is something I can try once the server can be rebooted. Here is current mounts on the server, /dev/sda3 on / type ext3 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/sda1 on /boot type ext3 (rw) /dev/sdc1 on /data type xfs (rw) /dev/sdb1 on /projects type xfs (rw) /dev/sde1 on /working type xfs (rw,nobarrier) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) nfsd on /proc/fs/nfsd type nfsd (rw) /dev/drbd0 on /newwing type xfs (rw) Here is /etc/exports on the server, /data 10.10.10.0/24(rw,no_root_squash,async) /data 10.10.11.0/24(rw,no_root_squash,async) /data 150.x.x.192/27(rw,no_root_squash,async) /data 150.x.x.64/26(rw,no_root_squash,async) /home 10.10.10.0/24(rw,no_root_squash,async) /home 10.10.11.0/24(rw,no_root_squash,async) /opt 10.10.10.0/24(rw,no_root_squash,async) /opt 10.10.11.0/24(rw,no_root_squash,async) /projects 10.10.10.0/24(rw,no_root_squash,async) /projects 10.10.11.0/24(rw,no_root_squash,async) /projects 150.x.x.192/27(rw,no_root_squash,async) /projects 150.x.x.64/26(rw,no_root_squash,async) /tools 10.10.10.0/24(rw,no_root_squash,async) /tools 10.10.11.0/24(rw,no_root_squash,async) /usr/share/gridengine 10.10.10.10/24(rw,no_root_squash,async) /usr/share/gridengine 10.10.11.10/24(rw,no_root_squash,async) /usr/local 10.10.10.10/24(rw,no_root_squash,async) /usr/local 10.10.11.10/24(rw,no_root_squash,async) /working 10.10.10.0/24(rw,no_root_squash,async) /working 10.10.11.0/24(rw,no_root_squash,async) /working 150.x.x.192/27(rw,no_root_squash,async) /working 150.x.x.64/26(rw,no_root_squash,async) /newwing 10.10.10.0/24(rw,no_root_squash,async) /newwing 10.10.11.0/24(rw,no_root_squash,async) /newwing 150.x.x.192/27(rw,no_root_squash,async) /newwing 150.x.x.64/26(rw,no_root_squash,async) The 10.10.10.0/24 network is 1GbE and the 10.10.11.0/24 is the Infiniband. The other networks are also 1GbE. Our cluster nodes will normally mount all of these using the Infiniband with RDMA and the computation jobs will normally be using /working which will see the most reading/writing but /newwing, /projects, and /data are also used. Here is an /etc/fstab from the nodes, #NFS/RDMA #10.10.11.100:/opt /opt nfs rdma,port=20049 0 0 #10.10.11.100:/data /data nfs rdma,port=20049 0 0 #10.10.11.100:/tools /tools nfs rdma,port=20049 0 0 #10.10.11.100:/home /home nfs rdma,port=20049 0 0 #10.10.11.100:/usr/local /usr/local nfs rdma,port=20049 0 0 #10.10.11.100:/usr/share/gridengine /usr/share/gridengine nfs rdma,port=20049 0 0 #10.10.11.100:/projects /projects nfs rdma,port=20049 0 0 #10.10.11.100:/working /working nfs rdma,port=20049 0 0 #10.10.11.100:/newwing /newwing nfs rdma,port=20049 0 0 #NFS/IPoIB 10.10.11.100:/opt /opt nfs tcp 0 0 10.10.11.100:/data /data nfs tcp 0 0 10.10.11.100:/tools /tools nfs tcp 0 0 10.10.11.100:/home /home nfs tcp 0 0 10.10.11.100:/usr/local /usr/local nfs tcp 0 0 10.10.11.100:/usr/share/gridengine /usr/share/gridengine nfs tcp 0 0 10.10.11.100:/projects /projects nfs tcp 0 0 10.10.11.100:/working /working nfs tcp 0 0 10.10.11.100:/newwing /newwing nfs tcp 0 0 #NFS/TCP #10.10.10.100:/opt /opt nfs defaults 0 0 #10.10.10.100:/data /data nfs defaults 0 0 #10.10.10.100:/tools /tools nfs defaults 0 0 #10.10.10.100:/home /home nfs defaults 0 0 #10.10.10.100:/usr/local /usr/local nfs defaults 0 0 #10.10.10.100:/usr/share/gridengine /usr/share/gridengine nfs defaults 0 0 #10.10.10.100:/projects /projects nfs defaults 0 0 #10.10.10.100:/working /working nfs defaults 0 0 #10.10.10.100:/newwing /newwing nfs defaults 0 0 Here I can switch between different interfaces/protocols for the NFS mounts. Currently we are trying the IPoIB. We haven't started a cluster job yet so not sure how it will perform. With the NFS/TCP over 1GbE the server/nodes would hang from time to time but still did not crash at least, however was of course slow being limited by 1GbE. We haven't had this problem until recently. I upgraded our cluster to add the two additional nodes (n008 and n009) and we also added more storage to the server (/newwing and /working). The new nodes are AMD EPYC platform whereas the server and the nodes n001-n007 are Intel Xeon platform, not sure if that would cause such a crash. The new nodes were cloned from n001 and only kernel command line and network parameters were changed. The jobs are submitted to the cluster via Sun Grid Engine, and in total there are about 61 jobs that may start at once and open connections to the NFS server... it sounds like it is a system overload, although the load on the server remains low, under 10%, even as it hangs the load may increase to 80%. The server is a few years old but still has 2x 6-core Intel Xeon E5-2620 v2 @ 2.10GHz with 128GB of RAM. Would appreciate your assistance to troubleshoot this critical problem and, if needed, gather the required information to submit a bug to the tracker! Thanks, -- Chandler Arizona Genomics Institute www.genome.arizona.edu

1 1

Desktop lag with CentOS7/Mate and high CPU usage
by James Pearson 02 Aug '18

02 Aug '18

We have noticed significant desktop/UI lag on CentOS7 workstations using Mate when the CPU usage is high - i.e. the mouse pointer lags and moving windows (e.g. terminal windows) become jumpy (not smooth) We didn't see (or notice) this issue with CentOS6/Gnome2 This can easily be shown by running something like 'cpuburn' (https://patrickmn.com/projects/cpuburn/) and moving a mate-terminal window around the screen We can make things 'better' by running CPU intensive apps via 'nice' (without any noticeable performance hit to the CPU intensive app) - but this is a rather messy way of fixing the issue We can also make things better by renice'ing X to a negative nice level However, both these approaches seem wrong to me - as I'm probably missing something straightforward here Does anyone know of any CentOS7/Mate settings that could be used to improve desktop/UI responsiveness with high CPU usage ? Thanks James Pearson

5 5

Screensavers on Centos-7
by Fred Smith 02 Aug '18

02 Aug '18

Hi all! I keep having problems with screensaver(s) on Centos-7. I have in the past liked Xscreensaver, so I've installed it and tried to suppress whatever other screensaver is on the system. Xscreensaver works fine for a day or 20 then quits working. After a lengthy battle I gave up and removed it. I'm now trying mate-screensaver, which does the same thing! when I say "quits working" I mean just that. one night it goes to a black screen (as configured) then a minute or two later the power manager shuts off the screen. The next night it does neither, and forever after. Sometimes after a reboot it'll work again for a while then it starts misbehaving again. First question: Anybody have any similar issues? Anybody have any ideas on what's going on here and what I can do about it? So, not being in a position to reboot, last night I killed mate-screensaver and mate-powermanager, with the hopes the daemons would restart themselves. No such luck. so I tried to figure out what programs I could run to get them started again. So far I'm too stupid to be able to figure that out, as well. Second question: Anybody able to clue me in on how the screensavers and power managers are managed/started? there isn't a systemctl module for it, as far as I can see. if I run mate-screensaver from the commandline (as me, not root) I get no prompt back, so I assume it's running silently, but it also doesn't blank the screen at the specified time. So, thanks in advance for any assistance! -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- "Not everyone who says to me, 'Lord, Lord,' will enter the kingdom of heaven, but only he who does the will of my Father who is in heaven." ------------------------------ Matthew 7:21 (niv) -----------------------------

1 0

C7 Xfce group
by Robert Moskowitz 01 Aug '18

01 Aug '18

I am working with Centos-arm which right now only has the gnome and kde desktops. I am spoiled with using Xfce on all my Fedora systems (MUCH longer battery life on my notebook, for example). I like its simplicity. I see from messages here that mainline C7 does have the Xfce desktop. Can someone give me a list of rpms that make up the group, so I can try starting with the minimal image and see if I can build an Xfce desktop? Meanwhile I am going to put in a request for Xfce on the centos-arm list. thanks

2 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss