Discuss October 2017

discuss@lists.centos.org

128 participants
113 discussions

nfsvers and nfs-utils-1.3.0-0.48.el7
by Paul Heinlein 12 Oct '17

12 Oct '17

We encountered a weird problem today, and I thought some of you might like to hear the solution. The underlying change was listed in the 7.4 changelog, so it's not a bug, but it may drive you buggy. The majority of our HPC cluster nodes run CentOS 7, though the exact patch levels vary from node to node. None is older than 7.3, but a few newer nodes were kickstarted right to 7.4. The problem was that our mounts of Isilon NFS exports were failing randomly among the nodes. Routing was fine. Network connectivity was fine. The short answer is that the default in 7.4, and I think in the nfs-utils-1.3.0-0.48.el7 package in particular, has changed. While NFS v4.0 was the default up to 7.3, the 7.4 protocols are subtly different: 1. Try NFS v4.1 first 2. Fail down to NFS v3 3. Fail down to NFS v2 The problem is that our Isilon works with NFS v4.0, not 4.1, but 4.0 is not in the fail-down path. The short-term answer is to specify nfsvers=4.0 in our autofs configuration files, which works like a charm. Like I said, this was an announced change, but the implications escaped us until now. So this little writeup is just for the record. -- Paul Heinlein heinlein(a)madboa.com 45°38' N, 122°6' W

2 1

yum-cron hourly errors
by John Ratliff 12 Oct '17

12 Oct '17

I receive messages like this from cron often. Not every hour, and not consistently between the servers running CentOS, but at least two per day. Is this normal? /etc/cron.hourly/0yum-hourly.cron: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was 14: HTTP Error 403 - Forbidden Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=extras&infra=stock error was 14: HTTP Error 403 - Forbidden Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=updates&infra=stock error was 14: HTTP Error 403 - Forbidden

1 0

CentOS-announce Digest, Vol 152, Issue 4
by centos-announce-request＠centos.org 12 Oct '17

