Discuss August 2019

discuss@lists.centos.org

82 participants
60 discussions

NFS Server on Centos 7.6.1810 dying without reason
by Erick Perez - Quadrian Enterprises 07 Sep '19

07 Sep '19

Good morning, in order to post proper documentation, what logs (or log level) do I need to troubleshoot a Centos 7.6.1810 3.10.0-957.27.2.el7.x86_64 tha tis running a NFS server on top LVM on top of XFS on top of VDO on top of MDAM on a 6 SSD disk RAID6 ? This physical NFS server is servign 2 NFS v4.2 shares to 2 physical KVM virtualization hosts. When remote NFS clients start doing intensive stuff (massive writes) , the NFS server crashes and sometimes make the Linux server reboot. form KVM side this is all I get: hvm002 kernel: nfs: server 10.10.10.2 not responding, timed out thanks --------------------- Erick ---------------------

2 2

CUPS job handling
by hw 06 Sep '19

06 Sep '19

Hi, is it somehow possible to make CUPS automatically redirect jobs, and following jobs, away from printers which can not print them to other printers that can print them until the printers that couldn't print them are again able to print them? Like I have a bunch of label printers which are all the same, and all of which are prone to run out of labels or out of ribbon every now and then. It can take hours or even days before someone can refill a printer. Hence it would be very useful if CUPS could be told something like "if printer A doesn't print, move its current job to printer B and divert all new jobs sent to A to printer B instead until A prints again". What exactly happens when a printer that is member of a class can not print a job that was sent to the class? Will the unprintable job be automatically moved to another member of the same class, or will it only be aborted and never printed? With a class of two printers and one of them running out of labels, /var/log/cups/error_log only holds: ... [Job 174733] Stopping unresponsive job. What does this mean? Has the job been printed or not? Has it been printed after I refilled the printer?

5 6

CentOS 8 will be released soon?
by Turritopsis Dohrnii Teo En Ming 05 Sep '19

05 Sep '19

Good afternoon from Singapore, According to the CentOS 8 build timeline, everything has been completed except release work. Does this mean CentOS 8 will be released soon? https://wiki.centos.org/About/Building_8 -----BEGIN EMAIL SIGNATURE----- The Gospel for all Targeted Individuals (TIs): [The New York Times] Microwave Weapons Are Prime Suspect in Ills of U.S. Embassy Workers Link: https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html ******************************************************************************************** Singaporean Mr. Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 14 Feb 2019 [1] https://tdtemcerts.wordpress.com/ [2] https://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming -----END EMAIL SIGNATURE-----

7 7

I broke "yum update" - C7
by Gary Stainburn 30 Aug '19

30 Aug '19

This evening I decided to do some work on my development C7 system. As I have not touched it for a while, and wanted to install new services I thought I'd better yum update first. I saw that it only did updates from Google and PHP, and none from the system repo's so I had a closer look. It showed certificate errors on a number of repo's. [root@stan2 ~]# yum update Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64 error was 14: curl#60 - "Peer's Certificate issuer is not recognized." * base: mirrors.clouvider.net * epel: mirrors.coreix.net * extras: mirrors.clouvider.net * remi-php72: mirror.netweaver.uk * remi-safe: mirror.netweaver.uk * updates: mirrors.vooservers.com https://rpm.nodesource.com/pub_6.x/el/7/x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "Peer's Certificate issuer is not recognized." Trying other mirror. It was impossible to connect to the CentOS servers. This could mean a connectivity issue in your environment, such as the requirement to configure a proxy, or a transparent proxy that tampers with TLS security, or an incorrect system clock. You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. https://download.postgresql.org/pub/repos/yum/10/redhat/rhel-7-x86_64/repod…: [Errno 14] curl#60 - "Peer's Certificate issuer is not recognized." Trying other mirror. https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-7-x86_64/repo…: [Errno 14] curl#60 - "Peer's Certificate issuer is not recognized." Trying other mirror. No packages marked for update [root@stan2 ~]# I wrongly followed the instructions in https://wiki.centos.org/yum-errors hoping that it would resolve the problems but it's only made it worse. Now all I get is: [root@stan2 ~]# yum clean all Loaded plugins: fastestmirror, langpacks Cleaning repos: base epel extras google-chrome nodesource pgdg10 pgdg96 remi-php72 remi-safe updates Cleaning up list of fastest mirrors [root@stan2 ~]# rm -rf /var/cache/yum/* [root@stan2 ~]# yum update Loaded plugins: fastestmirror, langpacks Determining fastest mirrors 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 retrieve metalink for repository: epel/x86_64. Please verify its path and try again [root@stan2 ~]# I removed and re-installed the epel-release RPM which made no difference. I've also tried disabling each repo in turn, pgdg10, remi-php72, nodesource-el, pgdg96, google-chrome but still have no success. Anyone got any suggestions?

7 28

CentOS CR Released with 7.7.1908 Packages
by Johnny Hughes 30 Aug '19

30 Aug '19

