Discuss

discuss@lists.centos.org

9 participants
34745 discussions

Problem installing glibc-devel.i686 on CentOS 7
by Alfred von Campe 28 Aug '17

28 Aug '17

The following transcript should provide all the necessary details: # yum install glibc-devel-2.17-157.el7.i686 Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * base: mirrors.gigenet.com * epel: mirrors.xmission.com * extras: mirrors.gigenet.com * updates: ftp.osuosl.org Resolving Dependencies --> Running transaction check ---> Package glibc-devel.i686 0:2.17-157.el7 will be installed --> Processing Dependency: glibc-headers = 2.17-157.el7 for package: glibc-devel-2.17-157.el7.i686 --> Processing Dependency: glibc = 2.17-157.el7 for package: glibc-devel-2.17-157.el7.i686 --> Finished Dependency Resolution Error: Package: glibc-devel-2.17-157.el7.i686 (base) Requires: glibc-headers = 2.17-157.el7 Installed: glibc-headers-2.17-157.el7_3.5.x86_64 (@updates) glibc-headers = 2.17-157.el7_3.5 Available: glibc-headers-2.17-157.el7.x86_64 (base) glibc-headers = 2.17-157.el7 Available: glibc-headers-2.17-157.el7_3.1.x86_64 (updates) glibc-headers = 2.17-157.el7_3.1 Available: glibc-headers-2.17-157.el7_3.2.x86_64 (updates) glibc-headers = 2.17-157.el7_3.2 Available: glibc-headers-2.17-157.el7_3.4.x86_64 (updates) glibc-headers = 2.17-157.el7_3.4 Error: Package: glibc-devel-2.17-157.el7.i686 (base) Requires: glibc = 2.17-157.el7 Installed: glibc-2.17-157.el7_3.5.i686 (@updates) glibc = 2.17-157.el7_3.5 Available: glibc-2.17-157.el7.i686 (base) glibc = 2.17-157.el7 Available: glibc-2.17-157.el7_3.1.i686 (updates) glibc = 2.17-157.el7_3.1 Available: glibc-2.17-157.el7_3.2.i686 (updates) glibc = 2.17-157.el7_3.2 Available: glibc-2.17-157.el7_3.4.i686 (updates) glibc = 2.17-157.el7_3.4 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest I tried the two suggesting above to no avail. Has anyone else been able to install glib-devel.i686 successfully on CentOS 7? Alfred

2 2

CentOS 7 (1708) CR content
by Johnny Hughes 28 Aug '17

28 Aug '17

We have released the CR repo with what will be the CentOS 7 (1708) content. Please see this link for details: http://bit.ly/2w7eIe6 Release Notes: http://bit.ly/2is4Kku Announcements: http://bit.ly/2viRAIl Special thanks, as always, to our community based QA team. We could never get this stuff done without them. You guys and gals ROCK! Enjoy ! Thanks, Johnny Hughes

4 3

xorg-x11-drv-intel CR update breaks X server for Intel HD520
by milos.blazevic 28 Aug '17

28 Aug '17

Hi, As a consequence of rolling out CR updates on Latitude E7470 (Skylake chipset), X would no longer start until I rolled back all of the xorg-\* packages. And to be more precise, looks like the culprit is xorg-x11-drv-intel: https://bugzilla.redhat.com/show_bug.cgi?id=1445583 as the CR package release version matches the one mentioned in Comment #2, in the regression context. I've already submitted a bug report: https://bugs.centos.org/view.php?id=13717 so I just wanted to bring this issue to attention of anyone who's running this chipset/VGA. Thanks, Milos.

2 3

CentOS 7, nfs & autofs
by m.roth＠5-cent.us 28 Aug '17

28 Aug '17

Hi, folks, We've been seeing this almost since we started rolling out C7: for no apparent reason, it will automount *everyone* in /etc/auto.home, even though most of those folks not only have never logged onto that server or workstation, but are not allowed to. We distribute to all our systems the same auto.home, and we certainly don't want to customize it for nearly 200 systems, we like it under central control. Any clues as to why it does this? Note that kill -USR1 <autofs pid) makes the unused ones umount in a minute or two. mark

1 0

anybody else had this problem since the CR updates?
by Fred Smith 27 Aug '17

27 Aug '17

I'm running Mate on my C7 boxen, a desktop and a netbook.\ Mate comes from epel, so it's probably not a CentOS problem, but lemme ask here in case anybody else has seen it: some tools (nm, pavucontrol, and possibly others I haven't noted down) no longer have the correct formatting on screen. there are no backgrounds, i.e., backgrounds that define areas of the screen by shading or borders. clickable text tends to be jammed together. pavucontrol has no sliders for any of the level controls. an example, at the top of pavucontrol it has no visible tabs, just the text: PlaybackRecordingOutput DevicesInput DevicesConfiguration spaced as shown. they work when you click them, however. but since none of the sliders are visible (and I can't find 'em by randomly poking around with the mouse pointer) it's a little hard to use. :( If I can find a place to post some screenshots, I'll try the posting a note on the epel IRC. Thanks in advance! -- ------------------------------------------------------------------------------- Under no circumstances will I ever purchase anything offered to me as the result of an unsolicited e-mail message. Nor will I forward chain letters, petitions, mass mailings, or virus warnings to large numbers of others. This is my contribution to the survival of the online community. --Roger Ebert, December, 1996 ----------------------------- The Boulder Pledge -----------------------------

3 4

Re: [CentOS] Vmware No Longer Build on the New 693.1.1 kernel
by pro alias 27 Aug '17

27 Aug '17

>Build error "Failed to build vmnet. Failed to execute the build command." >when trying to compile vmnet.Not one other shred of data in the logs >telling me WHY it failed to build. >I have rolled back to the last 514 kernel to use vmware but I >don't want to recompile vmware because of the liability of not being able to >get it running again if the compilation problem is caused by one of the >other updates. >Anyone else found vmware problems after CR update?? The answer is to recompile the source tarball with a patch which appeared at: https://communities.vmware.com/message/2686431?tstart=0#2686431 generously provided by https://communities.vmware.com/people/dariusd . Tried it and it works swimmingly. Whew!

1 0

Vmware No Longer Build on the New 693.1.1 kernel
by pro alias 27 Aug '17

27 Aug '17

Build error "Failed to build vmnet. Failed to execute the build command." when trying to compile vmnet.Not one other shred of data in the logs telling me WHY it failed to build. I have rolled back to the last 514 kernel to use vmware but I don't want to recompile vmware because of the liability of not being able to get it running again if the compilation problem is caused by one of the other updates. Anyone else found vmware problems after CR update??

1 0

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

27 Aug '17

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

1 0

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

26 Aug '17

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

3 5

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

26 Aug '17

Hi! Thanks to some of you I got autofs set up on my C7 netbook for mounting local cifs filesytems. Now I want to do something on my C7 desktop machine, that seems to me to be a little different, and I"m not sure how to do it. I have an external RAID1 box that attaches via USB. It is/will be nearly always /dev/sdc, but being USB I can't guarantee that it will always be found there. accordingly, in my /etc/fstab I have an entry that mounts it via its UUID: UUID=09bfc97a-8db2-46de-b4dd-427da19b114 /mnt/backup xfs defaults,noauto,users 0 2 and I'm wondering how to specify that in an autofs recipe instead... If doing cifs mounts, /etc/auto.master may contain this line: /mymount /etc/auto.mymount then there would be a file /etc/auto.mymount that contains a line similar to this: winbox -fstype=cifs,rw,noperm,user=sushi,pass=yummy ://winbox/getme so, in my case, the USB drive contains an xfs filesystem. would I do something like this: in /etc/auto.master: backup /etc/auto.backup and in /etc/auto.backup backup -fstype=xfs,defaults,noauto,users :UUID=09bfc97a-8db2-46de-b4dd-427da19b114 Would that be expected to work, or am I all overlooking something obvious? Thanks in advance for your advice! Fred -- ------------------------------------------------------------------------------- Under no circumstances will I ever purchase anything offered to me as the result of an unsolicited e-mail message. Nor will I forward chain letters, petitions, mass mailings, or virus warnings to large numbers of others. This is my contribution to the survival of the online community. --Roger Ebert, December, 1996 ----------------------------- The Boulder Pledge -----------------------------

2 10

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