Discuss

discuss@lists.centos.org

5 participants
34752 discussions

Kernel:[Hardware Error]:
by Fred Smith 13 Aug '17

13 Aug '17

I had a series of kernel hardware error reports today while I was away from my computer: Message from syslogd@fcshome at Aug 12 10:12:24 ... kernel:[Hardware Error]: MC2 Error: VB Data ECC or parity error. Message from syslogd@fcshome at Aug 12 10:12:24 ... kernel:[Hardware Error]: Error Status: Corrected error, no action required. Message from syslogd@fcshome at Aug 12 10:12:24 ... kernel:[Hardware Error]: CPU:2 (15:2:0) MC2_STATUS[-|CE|MiscV|-|-|-|-|CECC]: 0x98444000010c0176 Message from syslogd@fcshome at Aug 12 10:12:24 ... kernel:[Hardware Error]: cache level: L2, tx: DATA, mem-tx: EV never saw anything like that before. cpu is: $ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 2 model name : AMD FX(tm)-6300 Six-Core Processor stepping : 0 microcode : 0x600084f cpu MHz : 1400.000 cache size : 2048 KB physical id : 0 siblings : 6 core id : 0 cpu cores : 3 apicid : 16 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc art rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb arat cpb hw_pstate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold bmi1 bogomips : 7023.90 TLB size : 1536 4K pages clflush size : 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro six core AMD, above is one of the cores. Any clues to figure out the errors, and/or mitigate? thanks! Fred -- ------------------------------------------------------------------------------- .---- Fred Smith / ( /__ ,__. __ __ / __ : / / / / /__) / / /__) .+' Home: fredex(a)fcshome.stoneham.ma.us / / (__ (___ (__(_ (___ / :__ 781-438-5471 -------------------------------- Jude 1:24,25 ---------------------------------

6 7

what is CodeMeter and why is it running on my CentOS box?
by Fred Smith 13 Aug '17

13 Aug '17

I just stumbled over /var/log/CodeMeter, which contains a number of large log files. I know I'm getting old and forgetful, but I can't remember intentionally installing that package. Yum just says "installed" instead of listing a repo. Looking at codemeter.com, it seems to work with something called a "cm stick". I don't have one, don't want one, and never heard of them. Is there any reason I should be leery of just "yum remove"ing the package? thanks! Fred -- ---- 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) -----------------------------

3 4

ovirt-engine package for oVirt 4.1.x in CentOS offical mirrors disappears?
by C. L. Martinez 13 Aug '17

13 Aug '17

Hi all, I am trying to install oVirt 4.1.x from centos repos but it seems ovirt-engine doesn't exists. But instead, ovirt-hosted-engine-setup exists? Is ovirt-engine package removed? In the official oVirt repos, exists. Thanks.

2 3

Acroread9 crash in CentOS7
by wwp 13 Aug '17

13 Aug '17

Hello, I'm getting a crash with acroread on my CentOS7 (AdobeReader_enu-9.5.5-1.i486). I install the official rpms from ftp://ftp.adobe.com/pub/adobe/reader/unix/, tried 9.5.5, and former v9, v8, v7. /usr/bin/acroread loads well, but when you click a menu, bang. Same if you start acroread w/ a .pdf filename in parameter, the window opens up then crashes. I modified the acroread script to run the binary from within gdb, I get this: Program received signal SIGSEGV, Segmentation fault. 0xf5437cee in compute_face () from /lib/libcairo.so.2 Unfortunately, the system completely hangs when it happens (acroread from gdb) and I must kill acroread from a tty, so I cannot get a more detailed backtrace for now. Is that something somebody here already saw? Regards, -- wwp

3 4

Re: [CentOS] Btrfs going forward, was: Errors on an SSD drive
by Chris Murphy 12 Aug '17

12 Aug '17

