Discuss

discuss@lists.centos.org

7 participants
34743 discussions

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

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