You guys may have noticed that the 7.7.1908 packages for the GA release have been posted to QA for all arches (x86_64, ppc64le, aarch64. ppc64, armhfp, i386). These are just the items that will be in the os/ (base) repository and not the zero day updates. We are working on the updates now. Announcements here: https://lists.centos.org/pipermail/centos-cr-announce/2019-August/thread.ht… Thanks, Johnny Hughes

1 0

Giving full administrator privileges through sudo on production systems
by Bagas Sanjaya 29 Aug '19

29 Aug '19

Hello, Consider two following cases: 1. On production systems on television stations, a sysadmin give teens (remaja group, age 13 and older) full administrator privileges by adding this line to sudoers: %remaja ALL=(ALL:ALL) ALL Rationale: Almost all programs on the system can only be run by teens as root. 2. On production systems on tobacco factories, a sysadmin also give adults (age 18 and older, dewasa group) full administrator privileges by adding this line to sudoers: %dewasa ALL=(ALL:ALL) ALL Also, the sudo lecture file configured in sudoers (/etc/sudo.lecture) contain the following: WARNING: I BROKE MY SYSTEM BECAUSE OF SUDO. CUSTOMER SERVICE: ($a_random_phone_number) Rationale: All programs on system can only be run by adults, because such programs might break system. However, instead of calling sysadmin when something breaks the system, adults can call customer service instead, which isn't qualified for system maintenance. Based on above cases, is it OK to give group of random users full administrator privileges using sudo, by adding them to sudoers with ALL privileges? Should sudoers call customer service number instead of sysadmin when something breaks? Cheers, Bagas -- An old man doll... just what I always wanted! - Clara

9 14

Ran across this process to upgrade from C6 to C7, will it work???
by Jay Hart 29 Aug '19

29 Aug '19

I figure it won't. Hope the experts can clarify. I'm still using C6 and want to C7 and really to C8. https://www.psychz.net/client/kb/en/upgrade-centos-6-to-centos-7.html

3 3

Re: [CentOS] CentOS 8 will be released soon?
by Stephen John Smoogen 28 Aug '19

28 Aug '19

On Sat, 24 Aug 2019 at 13:58, Alan Mead <amead(a)alanmead.org> wrote: > > On 8/24/2019 12:49 PM, Stephen John Smoogen wrote: > > On Sat, 24 Aug 2019 at 01:09, Turritopsis Dohrnii Teo En Ming > <ceo(a)teo-en-ming-corp.com> wrote: > > Good afternoon from Singapore, > > According to the CentOS 8 build timeline, everything has been completed except release work. Does this mean CentOS 8 will be released soon? > > https://wiki.centos.org/About/Building_8 > > It means dealing with a ton of little IRQ's that built up over the > builds. There are all the updates which have gone out from Red Hat > since their .0. There are trying to find all the little nagging things > people find which someone will say 'Why didn't CentOS people actually > find this blaringly obvious problem I found in 30 seconds.. are they > all idiots?' which happens right after every release. And there are > the 'ok could we get this one more thing?' stuff which pile up also. > This happens in some every .0 release from 4 onward.. 2-3 weeks where > people wonder why stuff is being held from them... > > > No one called anyone an 'idiot.' > > Actually, I think several people (including myself) just don't know what "Release work" means or what it means that the wiki says that the release work is "Not started" > > So thanks for your unfriendly answer. It sounds like your speculation is that there might be a release in 2-3 weeks. > > I have had several people explain to me that my comments were out-of-place and out-of-turn. When I wrote them originally I thought I was going from experience of previous releases and thought I was being matter of fact. In rereading I realized I was crass and grumpy. My un-reserved apologies for that. I should have either not posted or waited, reread and rewritten. -- Stephen J Smoogen.

5 4

xfs
by Jerry Geis 28 Aug '19

28 Aug '19

I used to be able to 'repair' ext4 fs issue (when the boot process drops you into emergency mode)... but now with xfs - it does not seem to let me do that. xfs_repair /dev/sda3 or xfs_repair -L /dev/sda3 both say fatal error fatal error -- couldn’t initialize XFS library How can I repair XFS with burning a DVD and finding an external USB reader etc... Thanks, Jerry

2 1

OT: mostly gone
by mark 28 Aug '19

28 Aug '19

Hi, folks, Well, it's ten years that I've been on this list, right when I started this job. But, it's time to move on... I'm retiring. (Yeah, that old.) So, though I'll be part time for a few months, and running CentOS at home (in spite of my manager's pushing me to do Ubuntu). This list is *so* much more useful than any of the ones I've seen for Ubuntu, or much else. I'm very much looking forward to C 8. One more thing: I know I've been over the top on ethics "I work for a US federal contractor, but not saying more", even though there's folks like Todd, who's military. Anyway, now that I'm out, today, my line (in person) was, "I'm with the federal goverment, and I'm here to help you." Then, after they ask if I'll have to kill them, I can say, no: I've been with the NIH, and so, yes, I really meant it. I'll show up occasionally, but not like I have been. So long, and thanks for all the fish. mark

5 6

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss August 2019