12 Oct '17

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-2017:2882 Moderate CentOS 7 httpd Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 11 Oct 2017 20:46:20 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:2882 Moderate CentOS 7 httpd Security Update Message-ID: <20171011204620.GA63152(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:2882 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2017:2882 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 41421bbfa809cd1fea427ffd689e2caa4d92643aec1094ce7c2271702f19480a httpd-2.4.6-67.el7.centos.5.x86_64.rpm 2814b75b35bf8fed0fd12033d1fc0b6203a60926646fb3151cbda49260175522 httpd-devel-2.4.6-67.el7.centos.5.x86_64.rpm 2156dda1f88729bbf47dcd000911942d122a0797d55fcfdcb65e1ead2e3601e8 httpd-manual-2.4.6-67.el7.centos.5.noarch.rpm d1152bdf63709d455dbba51fd7aafc4b69cb45dd48073edfe4b337157a3974b4 httpd-tools-2.4.6-67.el7.centos.5.x86_64.rpm 0e4029a1ac0b75e2363c7803282e5230cdf4260122ffbf2daeaec955a94f71ac mod_ldap-2.4.6-67.el7.centos.5.x86_64.rpm fe94afba530fb88bfbe1bd782afe61dd69212c30920d14574099468a2ce76844 mod_proxy_html-2.4.6-67.el7.centos.5.x86_64.rpm cae78de9a2bb32f12af2bf7895cc27c2f95119787b7139b5ab0ea018b6738113 mod_session-2.4.6-67.el7.centos.5.x86_64.rpm 829d9f95fafbdc31c0e14180b688f27beb329c00961c5340e9609b9789070ea6 mod_ssl-2.4.6-67.el7.centos.5.x86_64.rpm Source: 5cc7d1292f22dc068f166c8e722456158f9856c29a71887581394a99a4615ab0 httpd-2.4.6-67.el7.centos.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 152, Issue 4 ***********************************************

1 0

Seagate's firmware flash until in Centos 7.x - does it work?
by lejeczek 12 Oct '17

12 Oct '17

hi fellas I wonder if any of you use(d) dl_sea_fw to flash SAS drive? I try dl_sea_fw-0.2.3_64 to flash ST32000444SS but it fails: $ ./linux\ cli\ tools/dl_sea_fw-0.2.3_64 -m ST32000444SS -f firmware/MU-SAS-0008.LOD -d /dev/sg59 ================================================================================ Seagate Firmware Download Utility v0.2.3 Build Date: Jan 9 2013 Copyright (c) 2012 Seagate Technology LLC, All Rights Reserved Thu Oct 12 11:33:05 2017 ================================================================================ Downloading file firmware/MU-SAS-0008.LOD to /dev/sg59 send_io: Success ! FW Download FAILED Would you have some advice? many thanks, L.

1 0

I do not love thee, kernel-3.10.0-693.2.2.el7.x86_64
by m.roth＠5-cent.us 12 Oct '17

12 Oct '17

I've been having a lot of issues with video, for example. However, this one... I have a user with a Dell R730. I install kernel and kernel devel, and the rest of the full update, and rebooted. Nope. 100% kernel panic, right around the time it switches root. I even rebuilt the initramfs, nope. And speaking of kernel panics, has *anyone* ever considered that all the data dumped to the console during one results in NOT BEING ABLE TO READ ANYTHING BUT THE LAST 24 or less, mostly less, lines? mark, frustrated, removed that kernel

4 4

Flame war police
by Andrew Holway 11 Oct '17

11 Oct '17

Hiya everyone, Is there a way to disable a thread that has degenerated into flaming? The recent "discussion" on /var/run descended into some quite nasty places and perhaps a lid should have been put on it. This seems to happen every few weeks and is somewhat embarrassing when I'm trying to persuade people of the "active and friendly Centos community" It was a shame that no one actually read past the belligerence his original post enough to come up with a solution. It was quite clearly a problem with third party packages not coming with SELinux policies. Cheers, Andrew

6 7

Location of grub.conf etc. with UEFI boot (CentOS 6)
by Toralf Lund 11 Oct '17

11 Oct '17

Hi, What's the proper/normal way of setting up GRUB for a CentOS 6 installation that boots using UEFI? I've recently set up such a system, but for technical reasons I mentioned in an earlier post, I booted in "legacy" mode during installation, which meant I didn't get the correct UEFI boot configuration, and had to set it up subsequently "by hand". I've managed to get the system to start up, but I had to place grub.conf under "/EFI/redhat/" on the EFI partition; without it, the system only boots into the grub shell. Is this normal, or is GRUB supposed to be able to find grub.conf under /boot? If not, how are updates on kernel upgrade etc. supposed to get done? Do I need a symlink from /boot/grub/grub.conf to the EFI parition? And will grub-install help with some of this? I haven't dared to try it, as I'm afraid it may break everything because it assumes an "MBR" configuration, or something. Also, how is /boot supposed to be set up anyway? Will it still normally be configured as a separate partition? Yeah, I know, I could re-install in UEFI mode (as I think I know how now), but I'm hoping you will save me from the effort. I also have a workable system anyhow, but kernel upgrades could be an issue, and it's nice to know the "right" way of setting up. Thanks, -Toralf

2 1

How can I disable at-spi-bus-launcher
by Frank Cox 11 Oct '17

11 Oct '17

I have a laptop that hangs up on shutdown saying that at-spi-bus-launcher is still running. Since I have no use for at-spi-bus-launcher anyway, I would like to get rid of it, but attempting to remove the at-spi2-core rpm wants to remove 99% of my desktop as well. The only way that I can see to get rid of it is to make /usr/libexec/at-spi-bus-launcher non-executable, but that's a pretty horrible hack. Can I permanently disable it without resorting to that? -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

2 1

yum security update issue
by Thomas Roth 10 Oct '17

10 Oct '17

Hi all, I have used http://cefs.steve-meier.de/ plus https://github.com/vmfarms/generate_updateinfo to insert some security-information into my os-updates - mirror. This seems to work, but only partially. On my 7.4 test server, > yum --security -v check-update gives me dnsmasq, nss, nss-sysinit and nss-tools as the packages to install. The nss-packages are all of "severity = Important" But there are more of this type of packages, e.g. emacs. The centos-announce mails as well as the errata of Steve Meier as well as the generated updateinfo.xml all contain "CESA-2017:2771 Important CentOS 7 emacs Security Update" Just like the mentioned nss-packages, emacs is also labeled "severity = Important". But yum doesn't like it ;-( The output of > yum --security -v check-update tells me more, of course: --> 1:emacs-24.3-20.el7_4.x86_64 from os-updates excluded (updateinfo) Neither dnsmasq nor the nss-packages are listed, in particular not as excluded -? And at the end it says > Nothing matches emacs.x86_64 1:24.3-20.el7_4 from update Btw, "yum info emacs" lists the installed and wanted emacs versions correctly. What did I miss? Regards, Thomas

2 1

Lock-up during boot when Logitech unifying receiver is connected (UEFI problem?)
by Toralf Lund 10 Oct '17

10 Oct '17

Hi, I've got a bit of an issue after I switched to a new laptop for my CentOS 6.9 installation: I'm using a Logitech cordless keyboard and mouse that communicate with the system via a so-called "unifying receiver". If this unit (a small USB thingummy) is connected when I try to boot the system, it locks up completely. This happens before the GRUB screen is displayed. The set-up otherwise works just fine, i.e. I notice no ill effects of connecting the receiver once the system is up-and-running. I did not not have this problem on my old laptop, which ran a more or less identical Linux configuration (I cloned the partition.) Something that's new, though, is that I now have GPT partitions and boot using UEFI, where the old PC used traditional BIOS. I also had a hard time installing in the first place because I got similar issues when trying to boot the installer as well as "stand-alone" tools like "parted" and "clonezilla" from USB sticks, and these seemed to be restricted to GPT and UEFI, too. (I didn't realise at the time that the unifying receiver was the problem, so I ended up installing via "legacy" boot.) Has anyone else seen this? Any suggestions? I can live with the problem, I guess, but having to unplug and reconnect the unit every time I boot is a bit annoying. I've tried connecting the unit to several different USB ports, with the same result. I've also searched for firmware updates, but didn't find anything. TIA, - Toralf

2 1

← Newer
1
...
5
6
7
8
9
10
11
12
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss October 2017