Changing the subject since this is rather Btrfs specific now. On Fri, Aug 11, 2017 at 5:41 AM, hw <hw(a)gc-24.de> wrote: > Chris Murphy wrote: >> >> On Wed, Aug 9, 2017, 11:55 AM Mark Haney <mark.haney(a)neonova.net> wrote: >> >>> To be honest, I'd not try a btrfs volume on a notebook SSD. I did that on >>> a >>> couple of systems and it corrupted pretty quickly. I'd stick with >>> xfs/ext4 >> >> >> if you manage to get the drive working again. >>> >>> >> >> Sounds like a hardware problem. Btrfs is explicitly optimized for SSD, the >> maintainers worked for FusionIO for several years of its development. If >> the drive is silently corrupting data, Btrfs will pretty much immediately >> start complaining where other filesystems will continue. Bad RAM can also >> result in scary warnings where you don't with other filesytems. And I've >> been using it in numerous SSDs for years and NVMe for a year with zero >> problems. > > > That´s one thing I´ve been wondering about: When using btrfs RAID, do you > need to somehow monitor the disks to see if one has failed? Yes. The block layer has no faulty device handling, i.e. it just reports whatever problems the device or the controller report. Where md/mdadm and md/LVM have implemented policies for ejecting (setting a device to faulty) a block device. Btrfs does not do that, it'll just keep trying to use a faulty device. So you have to setup something that monitors for either physical device errors, or btrfs errors or both, depending on what you want. > >> On CentOS though, I'd get newer btrfs-progs RPM from Fedora, and use >> either >> an elrepo.org kernel, a Fedora kernel, or build my own latest long-term >> from kernel.org. There's just too much development that's happened since >> the tree found in RHEL/CentOS kernels. > > > I can´t go with a more recent kernel version before NVIDIA has updated their > drivers to no longer need fence.h (or what it was). > > And I thought stuff gets backported, especially things as important as file > systems. There's 1500 to 3000 line changes to Btrfs code per kernel release. There's too much to backport most of it. Serious fixes do get backported by upstream to longterm kernels, but to what degree, you have to check the upstream changelogs to know about it. And right now most backports go to only 4.4 and 4.9. And I can't tell you what kernel-3.10.0-514.10.2.el7.x86_64.rpm translates into, that requires a secret decoder ring near as I can tell as it's a kernel made from multiple branches, and then also a bunch of separate patches. >> Also FWIW Red Hat is deprecating Btrfs, in the RHEL 7.4 announcement. >> Support will be removed probably in RHEL 8. I have no idea how it'll >> affect >> CentOS kernels though. It will remain in Fedora kernels. > > > That would suck badly to the point at which I´d have to look for yet another > distribution. The only one ramaining is arch. > > What do they suggest as a replacement? The only other FS that comes close > is > ZFS, and removing btrfs alltogether would be taking living in the past too > many > steps too far. Red Hat are working on a new user space wrapper and volume format based on md, device mapper, LVM, and XFS. http://stratis-storage.github.io/ https://stratis-storage.github.io/StratisSoftwareDesign.pdf It's an aggressive development schedule and as so much of it is journaling and CoW based I have no way to assess whether it ends up with its own set of problems, not dissimilar to Btrfs. We'll just have to see. But if there are underlying guts in the device-mapper that do things better/faster/easier than Btrfs, the Btrfs devs have said they can hook into device-mapper for these things to consolidate code base, in particular for the multiple device handling. By its own vague time table it will be years before it has "rough ZFS features" and again estimating bootloader support, and to what degree other distros pick up on it, it very well could end up being widely adopted, or it could be a Red Hat only thing in practice. Canonical appears to be charging ahead with OpenZFS included by default out of the box (although not for rootfs yet I guess), and that has an open ended and possibly long window before legal issues get tested. But this is by far the most cross platform solution: FreeBSD, Illumos, Linux, macOS. And ZoL has RHEL/CentOS specific packages. But I can't tell you for sure what ZoL's faulty device behavior is either, whether it ejects faulty or flaky devices and when, or if like Btrfs is just tolerates it. The elrepo.org folks can still sanely set CONFIG_BTRFS_FS=m, but I suspect if RHEL unsets that in RHEL 8 kernels, that CentOS will do the same. -- Chris Murphy

7 13

CentOS7 gnome apps look in Mate
by wwp 12 Aug '17

12 Aug '17

Hello there, using CentOS7 with Mate desktop.. when I run gnome apps, the mate look doesn't apply to them. Say that my mate theme is dark. I've even logged in my user in Gnome, set a dark theme too. But back to Mate, Gnome apps are still light-grey (default theme). Is there a gnome-settings daemon to start or what? Tk and Qt apps get the right (dark) theme automagically, BTW. Regards, -- wwp

1 0

Errors on an SSD drive
by Robert Moskowitz 11 Aug '17

11 Aug '17

I am building a new system using an Kingston 240GB SSD drive I pulled from my notebook (when I had to upgrade to a 500GB SSD drive). Centos install went fine and ran for a couple days then got errors on the console. Here is an example: [168176.995064] sd 0:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [168177.004050] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 01 04 68 b0 00 00 08 00 [168177.011615] blk_update_request: I/O error, dev sda, sector 17066160 [168487.534510] sd 0:0:0:0: [sda] tag#17 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [168487.543576] sd 0:0:0:0: [sda] tag#17 CDB: Read(10) 28 00 01 04 68 b0 00 00 08 00 [168487.551206] blk_update_request: I/O error, dev sda, sector 17066160 [168787.813941] sd 0:0:0:0: [sda] tag#20 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [168787.822951] sd 0:0:0:0: [sda] tag#20 CDB: Read(10) 28 00 01 04 68 b0 00 00 08 00 [168787.830544] blk_update_request: I/O error, dev sda, sector 17066160 Eventually, I could not do anything on the system. Not even a 'reboot'. I had to do a cold power cycle to bring things back. Is there anything to do about this or trash the drive and start anew? Thanks

12 30

BIND 9.9 RRL
by Mark Haney 11 Aug '17

11 Aug '17

I can't seem to find anything clear on this, but is the C7 version of BIND 9.9 built with Request Rate Limiting? -- Mark Haney Network Engineer at NeoNova 919-460-3330 option 1 mark.haney(a)neonova.net www.neonova.net

3 3

gluster-containers with CentOS and Gluster 3.11
by Christopher Schmidt 10 Aug '17

10 Aug '17

Hi, I am trying to get a glusterfs container based on CentOS and GlusterFS version 3.11 (https://github.com/gluster/gluster-containers) But there is no centos-release-gluster311 package, right? Or have I missed something? How can I yum install version 3.11? best Christopher

1 0

Centos7 - Mate : screensaver troubles after Freeipa-config
by johan.vermeulen7＠telenet.be 10 Aug '17

10 Aug '17

Hello All, these days one of my tasks is connecting some Centos7 laptops to Freeipa, also running on Centos7. After doing that, some users report nog being able to unlock their screens. Only after reboot are they able to login again. I see this em in /var/log/secure: Aug 10 13:34:37 **** mate-screensaver-dialog: pam_sss(mate-screensaver:auth): authentication failure; logname= uid=382900663 euid=382900663 tty=:0.0 ruser= rhost= user=***** Aug 10 13:34:37 **** mate-screensaver-dialog: pam_sss(mate-screensaver:auth): received for user ******: 17 (Fout tijdens het instellen van legitimatiegegevens van gebruiker) Aug 10 13:34:37 **** mate-screensaver-dialog: gkr-pam: the password for the login keyring was invalid. Out of the 50 people or so I now have connected to Freeipa, I received some 5 reports. All users are on fully updated Centos7 machines configured with epel-provided Mate desktop. I see a lot of these problems when googling this, but none in Centos. Help would be very much appreciated. Greetings, J.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss