Discuss January 2020

discuss@lists.centos.org

93 participants
71 discussions

CentOS 7 yum update
by Jerry Geis 08 Jan '20

08 Jan '20

I was in the middle of a yum update on physical box over teh weekend and power died. Ssytem came pack up. But now when I run yum-complete-transaction I get all kinds of errors (these are just the last 4, there are many) systemtap-runtime-4.0-10.el7_7.x86_64 has installed conflicts systemtap-devel < ('0', '4.0', '10.el7_7'): systemtap-devel-4.0-9.el7.x86_64 systemtap-runtime-4.0-10.el7_7.x86_64 has installed conflicts systemtap-client < ('0', '4.0', '10.el7_7'): systemtap-client-4.0-9.el7.x86_64 systemtap-runtime-4.0-10.el7_7.x86_64 is a duplicate with systemtap-runtime-4.0-9.el7.x86_64 util-linux-2.23.2-61.el7_7.1.x86_64 is a duplicate with util-linux-2.23.2-61.el7.x86_64 what to do ? Thanks, Jerry

3 2

can't boot after volume rename
by Paul Amaral 07 Jan '20

07 Jan '20

I renamed my volume with vgrename however I didn't complete the other steps. Mainly update fstab and intiramfs. Once I booted, I was dropped on the Dracut shell. From here I can see the newly rename VG and I can lvm lvscan as well as activate it, lvm vgchange -ay. However I can't figure out what to do next, I'm assuming I need to regenerate the initramfs and then boot to change grub? Could someone point me in the right direction to recovering a FS from Dracut, or other means, once the volume group name was changed. TIA, Paul

3 4

Network Diagnostics
by Chris Olson 07 Jan '20

07 Jan '20

In our smallest office, we have a Dell CentOS 7 system, a Windows system and an HP 8610 printer, all hard-wire Ethernet connected with a Linksys router. The router provides Internet connection. All of the network-connected systems get their IP address from the router at power up. Successful network connection of the printer at power up has recently started taking much longer than usual. The display on the front of the printer indicates that it is initially attempting wireless connection even though this feature is turned off. Ethernet connection is eventually achieved and the printer functions normally on the network but just for a few minutes. After about five minutes, the printer drops its Ethernet connection and appears to be attempting wireless connection once again. During this period, network connectivity is disrupted for the other systems on the network. They are not able to communicate with each other or access the Internet through the router. Turning off the printer restores network connection for the other systems. One of our personnel at another office suggested using Wireshark to check out the network when the printer is having difficulty. Wireshark was apparently not on this system so we installed it using yum install. The tail end of the apparently successful installation process is shown below. Unfortunately, we cannot seem to find Wireshark on the system. Is it possible that Wireshark was not actually installed or do we just not know how to locate and use it? Is this printer networking issue a known problem and is Wireshark the right tool to diagnose the problem? Thanks. Installed: wireshark.x86_64 0:1.10.14-16.el7 Dependency Installed: libsmi.x86_64 0:0.4.8-13.el7 Complete! [user@computer ~]$ [user@computer ~]$ which wireshark /usr/bin/which: no wireshark in (/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/home/user/.local/bin:/home/user/bin) [user@computer ~]$ Recent successful installations: -------------------------------- [user@computer ~]$ [user@computer ~]$ which mplayer /usr/bin/mplayer [user@computer ~]$ which ffmpeg /usr/bin/ffmpeg [user@computer ~]$

3 2

USB drive very slow on CentOS 8
by Michael Eager 04 Jan '20

04 Jan '20

I recently upgraded from CentOS 7 to CentOS 8. I have a Mediasonic HF2-SU3S2 external drive enclosure with 4x3Tb drives configured as a software RAID 5 array (mdadm) with LVM. It's connected to a USB 3.0 port. On CentOS 7, the drive performance is reasonable. On CentOS 8, performance is extremely slow, about USB 1.0 performance. Maybe worse. Connecting an external USB SSD to the CentOS 8 system appears to perform well. I've updated the ASUS Prime-B350-Plus motherboard with the latest BIOS, but it doesn't appear to make any difference. Does anyone have any idea what might be different between CentOS 7 and 8 that would cause this? -- Michael Eager eager(a)eagerm.com 1960 Park Blvd., Palo Alto, CA 94306

1 0

Re: [CentOS] CentOS 7 as a Fibre Channel SAN Target
by Steffan Cline 04 Jan '20

04 Jan '20

In waiting, I tried CentOS 8 which was an even bigger bust. I wiped that clean and tried again with Fedora 31. Same darn error "Could not create Target in configFS". Anyone?? Thank you, Steffan Cline steffan(a)hldns.com 602-793-0014 On 1/2/20, 2:00 AM, "CentOS on behalf of Steffan Cline via CentOS" <centos-bounces(a)centos.org on behalf of centos(a)centos.org> wrote: It took me some time to come back full circle to this. I've worked quite a bit on this with little success so far. It seems like it's been done but on some of the forums and Github, there are no responses yet. This is essentially a cross post from a seemingly dead list. Hopefully someone here will have some suggestions. I've googled this particular issue and not really finding any good results on how to resolve it. I installed targetcli via yum on CentOS 7 and this is the version in the repo: # targetcli targetcli shell version 2.1.fb49 Copyright 2011-2013 by Datera, Inc and others. For help on commands, type 'help'. I downloaded the .zip of the targetcli-fb version and tried it too from the scripts folder and same results. Python: # python --version Python 2.7.5 Libs: Installed Packages python-configshell.noarch 1:1.1.fb25-1.el7 @base python-rtslib.noarch 2.1.fb69-3.el7 @base python-rtslib-doc.noarch 2.1.fb69-3.el7 @base The error comes up when using create. /> /qla2xxx create naa.xxxxxxxxxxxxxxx Could not create Target in configFS Below is the info on my FC /> qla2xxx/ info Fabric module name: qla2xxx ConfigFS path: /sys/kernel/config/target/qla2xxx Allowed WWN types: naa Allowed WWNs list: naa.xxxxxxxxxxxxxxx, naa.xxxxxxxxxxxxxxx, naa.xxxxxxxxxxxxxxx, naa.xxxxxxxxxxxxxxx, naa.xxxxxxxxxxxxxxx, naa.xxxxxxxxxxxxxxx, naa.xxxxxxxxxxxxxxx, naa.xxxxxxxxxxxxxxx Fabric module features: acls Corresponding kernel module: tcm_qla2xxx I have attached the log but don't see anything that really stands out. log.txt I checked per the link http://www.linux-iscsi.org/wiki/Fibre_Channel#Enable_target_mode to ensure that I have initiator mode disabled # cat /sys/module/qla2xxx/parameters/qlini_mode disabled The kernel modules are loaded. # lsmod | grep qla2xxx tcm_qla2xxx 32768 1 target_core_mod 335872 4 tcm_qla2xxx,iscsi_target_mod qla2xxx 634880 1 tcm_qla2xxx scsi_transport_fc 65536 3 bfa,qla2xxx,tcm_qla2xxx configfs is mounted: # cat /proc/mounts | grep configfs configfs /sys/kernel/config configfs rw,relatime 0 0 In the kernel config: CONFIG_CONFIGFS_FS=y Kernel: 4.4.207-1.el7.elrepo.x86_64 Should I be able to create a directory in /sys/kernel/config/target/qla2xxxx? # mkdir naa.10008c7cffc7ef01 mkdir: cannot create directory ‘naa.xxxxxxxxxxxxxxx’: Invalid argument I did notice that when I rebooted, there was no qla2xxx folder in /sys/kernel/config/target/ but after trying to use targetcli, it did make one so I'm not sure what else would cause it to fail. Suggestions? Thank you, Steffan Cline steffan(a)hldns.com 602-793-0014 On 1/11/19, 12:01 AM, "Steffan A. Cline" <steffan(a)hldns.com> wrote: For quite some time I’ve been using FreeNAS to provide services as a NAS over ethernet and SAN over Fibre Channel to CentOS 7 servers each using their own export, not sharing the same one. It’s time for me to replace my hardware and I have a new R720XD that I’d like to use in the same capacity but configure CentOS 7 as a Fibre Channel target rather than use FreeNAS any further. I’m doing virtualization and this will allow me to have failover from one node to the other since they’ll all be sharing the same export rather than me simply backing up to the FreeNAS server the way I am now. Does anyone know of any really good current articles that explain how to set up CentOS 7 as the target in such a configuration and also setting up CLVMd so they can all share an export over Fibre Channel from CentOS 7? Steffan A. Cline steffan(a)hldns.com 602-793-0014 _______________________________________________ CentOS mailing list CentOS(a)centos.org https://lists.centos.org/mailman/listinfo/centos

1 0

systemd-coredump service
by sthustfo 04 Jan '20

04 Jan '20

I am unable to locate systemd-coredump service on CentOS 7.5. It is not listed under "systemctl -a" and also I'm unable to locate the associated unit file (folder /usr/lib/systemd/system/ ). Am I missing any package which installs this service?

2 2

tomcat package and repo for centos8
by Rainer Traut 02 Jan '20

02 Jan '20

Hi all, sadly there is no epel tomcat package so far. As per https://bugzilla.redhat.com/show_bug.cgi?id=1745960 there is no progress for three months. Is there any other third party repository which builds tomcat for centos/rhel 8? Thx Rainer

2 3

Nasty Fail2Ban update for Centos 7
by Allan 02 Jan '20

02 Jan '20

Hi all... Recently a new Fail2Ban was available among some other updates for my Centos 7 system, and I just updated all. It seems that was a very BAD idea. Just noticed that Fail2Ban have generated a 6MB error log because of the update, and FirewallD a 1MB log of errors ! (not sure if any of those were really working after this) ok, I'll just run yum downgrade fail2ban I thought. Naa, no way back - Epel doesn't have a fallback option ! Then gotta dig into Koji, to find the old version, download it, and downgrade to that - and pew, everything is back to normal. The old one seems to be version 0.9.7 and the new one is 0.10.4 I haven't had time to look into Fail2Bans info about these 2 version, but since there is a major version change - is it really possible to just upgrade these ? Sure, I would love to have a working 0.10.4 for my Centos 7 - but it shouldn't destroy my existing system - or it should at least warn me about that - or what to fix. Allan.

6 8

CentOS 7 as a Fibre Channel SAN Target
by Steffan A. Cline 02 Jan '20

02 Jan '20

For quite some time I’ve been using FreeNAS to provide services as a NAS over ethernet and SAN over Fibre Channel to CentOS 7 servers each using their own export, not sharing the same one. It’s time for me to replace my hardware and I have a new R720XD that I’d like to use in the same capacity but configure CentOS 7 as a Fibre Channel target rather than use FreeNAS any further. I’m doing virtualization and this will allow me to have failover from one node to the other since they’ll all be sharing the same export rather than me simply backing up to the FreeNAS server the way I am now. Does anyone know of any really good current articles that explain how to set up CentOS 7 as the target in such a configuration and also setting up CLVMd so they can all share an export over Fibre Channel from CentOS 7? Steffan A. Cline steffan(a)hldns.com 602-793-0014

2 1

KVM Random Reboots AMD EPYC Server
by Helmut Drodofsky 01 Jan '20

01 Jan '20

our new Server with AMD EPYC and super micro board reboots ramdonly. There is no error message before the reboot in /var/log/messages. we are running 2 Server with VMWare workstation without any problem. The new server should run KVM. older servers with AMD (before EPYC) running KVM without any problem. any idea or recommendation? -- Viele Grüße Helmut Drodofsky Internet XS Service GmbH Heßbrühlstraße 15 70565 Stuttgart Geschäftsführung Helmut Drodofsky HRB 21091 Stuttgart USt.ID: DE190582774 Fon: 0711 781941 0 <tel:+497117819410> Fax: 0711 781941 79 Mail: info(a)internet-xs.de www.internet-xs.de

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss January 2020