Discuss

discuss@lists.centos.org

3 participants
34748 discussions

Some problems with Unbound under CentOS8
by Carlos Lopez 30 Mar '20

30 Mar '20

Good morning, I have detected two strange problems with unbound under CentOS8 (fully patched). I have tried same configuration in an OpenBSD host, and these problems do not appear. a/ Error mesage “connection refused”. I am using this unbound server to resolv DNS records for our internal domain (Bind9 is configured to listen in localhost interface, port 5353 udp and in the same host where unbound runs). When I try to run a nslookup query like this: > set q=any > my.internal.dom ;; Connection to 127.0.0.1#53(127.0.0.1) for my.internal.dom failed: connection refused. > And I don’t understand why. Bind9 resolves this without problems, but unbound returns connection refused. Unbound is configured to listen in 0.0.0.0 and allow all connections (access-control: 0.0.0.0/0 allow). The strange thing is that it only happens with that kind of request, any other request works fine. b/ Unbound tries to connect to Root DNS servers directly. Every time unbound starts, it tries to connect to root DNS servers directly and not through internal DNS. I am using a second unbound server as a cache nameserver in a DMZ zone and unbound anchor timer service is disabled. My forward config is: forward-zone: name: "." forward-addr: 172.22.54.6@53<mailto:172.22.54.6@53> Any idea why these problems occur? -- Regards, C. L. Martinez

2 4

Upgrade to CentOS8
by Patrick DERWAEL 30 Mar '20

30 Mar '20

Hi folks I have a couple of Zotac mini PCs running CentOS7 which I want/need to upgrade to CentOS8 In theory, they are CentOS8 capable, but assuming Murphy might be lurking around, I prefer validating the hardware before starting the effective installation As there is no LiveCD, what would be the recommended way to do this? Thanks! <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

5 7

Need help to fix bug in rsync
by Simon Matter 28 Mar '20

28 Mar '20

Hi, I've discovered a bug in rsync which leads to increased CPU usage and slower transfers in many situations. When syncing with compression (-z), certain file types should not be compressed during the transfer because they are already compressed. The file types which are not to be compressed can be seen in the man page section --skip-compress. Unfortunately skipping the default file types doesn't work and all transferred data is being compressed during the transfer. This is true for all versions since 3.1.0. Steps to Reproduce: 1. run 'rm -f Z ; rsync -azv alpha:z.gz Z' Actual results, transferred data was compressed during the transfer: sent 43 bytes received 63,873 bytes 25,566.40 bytes/sec total size is 628,952 speedup is 9.84 Expected results: No compression should happen for .gz file. Additional info: Note that the source file 'z.gz' was an ascii text file to show clearly that compression took place. Please the following BZ for more info: https://bugzilla.samba.org/show_bug.cgi?id=14323 https://bugzilla.redhat.com/show_bug.cgi?id=1816528 I tried to locate the bug in the code but failed. That said I'm not a C developer and therefore need some help from someone who understands C better than me. Any help is much appreciated! Thanks and kind regards, Simon

13 28

directfb on CentOS 7
by Jerry Geis 28 Mar '20

28 Mar '20

I have another package (baresip) that needs "directfb". from baresip make MOD := directfb $(MOD)_SRCS += directfb.c $(MOD)_LFLAGS += $(shell pkg-config --libs directfb) $(MOD)_CFLAGS += $(shell pkg-config --cflags directfb \ | sed -e 's/-I/-isystem/g') include mk/mod.mk I tried to find with: yum provides "*/directfb.pc" but nothing is returned. Where can I get/find directfb for CentOS 7 ? Thanks, Jerry

2 2

CentOS 8 two installs one is X and one is Xwayland
by Jerry Geis 27 Mar '20

27 Mar '20

HI All, I have two installs of CentOS 8. One is a VM and uses what sees as the OLD X as I get /var/log/X* files ... the other is on a real machine and seems to be using Xwayland and I have no /var/log/X* files. Couple things: 1) The VM is using qxl driver it seems. I do not see Xwayland running. 2) Xwayland is running on the physical box - and where are log files for it. Surprised its running two different ways. Thanks, Jerry

2 1

CentOS 8
by Jerry Geis 27 Mar '20

27 Mar '20

I have for CentOS 8 - totem and totem-pl-parser installed - but I cannot find the -devel packages for CentOS 8. Where are they ? Thanks, Jerry

1 0

X module not loading
by Jerry Geis 26 Mar '20

26 Mar '20

HI - On CentOS 8 I see this in my X log intel: waited 2020 ms for i915.ko driver to load I find this: find . | grep i915.ko ./4.18.0-147.5.1.el8_1.x86_64/kernel/drivers/gpu/drm/i915/i915.ko.xz uname -r 4.18.0-147.5.1.el8_1.x86_64 Why might it not be loading ? Thanks, Jerry

2 2

CentOS 6.10 bind DNSSEC issues
by Support 25 Mar '20

25 Mar '20

Hi, Anyone else had any issues with CentOS 6.10 bind DNS server issues this afternoon. At 16:26 (GMT) had alerts for DNS failures against our CentOS 6.10 bind DNS servers from our monitoring system. Sure enough DNS requests via the server was failing, checking the named.log showed dnssec issues; 25-Mar-2020 16:26:10.285 dnssec: info: validating @0xb48b17c0: push.services.mozilla.com A: bad cache hit (push.services.mozilla.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.337 dnssec: info: validating @0xb4858cb0: push.services.mozilla.com AAAA: bad cache hit (push.services.mozilla.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.349 dnssec: info: validating @0xb48b17c0: push.services.mozilla.com AAAA: bad cache hit (push.services.mozilla.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.349 dnssec: info: validating @0xb4858cb0: push.services.mozilla.com A: bad cache hit (push.services.mozilla.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.359 dnssec: info: validating @0xb1ec0030: push.services.mozilla.com A: bad cache hit (push.services.mozilla.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.360 dnssec: info: validating @0xb462c430: push.services.mozilla.com AAAA: bad cache hit (push.services.mozilla.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.441 dnssec: info: validating @0xb48b17c0: push.services.mozilla.com A: bad cache hit (push.services.mozilla.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.441 dnssec: info: validating @0xb4858cb0: push.services.mozilla.com AAAA: bad cache hit (push.services.mozilla.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.451 dnssec: info: validating @0xb1ec0030: push.services.mozilla.com A: bad cache hit (push.services.mozilla.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.452 dnssec: info: validating @0xb462c430: push.services.mozilla.com AAAA: bad cache hit (push.services.mozilla.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.463 dnssec: info: validating @0xb1ec0030: push.services.mozilla.com A: bad cache hit (push.services.mozilla.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.463 dnssec: info: validating @0xb462c430: push.services.mozilla.com AAAA: bad cache hit (push.services.mozilla.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.474 dnssec: info: validating @0xb1ec0030: push.services.mozilla.com AAAA: bad cache hit (push.services.mozilla.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.474 dnssec: info: validating @0xb462c430: push.services.mozilla.com A: bad cache hit (push.services.mozilla.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.898 dnssec: info: validating @0xb48b17c0: www.kernel.org AAAA: bad cache hit (www.kernel.org.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.899 dnssec: info: validating @0xb4858cb0: www.kernel.org A: bad cache hit (www.kernel.org.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.902 dnssec: info: validating @0xb1ec0030: www.national-lottery.co.uk A: bad cache hit (www.national-lottery.co.uk.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.902 dnssec: info: validating @0xb48b17c0: www.mirrorservice.org A: bad cache hit (www.mirrorservice.org.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.902 dnssec: info: validating @0xb462c430: www.national-lottery.co.uk AAAA: bad cache hit (www.national-lottery.co.uk.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.903 dnssec: info: validating @0xb48b17c0: www.mirrorservice.org AAAA: bad cache hit (www.mirrorservice.org.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.908 dnssec: info: validating @0xb1ec0030: www.kernel.org A: bad cache hit (www.kernel.org.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.909 dnssec: info: validating @0xb462c430: www.kernel.org AAAA: bad cache hit (www.kernel.org.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.914 dnssec: info: validating @0xb48b17c0: www.mirrorservice.org A: bad cache hit (www.mirrorservice.org.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.915 dnssec: info: validating @0xb4858cb0: www.mirrorservice.org AAAA: bad cache hit (www.mirrorservice.org.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.915 dnssec: info: validating @0xb48b17c0: www.national-lottery.co.uk AAAA: bad cache hit (www.national-lottery.co.uk.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.916 dnssec: info: validating @0xb48b17c0: www.national-lottery.co.uk A: bad cache hit (www.national-lottery.co.uk.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.925 dnssec: info: validating @0xb1ec0030: www.boredpanda.com A: bad cache hit (www.boredpanda.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.925 dnssec: info: validating @0xb48b17c0: www.boredpanda.com AAAA: bad cache hit (www.boredpanda.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.927 dnssec: info: validating @0xb48b17c0: www.bbc.co.uk AAAA: bad cache hit (www.bbc.co.uk.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.927 dnssec: info: validating @0xb4858cb0: www.bbc.co.uk A: bad cache hit (www.bbc.co.uk.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.935 dnssec: info: validating @0xb48b17c0: www.boredpanda.com A: bad cache hit (www.boredpanda.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.935 dnssec: info: validating @0xb4858cb0: www.boredpanda.com AAAA: bad cache hit (www.boredpanda.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.938 dnssec: info: validating @0xb1ec0030: www.bbc.co.uk A: bad cache hit (www.bbc.co.uk.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.938 dnssec: info: validating @0xb462c430: www.bbc.co.uk AAAA: bad cache hit (www.bbc.co.uk.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.950 dnssec: info: validating @0xb48b17c0: www.fosslinux.com A: bad cache hit (www.fosslinux.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.951 dnssec: info: validating @0xb4858cb0: www.fosslinux.com AAAA: bad cache hit (www.fosslinux.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.962 dnssec: info: validating @0xb48b17c0: www.fosslinux.com A: bad cache hit (www.fosslinux.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:10.962 dnssec: info: validating @0xb4858cb0: www.fosslinux.com AAAA: bad cache hit (www.fosslinux.com.dlv.isc.org/DLV) 25-Mar-2020 16:26:11.021 dnssec: info: validating @0xb1ec0030: uk.yahoo.com AAAA: bad cache hit (uk.yahoo.com.dlv.isc.org/DLV) Followed by; 25-Mar-2020 16:26:25.828 dnssec: info: validating @0xb48fdcd0: dlv.isc.org NSEC: verify failed due to bad signature (keyid=64263): RRSIG has expired 25-Mar-2020 16:26:25.828 dnssec: info: validating @0xb48fdcd0: dlv.isc.org NSEC: no valid signature found 25-Mar-2020 16:29:05.075 dnssec: info: validating @0xb473dc48: dlv.isc.org DNSKEY: verify failed due to bad signature (keyid=19297): RRSIG has expired 25-Mar-2020 16:29:05.075 dnssec: notice: validating @0xb473dc48: dlv.isc.org DNSKEY: unable to find a DNSKEY which verifies the DNSKEY RRset and also matches a trusted key for 'dlv.isc.org' 25-Mar-2020 16:29:05.075 dnssec: notice: validating @0xb473dc48: dlv.isc.org DNSKEY: please check the 'trusted-keys' for 'dlv.isc.org' in named.conf. No issues with our CentOS 7.7.1908 bind DNS servers. To fix I had to set the following in /etc/named.conf and restart the named service. dnssec-enable no; dnssec-validation no; Anyone else had this issue? Is there and updated key that is needed in CentOS 6.10 version of bind so that I can turn dnssec back on. regards Tim Tim D'Cruz

3 2

Building a NFS server with a mix of HDD and SSD (for caching)
by kadafax＠gmail.com 25 Mar '20

25 Mar '20

Hi list, I'm building a NFS server on top of CentOS 8. It has 8 x 8 TB HDDs and 2 x 500GB SSDs. The spinning drives are in a RAID-6 array. They are 4K sector size. The SSDs are in RAID-1 array and with a 512bytes sector size. I want to use the SSDs as a cache using dm-cache. So here what I've done so far: /dev/sdb ==> SSD raid1 array /dev/sdd ==> spinning raid6 array I've added "allow_mixed_block_sizes = 1" to lvm.conf to be able to add sdb and sdd in the same VG (because of the sector size missmatch). But as the LVs will only use one and only one PV I guess it's OK. # lvcreate -L 500M -n lv_cache_meta VGnfs /dev/sdb # lvcreate -l +100%FREE -n lv_cache VGnfs /dev/sdb # lvconvert --type cache-pool /dev/VGnfs/lv_cache --poolmetadata /dev/VGnfs/lv_cache_meta # lvcreate -l +100%FREE -n LVnfs VGnfs /dev/sdd # lvconvert --type cache /dev/VGnfs/LVnfs --cachepool /dev/VGnfs/lv_cache # lvconvert --cachemode writeback --type cache /dev/VGnfs/LVnfs --cachepool /dev/VGnfs/lv_cache # mkfs.xfs /dev/VGnfs/LVnfs And now I'm asking myself if I'm not doing something somewhat dangerous for a server that will be critical when in production :] The server has 128GB of RAM so maybe the caching in memory will be sufficient to achieve good performance ? What do you think ? Do you use something similar ? Thanks !

2 2

Firewalld direct.xml
by Jerry Geis 25 Mar '20

25 Mar '20

HI All - I created a /etc/firewalld/direct.xml file and put in it : <?xml version="1.0" encoding="utf-8"?> <direct> <chain ipv="ipv4" table="raw" chain="blacklist"/> <rule ipv="ipv4" table="raw" chain="PREROUTING" priority="0">-s 192.168.1.8 -j blacklist</rule> </direct> I rebooted, so then from the 192.168.1.8 machine I tried to ping the machine. I responds. I was expecting it not to respond? What do I not have right with the direct.xml file ? Thanks Jerry

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