Discuss October 2019

discuss@lists.centos.org

125 participants
121 discussions

browsers slowing Centos 7 installation to a crawl
by Michael Hennebry 04 Dec '19

04 Dec '19

My video problems mentioned in a previous thread are gone, though I do not know why. Now my problem is that whenever I have a browser open and an internet connection, my Centos 7 slows to a crawl. Chromium seems to be the least bad. Sometimes it slows to the point that I cannot even move the mouse. Even switching between virtual terminals takes a while sometimes. When I get there, top generally shows me between two and five D states. I've changed service providers lately. The problem survived the change. Some sites seem to aggravate the problem. Most recently, a site tried to connect to c.amazon.adsystem.com . I got the message waiting for c.amazon.adsystem.com . I have that address in my hosts file as 127.0.0.1 . ping finds it and pings. nslookup does not: > [hennebry@localhost ~]$ nslookup c.amazon.adsystem.com > Server: 192.168.0.1 > Address: 192.168.0.1#53 > > ** server can't find c.amazon.adsystem.com: NXDOMAIN Whether the slow-to-crawl problem is related to the failure to redirect, I do not know. The former is clearly more important. Any suggestions on how to diagnose it? Any ideas on why chromium is waiting for c.amazon.adsystem.com and how I can fix it? -- Michael hennebry(a)web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards

13 45

CentOS7 sometimes don't detect NIC after reboot
by Miroslav Geisselreiter 20 Nov '19

20 Nov '19

I have brand new PC with this components: CPU Intel® Pentium G5400, LGA1151 motherboard ASUS PRIME B360M-C 16 GB RAM HDD 2x ADATA SSD 256GB XPG GAMMIX S11, PCIe Gen3x4 M.2 2280 (RAID1) NIC Intel X550-T1 Ethernet Converged Network Adapter I installed CentOS 7 and two NICs were detected: eno1 (on motherboard) enp1s0 (Intel X550-T1) When I restart the machine sometimes enp1s0 is missing. It is not detected during boot. It looks like NIC card is not installed / not present. After next reboot everything is fine and I do not see any problems with NIC card. How can I avoid this problem with missing NIC? Can you help me, please? Miroslav Geisselreiter

4 10

named errors in /var/log/messages
by Walter H. 09 Nov '19

09 Nov '19

Hello, can someone explain these errors Oct 27 15:34:05 vhost01 named[1316]: zone #ZONE#/IN/auth: refresh: retry limit for master IPV6-MASTER#53 exceeded (source IPV6-THIS#0) Oct 27 15:34:05 vhost01 named[1316]: zone #ZONE#/IN/auth: Transfer started. Oct 27 15:34:06 vhost01 named[1316]: zone #ZONE#/IN/auth: refresh: retry limit for master IPV6-MASTER#53 exceeded (source IPV6-THIS#0) Oct 27 15:34:06 vhost01 named[1316]: zone #ZONE#/IN/auth: Transfer started. Oct 29 04:06:19 vhost01 named[1316]: zone #ZONE#/IN/auth: refresh: retry limit for master IPV6-MASTER#53 exceeded (source IPV6-THIS#0) Oct 29 04:06:19 vhost01 named[1316]: zone #ZONE#/IN/auth: Transfer started. is this caused by a misconfiguration at the master dns or this dns (slave)? (the master dns can only be connected by IPv6) is there a serious problem? there also can be found such entries Oct 29 04:06:21 vhost01 named[1316]: transfer of '#ZONE#/IN/auth' from IPV6-MASTER#53: connected using IPV6-THIS#46019 Oct 29 04:06:21 vhost01 named[1316]: transfer of '#ZONE#/IN/auth' from IPV6-MASTER#53: Transfer completed: 0 messages, 1 records, 0 bytes, 0.064 secs (0 bytes/sec) or is this just caused by #0 - I guess source port 0? these are the ip6tables entries on this dns (slave) -A INPUT -i eth0 -d IPV6-THIS -m tcp -p tcp --dport 53 -m state --state NEW -j ACCEPT -A INPUT -i eth0 -d IPV6-THIS -m udp -p udp --dport 53 -j ACCEPT the master has these for each dns -A INPUT -i sit1 -s IPV6-SLAVE -d IPV6-MASTER -m tcp -p tcp --dport 53 -m state --state NEW -j ACCEPT -A INPUT -i sit1 -s IPV6-SLAVE -d IPV6-MASTER -m udp -p udp --dport 53 -j ACCEPT the master DNS has this in /etc/named.conf acl dns-hosts { IPV6-SLAVE; // IPv6only: slave ... }; view "auth" { match-clients { dns-hosts; }; empty-zones-enable no; recursion no; additional-from-auth no; additional-from-cache no; also-notify { IPV6-SLAVE; // IPv6only: slave ... }; notify-source 0.0.0.0; notify-source-v6 IPV6-MASTER; transfer-source 0.0.0.0; transfer-source-v6 IPV6-MASTER; zone "#ZONE#" IN { type master; notify yes; file "named._authzone-#ZONE#"; allow-transfer { dns-hosts; }; allow-update { none; }; }; ... }; the slaves itself have this in /etc/named.conf masters masterhost { IPV6-MASTER; // IPv6only: master }; view "auth" { match-clients { any; }; empty-zones-enable no; recursion no; transfer-source 0.0.0.0; transfer-source-v6 IPV6-SLAVE; additional-from-auth no; additional-from-cache no; zone "#ZONE#" IN { type slave; masters { masterhost; }; file "slaves/named._authzone-#ZONE#"; }; ... }; I have 3 slave DNS servers, each has the same master; and such log entries are at all three slave DNS servers; each of these 3 slaves is DualStack (in the wild) and the master is IPv6only (at home) Thanks, Walter

2 1

PHP FPM issue
by Thomas Stephen Lee 01 Nov '19

01 Nov '19

Hi, what is the workaround for this? https://www.nginx.com/blog/php-fpm-cve-2019-11043-vulnerability-nginx/ in either CentOS 7 or 8 ? thanks --- Thomas Stephen Lee

4 8

Re: [CentOS] NFS shutdown issue
by Darby Vicker 01 Nov '19

01 Nov '19

> I disagree. This is probably part of the NFS server, to catch when > systems are being shut down and cleanly notifying and disconnecting > clients. Interesting - thanks for the info. I can understand that behavior in a shutdown situation. But I'm surprised that unmounting (either cleanly or uncleanly) one of two exported filesystems triggers the NFS service to shutdown completely. Is this consistent with other peoples experiences?

2 1

Help with CentOS 7 and nvidia
by Jerry Geis 01 Nov '19

01 Nov '19

Hello my hardware has: 03:00.0 VGA compatible controller: NVIDIA Corporation GT218 [ION] (rev a2) rpm -qa | grep nvidia nvidia-detect-410.78-1.el7.elrepo.x86_64 kmod-nvidia-340xx-340.107-2.el7_6.elrepo.x86_64 nvidia-x11-drv-340xx-340.107-1.el7.elrepo.x86_64 rpm -qa | grep libva libva-vdpau-driver-0.7.4-19.el7.x86_64 libva-utils-1.8.3-4.el7.x86_64 libva-devel-1.8.3-1.el7.x86_64 libva-1.8.3-1.el7.x86_64 rpm -qa | grep vdpau libva-vdpau-driver-0.7.4-19.el7.x86_64 libvdpau-1.1.1-3.el7.x86_64 vainfo libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/nvidia_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.40 (libva ) vainfo: Driver version: Splitted-Desktop Systems VDPAU backend for VA-API - 0.7.4 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG4Simple : VAEntrypointVLD VAProfileMPEG4AdvancedSimple : VAEntrypointVLD VAProfileH264Main : VAEntrypointVLD VAProfileH264High : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD grep Driver /var/log/Xorg.0.log [ 43.069] X.Org Video Driver: 24.0 [ 45.744] Module class: X.Org Video Driver [ 45.744] (II) NVIDIA dlloader X Driver 340.107 Thu May 24 21:18:05 PDT 2018 [ 45.744] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [ 47.328] Module class: X.Org XInput Driver grep -i vdpau /var/log/Xorg.0.log [ 46.978] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia So to me all looks good - but there is no hardware acceleration??? When I play the video with totem its taking way too much CPU. I removed the ~/.cache/gstreamer* . What have I missed ? Jerry

3 2

HA tools from clusterlabs.org
by lejeczek 31 Oct '19

31 Oct '19

hi everybody, would you know if 8 version is going to have HA solutions from clusterlabs.org available, just like Centos7 has? (from Centos' own repos/streams) many thanks, L.

2 2

Limit user password by time
by Gestió Servidors 31 Oct '19

31 Oct '19

Hello, I would like to know if it is possible to configure a password that expires, once user has logged, after 2 hours, for example. Thanks.

2 1

udev on CEntOS7 - can't get a match, looking for tips...
by John H Nyhuis 30 Oct '19

30 Oct '19

The mtx binary requires my tape library to be assigned a sg# driver, but the kernel periodically renumbers the sg devices. Normally, we would write a udev rule to manually assign a persistent name, but it looks like things have changed as I can't seem to get a match on CEntOS7. I'd appreciate any feedback or pointers to help me get my rule working. My two attempts are below. cat /etc/udev/rules.d/90-local.rules KERNEL=="sg[0-9]*", SUBSYSTEM=="scsi_generic", \ ENV{ID_SERIAL}=="1QUANTUM_D0H0112430_LLA", SYMLINK+="sg8" SUBSYSTEM=="scsi", SUBSYSTEMS=="scsi_genric", \ ATTRS{model}=="Scalar i40-i80 ", SYMLINK:="sg8" Neither rule above generates a match with udev, so I still have something wrong. Right now the assignment is sg7 (but it's had other names in the past. udevadm info --query=all --name=/dev/sg7 P: /devices/pci0000:00/0000:00:07.0/0000:04:00.0/0000:05:00.0/0000:06:00.1/host8/rport-8:0-0/target8:0:0/8:0:0:1/scsi_generic/sg7 N: sg7 S: tape/by-id/scsi-1QUANTUM_D0H0112430_LLA E: DEVLINKS=/dev/tape/by-id/scsi-1QUANTUM_D0H0112430_LLA E: DEVNAME=/dev/sg7 E: DEVPATH=/devices/pci0000:00/0000:00:07.0/0000:04:00.0/0000:05:00.0/0000:06:00.1/host8/rport-8:0-0/target8:0:0/8:0:0:1/scsi_generic/sg7 E: ID_MODEL=Scalar_i40-i80 E: ID_MODEL_ENC=Scalar\x20i40-i80\x20\x20 E: ID_REVISION=190G E: ID_SCSI=1 E: ID_SCSI_SERIAL=QUANTUMD0H0112430_LLA E: ID_SERIAL=1QUANTUM_D0H0112430_LLA E: ID_SERIAL_SHORT=QUANTUM_D0H0112430_LLA E: ID_TYPE=generic E: ID_VENDOR=QUANTUM E: ID_VENDOR_ENC=QUANTUM\x20 E: MAJOR=21 E: MINOR=7 E: SUBSYSTEM=scsi_generic E: USEC_INITIALIZED=28815292891 Assigned and parent device listed below: udevadm info -a -p `udevadm info -q path -n /dev/sg7` looking at device '/devices/pci0000:00/0000:00:07.0/0000:04:00.0/0000:05:00.0/0000:06:00.1/host8/rport-8:0-0/target8:0:0/8:0:0:1/scsi_generic/sg7': KERNEL=="sg7" SUBSYSTEM=="scsi_generic" DRIVER=="" looking at parent device '/devices/pci0000:00/0000:00:07.0/0000:04:00.0/0000:05:00.0/0000:06:00.1/host8/rport-8:0-0/target8:0:0/8:0:0:1': KERNELS=="8:0:0:1" SUBSYSTEMS=="scsi" DRIVERS=="ch" ATTRS{rev}=="190G" ATTRS{type}=="8" ATTRS{scsi_level}=="4" ATTRS{model}=="Scalar i40-i80 " ATTRS{state}=="running" ATTRS{unpriv_sgio}=="0" ATTRS{queue_type}=="none" ATTRS{iodone_cnt}=="0xe2" ATTRS{iorequest_cnt}=="0xe2" ATTRS{queue_ramp_up_period}=="120000" ATTRS{device_busy}=="0" ATTRS{evt_capacity_change_reported}=="0" ATTRS{timeout}=="0" ATTRS{evt_media_change}=="0" ATTRS{ioerr_cnt}=="0x7" ATTRS{queue_depth}=="30" ATTRS{vendor}=="QUANTUM " ATTRS{evt_soft_threshold_reached}=="0" ATTRS{device_blocked}=="0" ATTRS{evt_mode_parameter_change_reported}=="0" ATTRS{evt_lun_change_reported}=="0" ATTRS{evt_inquiry_change_reported}=="0" ATTRS{dh_state}=="detached" ATTRS{iocounterbits}=="32" ATTRS{eh_timeout}=="10" Would anyone mind pointing out the error in my udev rule or proposing a better way of getting a persistent sg device name? -- Thanks in advance, John H. Nyhuis Desk: (206)-685-8334 jnyhuis(a)uw.edu Box 359461, 15th floor, 106

4 6

No IrDA Support with CentOS anymore?
by andreas.reschke＠mahle.com 30 Oct '19

30 Oct '19

Hi there, I've a laptop with CentOS 8 and a PC with CentOS 7. After 3 years of break I was Scuba Diving last 3 weeks. Back at home I wish to download all dive logs from my divecomputer connext via IrDA to my PC. But no kernel modul for IrDA was found. [root@rechner1 ~]# modprobe ircomm modprobe: FATAL: Module ircomm not found in directory /lib/modules/4.18.0-147.6.el8.x86_64 [root@rechner1 ~]# modprobe ircomm_tty modprobe: FATAL: Module ircomm_tty not found in directory /lib/modules/4.18.0-147.6.el8.x86_64 [root@destn40768 ~]# [root@rechner1 ~]# lsusb | grep -i irda Bus 002 Device 011: ID 9710:7780 MosChip Semiconductor MCS7780 4Mbps Fast IrDA Adapter [root@rechner1 ~]# Same with CentOS7 How do I get IrDA support? Mit freundlichen Grüßen / Kind regards Andreas Reschke MAHLE International GmbH Unix/Linux-Administration (FIE4.1) Pragstr. 26 - 46, 70376 Stuttgart, Germany Phone: +49 711 501-475 98 Mobile: +49 173 3197397 andreas.reschke(a)mahle.com, https://www.mahle.com MAHLE International GmbH, Location: Stuttgart, Registered: Amtsgericht Stuttgart HRB 16413 Management Board: Dr. Jörg Stratmann, Michael Frick, Michael Glowatzki, Martin Wellhöffer

2 2

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 October 2019