Discuss

discuss@lists.centos.org

2 participants
34758 discussions

ssh failure from CentOS7 to Centos6
by Patrick Bégou 19 Jan '20

19 Jan '20

Hi, I have a strange problem with a freshly installed Centos7 desktop (most8pc25). I can't ssh to 2 CentOS6 servers, even with firewall disabled on the client and on the server. But I can connect from the server to the client, all in the same VLAN. I can also ssh from this desktop to centos7 servers in the same VLAN or in another VLAN. No idea about this problem. On the server kareline (client is most8pc25), tcpdump says: tcpdump: listening on p5p1, link-type EN10MB (Ethernet), capture size 65535 bytes 18:17:25.844816 IP (tos 0x0, ttl 64, id 19021, offset 0, flags [DF], proto TCP (6), length 60) most8pc25.legi.grenoble-inp.fr.36414 > kareline.legi.grenoble-inp.fr.ssh: Flags [S], cksum 0xfff1 (correct), seq 3060883003, win 26880, options [mss 8960,sackOK,TS val 2888822 ecr 0,nop,wscale 7], length 0 18:17:25.844927 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 52) kareline.legi.grenoble-inp.fr.ssh > most8pc25.legi.grenoble-inp.fr.36414: Flags [S.], cksum 0xa1f5 (correct), seq 1624136656, ack 3060883004, win 17920, options [mss 8960,nop,nop,sackOK,nop,wscale 7], length 0 18:17:25.845014 IP (tos 0x0, ttl 64, id 19022, offset 0, flags [DF], proto TCP (6), length 40) most8pc25.legi.grenoble-inp.fr.36414 > kareline.legi.grenoble-inp.fr.ssh: Flags [.], cksum 0x4542 (correct), ack 1, win 210, length 0 18:17:25.845406 IP (tos 0x0, ttl 64, id 19023, offset 0, flags [DF], proto TCP (6), length 61) most8pc25.legi.grenoble-inp.fr.36414 > kareline.legi.grenoble-inp.fr.ssh: Flags [P.], cksum 0x817c (correct), seq 1:22, ack 1, win 210, length 21 18:17:25.845435 IP (tos 0x0, ttl 64, id 27577, offset 0, flags [DF], proto TCP (6), length 40) kareline.legi.grenoble-inp.fr.ssh > most8pc25.legi.grenoble-inp.fr.36414: Flags [.], cksum 0x4573 (correct), ack 22, win 140, length 0 18:17:25.854750 IP (tos 0x0, ttl 64, id 27578, offset 0, flags [DF], proto TCP (6), length 61) kareline.legi.grenoble-inp.fr.ssh > most8pc25.legi.grenoble-inp.fr.36414: Flags [P.], cksum 0x0a4e (incorrect -> 0x84ad), seq 1:22, ack 22, win 140, length 21 18:17:25.854887 IP (tos 0x0, ttl 64, id 19024, offset 0, flags [DF], proto TCP (6), length 40) most8pc25.legi.grenoble-inp.fr.36414 > kareline.legi.grenoble-inp.fr.ssh: Flags [.], cksum 0x4518 (correct), ack 22, win 210, length 0 18:17:25.856766 IP (tos 0x0, ttl 64, id 27579, offset 0, flags [DF], proto TCP (6), length 880) kareline.legi.grenoble-inp.fr.ssh > most8pc25.legi.grenoble-inp.fr.36414: Flags [P.], cksum 0x0d81 (incorrect -> 0x8fa1), seq 22:862, ack 22, win 140, length 840 18:17:25.896278 IP (tos 0x0, ttl 64, id 19026, offset 0, flags [DF], proto TCP (6), length 40) most8pc25.legi.grenoble-inp.fr.36414 > kareline.legi.grenoble-inp.fr.ssh: Flags [.], cksum 0x3bea (correct), ack 862, win 224, length 0 18:17:26.055314 IP (tos 0x0, ttl 64, id 19027, offset 0, flags [DF], proto TCP (6), length 64) most8pc25.legi.grenoble-inp.fr.36414 > kareline.legi.grenoble-inp.fr.ssh: Flags [P.], cksum 0x0594 (correct), seq 1518:1542, ack 862, win 224, length 24 18:17:26.055348 IP (tos 0x0, ttl 64, id 27580, offset 0, flags [DF], proto TCP (6), length 52) kareline.legi.grenoble-inp.fr.ssh > most8pc25.legi.grenoble-inp.fr.36414: Flags [.], cksum 0xd6b0 (correct), ack 22, win 140, options [nop,nop,sack 1 {1518:1542}], length 0 18:18:22.446296 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has kareline.legi.grenoble-inp.fr tell most8pc25.legi.grenoble-inp.fr, length 46 18:18:22.446318 ARP, Ethernet (len 6), IPv4 (len 4), Reply kareline.legi.grenoble-inp.fr is-at 00:10:18:e7:91:c0 (oui Unknown), length 28 18:19:14.030270 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has kareline.legi.grenoble-inp.fr tell most8pc25.legi.grenoble-inp.fr, length 46 18:19:14.030287 ARP, Ethernet (len 6), IPv4 (len 4), Reply kareline.legi.grenoble-inp.fr is-at 00:10:18:e7:91:c0 (oui Unknown), length 28 ..... On the Centos7 client, with "-v -v" ssh says: [tec21@most8pc25 ~]$ssh -v -v kareline OpenSSH_7.4p1, OpenSSL 1.0.2k-fips 26 Jan 2017 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 58: Applying options for * debug2: resolving "kareline" port 22 debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to kareline [194.254.66.8] port 22. debug1: Connection established. debug1: key_load_public: No such file or directory debug1: identity file /home/tec21/.ssh/id_rsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/tec21/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/tec21/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/tec21/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/tec21/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/tec21/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/tec21/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/tec21/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_7.4 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH_5* compat 0x0c000000 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to kareline:22 as 'tec21' debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1,ext-info-c debug2: host key algorithms: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ssh-dss debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: compression ctos: none,zlib(a)openssh.com,zlib debug2: compression stoc: none,zlib(a)openssh.com,zlib debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug2: peer server KEXINIT proposal debug2: KEX algorithms: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: host key algorithms: ssh-rsa,ssh-dss debug2: ciphers ctos: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc(a)lysator.liu.se debug2: ciphers stoc: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc(a)lysator.liu.se debug2: MACs ctos: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: MACs stoc: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: compression ctos: none,zlib(a)openssh.com debug2: compression stoc: none,zlib(a)openssh.com debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug1: kex: algorithm: diffie-hellman-group-exchange-sha256 debug1: kex: host key algorithm: ssh-rsa debug1: kex: server->client cipher: aes128-ctr MAC: umac-64(a)openssh.com compression: none debug1: kex: client->server cipher: aes128-ctr MAC: umac-64(a)openssh.com compression: none debug1: kex: diffie-hellman-group-exchange-sha256 need=16 dh_need=16 debug1: kex: diffie-hellman-group-exchange-sha256 need=16 dh_need=16 debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<3072<8192) sent Connection closed by 194.254.66.8 port 22 I'm stuck.... Patrick

5 5

After upgrade to CentOS 8.1 default gateway missing
by Asle Ommundsen 18 Jan '20

18 Jan '20

Hi, Tonight I upgraded two CentOS 8 boxes to CentOS 8.1 (1911). Then after a reboot of the first server the network was unavailable. In IPMI console everything except the network was looking good. Network was unreachable. No errors in NetworkManager. I also restarted NetworkManager, but it did not help. Then I discovered that the default gateway suddenly was missing. Then I rebooted the server one more time, but network was still down. Then both myself and a technician in my datcenter was debugging this (I had to wake him up in the middle of the night, costing me a lot of money), without finding any reason for why the default gateway was missing after reboot. Then we rebooted the server a third time, and all of a sudden the problem was gone and the default gateway was back. Then, after this, I also upgraded my second CentOS 8 server to CentOS 8.1 and did a reboot. And the very same thing happened to this server after reboot! The default gateway was missing after reboot, and network was down. Then I did a extra reboot of this server also, and when it came back up everything was working correct and the default gateway was back. So the first server I needed to reboot two extra times to have the default gateway back and network working. And the second server I needed to reboot only one extra time for the problem to be solved. The two boxes is not VPSs or anything, but bare metal dedicated servers. Also prior to upgrading to CentOS 8.1, these two boxes has been rebooted serveral times previously, without any problems at all. Only after upgrading to CentOS 8.1 this happened on both of them for the first time. I can't believe I am the only one that experience this? My guess is that this is a unknown random intermittent bug in CentOS 8.1 that kicked in. I just hope this does not continue to happen in the future. If you experienced the same, please share it with a reply. Thank you! Kind regards, Asle Ommundsen

3 6

Re: [CentOS] Centos 8 and E1000 intel driver
by david 18 Jan '20

18 Jan '20

At 03:27 PM 1/17/2020, Akemi Yagi wrote: >On Fri, Jan 17, 2020 at 3:16 PM david <david(a)daku.org> wrote: > > > > Folks > > > > I know that support for the network adaptors supported by the 'e1000' > > driver have been removed from the base distribution. However, I have > > exactly that controller (Broadcom Gigabit Ethernet PCI, not > > PCIe). Is there a way for me to add support for that on Centos > > 8.1? Perhaps a driver in an RPM package? > > > > Thanks > > > > David > >The e1000 driver should be in the 8.1 kernel: > >$ modinfo e1000 >filename: >/lib/modules/4.18.0-147.3.1.el8_1.x86_64/kernel/drivers/net/ethernet/intel/e1000/e1000.ko.xz >version: 7.3.21-k8-NAPI >license: GPL >description: Intel(R) PRO/1000 Network Driver >author: Intel Corporation, <linux.nics(a)intel.com> >rhelversion: 8.1 > >Akemi >_________ Akemi Thanks for the suggestion. Modinfo does produce that result. But "the network doesn't work". My environment is a VirtualBox VM of Centos 8 on top of Windows 10. I've defined a bridged adaptor. The hardware is the Broadcom adaptor, using DHCP. No firewall is running in Centos 8 yet. This exact configuration works fine with Centos 7. The symptom I see is that DHCP, Ping, DNS Lookup all work, but no data transfer seems to work. I tried a CURL command to a local web machine (works with Centos 7), and it just hangs. The web server does not see the request. When I switch the network adaptor (in the VM) to NAT, everything works, probably indicating that the selection of the adaptor is the problem. I used the NAT interface to complete the install. Do you have any ideas? David *********** WHOA *************** It appears that this is not a Centos issue. My other VM's have stopped working also. The common factor is the use of a Bridged Network in VirtualBox on Windows 10 updated last week. Based upon prior similar events, I'd guess it's a Windows screw-up. Oh well. David

1 0

Re: [CentOS] Centos 8 and E1000 intel driver
by david 18 Jan '20

18 Jan '20

1 0

Centos 8 and E1000 intel driver
by david 17 Jan '20

17 Jan '20

Folks I know that support for the network adaptors supported by the 'e1000' driver have been removed from the base distribution. However, I have exactly that controller (Broadcom Gigabit Ethernet PCI, not PCIe). Is there a way for me to add support for that on Centos 8.1? Perhaps a driver in an RPM package? Thanks David

3 2

Limiting what devices can pair over Bluetooth?
by James Pearson 17 Jan '20

17 Jan '20

I've managed to get a Wacom Intuos Pro 2 (PTH-660) tablet working over Bluetooth to a CentOS 7 install. Well, I didn't actually have to do much to get it working ... However, we don't normally enable Bluetooth for security reasons, so I need to be able to configure things so Bluetooth can _only_ be used to pair with Wacom tablets As I never used Bluetooth in anger before, I'm struggling to find out where to start looking - does anyone know how to do this or any pointers on where I should start? Thanks James Pearson

4 9

Error in Centos 8 Linux 8.1.1911-x86_64 distro, syslinux 6.04 required vs. 6.03
by here Fishy 16 Jan '20

16 Jan '20

The image file includes the wrong (outdated) syslinux 6.03 and requires 6.04 per rufus. The fedora burner kept failing but rufus detected the issue and downloaded syslinux 6.04 files. Please update the distro.

1 0

CentOS 8 - auto-loading kickstart from USB doesn't work
by Chris Adams 16 Jan '20

16 Jan '20

While updating my base kickstart for CentOS 8.1, I noticed it won't auto-load from a USB device. I'm testing in a VM, but usually add a USB drive for the ks.cfg because my kickstart skips USB drives when picking where to install. If I leave the drive a virtio, or make it a CD, it works. I found https://bugzilla.redhat.com/show_bug.cgi?id=1770969 which then references a RHEL-subscriber-only solution. -- Chris Adams <linux(a)cmadams.net>

1 0

Re: [CentOS] CentOS 8: several packages have unresolved dependencies after "dnf update all "
by Stephen John Smoogen 16 Jan '20

16 Jan '20

On Thu, 16 Jan 2020 at 09:48, Philippe Piot <piot(a)nicadd.niu.edu> wrote: > > No it did not work; see: > [piot@paris ~]$ sudo dnf install --nobest --allowerasing gcc-c++ > Last metadata expiration check: 0:18:24 ago on Thu 16 Jan 2020 08:28:51 AM CST. > Error: > Problem: package gcc-8.3.1-4.5.el8.x86_64 requires glibc-devel >= 2.2.90-12, but none of the providers can be installed > - package glibc-devel-2.28-72.el8.i686 requires glibc-headers, but none of the providers can be installed > - package glibc-devel-2.28-72.el8.i686 requires glibc-headers = 2.28-72.el8, but none of the providers can be installed > - package glibc-devel-2.28-72.el8.x86_64 requires glibc-headers, but none of the providers can be installed > - package glibc-devel-2.28-72.el8.x86_64 requires glibc-headers = 2.28-72.el8, but none of the providers can be installed > - package gcc-c++-8.3.1-4.5.el8.x86_64 requires gcc = 8.3.1-4.5.el8, but none of the providers can be installed > - package glibc-headers-2.28-72.el8.i686 requires kernel-headers, but none of the providers can be installed > - package glibc-headers-2.28-72.el8.i686 requires kernel-headers >= 2.2.1, but none of the providers can be installed > - package glibc-headers-2.28-72.el8.x86_64 requires kernel-headers, but none of the providers can be installed > - package glibc-headers-2.28-72.el8.x86_64 requires kernel-headers >= 2.2.1, but none of the providers can be installed OK let us see if we can see what is on the system which is causing the problem. It is either going to be an existing gcc-XXX which needs to be removed or it is some other i686 item. rpm -qa | egrep 'glibc|gcc' rpm -qa | grep i686 # probably a big file so probably put it in a paste/gist somewhere would be better I just tested on an 8.0 box and was able to install gcc-c++ from 8.1 [root@li1064-117 ~]# yum install gcc-c++ Last metadata expiration check: 1:11:50 ago on 2020-01-16T16:41:09 UTC. Dependencies resolved. ============================================================================================================================================================================================== Package Arch Version Repository Size ============================================================================================================================================================================================== Installing: gcc-c++ x86_64 8.3.1-4.5.el8 AppStream 12 M Upgrading: glibc x86_64 2.28-72.el8 BaseOS 3.5 M glibc-common x86_64 2.28-72.el8 BaseOS 811 k glibc-langpack-en x86_64 2.28-72.el8 BaseOS 818 k libgcc x86_64 8.3.1-4.5.el8 BaseOS 78 k libgomp x86_64 8.3.1-4.5.el8 BaseOS 203 k libstdc++ x86_64 8.3.1-4.5.el8 BaseOS 450 k Installing dependencies: cpp x86_64 8.3.1-4.5.el8 AppStream 10 M gcc x86_64 8.3.1-4.5.el8 AppStream 23 M isl x86_64 0.16.1-6.el8 AppStream 841 k libmpc x86_64 1.0.2-9.el8 AppStream 59 k libstdc++-devel x86_64 8.3.1-4.5.el8 AppStream 2.0 M glibc-devel x86_64 2.28-72.el8 BaseOS 1.0 M glibc-headers x86_64 2.28-72.el8 BaseOS 469 k kernel-headers x86_64 4.18.0-147.3.1.el8_1 BaseOS 2.7 M libxcrypt-devel x86_64 4.1.1-4.el8 BaseOS 25 k Transaction Summary ============================================================================================================================================================================================== Install 10 Packages Upgrade 6 Packages Total download size: 59 M Is this ok [y/N]: y Downloading Packages: (1/16): cpp-8.3.1-4.5.el8.x86_64.rpm 31 MB/s | 10 MB 00:00 (2/16): isl-0.16.1-6.el8.x86_64.rpm 21 MB/s | 841 kB 00:00 (3/16): gcc-c++-8.3.1-4.5.el8.x86_64.rpm 28 MB/s | 12 MB 00:00 (4/16): libmpc-1.0.2-9.el8.x86_64.rpm 809 kB/s | 59 kB 00:00 (5/16): glibc-devel-2.28-72.el8.x86_64.rpm 26 MB/s | 1.0 MB 00:00 (6/16): libstdc++-devel-8.3.1-4.5.el8.x86_64.rpm 34 MB/s | 2.0 MB 00:00 (7/16): glibc-headers-2.28-72.el8.x86_64.rpm 17 MB/s | 469 kB 00:00 (8/16): libxcrypt-devel-4.1.1-4.el8.x86_64.rpm 2.1 MB/s | 25 kB 00:00 (9/16): kernel-headers-4.18.0-147.3.1.el8_1.x86_64.rpm 31 MB/s | 2.7 MB 00:00 (10/16): glibc-2.28-72.el8.x86_64.rpm 32 MB/s | 3.5 MB 00:00 (11/16): glibc-common-2.28-72.el8.x86_64.rpm 15 MB/s | 811 kB 00:00 (12/16): libgcc-8.3.1-4.5.el8.x86_64.rpm 6.8 MB/s | 78 kB 00:00 (13/16): glibc-langpack-en-2.28-72.el8.x86_64.rpm 31 MB/s | 818 kB 00:00 (14/16): libgomp-8.3.1-4.5.el8.x86_64.rpm 9.3 MB/s | 203 kB 00:00 (15/16): libstdc++-8.3.1-4.5.el8.x86_64.rpm 21 MB/s | 450 kB 00:00 (16/16): gcc-8.3.1-4.5.el8.x86_64.rpm 29 MB/s | 23 MB 00:00 ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 71 MB/s | 59 MB 00:00 > - conflicting requests > - package kernel-headers-4.18.0-147.0.3.el8_1.x86_64 is excluded > - package kernel-headers-4.18.0-147.3.1.el8_1.x86_64 is excluded > - package kernel-headers-4.18.0-147.el8.x86_64 is excluded > (try to add '--skip-broken' to skip uninstallable packages) > > > Philippe Piot, > https://www.niu.edu/advanced-accelerator-randd/ > Northern Illinois University, Dept of Physics and > Northern Illinois Center for Accelerator & Detector Development > DeKalb, IL 60115, USA > Tel: 815 753 6473, Web: http://www.physics.niu.edu/physics/ > > Argonne National Laboratory, Advanced Photon Source > Accelerator System Division > Lemont, IL 60439, USA > Tel: 630 252 2415, Web: https://www.aps.anl.gov/Accelerator-Systems-Division > > > On Thu, Jan 16, 2020 at 8:38 AM Stephen John Smoogen <smooge(a)gmail.com> wrote: >> >> On Thu, 16 Jan 2020 at 08:27, Philippe Piot <piot(a)nicadd.niu.edu> wrote: >> > >> > Also just to be more specific I am running CentOS 8.1. So the issue I >> > encounter were after upgrading to 8.1. Thank you! -- Philippe. >> > >> > >> > On Thu, Jan 16, 2020 at 6:48 AM Philippe Piot <piot(a)nicadd.niu.edu> wrote: >> > >> > > I am doing a dnf install package_without_version for instance for g++: >> > > >> > > [piot@paris opal]$ sudo dnf install gcc-c++ >> > > Last metadata expiration check: 0:01:06 ago on Thu 16 Jan 2020 06:45:59 AM >> > > CST. >> > > Error: >> > > Problem: package gcc-8.3.1-4.5.el8.x86_64 requires glibc-devel >= >> > > 2.2.90-12, but none of the providers can be installed >> > > - package glibc-devel-2.28-72.el8.i686 requires glibc-headers, but none >> > > of the providers can be installed >> >> OK I see the problem.. arch difficulties entered in sometime. You have >> some .i686 packages installed which got filtered into the compose at >> some point when they shouldn't have been. >> >> Please try adding --nobest --allowerasing to the install and see if it >> gets past this. >> >> >> >> -- >> Stephen J Smoogen. -- Stephen J Smoogen.

1 0

CentOS 8: several packages have unresolved dependencies after "dnf update all "
by Philippe Piot 16 Jan '20

16 Jan '20

All, While updating my package using dnf update all I allow dnf to clean some package with unresolved dependencies. I would like to reinstall some of them but got an error message "but none of the providers can be installed" during the install process as dnf is trying to install the dependencies. . This happens for some critical package like boost-openmpi-devel (see below for error). In fact the following package were removed and cannot be installed: annobin-8.64-1.el8.x86_64 glibc-headers-2.28-42.el8.1.x86_64 libdrm-devel-2.4.96-2.el8.x86_64 boost-devel-1.66.0-6.el8.x86_64 boost-openmpi-devel-1.66.0-6.el8.x86_64 boost-static-1.66.0-6.el8.x86_64 gcc-8.2.1-3.5.el8.x86_64 gcc-c++-8.2.1-3.5.el8.x86_64 gcc-gdb-plugin-8.2.1-3.5.el8.x86_64 gcc-gfortran-8.2.1-3.5.el8.x86_64 glibc-devel-2.28-42.el8.1.x86_64 hdf5-devel-1.10.5-4.el8.x86_64 hdf5-openmpi-devel-1.10.5-4.el8.x86_64 hdf5-openmpi-static-1.10.5-4.el8.x86_64 hdf5-static-1.10.5-4.el8.x86_64 libquadmath-devel-8.2.1-3.5.el8.x86_64 libtool-2.4.6-25.el8.x86_64 libxcrypt-devel-4.1.1-4.el8.x86_64 mesa-libEGL-devel-18.3.1-5.el8_0.x86_64 mesa-libGL-devel-18.3.1-5.el8_0.x86_64 openmpi-devel-3.1.2-5.el8.x86_64 poppler-qt5-devel-0.66.0-11.el8_0.12.x86_64 qscintilla-qt5-devel-2.11.2-6.el8.x86_64 qt5-doctools-5.11.1-5.el8.x86_64 qt5-qtbase-devel-5.11.1-5.el8.x86_64 qt5-qtscript-devel-5.11.1-2.el8.x86_64 qt5-qttools-devel-5.11.1-5.el8.x86_64 qt5-qttools-static-5.11.1-5.el8.x86_64 qt5-rpm-macros-5.11.1-2.el8.noarch systemtap-4.0-7.el8.x86_64 systemtap-devel-4.0-7.el8.x86_64 Thank you for any suggestions. -- Philippe. ERROR MESSAGE WHEN TRYING TO INSTALL ONE OF THESE PACKAGES: ------------------------------------------ [piot@paris ~]$ sudo dnf install boost-openmpi-devel [sudo] password for piot: Last metadata expiration check: 0:13:02 ago on Wed 15 Jan 2020 10:05:29 PM CST. Error: Problem: package libquadmath-devel-8.3.1-4.5.el8.x86_64 requires gcc = 8.3.1-4.5.el8, but none of the providers can be installed - package gcc-8.3.1-4.5.el8.x86_64 requires glibc-devel >= 2.2.90-12, but none of the providers can be installed - package boost-devel-1.66.0-6.el8.x86_64 requires libquadmath-devel(x86-64), but none of the providers can be installed - package glibc-devel-2.28-72.el8.i686 requires glibc-headers, but none of the providers can be installed - package glibc-devel-2.28-72.el8.i686 requires glibc-headers = 2.28-72.el8, but none of the providers can be installed - package glibc-devel-2.28-72.el8.x86_64 requires glibc-headers, but none of the providers can be installed - package glibc-devel-2.28-72.el8.x86_64 requires glibc-headers = 2.28-72.el8, but none of the providers can be installed - package boost-openmpi-devel-1.66.0-6.el8.x86_64 requires boost-devel(x86-64) = 1.66.0-6.el8, but none of the providers can be installed - package glibc-headers-2.28-72.el8.i686 requires kernel-headers, but none of the providers can be installed - package glibc-headers-2.28-72.el8.i686 requires kernel-headers >= 2.2.1, but none of the providers can be installed - package glibc-headers-2.28-72.el8.x86_64 requires kernel-headers, but none of the providers can be installed - package glibc-headers-2.28-72.el8.x86_64 requires kernel-headers >= 2.2.1, but none of the providers can be installed - cannot install the best candidate for the job - package kernel-headers-4.18.0-147.0.3.el8_1.x86_64 is excluded - package kernel-headers-4.18.0-147.3.1.el8_1.x86_64 is excluded - package kernel-headers-4.18.0-147.el8.x86_64 is excluded Philippe Piot, https://www.niu.edu/advanced-accelerator-randd/ <https://www.niu.edu/advanced-accelerator-randd/index.shtml> Northern Illinois University, Dept of Physics and Northern Illinois Center for Accelerator & Detector Development DeKalb, IL 60115, USA Tel: 815 753 6473, Web: http://www.physics.niu.edu/physics/ Argonne National Laboratory, Advanced Photon Source Accelerator System Division Lemont, IL 60439, USA Tel: 630 252 2415, Web: https://www.aps.anl.gov/Accelerator-Systems-Division

2 6

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss