Discuss August 2018

discuss@lists.centos.org

80 participants
76 discussions

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 16 Aug '18

16 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss August 2018