Discuss

discuss@lists.centos.org

8 participants
34745 discussions

[OT] EPEL update?
by isdtor 09 Dec '18

09 Dec '18

Hi, OT for this list, but maybe I can get some pointers - how hard is it to get some packages updated in EPEL? The project web site sends you from link to link, and the ML web interface is horrible. No interest here to become a package maintainer or regular contributor. I have taken it upon myself to rebuild MATE from Fedora 29, seeing that the current EPEL-7 packages are four revisions behind. Also updated a few packages to their latest upstream version.

7 10

rescue - UEFI revert to BIOS boot - how?
by lejeczek 08 Dec '18

08 Dec '18

hi guys I have a box on which UEFI boot has gone haywire and instead of boot it power the box down, that is before even going to grub2. (displays some error message) I if change to BIOS boot then I can start Centos' rescue - my question is: how can I rescue, re-build grub so it would boot from tradition BIOS? many thanks, L.

4 3

unable to stop drive timeout was reached
by Frank Cox 08 Dec '18

08 Dec '18

On a fully updated Centos 7 system with the Mate desktop, I've just encountered what appears to be a bug in.. something? I connected a USB portable hard drive and copied some files onto it, then right-clicked the icon and "Safely remove drive". After about thirty seconds I then unplugged the portable hard drive and removed it. Several minutes later a window appeared on my desktop that said "unable to stop drive timeout was reached". This is new; I've never seen it before so I think it's related to the last updates in some way. Google finds several mentions of this error message, here is one example: https://forum.manjaro.org/t/usb-drive-safely-remove-causes-delayed-error-me… -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

1 0

// RESEND // 7.6: Software RAID1 fails the only meaningful test
by Benjamin Smith 08 Dec '18

08 Dec '18

(Resend: message didn't show, was my original message too big? Posted one of the output files to a website to see) The point of RAID1 is to allow for continued uptime in a failure scenario. When I assemble servers with RAID1, I set up two HDDs to mirror each other, and test by booting from each drive individually to verify that it works. For the OS partitions, I use simple partitions and ext4 so it's as simple as possible. Using the CentOS 7.6 installer (v 1810) I cannot get this test to pass in any way, with or without LVM. Using an older installer, it works fine (v 1611) and I am able to boot from either drive but as soon as I do a yum update then it fails. I think this may be related or the same issue reported in "LVM failure after CentOS 7.6 upgrade" since that also involves booting from a degraded RAID1 array. This is a terrible bug. See below for some (hopefully) useful output while in recovery mode after a failed boot. ### output of fdisk -l Disk /dev/sda: 500.1 GB, 500107862016 bytes, 976773168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x000c1fd0 Device Boot Start End Blocks Id System /dev/sda1 2048 629409791 314703872 fd Linux raid autodetect /dev/sda2 * 629409792 839256063 104923136 fd Linux raid autodetect /dev/sda3 839256064 944179199 52461568 fd Linux raid autodetect /dev/sda4 944179200 976773119 16296960 5 Extended /dev/sda5 944181248 975654911 15736832 fd Linux raid autodetect ### output of cat /prod/mdstat Personalities : md126 : inactive sda5[0](S) 15727616 blocks super 1.2 md127 : inactive sda2[0](S) 104856576 blocks super 1.2 unused devices: <none> ### content of rdosreport.txt It's big; see http://chico.benjamindsmith.com/rdsosreport.txt

2 2

Can't configure GDM after update to CentOS 7.6
by Nicolas Kovacs 07 Dec '18

07 Dec '18

Hi, It looks like the upgrade to CentOS 7.6 has been unusually disruptive with the GNOME desktop version bump and a series of moving targets under the hood. The result is some wreckage at my client's desktop installations, which I've been busy to repair since yesterday. First things first. I have a custom configuration of GDM, which consists mainly of two things. 1. Display my company's logo instead of the CentOS logo. 2. Disable the user list (since I have about 100 users here). Until CentOS 7.5, here's what I did. 1. Create a file /etc/dconf/profile/gdm : user-db:user system-db:gdm file-db:/usr/share/gdm/greeter-dconf-defaults 2. Create a file /etc/dconf/db/gdm.d/01-logo : [org/gnome/login-screen] logo='/usr/share/pixmaps/microlinux-logo.png' 3. Create a file /etc/dconf/db/gdm.d/00-login-screen : [org/gnome/login-screen] disable-user-list=true 4. Update dconf : # dconf update Now with CentOS 7.6 this doesn't work anymore. The /etc/dconf/db/gdm.d directory is nowhere to be found, and I'm currently mildly cursing the GNOME developers' (and Red Hat's) policy of releasing moving targets. Until now, the whole purpose of Enterprise Linux seemed to be low-risk updates. </rant> I've documented the whole GDM customization process until CentOS 7.5 in a short article on my french blog : * https://blog.microlinux.fr/gdm-centos/ Any idea how I can configure GDM with the new version ? 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

7 8

DNS bind - use of /etc/named directory
by John Horne 07 Dec '18

07 Dec '18

Hello, For many years we have modified the '/etc/named.conf' file to include local settings. The disadvantage with this is of course that when bind is updated, it creates an '/etc/named.conf.rpmnew' file. We then have to determine what is new, and apply the relevant changes to our modified named.conf file. There is, however, an '/etc/named' directory which I assumed was for local configuration settings. The main '/etc/named.conf' file makes no mention of this directory, so (I suspect) any config files in '/etc/named' would, by default, just be ignored. As far as I can tell we could put our local configuration settings into a file in '/etc/named', but we would then, once again, have to modify '/etc/named.conf' to tell it to include config files in '/etc/named'. We would then be back at square one in that any bind update would create an 'rpmnew' file. I admit I haven't actually tested this, but has anyone used the '/etc/named' directory and not had to modify the main '/etc/named.conf' file? I suspect, if not, then this should be raised as a possible bug since it would make sense not to have to modify the main configuration file at all. Thanks, John. -- John Horne | Senior Operations Analyst | Technology and Information Services University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK ________________________________ [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass> This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, University of Plymouth accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. University of Plymouth does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.

2 4

New CentOS7 Install Yum will not work
by Ed Morrison 07 Dec '18

07 Dec '18

Hi Everyone: I have been fighting this all morning. I did a new (several) installs of CentOS7. Yum will not update the system. I have disabled ipv6, set yum.conf to use IPv4 only, disabled firewalld, disabled selinux, used both static ip and dhcp for network connectivity. I can ping any where on the Internet, including the mirrors, DNS works and ensured the base URL line was uncommented. Any help would be appreciated. Thanks, Ed This is the latest error I am seeing: [root@localhost ~]# yum check-update Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was 14: curl#7 - "Failed connect to mirrorlist.centos.org:80; Operation now in progress" Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=extras&infra=stock error was 14: curl#7 - "Failed connect to mirrorlist.centos.org:80; Operation now in progress" One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> or subscription-manager repos --disable=<repoid> 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true Cannot find a valid baseurl for repo: extras/7/x86_64

2 2

CentOS-announce Digest, Vol 166, Issue 2
by centos-announce-request＠centos.org 07 Dec '18

07 Dec '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. Announcing the release of Gluster 5 on CentOS Linux 7 x86_64 (Niels de Vos) 2. CEBA-2018:3764 CentOS 6 autofs BugFix Update (Johnny Hughes) 3. CESA-2018:3760 Important CentOS 6 ghostscript Security Update (Johnny Hughes) 4. CEBA-2018:3763 CentOS 6 kernel BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 5 Dec 2018 19:24:49 +0100 From: Niels de Vos <ndevos(a)redhat.com> To: centos-announce(a)centos.org Subject: [CentOS-announce] Announcing the release of Gluster 5 on CentOS Linux 7 x86_64 Message-ID: <20181205182449.GL4068@ndevos-x270> Content-Type: text/plain; charset="us-ascii" I am happy to announce the General Availability of Gluster 5 for CentOS 7 on x86_64. These packages are following the upstream Gluster Community releases, and will receive monthly bugfix updates. Gluster 5 is expected to receive updates until the end of October 2019. The maintanance and release schedule can be found at: https://www.gluster.org/community/release-schedule/ Users of CentOS 7 can now simply install Gluster 5 with only these two commands: # yum install centos-release-gluster # yum install glusterfs-server The centos-release-gluster package is delivered via CentOS Extras repos. This contains all the metadata and dependency information, needed to install Gluster 5. The actual package that will get installed is centos-release-gluster5. Users of Gluster 4.1 can stay on that release until June 2019. Users of Gluster 4.0 and earlier will need to manually upgrade by uninstalling the centos-release-gluster-legacy package, and replacing it with either the Gluster 5 or 4.1 version. Additional details about the upgrade process are linked in the announcement from the Gluster Community: https://lists.gluster.org/pipermail/announce/2018-October/000115.html We have a quickstart guide specifically built around the packages are available, it makes for a good introduction to Gluster and will help get you started in just a few simple steps, this quick start is available at https://wiki.centos.org/SpecialInterestGroup/Storage/gluster-Quickstart More details about the packages that the Gluster project provides in the Storage SIG is available in the documentation: https://wiki.centos.org/SpecialInterestGroup/Storage/Gluster The centos-release-gluster* repositories offer additional packages that enhance the usability of Gluster itself. Utilities and tools that were working with previous versions of Gluster are expected to stay working fine. If there are any problems, or requests for additional tools and applications to be provided, just send us an email with your suggestions. The current list of packages that is (planned to become) available can be found here: https://wiki.centos.org/SpecialInterestGroup/Storage/Gluster/Ecosystem-pkgs We welcome all feedback, comments and contributions. You can get in touch with the CentOS Storage SIG on the centos-devel mailing list (https://lists.centos.org ) and with the Gluster developer and user communities at https://www.gluster.org/mailman/listinfo , we are also available on irc at #gluster on irc.freenode.net, and on twitter at @gluster . Cheers, Niels de Vos Storage SIG member & Gluster maintainer

1 0

CVE-2018-1002105
by Adam Bishop 07 Dec '18

07 Dec '18

There was a critical vulnerability in Kubernetes published earlier in the week - CVE-2018-1002105. The vulnerability has been patched both the upstream project and by TUV, but the fix doesn't seem to have made it into the CentOS OpenShift build for 3.11: http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/ The fixed version is 3.11.43, version on the mirror is 3.11.0. I'm not 100% certain of the support state of OpenShift in CentOS as it's maintained by a SIG, so what needs to happen to get the vulnerability patched for CentOS? Adam Bishop gpg: E75B 1F92 6407 DFDF 9F1C BF10 C993 2504 6609 D460 jisc.ac.uk Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800. Jisc Services Limited is a wholly owned Jisc subsidiary and a company limited by guarantee which is registered in England under company number 2881024, VAT number GB 197 0632 86. The registered office is: One Castle Park, Tower Hill, Bristol BS2 0JA. T 0203 697 5800.

1 0

invalid base url
by Jerry Geis 07 Dec '18

07 Dec '18

I have a number of updates to C7.6 but now I am getting Cannot find a valid baseurl for repo base/7/x86_64 Did something happen? What do I do ? This machine has internet access and appears to resolve other sites. I get a list when trying to access mirrorlist... Thanks, Jerry

2 1

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