Discuss

discuss@lists.centos.org

34729 discussions

NFSroot over wifi in CentOS 7 - graceful shutdown problem
by Dmitry E. Mikhailov 13 Aug '20

13 Aug '20

Hi, I've got a task to have a small number of laptops netboot Linux over WiFi. The kernel is loaded off the USB stick of cource, it's off topic for now. The WPA-supplicant daemon is started early by dracut off initrd. It works. Mostly. The problem is that upon shutdown systemd terminates all the processes FIRST and unmounts filesystems NEXT. Guess what? Upon termination, wpa-supplicant brings the wireless interface down and the system hangs being unable to unmount now-defunct NFSroot. There were some discussions regarding similar matter and there's even the RH Errata: https://access.redhat.com/errata/RHBA-2018:2447 But I'm woking on a fully updated CentOS Linux release 7.8.2003 and nevertheless I've got the problem. I don't have rights to see the BZ. https://bugzilla.redhat.com/show_bug.cgi?id=1593649 I'm deciding to use a quick and dirty hack to do a totally ungraceful shutdown/reboot: https://unix.stackexchange.com/questions/533307/systemd-fails-to-umount-man… Any better ideas? Best regards, Dmitry Mikhailov.

2 2

Install OpenVAS on CentOS Linux release 8.2.2004 (Core)
by Kaushal Shriyan 12 Aug '20

12 Aug '20

Hi, I am running CentOS Linux release 8.2.2004 (Core). Are there any instructions to install OpenVAS for CentOS Linux release 8.2.2004 (Core)? Thanks in advance and I look forward to hearing from you. Best Regards, Kaushal

4 6

Re: [CentOS] systemd syslog.target
by ctcard 11 Aug '20

11 Aug '20

Thanks Simon,I think my question got a bit lost amongst all the grub issues - does anyone else have information about whether any references to syslog.target in systemd unit files can be removed?ChrisSent from Samsung Mobile on O2 -------- Original message -------- From: Simon Matter via CentOS <centos(a)centos.org> Date: 31/07/2020 10:02 (GMT+00:00) To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] systemd syslog.target Hi,>> I've noticed that there are several systemd unit files in CentOS 7 and 8> with the optionAfter=syslog.targetin the [Unit] section, but since systemd> version 198 syslog.target has not existed.I deduce from this that> "After=syslog.target" is ignored by systemd and can therefore be removed.> Is this correct? I am writing some systemd unit files for our own services> which previously used init.d scripts, so I want to ensure I'm not causing> problems by omitting "After=syslog.target"ChrisSent from Samsung Mobile on> O2Interesting, there is really no syslog.target on either CentOS 7 or 8. Butif a service needs classic syslog, shouldn't it have another After=instead?Simon_______________________________________________CentOS mailing listCentOS@centos.orghttps://lists.centos.org/mailman/listinfo/centos

2 1

Docker container isolation not working in CentOS 7
by Nicolas Kovacs 11 Aug '20

11 Aug '20

Hi, I've decided to use these summer holidays to wrap my head around Docker and its quirks. Spent the last couple weeks working through a Udemy tutorial and a thick book about Docker, and I have Docker CE installed on two machines: * my workstation running OpenSUSE Leap 15.1 * a public sandbox server running CentOS 7 I'm currently fiddling with custom networks and container isolation, and it looks like I discovered a bug or at least an inconsistency in CentOS. Maybe the gurus among you have an explanation for this. Sorry if this is a bit long, but I try to be as clear as possible. OpenSUSE Leap 15.1 ------------------ For demonstration purposes on how things *should* be, I'm starting two Nginx containers named "webserver1" and "webserver2": $ docker run -dit --name webserver1 nginx $ docker run -dit --name webserver2 nginx These two containers have the respective 172.17.0.2 and 172.17.0.3 IP addresses: $ docker network inspect bridge | grep -i ipv4address "IPv4Address": "172.17.0.2/16", "IPv4Address": "172.17.0.3/16", The "webserver1" container has the 172.17.0.2 IP address: $ docker exec -it webserver1 hostname -I 172.17.0.2 Since "webserver1" and "webserver2" are both on the "bridge" network, they can communicate with each other: $ docker exec -it webserver1 curl -m 5 http://172.17.0.3 <!DOCTYPE html> <html> <head> <title>Welcome to nginx!</title> ... Now I'm creating the custom "blog" network: $ docker network create blog $ docker network ls NETWORK ID NAME DRIVER SCOPE e02e6fc654c6 blog bridge local 3ea6f28134ba bridge bridge local 8d2b8dfe5352 host host local 0bd337e274c2 none null local I'm starting a third container named "webserver3" and assign it to the new "blog" network: $ docker run -dit --name webserver3 --network blog nginx This new container is in a whole new network segment: $ docker network inspect blog | grep -i ipv4address "IPv4Address": "172.20.0.2/16", As is to be expected, it can't communicate with the other two containers: $ docker exec -it webserver3 curl -m 5 http://172.17.0.2 curl: (28) Connection timed out after 5001 milliseconds $ docker exec -it webserver3 curl -m 5 http://172.17.0.3 curl: (28) Connection timed out after 5001 milliseconds So far so good. CentOS 7 -------- Now let's repeat the exact same experiment on a server running CentOS 7. First, create two containers on the default "bridge" network and check if they can communicate with each other: $ docker run -dit --name webserver1 nginx $ docker run -dit --name webserver2 nginx $ docker network inspect bridge | grep -i ipv4address "IPv4Address": "172.17.0.3/16", "IPv4Address": "172.17.0.2/16", $ docker exec -it webserver1 hostname -I 172.17.0.2 $ docker exec -it webserver1 curl -m 5 http://172.17.0.3 <!DOCTYPE html> <html> <head> <title>Welcome to nginx!</title> ... Now create a custom "blog" network and start a third container assigned to that network: $ docker network create blog $ docker network ls | grep blog 0571c80fef1b blog bridge local $ docker run -dit --name webserver3 --network blog nginx $ docker network inspect blog | grep -i ipv4address "IPv4Address": "172.19.0.2/16", $ docker exec -it webserver3 hostname -I 172.19.0.2 Now IN THEORY "webserver3" shouldn't be able to communicate with the "webserver1" and "webserver2" containers. But here's what happens IN PRACTICE (and only on CentOS 7): $ docker exec -it webserver3 curl -m 5 http://172.17.0.2 <!DOCTYPE html> <html> <head> <title>Welcome to nginx!</title> ... $ docker exec -it webserver3 curl -m 5 http://172.17.0.3 <!DOCTYPE html> <html> <head> <title>Welcome to nginx!</title> ... As far as I'm concerned, it looks like a bug, it walks like a bug and it quacks like a bug. Any remarks and/or suggestions? Cheers from the sunny South of France, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12

3 4

CentOS8 pxeboot Error setting up software source
by Satish Patel 10 Aug '20

10 Aug '20

Folks, Last month i have setup PXE server using CentOS8-1-1911 release and everything was working fine so today i thought let me upgrade it to CentOS8-2-2004 so i just did rsync and updated all packages but after that it started throwing following error during pxe installation Installation source (Error setting up software source) I have check logs and i can see its setting correct source which is my apache server also networking looks good. I can ping server from a kickstart client, i have tried to give multiple repo manually but still have the same error. I am using this repo, let me know if this is wrong place http://mirror.liquidtelecom.com/centos/8.1.1911/BaseOS/x86_64/os/ Is this a bug or something which i am not aware of?

1 0

ZFS fails with latest C8 kernel
by Robert G (Doc) Savage 10 Aug '20

10 Aug '20

As if last weekend's UEFI debacle wasn't bad enough, it now seems the latest C8 kernel (4.18.0-193.14.2) is incompatible with the current ZFSOnLinux packages (0.8.4-1). When booted to the latest kernel, ZFS is inaccessible on my C8 storage server. When I back off to the prior kernel (4.18.0-193.6.3), all is well. If a local ZFS system is unavailable to the C8 kernel support folks, I'll be happy to assist them by volunteering my system as a lab rat. --Doc Savage Fairview Heights, IL

4 3

python problem
by Chuck Campbell 09 Aug '20

09 Aug '20

Question for the list: I have a small, aircooled pc server, which is running fine, but the log gets filled with a series of messages saying the package, and each of 8 cpus is throttled because of thermal issues. Then, within the same second according to the timestamps, it reports everything is OK and throttling is off. This happens once every minute. In reality, when I try performance tests, I believe the processor is actually spending measurable time in the throttled condition. I have installed lmsensors, and am monitoring temps as frequently as the reported throttling occurs, but I never see any high cpu temps. I see them vary, based on load, but never high enough to be alarmed, or to be throttled. I did a lot of googling, and I see some intel issues in some lenovo laptops, and a potential fix. I did the following: dnf copr enable abn/throttled dnf install -y throttled but I get this output: Error: Problem: conflicting requests - nothing provides python3-configparser needed by throttled0.7-1.x86_64 I have no guess what to do about this. Thanks, -chuck -- ACCEL Services, Inc.| Specialists in Gravity, Magnetics | (713)993-0671 ph. | and Integrated Interpretation | (713)993-0608 fax 448 W. 19th St. #325| Since 1992 | (713)306-5794 cell Houston, TX, 77008 | Chuck Campbell | campbell(a)accelinc.com | President & Senior Geoscientist | "Integration means more than having all the maps at the same scale!"

3 2

python problem while trying to fix a separate issue
by Chuck Campbell 09 Aug '20

09 Aug '20

Question for the list: I have a small, aircooled pc server, which is running fine, but the log gets filled with a series of messages saying the package, and each of 8 cpus is throttled because of thermal issues. Then, within the same second according to the timestamps, it reports everything is OK and throttling is off. This happens once every minute. In reality, when I try performance tests, I believe the processor is actually spending measurable time in the throttled condition. I have installed lmsensors, and am monitoring temps as frequently as the reported throttling occurs, but I never see any high cpu temps. I see them vary, based on load, but never high enough to be alarmed, or to be throttled. I did a lot of googling, and I see some intel issues in some lenovo laptops, and a potential fix. I did the following: dnf copr enable abn/throttled dnf install -y throttled but I get this output: Error: Problem: conflicting requests - nothing provides python3-configparser needed by throttled0.7-1.x86_64 I have no guess what to do about this. Thanks, -chuck -- campbell(a)accelinc.com | President & Senior Geoscientist | "Integration means more than having all the maps at the same scale!"

1 0

erroneous cpu thermal throttling / actually a python3 question
by Chuck Campbell 09 Aug '20

09 Aug '20

I have a small, aircooled pc server, which is running fine, but the log gets filled with a series of messages saying the package, and each of 8 cpus is throttled because of thermal issues. Then, within the same second according to the timestamps, it reports everything is OK and throttling is off. This happens once every minute. In reality, when I try performance tests, I believe the processor is actually spending measurable time in the throttled condition. I have installed lmsensors, and am monitoring temps as frequently as the reported throttling occurs, but I never see any high cpu temps. I see them vary, based on load, but never high enough to be alarmed, or to be throttled. I did a lot of googling, and I see some intel issues in some lenovo laptops, and a potential fix. I did the following: dnf copr enable abn/throttled dnf install -y throttled but I get this output: Error: Problem: conflicting requests - nothing provides python3-configparser needed by throttled0.7-1.x86_64 I have no guess what to do about this. --

1 0

Fixing grub/shim issue Centos 7
by david 09 Aug '20

09 Aug '20

After trying several paths, some suggested on this list, here's my results. 1) Fixing a unbootable system wasn't practical in my case. Fortunately, all my systems can be rebuilt from scratch. 2) When I was lucky enough to catch an updated system before reboot, backing out the defective updates wasn't possible. Yum said there were no prior versions. 3) The most reliable method I found for Centos 7 was: - Re=install from scratch (luckily, my data files were safe and restorable) - Before running any updates, apply the fix suggested by Redhat and exclude updates to grub2, shim and mokutil. - Without the above 'exclude', the system became unbootable after a yum update even though the corrected versions of shim should have been loaded. The system I'm dealing with is Centos 7. I can easily rebuild it from scratch and test stuff without losing crucial data, if it would helpful. 4) I haven't experimented yet with centos 8 because the hardware is remote and requires me to get a friend involved to help. My local hardware is not supported by Centos 8, so it will remain on Centos 7 until I replace the hardware or switch to a different Linux. David

16 35

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss