- Discuss - lists.centos.org

Re: [CentOS] [PROVENANCE INTERNET] Re: Missing packages in centos8 mirrors or do I miss something?
by LAHAYE Olivier 26 Sep '19

26 Sep '19

For those who come across this thread, I've found the exact list of changed and dropped package between rhel:7 and rhel:8: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/ht… Too bad that the "note" column is empty in the dropped package table. NO word about reason or possible alternatives. Also too bad that those drops were not advertised before release so developers could think about migrating there code. That would have helped me a lot if I had knew that docbook-utils-pdf would be dropped....I would have searched for an alternative long ago. Olivier. Le 26/09/2019 16:02, « CentOS au nom de LAHAYE Olivier » <centos-bounces(a)centos.org au nom de olivier.lahaye(a)cea.fr> a écrit : [...] -Is there a place where I could read about all dropped packages? I've searched in redhat changelog and centos and all I could find is a few packages dropped like NIS related or so. [...]

3 2

How to dump/restore a CentOS 7 system
by Xinhuan Zheng 26 Sep '19

26 Sep '19

Hello All, I guess it is very common for administrative purpose, to dump and restore a CentOS 7 system. I usually use dump/restore commands. However, I’m having trouble to handle installing bootloader and creating initramfs for C7 system. Does anyone know a good document source that details those procedure? Thank you, Xinhuan Zheng

11 11

Any ETA for the cloud-images?
by rainer＠ultra-secure.de 26 Sep '19

26 Sep '19

Hi, I see they are being built, but they can't be accessed directly. Rainer

1 0

Missing packages in centos8 mirrors or do I miss something?
by LAHAYE Olivier 26 Sep '19

26 Sep '19

Hi, I need to port OSCAR Cluster and SystemImager softwares to centos8, but I miss a lot of package that seems to be built for centos-8. For example, I cant find docbook-utils and docbook-utls-pdf while I see them here: https://koji.mbox.centos.org/koji/buildinfo?buildID=651 I’ve installed epel-release and elrepo-release and centos-release-stream. Do I miss something or is it a matter of time due to mirro syncs? I misse btrfs packages, perl-Tk packages, docbook packages and many more that I can find on https://koji.mbox.centos.org/koji/builds Where am I wrong? PS: I’m running CentOS-8 in docker (roboxes/centos8 wainting for official centos:8 container). (I think that my issue is not related to the container though as I can’t find packages on mirror repos. -- Olivier LAHAYE

2 2

USB of ISO image
by Jerry Geis 26 Sep '19

26 Sep '19

Hi I did the dd iso to my USB. all is fine. I can mount the second partition (which is not iso 9660) and edit the grub.cfg file. Question is what do I run after that so my new menu option appears ? grub2-install /dev/sdd Is that the correct command to get grub to notice my new file ? Assuming sdd is the USB disk of course. Thanks, jerry

1 1

USB thumb drive for CentOS 7.7 to install
by Jerry Geis 25 Sep '19

25 Sep '19

I took the "everything" iso and did the dd command to my 16G thumb drive. I booted and entered my usual ks=http://xxx on the boot line. All good so far. It gets my kickstart file and installation begins. At some point it says Installing libreoffice-opensymbol-fonts (492/1948) Retrying download of 1:libreoffice-opensymbol-fonts-5.3.6.1-21.el7.norarch then after 10 retries it fails. I have verfied this file is on my USB disk, I have re-downloaded from different mirror, the Everything file, dd that to my USB disk, tried the re-install and still the error. I don't know what to try next. Jerry

2 2

CentOS 8
by mark 25 Sep '19

25 Sep '19

I just skimmed through the deprecated, and there's a *lot*. But one hit me in the face: if you make a change to /etc/nsswitch.conf, you need to REBOOT THE SERVER? Ok, did this come from Redmond?* Oh, and I note virt-manager replaced by cockpit. Can someone pass along a little note: Sybase has had, for a bunch of years, a required program... called cockpit. I think they've got the name by priority.... * I thought that "your cursor has moved; please reboot Windows to have this change take effect was a joke... until, about 5-6 years ago, I found in trying to set up samba at home on Win 8 that if I changed the workgroup name... it required Windows to be rebooted. So... really? nsswitch.conf, and reboot? Now I think I'll install C 7 to dual boot on my lady's workstation, rather than 8. mark "or my manager this I should go to ubuntu, which I dislike...." mark

3 2

CentOS-announce Digest, Vol 175, Issue 3
by centos-announce-request＠centos.org 25 Sep '19

25 Sep '19

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. Release for CentOS Linux 8 and CentOS Streams (Karanbir Singh) ---------------------------------------------------------------------- Message: 1 Date: Tue, 24 Sep 2019 17:38:36 +0100 From: Karanbir Singh <kbsingh(a)centos.org> To: CentOS Announcements List <centos-announce(a)centos.org> Subject: [CentOS-announce] Release for CentOS Linux 8 and CentOS Streams Message-ID: <beeca6a3-6abd-2416-85e9-311571fc9990(a)centos.org> Content-Type: text/plain; charset="utf-8" We would like to announce the general availability of CentOS Linux 8 and the new CentOS Stream, on all architectures. ---------- CentOS Linux 8 This is the first release for CentOS Linux 8 and is version marked as 8.0-1905, derived from sources published by Red Hat, delivered via git.centos.org First, please read through the release notes at : http://wiki.centos.org/Manuals/ReleaseNotes/CentOSLinux8 - these notes contain important information about the release and details about some of the content inside the release from the CentOS QA team. These notes are updated constantly to include issues and incorporate feedback from the users and should be the first port of call for anyone looking to use CentOS Linux 8. ---------- CentOS Stream When the CentOS Project announced it was joining forces with Red Hat in January 2014, we put an emphasis on how the new relationship would ?(drive) forward development and adoption of next-generation open source technologies?: https://www.redhat.com/en/about/press-releases/red-hat-and-centos-join-forc… In the intervening years, the Project has grown to deliver not just a Linux distribution, but an entire set of sub-communities using new services in support of development work done on top of that distro. Special interest groups (SIGs) have provided a base for layered projects to develop on a stable platform. Additionally, CI/CD, the community build system, better Git repository hosting, and container pipelines, amongst others, have brought modern code and development practices to the broader CentOS community. With the introduction of CentOS Stream https://wiki.centos.org/Manuals/ReleaseNotes/CentOSStream we are excited to continue working with Red Hat http://redhat.com/en/blog/transforming-development-experience-within-centos to bring you the biggest step forward the CentOS Project has ever undertaken. CentOS Stream is a rolling-release Linux distro that exists as a midstream between the upstream development in Fedora Linux and the downstream development for Red Hat Enterprise Linux (RHEL). It is a cleared-path to contributing into future minor releases of RHEL while interacting with Red Hat and other open source developers. This pairs nicely with the existing contribution path in Fedora for future major releases of RHEL. In practice, CentOS Stream will contain the code being developed for the next minor RHEL release. This development model will allow the community to discuss, suggest, and contribute features and fixes into RHEL more quickly. To do this, Red Hat Engineering is planning to move parts of RHEL development into the CentOS Project in order to collaborate with everyone on updates to RHEL. There will not be a CentOS Stream for versions released in the past, this is only a forward-looking version target. Please read through the release notes at : http://wiki.centos.org/Manuals/ReleaseNotes/CentOSStream - these notes contain important information about the release and details about some of the content inside the release from the CentOS QA team. These notes are updated constantly to include issues and incorporate feedback from the users. ---------- Updates, Sources and DebugInfos Updates for both distributions are being built and will be online in the next few days to catchup. Sources and debuginfo for all the released content is also available online at mirror.centos.org and vault.centos.org; In the coming days, we will work to get the cbs.centos.org service enabled for both the new distributions, and encourage the SIG's to start considering their executions plans forward. ---------- Download In order to conserve donor bandwidth, and to make it possible to get the mirror content sync'd out as soon as possible, we recommend using torrents to get your initial installer images: Get the torrent now : http://mirror.centos.org/centos/8/isos/x86_64/CentOS-8-x86_64-1905-dvd1.tor… SHA256 707a66357f72eb822ca113991f3bb86a1ac1ed5fbc2fa5d968ed25fb48ee985c http://mirror.centos.org/centos/8-stream/isos/x86_64/CentOS-Stream-x86_64-d… SHA256: 88604a95189f91162d1f89f0ac7436f3413812506a41b8ec286baeaa833b1e91 Images, sizes and their SHA256Sum's: CentOS-8-x86_64-1905-boot.iso: 559939584 bytes SHA256 a7993a0d4b7fef2433e0d4f53530b63c715d3aadbe91f152ee5c3621139a2cbc CentOS-8-x86_64-1905-dvd1.iso: 7135559680 bytes SHA256 ea17ef71e0df3f6bf1d4bf1fc25bec1a76d1f211c115d39618fe688be34503e8 CentOS-8-ppc64le-1905-boot.iso: 567736320 bytes SHA256 9062ae0d892126f57429c3194143e6e6e5485e5f32834e03d849bf5cf075ca7a CentOS-8-ppc64le-1905-dvd1.iso: 6376304640 bytes SHA256 bfd27297da1ddc1185a08fc65e46c58efebf51b25758ff8f12d29a6214aeae39 CentOS-8-aarch64-1905-boot.iso: 520048640 bytes SHA256 18a211a826bd3dd4d034ddc529303bc2b5dc6e1b63ea311644d7698e7b67fb3e CentOS-8-aarch64-1905-dvd1.iso: 5150640128 bytes SHA256 c950cf7599a2317e081506a3e0684f665ef9c8fe66963bf7492595d7c6ccc230 CentOS-Stream-x86_64-boot.iso: 558891008 bytes SHA256 e38192400212796085b7996f21828aa8f8a72d44b64059572eb8c725e13be4cc CentOS-Stream-x86_64-dvd1.iso: 8572108800 bytes SHA256 559715017959f5967d2b9876bd27f46d8a740e1d02f59dfb8fd5e7114dd5cc79 The iso files are also available for direct download from http://mirror.centos.org/centos/8/isos/x86_64 and http://mirror.centos.org/centos/8-stream/isos/x86_64 Other media, including container, cloud, live media etc will be posted in the near future. ---------- Events We try and organise Dojo's in various parts of the world as a one day event, to bring together people who use CentOS and others who are keen to learn about CentOS. The day's focus is on sharing technical knowledge and success stories. Its also a great place to meet and talk about upcoming technologies and learn how others are using them on CentOS. Dojo at fosdem - https://wiki.centos.org/Events/Dojo/Brussels2020 Please track the page at https://wiki.centos.org/Events/ for upcoming events, and if you would like to help organise something, do get in touch with us. ---------- Getting Help The CentOS ecosystem is sustained by community driven help and guidance. The best place to start for new users is at http://wiki.centos.org/GettingHelp ---------- Thanks I'd also like to thank our donors and sponsors for their continued support for the project. Additionally, the CentOS QA team, the Core SIG team and all the associated SIG's. And thanks to everyone who contributed with ideas, code, test feedback and promoting CentOS into the ecosystem. Enjoy! - -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | https://www.centos.org/ | twitter.com/CentOSProject

1 0

Video projector vs. onboard video card
by Nicolas Kovacs 25 Sep '19

25 Sep '19

Hi, I have a CentOS 7 desktop client installed on an old Dell Optiplex computer with an Intel video card integrated into the motherboard. The card has a single VGA connector, and the 19" monitor is connected to it. I wonder how I could connect a video projector to this computer while keeping the monitor, in a mirroring configuration, e. g. output is the same on the video projector and the monitor. Do I have to replace my onboard video card by something like an NVidia GT710 graphic card with two video connectors ? Or is there a different solution for this? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12

2 2

CentOS 8 Boot.iso image DHCP4 not working?
by Young, Gregory 24 Sep '19

24 Sep '19

I'm just wondering if anyone else is not getting a DHCPv4 address in Anaconda, using the CentOS 8 Boot.iso image? I get an IPv6 Autoconfig address, but it doesn't want to pick up a DHCPv4. This is in a Hyper-V Gen2 VM, connected to the same network all my other dev VMs are on, and picking up DHCPv4 without issue. And, congratz to the CentOS team on 2 releases in a week (or so)! Gregory Young

1 2

CentOS 8 Everything
by Jerry Geis 24 Sep '19

24 Sep '19

HI All - Great work on 7.7 and 8.0! Will there be a "Everything" iso coming ? perhaps just not sync'd yet on mirrors? Does 7.7 support an upgrade to 8 path ? Thanks! all great stuff. Jerry

2 1

updates repo for 8
by sberg＠mississippi.com 24 Sep '19

24 Sep '19

I've checked a couple of mirrors and centos.org itself and I don't see updates for the 8 repos yet. Is there a new location for updates now that we're seeing the 8 repos or do I just need to wait for the repos to get a chance to synchronize fully?

3 2

CO 7.7.1908 Updates not getting to mirrors?
by Phelps, Matthew 24 Sep '19

24 Sep '19

I *know* there has been a lot going on, and congratulations on getting CentOS 8 out! But(!), I don't see any updates to CO 7.7.1908 in the "updates" directory on the mirrors I typically use. All the files date from Sept. 14th. Is something broken? -- *Matt Phelps* *Information Technology Specialist, Systems Administrator* (Computation Facility, Smithsonian Astrophysical Observatory) Center for Astrophysics | Harvard & Smithsonian 60 Garden Street | MS 39 | Cambridge, MA 02138 email: mphelps(a)cfa.harvard.edu cfa.harvard.edu | Facebook <http://cfa.harvard.edu/facebook> | Twitter <http://cfa.harvard.edu/twitter> | YouTube <http://cfa.harvard.edu/youtube> | Newsletter <http://cfa.harvard.edu/newsletter>

1 2

Interesting update problem
by isdtor 24 Sep '19

24 Sep '19

I had problems updating a 7.6 machine to 7.7, so I reinstalled it from scratch and applied all the 7.6 updates, then attempted the 7.7 upgrade again. It failed with the same errors. I'm wondering where the problem is? # yum update ... [hundreds of lines of the next line] warning: Unable to get systemd shutdown inhibition lock Error in PRETRANS scriptlet in rpm package 1:java-1.8.0-openjdk-headless-1.8.0.222.b10-1.el7_7.x86_64 Error in PRETRANS scriptlet in rpm package 1:java-11-openjdk-headless-11.0.4.11-1.el7_7.x86_64 Error in PRETRANS scriptlet in rpm package kmod-kvdo-6.1.2.41-5.el7.x86_64 mesa-libEGL-devel-18.3.4-5.el7.x86_64 was supposed to be installed but is not! Verifying : mesa-libEGL-devel-18.3.4-5.el7.x86_64 1/3285 [repeating for dozens or hundreds of other packages] ... Failed: [list of all upgrade packages] Of course mesa-libEGL-devel-18.3.4-5.el7.x86_64 is not installed, that's the new version. The installed version is mesa-libEGL-devel-18.0.5-4.el7_6.x86_64. Where did it all go wrong? I tried clearing the yum cache and rebuilding the rpm db, no joy. Another 7.6 machine upgraded fine, although from a smaller installed package set.

1 0

deprecations leading up to C8
by Fred Smith 23 Sep '19

23 Sep '19

Was reading the long list of things being deprecated in the RHEL 8 release notes t'other day, and saw my old friend sendmail on the list. I've stuck by her because I've learned how she likes to be stroked to get the best out of her, and quail at the thought of taking on a new MTA and having to learn it all all over again. But I guess I'm going to have to, soon or late, probably sooner than later. :( Can anyone point me to resources specifically for helping us ignorant folk in converting all the arcan-ity in sendmail.mc into something equivalent for Postfix? Thanks in advancce! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- I can do all things through Christ who strengthens me. ------------------------------ Philippians 4:13 -------------------------------

14 24

JOB | Web Architect (London, UK)
by James Tobin 22 Sep '19

22 Sep '19

Hello, I'm working with an employer that is looking to hire a permanent front end architect to join their London office. You should have experience with Javascript and frameworks such as (but not only) React. Consequently, I had hoped that some members of this mailing list may like to discuss further off-list using "JamesBTobin (at) Gmail (dot) Com". Kind regards, James

1 0

Booting new virtual image with 7.7 and with EFI
by Jerry Geis 20 Sep '19

20 Sep '19

Is booting a new centos virtual image (centos 7.7 host) supported with EFI under 7.7 If so how. Last time on 7.6 it was a technology preview or something. Thanks Jerry

2 1

7.7.1908, interface bonding, and default route
by Carlos A. Carnero Delgado 20 Sep '19

20 Sep '19

Hi! I just upgraded a machine to 7.7.1908 and the default route is not being set on boot. This particular server has a bonded interface, and the corresponding configuration for the master is ( /etc/sysconfig/network-scripts/ifcfg-bond0): TYPE=Bond BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=yes NAME=bond0 DEVICE=bond0 ONBOOT=yes IPADDR=10.3.20.131 PREFIX=24 GATEWAY=10.3.20.1 DNS1=10.3.2.8 BONDING_MASTER=yes BONDING_OPTS="mode=802.3ad xmit_hash_policy=layer2 miimon=100" The slaves (two of them) are configured like TYPE=Ethernet BOOTPROTO=none NAME=bond0-slave0 DEVICE=em3 ONBOOT=yes MASTER=bond0 SLAVE=yes After booting, the routing table is 10.3.20.0/24 dev bond0 proto kernel scope link src 10.3.20.131 metric 300 with no default route configured (manually adding it will work, of course.) This machine worked perfectly before, and it did during previous upgrades and reboots. Has anyone ever had this problem before? Thanks, Carlos.

3 4

running init disconnects ssh session
by Stephen Berg (Code 7309) 20 Sep '19

20 Sep '19

Noticing a new behavior lately. Logged in via sshd and ssh keys as root to a remote system. When changing runlevels between multi-user or graphical the ssh session is disconnected. It's not a big deal but annoying if I have other tasks to do on that particular system. I've tried logging in as normal user, su to root and it still disconnects the ssh session upon either an "init 3" or "systemctl isolate multi-user.target" command. -- Stephen Berg, IT Specialist, Ocean Sciences Division, Code 7309 Naval Research Laboratory W: (228) 688-5738 <- (Preferred contact) DSN: (312) 823-5738 C: (228) 365-0162

2 4

CentOS 8 will be released on 24 Sep 2019
by Turritopsis Dohrnii Teo En Ming 20 Sep '19

20 Sep '19

Good morning from Singapore, CentOS 8 will be released on 24 Sep 2019, that is, in 4 days' time. Read link below: https://wiki.centos.org/About/Building_8 It says Final release slated for 24 Sep 2019. Thank you. -----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 and refugee seeking attempts at the United Nations Refugee Agency Bangkok (21 Mar 2017) and in Taiwan (5 Aug 2019): [1] https://tdtemcerts.wordpress.com/ [2] https://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming -----END EMAIL SIGNATURE-----

1 0

selinux reports
by Fred Smith 19 Sep '19

19 Sep '19

Hi all! I keep getting reports from selinux, like below, and I have no clue what the app is it's talking about, nor how do figure out if it should be allowed access or not. Anyone got any advice to offer? It says: The source process: /usr/sbin/xtables-multi attempted this access: open on this file: /run/xtables.lock Having no clue what xtables-multi is, or why or even if it should be able to open that file, I am at a loss: should I take action to enable it, or not? Thanks in advance! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- I can do all things through Christ who strengthens me. ------------------------------ Philippians 4:13 -------------------------------

1 0

UEFI booting
by Jerry Geis 19 Sep '19

19 Sep '19

I installed my first UEFI disk yesterday. Seemed to go fine. CentOS 7.6 x86_64 I then took that disk "out" of that machine and put it another machine - it seems to not even boot. I put the original disk back in that machine and it boots fine. I put the UEFI disk back in the machine I built it on and it works fine. They are similar machines either and i3 and i7. Shouldn't that work? Build a UEFI disk on machine A - move it to machine B? Thanks Jerry

6 6

Postfix vs. Thunderbird on Mac OS
by Nicolas Kovacs 19 Sep '19

19 Sep '19

Hi, I'm running our local school's mail server on CentOS 7, Postfix and Dovecot. We get quite a lot of spam, so I have the following sender restrictions in my /etc/postfix/main.cf: --8<------------------------------------------------------ # Restrictions SMTP smtpd_helo_restrictions = reject_unknown_helo_hostname smtpd_sender_restrictions = reject_unknown_sender_domain, check_sender_access hash:/etc/postfix/sender_access smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_rbl_client zen.spamhaus.org, reject_rhsbl_reverse_client dbl.spamhaus.org, reject_rhsbl_helo dbl.spamhaus.org, reject_rhsbl_sender dbl.spamhaus.org smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_data_restrictions = reject_unauth_pipelining --8<------------------------------------------------------ Most folks are using Thunderbird on Linux, and everything works perfectly. One single user has a MacBook Air with Thunderbird on Mac OS Mojave, and her outgoing mails are rejected with the following error message in /var/log/maillog on the server: --8<------------------------------------------------------ Sep 16 14:22:32 sd-48011 postfix/smtps/smtpd[14434]: NOQUEUE: reject: RCPT from villa.figaret.pck.nerim.net[62.212.106.47]: 450 4.7.1 <Air-de-bea.scholae.lan>: Helo command rejected: Host not found; from=<xxxxx.yyyyyyyy(a)scholae.fr> to=<info(a)microlinux.fr> proto=ESMTP helo=<Air-de-bea.scholae.lan> --8<------------------------------------------------------ As far as I understand, it has to do with this MacBook's host configuration. Any suggestions? Cheers from the sunny South of France, Niki Kovacs -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12

4 3

conflicts in updating to CR repo
by Fred Smith 19 Sep '19

19 Sep '19

Note, first of all I haven't actually updated, I'm just running "yum update" to see what conflicts, if any, I get so I can be prepared when the final 7.7 release happens. I've traditionally used the nvidia packages from elrepo, but recently enabled rpmfusion (back when I started using 7.x, I disabled rpmfusion because it took them a looooong time to get a EL7 repository up). I use the priority plugin in yum, and have elrepo at priority 50 and rpmfusion at priority 60, so the elrepo nvidia packages should "win", but yum seems to be confused about which packages to use. So now when doing yum update (with CR enabled) I get this long list of dependency issues regarding the nvidia packages. I don't see any reason to switch to the rpmfusion packages, elrepo seems to do a good job of packaging and keeping them up to date: --> Processing Dependency: xorg-x11-drv-nvidia-390xx-libs(x86-64) = 3:390.129-1.el7 for package: 3:xorg-x11-drv-nvidia-390xx-390.129-1.el7.x86_64 --> Processing Dependency: nvidia-settings-390xx(x86-64) = 390.129 for package: 3:xorg-x11-drv-nvidia-390xx-390.129-1.el7.x86_64 --> Processing Dependency: libnvidia-tls.so.390.129()(64bit) for package: 3:xorg-x11-drv-nvidia-390xx-390.129-1.el7.x86_64 --> Processing Dependency: libnvidia-glcore.so.390.129()(64bit) for package: 3:xorg-x11-drv-nvidia-390xx-390.129-1.el7.x86_64 --> Running transaction check ---> Package nvidia-settings-390xx.x86_64 0:390.129-1.el7 will be installed ---> Package xorg-x11-drv-nvidia-390xx-libs.x86_64 3:390.129-1.el7 will be installed --> Processing Conflict: nvidia-x11-drv-430.50-1.el7_7.elrepo.x86_64 conflicts xorg-x11-drv-nvidia-390xx Removing kmod-nvidia.x86_64 0:430.50-1.el7_7.elrepo - u due to obsoletes from kmod-nvidia-390xx.x86_64 3:390.129-3.el7 - u --> Restarting Dependency Resolution with new changes. --> Running transaction check ---> Package kmod-nvidia.x86_64 0:430.50-1.el7_7.elrepo will be an update --> Processing Dependency: nvidia-kmod = 430.50 for package: nvidia-x11-drv-430.50-1.el7_7.elrepo.x86_64 --> Processing Dependency: nvidia-kmod = 430.50 for package: nvidia-x11-drv-430.50-1.el7_7.elrepo.x86_64 ---> Package nvidia-x11-drv.x86_64 0:430.40-1.el7_6.elrepo will be updated ---> Package nvidia-x11-drv.x86_64 0:430.40-1.el7_6.elrepo will be updated --> Finished Dependency Resolution --> Running transaction check ---> Package kernel.x86_64 0:3.10.0-957.21.2.el7 will be erased ---> Package kernel-devel.x86_64 0:3.10.0-957.21.2.el7 will be erased ---> Package kmod-nvidia.x86_64 0:430.50-1.el7_7.elrepo will be an update --> Processing Dependency: nvidia-kmod = 430.50 for package: nvidia-x11-drv-430.50-1.el7_7.elrepo.x86_64 --> Processing Dependency: nvidia-kmod = 430.50 for package: nvidia-x11-drv-430.50-1.el7_7.elrepo.x86_64 --> Processing Conflict: nvidia-x11-drv-430.50-1.el7_7.elrepo.x86_64 conflicts xorg-x11-drv-nvidia-390xx --> Finished Dependency Resolution Error: nvidia-x11-drv conflicts with 3:xorg-x11-drv-nvidia-390xx-390.129-1.el7.x86_64 Error: Package: nvidia-x11-drv-430.50-1.el7_7.elrepo.x86_64 (elrepo) Requires: nvidia-kmod = 430.50 Removing: kmod-nvidia-430.40-1.el7_6.elrepo.x86_64 (@elrepo) nvidia-kmod = 430.40-1.el7_6.elrepo Obsoleted By: 3:kmod-nvidia-390xx-390.129-3.el7.x86_64 (rpmfusion-nonfree-updates) Not found Updated By: kmod-nvidia-430.50-1.el7_7.elrepo.x86_64 (elrepo) nvidia-kmod = 430.50-1.el7_7.elrepo Available: 3:akmod-nvidia-430.40-2.el7.x86_64 (rpmfusion-nonfree-updates) nvidia-kmod = 3:430.40-2.el7 Available: kmod-nvidia-430.14-1.el7_6.elrepo.x86_64 (elrepo) nvidia-kmod = 430.14-1.el7_6.elrepo Available: kmod-nvidia-430.26-1.el7_6.elrepo.x86_64 (elrepo) nvidia-kmod = 430.26-1.el7_6.elrepo Available: kmod-nvidia-430.34-1.el7_6.elrepo.x86_64 (elrepo) nvidia-kmod = 430.34-1.el7_6.elrepo Available: kmod-nvidia-430.40-2.el7_7.elrepo.x86_64 (elrepo) nvidia-kmod = 430.40-2.el7_7.elrepo Available: 3:kmod-nvidia-430.40-2.el7.x86_64 (rpmfusion-nonfree-updates) nvidia-kmod = 3:430.40-2.el7 Available: 3:kmod-nvidia-3.10.0-1062.el7.x86_64-430.40-2.el7.x86_64 (rpmfusion-nonfree-updates) nvidia-kmod = 3:430.40-2.el7 You could try using --skip-broken to work around the problem Thanks in advance for advice! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- Show me your ways, O LORD, teach me your paths; Guide me in your truth and teach me, for you are God my Savior, And my hope is in you all day long. -------------------------- Psalm 25:4-5 (NIV) --------------------------------

3 4

Updates
by Jerry Geis 19 Sep '19

19 Sep '19

I did yum -y update --exclude=vulkan*; then rebooted When I do yum check-updates I get this: (which I expect) vulkan.x86_64 1.1.97.0-1.el7 base vulkan-filesystem.noarch 1.1.97.0-1.el7 base When I do the yum -y update I get this: Transaction check error: file /usr/lib64/libSPIRV-Tools-opt.so from install of vulkan-1.1.97.0-1.el7.x86_64 conflicts with file from package spirv-tools-libs-2019.1-1.el7.x86_64 file /usr/lib64/libSPIRV-Tools.so from install of vulkan-1.1.97.0-1.el7.x86_64 conflicts with file from package spirv-tools-libs-2019.1-1.el7.x86_64 How do I get past that ? Vulkan is used by "wine" I believe. THanks Jerry

3 2

What about Mate Desktop on Centos 8?
by Frank Cox 18 Sep '19

18 Sep '19

According to Twitter: https://mobile.twitter.com/CentOSProject/status/1173652996305170432 "The next version of #CentOS is being released September 24 and will be announced in all the usual places." I'm wondering about the status of the Mate Desktop. Looking under M here: https://mirror.csclub.uwaterloo.ca/fedora/epel/8/Everything/x86_64/Packages… I don't see anything about Mate. Which leads me to ask, what's its status then? I hope it hasn't died since that's what I use for all of my computers. -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

6 8

CentOS-announce Digest, Vol 175, Issue 1
by centos-announce-request＠centos.org 18 Sep '19

18 Sep '19

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. Release for CentOS Linux 7 (1908) on the x86_64 Architecture (Johnny Hughes) 2. Release for CentOS Linux 7 (1810) on armhfp aarch64 i386 ppc64 ppc64le and power9 (Pablo Sebasti?n Greco) 3. Release for CentOS Linux 7 (1908) on armhfp aarch64 i386 ppc64 ppc64le and power9 (Johnny Hughes) 4. CESA-2019:2694 Critical CentOS 6 firefox Security Update (Johnny Hughes) 5. CESA-2019:2736 Important CentOS 6 kernel Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 17 Sep 2019 08:01:36 -0500 From: Johnny Hughes <johnny(a)centos.org> To: CentOS-Announce <centos-announce(a)centos.org> Subject: [CentOS-announce] Release for CentOS Linux 7 (1908) on the x86_64 Architecture Message-ID: <da1896ff-3527-ccef-4c92-7f463c63f4ae(a)centos.org> Content-Type: text/plain; charset="utf-8" Release for CentOS Linux 7 (1908) on the x86_64 Architecture We are pleased to announce the general availability of CentOS Linux 7 (1908) for the x86_64 architecture. Effectively immediately, this is the current release for CentOS Linux 7 and is tagged as 1908, derived from Red Hat Enterprise Linux 7.7 Source Code. As always, read through the Release Notes at : http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 - these notes contain important information about the release and details about some of the content inside the release from the CentOS QA team. These notes are updated constantly to include issues and incorporate feedback from the users. ---------- Updates, Sources, and DebugInfos Updates released since the upstream release are all posted, across all architectures. We strongly recommend every user apply all updates, including the content released today, on your existing CentOS Linux 7 machine by just running 'yum update'. As with all CentOS Linux 7 components, this release was built from sources hosted at git.centos.org. In addition, SRPMs that are a byproduct of the build (and also considered critical in the code and buildsys process) are being published to match every binary RPM we release. Sources will be available from vault.centos.org in their own dedicated directories to match the corresponding binary RPMs. Since there is far less traffic to the CentOS source RPMs compared with the binary RPMs, we are not putting this content on the main mirror network. If users wish to mirror this content they can do so using the reposync command available in the yum-utils package. All CentOS source RPMs are signed with the same key used to sign their binary counterparts. Developers and end users looking at inspecting and contributing patches to the CentOS Linux distro will find the code hosted at git.centos.org far simpler to work against. Details on how to best consume those are documented along with a quick start at : http://wiki.centos.org/Sources Debuginfo packages are also being signed and pushed. Yum configs shipped in the new release file will have all the context required for debuginfo to be available on every CentOS Linux install. This release supersedes all previously released content for CentOS Linux 7, and therefore we highly encourage all users to upgrade their machines. Information on different upgrade strategies and how to handle stale content is included in the Release Notes. Note that older content, obsoleted by newer versions of the same applications are trim'd off from repos like Extras/ and Plus/ However this time we have also extended this to the SIG content hosted at mirror.centos.org, and some older End of Life content has been dropped. Everything we ever release, is always available on the vault service for people still looking for and have a real need for it. ---------- Download In order to conserve donor bandwidth, and to make it possible to get the mirror content sync'd out as soon as possible, we recommend using torrents to get your initial installer images: Details on the images are available on the mirrors at http://mirror.centos.org/centos/7/isos/x86_64/0_README.txt - that file clearly highlights the difference in the images, and when one might be more suitable than the others. sha256sum x86_64: ba827210d4eb9313fc19120b9b85e7baef234c7f81bc55847a336114ddac20cb CentOS-7-x86_64-LiveGNOME-1908.iso 9a2c47d97b9975452f7d582264e9fc16d108ed8252ac6816239a3b58cef5c53d CentOS-7-x86_64-Minimal-1908.iso 9bba3da2876cb9fcf6c28fb636bcbd01832fe6d84cd7445fa58e44e569b3b4fe CentOS-7-x86_64-DVD-1908.iso 0ef3310d13f7fc140ec5180dc05369d2f473e802577466825205d17e46ef5a9b CentOS-7-x86_64-LiveKDE-1908.iso bd5e6ca18386e8a8e0b5a9e906297b5610095e375e4d02342f07f32022b13acf CentOS-7-x86_64-Everything-1908.iso 6ffa7ad44e8716e4cd6a5c3a85ba5675a935fc0448c260f43b12311356ba85ad CentOS-7-x86_64-NetInstall-1908.iso Information for the torrent files and sums are available at http://mirror.centos.org/centos/7/isos/x86_64 -------- Additional Images The container, Vagrant, Cloud and Atomic Host images are being prepared and will be released in the next few days. Look for an announcement posted to the centos-announce list for more information on availability for these in the coming days. ---------- Getting Help The CentOS ecosystem is sustained by community driven help and guidance. The best place to start for new users is at http://wiki.centos.org/GettingHelp We are also on social media, you can find the project: on Twitter at? : http://twitter.com/CentOSProject on Facebook at : https://www.facebook.com/groups/centosproject/ on LinkedIn at : https://www.linkedin.com/groups/22405 And you will find the core team and a majority of the contributors on irc, on freenode.net in #centos ; talking about the finer points of distribution engineering and platform enablement. ---------- Contributors This release was made possible due to the hard work of many people, foremost on that list are the Red Hat Engineers for producing a great distribution and the CentOS QA team, without them CentOS Linux would look very different. Many of the team went further and beyond expectations to bring this release to you, and I would like to thank everyone for their help. We are also looking for people to get involved with the QA process in CentOS, if you would like to join this please introduce yourself on the centos-devel list (http://lists.centos.org/mailman/listinfo/centos-devel ). Finally, please join me in thanking the donors who all make this possible for us. Enjoy the fresh new release! Thanks, Johnny Hughes

1 0

OT: DMARC / DKIM Failure Reports
by Miroslav Geisselreiter 17 Sep '19

17 Sep '19

Hi guys, when I send e-mails to CentOS mailing list <centos(a)centos.org>, I received DMARC / DKIM failure reports. Is it possible to solve this problem and if so how? This is the first report: This is an email abuse report for an email message received from IP 208.100.23.70 on Tue, 17 Sep 2019 15:56:25 +0200. The message below did not meet the sending domain's DMARC policy. For more information about this format please seehttp://tools.ietf.org/html/rfc6591 . Feedback-Type: auth-failure User-Agent: Lua/1.0 Version: 1.0 Original-Mail-From:centos-bounces@centos.org Original-Rcpt-To:obodor@vub.sk Arrival-Date: Tue, 17 Sep 2019 15:56:25 +0200 Message-ID:<5502e8ac-6b01-18dd-e028-7d2dd666063b(a)intar.cz> Authentication-Results: dmarc=fail (p=none, dis=none) header.from=intar.cz Source-IP: 208.100.23.70 Delivery-Result: smg-policy-action Auth-Failure: dmarc Reported-Domain: intar.cz ------------ This is the seconf report: This is an authentication failure report for an email message received from IP 208.100.23.70 on Tue, 17 Sep 2019 15:56:32 +0200 (CEST). Feedback-Type: auth-failure Version: 1 User-Agent: OpenDMARC-Filter/1.3.2 Auth-Failure: dmarc Authentication-Results: mx.bitactive.com; dmarc=fail header.from=intar.cz Original-Envelope-Id: 46Xl5X0Ss6z1ltXM Original-Mail-From:centos-bounces@centos.org Source-IP: 208.100.23.70 (mail.centos.org) Reported-Domain: intar.cz Authentication-Results: mx.bitactive.com; dkim=fail reason="signature verification failed" (1024-bit key) header.d=intar.czheader.i=(a)intar.cz header.b="rSnG4eyi" Received: from mail.centos.org (mail.centos.org [208.100.23.70]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.bitactive.com (Postfix) with ESMTPS id 46Xl5X0Ss6z1ltXM for<mwanat(a)forall.pl>; Tue, 17 Sep 2019 15:56:32 +0200 (CEST) Received: from mail.centos.org (localhost [IPv6:::1]) by mail.centos.org (Postfix) with ESMTP id 011EE3C1F16; Tue, 17 Sep 2019 13:56:03 +0000 (UTC) X-Original-To:centos@centos.org Delivered-To:centos@centos.org Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=81.19.4.73; helo=nirvana.intar.cz;envelope-from=mg(a)intar.cz; receiver=centos(a)centos.org Received: from nirvana.intar.cz (nirvana.intar.cz [81.19.4.73]) by mail.centos.org (Postfix) with ESMTPS id 640643C1F0F for<centos(a)centos.org>; Tue, 17 Sep 2019 13:55:59 +0000 (UTC) Received: from larix.intarnet.cz (larix.intarnet.cz [192.168.1.53]) by nirvana.intar.cz (Postfix) with ESMTPS id 74992C045CD1; Tue, 17 Sep 2019 15:55:57 +0200 (CEST) Received: from [192.168.1.176] (nirvana.intar.cz [81.19.4.73]) by larix.intarnet.cz (Postfix) with ESMTPSA id 5EB62104F460; Tue, 17 Sep 2019 15:55:57 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intar.cz; s=larix; t=1568728557; bh=ezgga1YmsO9WxPgAc+7ouaZ9HJlG9XkA8LJjbiJd0yA=; h=Subject:To:References:From:Date:In-Reply-To; b=rSnG4eyiHg6tTDdBdCJyp1/ACUczgG+9usycftG3BMz1EwN0zPMPyo0gSkpvxwJUf aM/jvd/gzFJVz7Z6MEw1A9iCE0ZzJy931WvXG+rIJR+Set5hb3fMpu1PgaOz1MIYTF 7Z24H3X1KwUPof1RaKHrFQLYFbr011IbEwz613Xo= To: CentOS mailing list<centos(a)centos.org>, Mauricio Tavares<raubvogel(a)gmail.com> References:<b3f926b0-711f-4a32-4a61-644e707a8db8(a)intar.cz> <CAHEKYV42BVbAiPmCPnDPhQm53=+t6PVpjheXvjEY535kHFttSg(a)mail.gmail.com> <ea092741-5941-c49d-7fe2-b4e8df9944ed(a)intar.cz> <CAHEKYV5T8UJNB-PVoj=Aujje3MjN-HiAxKp9kcB24ZK6z8d2Kg(a)mail.gmail.com> From: Miroslav Geisselreiter<mg(a)intar.cz> Organization: INTAR a.s. Message-ID:<5502e8ac-6b01-18dd-e028-7d2dd666063b(a)intar.cz> Date: Tue, 17 Sep 2019 15:55:57 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 MIME-Version: 1.0 In-Reply-To:<CAHEKYV5T8UJNB-PVoj=Aujje3MjN-HiAxKp9kcB24ZK6z8d2Kg(a)mail.gmail.com> Subject: Re: [CentOS] CentOS7 sometimes don't detect NIC after reboot X-BeenThere:centos@centos.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe:<https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive:<http://lists.centos.org/pipermail/centos/> List-Post:<mailto:centos@centos.org> List-Help:<mailto:centos-request@centos.org?subject=help> List-Subscribe:<https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> Reply-To: CentOS mailing list<centos(a)centos.org> Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To:centos-bounces@centos.org Sender: "CentOS"<centos-bounces(a)centos.org>

3 2

Release for CentOS Linux 7 (1908) on armhfp aarch64 i386 ppc64 ppc64le and power9
by Johnny Hughes 17 Sep '19

17 Sep '19

On 9/17/19 8:23 AM, Pablo Sebastián Greco wrote: <snip> Should be .. CentOS 7 (1908)

1 0

audit freeing multiple contexts (when running certbot)
by tony＠softins.co.uk 17 Sep '19

17 Sep '19

Apologies if it's considered off-topic, but I'm not sure in what part of the system the issue lies. So I am giving as much info as possible, not knowing which is most relevant. I have two VMs hosted on ESX, running CentOS 6.10 One has kernel 2.6.32-754.11.1.el6.i686 and the other has 2.6.32-754.18.2.el6.i686 Both have selinux, currently in permissive mode. On both machines we have noticed messages like the following appear in /var/log/messages from time to time: Sep 17 10:32:28 merlin kernel: audit(:0): major=252 name_count=0: freeing multiple contexts (1) Sep 17 10:32:28 merlin kernel: audit(:0): major=355 name_count=0: freeing multiple contexts (2) Sep 17 10:32:29 merlin kernel: audit(:0): major=252 name_count=0: freeing multiple contexts (1) Sep 17 10:32:29 merlin kernel: audit(:0): major=355 name_count=0: freeing multiple contexts (2) On further investigation, this only happens when certbot-auto runs (under python 3.4), whether or not it renews the certificate. The above instance was created by running the following command: [root@merlin ~]# date ; cd /opt/letsencrypt && ./certbot-auto renew ; date Tue Sep 17 10:32:24 BST 2019 /opt/eff.org/certbot/venv/lib/python3.4/site-packages/cryptography/hazmat/bindings/openssl/binding.py:163: CryptographyDeprecationWarning: OpenSSL version 1.0.1 is no longer supported by the OpenSSL project, please upgrade. A future version of cryptography will drop support for it. utils.CryptographyDeprecationWarning Saving debug log to /var/log/letsencrypt/letsencrypt.log - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/xxxx.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cert not yet due for renewal - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The following certs are not due for renewal yet: /etc/letsencrypt/live/xxxx/fullchain.pem expires on 2019-11-15 (skipped) No renewals were attempted. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Tue Sep 17 10:32:30 BST 2019 [root@merlin letsencrypt]# Has anyone else seen anything similar? Is it something that can be fixed, or should be ignored? Cheers Tony -- Tony Mountifield Work: tony(a)softins.co.uk - http://www.softins.co.uk Play: tony(a)mountifield.org - http://tony.mountifield.org

1 0

reconfigure centos-6.9 host to ignore missing nic
by James B. Byrne 16 Sep '19

16 Sep '19

I need to work on a host which has been offline and powered down for some time. I has CentOS-6.9 installed. At some point it had two nics, one on the motherboard (still present and working) and one as an expansion card. When booted the console displays: pciehp 0000:00:1c:0:pcie04: Failed to check link status repeatedly. How do I tell the host to ignore the missing nic or remove it from the system configuration so that the error is removed. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 1

How to disable i915 module
by Ian Pilcher 15 Sep '19

15 Sep '19

I am setting up CentOS 7 on my new firewall. This will run as a head- less system, accessed via a serial console when necessary. It's only a 2GB system, so I don't see any reason to have the GPU consuming any of the RAM. I've blacklisted the i915, drm, and drm_kms_helper modules and rebuilt the initramfs, but the i915 module is still being loaded. Anyone know what might be loading the module and how I can stop it? TIA! -- ======================================================================== Ian Pilcher arequipeno(a)gmail.com -------- "I grew up before Mark Zuckerberg invented friendship" -------- ========================================================================

1 1

RPMDB problem
by Fred Smith 14 Sep '19

14 Sep '19

When doing yum operations I get this message at the end of whatever yum was doing: ** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows: brscan4-0.4.8-1.x86_64 is a duplicate with brscan4-0.4.3-1.x86_64 It is true, if I do "rpm -qa | grep brscan" it shows two of them. what's the best/proper way to deal with this? -remove both, reinstall one? -remove one? which one? I don't see a feature in rpm (or yum) for removing a single one of duplicate packages. How? Thanks in advance! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- "For the word of God is living and active. Sharper than any double-edged sword, it penetrates even to dividing soul and spirit, joints and marrow; it judges the thoughts and attitudes of the heart." ---------------------------- Hebrews 4:12 (niv) ------------------------------

3 2

File server as host for a Windows Server VM?
by miguel medalha 14 Sep '19

14 Sep '19

I hope that someone here can give some advice on the following: I have a Samba based Active Directory. A CentOS 7.6 machine runs as a file server and hosts the Windows user profiles for all the Windows workstations. Now management has decided that they need a Windows server for a couple of administrative applications, which need MS SQL Server. That would be the only role of this Windows. Since the above mentioned server has enough resources (2x Quad Core Xeon 2.66 GHz with HT and 48 GB of RAM, a dual port 10 Gb NIC) I thought of making it a host for a Windows virtual machine using KVM. Given the resources and current setup we have, at the moment it wouldn't be practical to implement both servers as VMs on top of a bare metal hypervisor. According to your experience, is there any motive why I shouldn't use such a setup? Thank you for any insights.

5 8

Opinions on using CR repository in production environments.
by Gwaland 13 Sep '19

13 Sep '19

I was wondering what people's opinions are on running the CR repository on production systems? I'm currently predisposed to not do it since it indicates it hasn't fully gone through QA yet. But from my understanding except for the alt-arch systems these are just recompiles of the redhat RPMs after debranding right? I'm Curious how other people are treating this repository since, from the sounds of it, rpms are going to be in holding here between releases. So would you treat it as a production repository or for testing only? Do we know how it's actually intended to be treated? Any opinion is appreciated.

2 1

why windows 10 can't access centos samba
by qw 13 Sep '19

13 Sep '19

Hi, I can access centos's samba via windows 7, but fail via windows 10. Why? Thanks! Regards Andrew

10 16

clamd / amavisd missing socket
by Jon LaBadie 12 Sep '19

12 Sep '19

I think something along these lines appeared before but I was unable to find them. I'm on a 7.6 system, been running clamav and amavisd-new since 6 days with little problem. On a recent reboot, clamd@amavisd does not start up and fails manual start. The problem seems to be the missing socket that connects the pair, "/var/run/clamd.amavisd/clamd.socket". I believe this should be created by systemd files but I see no indication of them on my system. Anyone know which files might be missing and where to get copies? Or a work around to run clamd@amavisd and get rid of the "*** UNCHECKED ***' additions to my my Subject lines? BTW manual creation of the socket with netcat had no effect on the startup. Jon -- Jon H. LaBadie jon(a)jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)

2 2

Increase logging verbosity of saslauthd?
by Jobst Schmalenbach 12 Sep '19

12 Sep '19

Hi CentOS 7.X, sendmail.x86_64 8.14.7-5.el7, cyrus-sasl.x86_64 2.1.26-23.el7 There are conflicting message on how to increase the logging of saslauthd. I know I can do this: /usr/sbin/saslauthd -d -n0 -m /var/run/saslauthd -a pam but that requires a terminal as saslauthd logs the output to STDOUT, this is not what I want. I would like to have it started as a daemon and verbosity of logging increased into a log file. How can I increase the verbosity of logging for saslauthd? thanks -- Jobst Schmalenbach If you think knowledge is expensive, try ignorance.

3 5

Need to update gcc to version >=6 on CentOS 7 ?
by John Chludzinski 11 Sep '19

11 Sep '19

I need to build u-boot on my CentOS 7 machine but encounter this: > *** Your GCC is older than 6.0 and is not supported I've updated the installation on my machine but the current version is: > gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36) How do I go about updating gcc to version 6 or greater on my CentOS 7 machine? And do so safely?

3 7

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

oval support for centos
by Sep0lkit 06 Sep '19

06 Sep '19

We use oval to check the system vulnerability. Redhat offer official oval(https://www.redhat.com/security/data/oval/), and it works well on redhat. There is no official centos oval, and using redhat oval on centos got false results. centos is based redhat, so I wrote a script fetch redhat oval files and convert it to useful for centos. And I push the oval to my github: https://github.com/Sep0lkit/oval-for-el Everyone interested in this can try to use it and tell me it works correctly or not.

2 2

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

nextcloud-client currently not installable from EPEL in CentOS7
by Kay Diederichs 02 Sep '19

02 Sep '19

Dear all, after enabling the EPEL repository, [root@localhost ~]# yum install nextcloud-client in a freshly installed and updated CentOS 7.6 machine gives Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * base: centos.bio.lmu.de * epel: ftp.uni-stuttgart.de * extras: centos.schlundtech.de * updates: mirror1.hs-esslingen.de Resolving Dependencies --> Running transaction check ---> Package nextcloud-client.x86_64 0:2.3.3-1.el7 will be installed --> Processing Dependency: nextcloud-client-libs(x86-64) = 2.3.3-1.el7 for package: nextcloud-client-2.3.3-1.el7.x86_64 --> Processing Dependency: libQt5WebKitWidgets.so.5(Qt_5)(64bit) for package: nextcloud-client-2.3.3-1.el7.x86_64 --> Processing Dependency: libQt5Solutions_LockedFile-2.4.so.1()(64bit) for package: nextcloud-client-2.3.3-1.el7.x86_64 --> Processing Dependency: libQt5Solutions_SingleApplication-2.6.so.1()(64bit) for package: nextcloud-client-2.3.3-1.el7.x86_64 --> Processing Dependency: libQt5WebKit.so.5()(64bit) for package: nextcloud-client-2.3.3-1.el7.x86_64 --> Processing Dependency: libQt5WebKitWidgets.so.5()(64bit) for package: nextcloud-client-2.3.3-1.el7.x86_64 --> Processing Dependency: libnextcloudsync.so.0()(64bit) for package: nextcloud-client-2.3.3-1.el7.x86_64 --> Processing Dependency: libocsync.so.0()(64bit) for package: nextcloud-client-2.3.3-1.el7.x86_64 --> Processing Dependency: libqt5keychain.so.1()(64bit) for package: nextcloud-client-2.3.3-1.el7.x86_64 --> Running transaction check ---> Package nextcloud-client-libs.x86_64 0:2.3.3-1.el7 will be installed ---> Package qt5-qtwebkit.x86_64 0:5.9.1-2.el7 will be installed --> Processing Dependency: qt5-qtbase(x86-64) = 5.9.7 for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: qt5-qtdeclarative(x86-64) = 5.9.7 for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5Positioning.so.5(Qt_5)(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5Qml.so.5(Qt_5)(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5Quick.so.5(Qt_5)(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5Quick.so.5(Qt_5_PRIVATE_API)(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5Sensors.so.5(Qt_5)(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5WebChannel.so.5(Qt_5)(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5Positioning.so.5()(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5Qml.so.5()(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5Quick.so.5()(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5Sensors.so.5()(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5WebChannel.so.5()(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 ---> Package qtkeychain-qt5.x86_64 0:0.7.0-1.el7 will be installed --> Processing Dependency: qtkeychain(x86-64) = 0.7.0-1.el7 for package: qtkeychain-qt5-0.7.0-1.el7.x86_64 ---> Package qtlockedfile-qt5.x86_64 0:2.4-20.20150629git5a07df5.el7 will be installed ---> Package qtsingleapplication-qt5.x86_64 0:2.6.1-28.el7 will be installed --> Running transaction check ---> Package qt5-qtdeclarative.x86_64 0:5.9.2-1.el7 will be installed --> Processing Dependency: libQt5XmlPatterns.so.5(Qt_5)(64bit) for package: qt5-qtdeclarative-5.9.2-1.el7.x86_64 --> Processing Dependency: libQt5XmlPatterns.so.5()(64bit) for package: qt5-qtdeclarative-5.9.2-1.el7.x86_64 ---> Package qt5-qtlocation.x86_64 0:5.9.2-1.el7 will be installed ---> Package qt5-qtsensors.x86_64 0:5.9.2-1.el7 will be installed ---> Package qt5-qtwebchannel.x86_64 0:5.9.2-1.el7 will be installed ---> Package qt5-qtwebkit.x86_64 0:5.9.1-2.el7 will be installed --> Processing Dependency: qt5-qtbase(x86-64) = 5.9.7 for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: qt5-qtdeclarative(x86-64) = 5.9.7 for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 ---> Package qtkeychain.x86_64 0:0.7.0-1.el7 will be installed --> Processing Dependency: libQtCore.so.4()(64bit) for package: qtkeychain-0.7.0-1.el7.x86_64 --> Processing Dependency: libQtDBus.so.4()(64bit) for package: qtkeychain-0.7.0-1.el7.x86_64 --> Running transaction check ---> Package qt.x86_64 1:4.8.7-3.el7_6 will be installed --> Processing Dependency: qt-settings for package: 1:qt-4.8.7-3.el7_6.x86_64 ---> Package qt5-qtwebkit.x86_64 0:5.9.1-2.el7 will be installed --> Processing Dependency: qt5-qtbase(x86-64) = 5.9.7 for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: qt5-qtdeclarative(x86-64) = 5.9.7 for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 ---> Package qt5-qtxmlpatterns.x86_64 0:5.9.2-1.el7 will be installed --> Running transaction check ---> Package qt-settings.noarch 0:19-23.8.el7.centos will be installed ---> Package qt5-qtwebkit.x86_64 0:5.9.1-2.el7 will be installed --> Processing Dependency: qt5-qtbase(x86-64) = 5.9.7 for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: qt5-qtdeclarative(x86-64) = 5.9.7 for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Finished Dependency Resolution Error: Package: qt5-qtwebkit-5.9.1-2.el7.x86_64 (epel) Requires: qt5-qtbase(x86-64) = 5.9.7 Installed: qt5-qtbase-5.9.2-3.el7.x86_64 (@anaconda) qt5-qtbase(x86-64) = 5.9.2-3.el7 Error: Package: qt5-qtwebkit-5.9.1-2.el7.x86_64 (epel) Requires: qt5-qtdeclarative(x86-64) = 5.9.7 Available: qt5-qtdeclarative-5.9.2-1.el7.x86_64 (base) qt5-qtdeclarative(x86-64) = 5.9.2-1.el7 Error: Package: qt5-qtwebkit-5.9.1-2.el7.x86_64 (epel) Requires: qt5-qtdeclarative(x86-64) = 5.9.7 Installing: qt5-qtdeclarative-5.9.2-1.el7.x86_64 (base) qt5-qtdeclarative(x86-64) = 5.9.2-1.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@localhost ~]# The culprit appears to be the current qt5-qtwebkit-5.9.1-2 from EPEL. A workaround is: downloading and installing qt5-qtwebkit-5.9.1-1 (from https://archive.fedoraproject.org/pub/archive/epel/7/x86_64/Packages/ ) lets the installation succeed. However, /etc/yum.conf then needs exclude=qt5-qtwebkit I think this is is due to the fact that EPEL is synchronized with RedHat (which has version 7.7), but CentOS is still at 7.6 This type of problem has bitten us a couple of times (mostly with ElRepo and the NVidia kmod and driver) - whenever a CentOS update was not yet ready, but the corresponding RedHat point release was out. ElRepo seems to have an elegant solution for this solution - yum-plugin-elrepo . Is there anything like that available for EPEL ? thanks, Kay

1 0

Mailbox for Sysadmin
by Administrator 01 Sep '19

01 Sep '19

Good day Administrator, Every self-respecting Admin should have a mailbox in worthy domain. Do you have it already? If no - go to https://nox11.com choose one and start new life If you aren't interested accept apology for spam. --- Cheers admin(a)nox11.com

3 2

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss