Re: [CentOS] Solved: NFSroot over wifi in CentOS 7 - graceful shutdown problem
On 8/3/20 6:50 PM, Simon Matter via CentOS wrote: 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. Short answer: Looks like this should be fixed in systemd or its configuration. Long answer is the one I already gave you on centos-devel. I post it here because someone may have deeper knowledge of what exactly goes on: What I'm wondering here is, do you see the hangs because of wpa_supplicant was terminated and therefore also the wireless interface is down, or do you see the hangs because networking is already completely down. It's because of wpa_supplicant. When I run the same config over wired network, it shuts down gracefully. A dirty solution I found is to kill (-9) wpa_supplicant daemon right before shutdown. WiFi keeps running for a second it requires to do a graceful NFS unmount. Best regards, Dmitry Mikhailov ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Docker swarm service misconfigured in FirewallD / CentOS 7
Hi, I'm currently fiddling with Docker Swarm on three sandbox servers running CentOS 7. Unfortunately I couldn't get even the most basic configuration running. After some experimenting and investigating, it turns out there's a problem with FirewallD. Here's what I did first on every single node. # firewall-cmd --permanent --add-service=docker-swarm # firewall-cmd --reload I launched a simple web service like this: # docker service create --name web -p 80:80 nginx My three nodes appear correctly with 'docker node ls'. From here, I should be able to open the Nginx default web page in a web browser using any node's hostname. But nothing happens. No page is loaded. On a whim, I turned off FirewallD, and suddenly everything worked as expected. Now here's the list of ports that have to be open on every single node for Docker Swarm to work: * 2376/tcp * 2377/tcp * 7946/tcp * 7946/udp * 4789/udp And here's what docker-swarm.xml looks like under CentOS 7: # cat /usr/lib/firewalld/services/docker-swarm.xml Docker integrated swarm mode Natively managed cluster of Docker Engines (>=1.12.0), where you deploy services. So it looks like TCP port 2376 was forgotten in that service definition. I opened it up manually on every node: # firewall-cmd --permanent --add-port=2376/tcp # firewall-cmd --reload And now Docker Swarm works correctly. Cheers from the sunny South of France, Niki Kovacs -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : i...@microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Docker swarm service misconfigured in FirewallD / CentOS 7
Who packaged this docker swarm thing? On Thu, Aug 13, 2020, 1:27 AM Nicolas Kovacs wrote: > Hi, > > I'm currently fiddling with Docker Swarm on three sandbox servers running > CentOS 7. > > Unfortunately I couldn't get even the most basic configuration running. > After > some experimenting and investigating, it turns out there's a problem with > FirewallD. > > Here's what I did first on every single node. > > # firewall-cmd --permanent --add-service=docker-swarm > # firewall-cmd --reload > > I launched a simple web service like this: > > # docker service create --name web -p 80:80 nginx > > My three nodes appear correctly with 'docker node ls'. > > From here, I should be able to open the Nginx default web page in a web > browser > using any node's hostname. > > But nothing happens. No page is loaded. > > On a whim, I turned off FirewallD, and suddenly everything worked as > expected. > > Now here's the list of ports that have to be open on every single node for > Docker Swarm to work: > > * 2376/tcp > * 2377/tcp > * 7946/tcp > * 7946/udp > * 4789/udp > > And here's what docker-swarm.xml looks like under CentOS 7: > > # cat /usr/lib/firewalld/services/docker-swarm.xml > > > Docker integrated swarm mode > Natively managed cluster of Docker Engines (>=1.12.0), > where you > deploy services. > > > > > > > > So it looks like TCP port 2376 was forgotten in that service definition. > > I opened it up manually on every node: > > # firewall-cmd --permanent --add-port=2376/tcp > # firewall-cmd --reload > > And now Docker Swarm works correctly. > > Cheers from the sunny South of France, > > Niki Kovacs > > > -- > Microlinux - Solutions informatiques durables > 7, place de l'église - 30730 Montpezat > Site : https://www.microlinux.fr > Blog : https://blog.microlinux.fr > Mail : i...@microlinux.fr > Tél. : 04 66 63 10 32 > Mob. : 06 51 80 12 12 > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Testing
Testing ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 8.2 (2004) Linux Server is Compatible with Dell PowerEdge R640 1U Server
There are no issues so far. I am just reporting that CentOS 8.2 (2004) is compatible with Dell PowerEdge R640 after installing it. On 2020-08-12 22:13, Peter Kjellström wrote: On Wed, 12 Aug 2020 21:46:19 +0800 Turritopsis Dohrnii Teo En Ming wrote: Subject: [Sharing] CentOS 8.2 (2004) Linux Server is Compatible with Dell PowerEdge R640 1U Server This server should be fully ok to run RHEL8 and CentOS8. What exactly goes wrong? https://access.redhat.com/ecosystem/hardware/2941651 /Peter K Good day from Singapore, I have just installed CentOS 8.2 (2004) Linux Server on Dell PowerEdge R640 1U Server for "Donald Trump and Xi Jinping Investment Company LLP" (fictitious/fictional company name used) in Singapore on 11 August 2020 Tuesday. I can confirm that CentOS 8.2 (2004) is compatible with Dell PowerEdge R640. The hardware specifications of Dell PowerEdge R640 are: (1) Processor: Intel Xeon Silver 4210R CPU @ 2.40 GHz (10 cores, 20 threads) (2) 128 GB DDR4-2400 RAM (8 pieces of 16 GB RAM, all 8 slots filled up) (3) PERC H740P Mini RAID Controller (4) 2 units of 960 GB SATA 6 Gbps SSD in RAID 1 configuration (5) Network Ports: 4 x 1 GbE 2 x 10 GbE + 2 x 1 GbE Just sharing only. -- -BEGIN EMAIL SIGNATURE- The Gospel for all Targeted Individuals (TIs): [The New York Times] Microwave Weapons Are Prime Suspect in Ills of U.S. Embassy Workers Link: https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html Singaporean Mr. Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 14 Feb 2019 and refugee seeking attempts at the United Nations Refugee Agency Bangkok (21 Mar 2017), in Taiwan (5 Aug 2019) and Australia (25 Dec 2019 to 9 Jan 2020): [1] https://tdtemcerts.wordpress.com/ [2] https://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming -END EMAIL SIGNATURE- ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 8.2 (2004) Linux Server is Compatible with Dell PowerEdge R640 1U Server
On Thu, 13 Aug 2020 21:59:42 +0800 Turritopsis Dohrnii Teo En Ming wrote: > There are no issues so far. Hahaha, I read _in_Compatible :-D ...generally nobody reports a server compatible. /Peter ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] kvm & external snapshots
Everyone, I am trying to create external snapshots of a kvm guest machine and have not been able to do so. In accordance with : https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/sect-troubleshooting-workaround_for_creating_external_snapshots_with_libvirt I have used the command line : snapshot-create-as --diskspec vda,snapshot=external,file=/u4/guest/MaBa- clone/test.snap.img--domain MaBa-clone --name MaBa-clone_snap --description "Snap before 9Aug2020" This command line gives me the error : error: unsupported configuration: disk 'vda' must use snapshot mode 'internal' Is it possible to perform an external snapshot of a kvm guest? Greg Ennis ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kvm & external snapshots
Once upon a time, Gregory P. Ennis said: > I have used the command line : > > snapshot-create-as --diskspec vda,snapshot=external,file=/u4/guest/MaBa- > clone/test.snap.img--domain MaBa-clone --name MaBa-clone_snap --description > "Snap > before 9Aug2020" I believe that when creating an external snapshot, you have to either specify --disk-only (to not snapshot RAM), or supply --memspec (to specify how/where to save RAM). -- Chris Adams ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] After update to 8 (2004) ... system is unbootable - UEFI Secure boot
Am 29.07.20 um 20:43 schrieb Leon Fauster: Am 16.06.20 um 22:04 schrieb Fabian Arrotin: On 16/06/2020 15:06, Leon Fauster via CentOS wrote: Hi all, I updated a Dell XPS laptop from CentOS 8.1 (1911) to 8.2 (2004). Installed kernels are kernel-4.18.0-147.5.1.el8_1.x86_64 kernel-4.18.0-147.8.1.el8_1.x86_64 kernel-4.18.0-193.6.3.el8_2.x86_64 Unfortunately I can not boot into the latest kernel-4.18.0-193.6.3.el8_2.x86_64. After grub2 screen I only see following line: EFI stub: UEFI Secure Boot is enabled Booting into the older kernel is still possible. The above line appears and after that the normal kernel output scrolls over the screen (rhgb quiet disabled). Is the new kernel correctly signed? What can I do? -- Thanks Leon Hi Leon, Don't think that it's due to secureboot, as on my work laptop (thinkpad t490s), I have secureboot on, and kernel working fine. OTOH, on my family laptop (also in secureboot mode), when I updated from 8.1.1011 to 8.2.2004, laptop became unresponsive during the microcode_ctl update (in scriptlet) and after that it auto-reset itself , so in the middle of the whole rpm transaction. I tried to recover it but it was to a point where it was faster to just reinstall from scratch with 8.2.2004, which I did ... and in gnome, everything was fine, etc (adding repo, pkgs) but then on the *same* kernel it was installed with, just tried a reboot, and nothing : grub shows menu, you select kernel and on upper left there is only cursor (fixed) and nothing happens .. I'll try to diagnose what's the issue as actually that means troubles with family using that laptop :) Did you got managed to boot kernel-4.18.0-193.14.2.el8_2 or a newer one? I must still boot into kernel-4.18.0-147.8.1.el8_1.x86_64 ... and with the upcoming new kernel that depends on a new shim and grub2 package I wonder about the implications for my XPS hardware ... JFYI: latest (kernel-4.18.0-227.el8.x86_64) 8-stream kernel is bootable on this machine ... (full updated (C8.2.2004) with latest shim, grub2 stuff. Just the kernel is from 8-stream) ... -- Leon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS 8 kernel-4.18.0-193 shim issue
Hey All, Is it safe to allow the 193 series kernel update now? Last time I tried that my system refused to boot. I had to roll back to the 4.18.0-147 kernel to get my machine to reboot. Since that happened I've been watching this mail list for acknowledgement that the problem has been corrected while refusing the kernel update. I may have missed the announcement that the issue was resolved and the the update is now approved. -- _ °v° /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 8 kernel-4.18.0-193 shim issue
I was successful in installing the latest updates on a Supermicro X10SRL-F motherboard with an E5-2630L v4 CPU that uses UEFI for boot. On Thu, Aug 13, 2020 at 9:24 PM Mark LaPierre wrote: > > Hey All, > > Is it safe to allow the 193 series kernel update now? Last time I tried > that my system refused to boot. I had to roll back to the 4.18.0-147 > kernel to get my machine to reboot. > > Since that happened I've been watching this mail list for > acknowledgement that the problem has been corrected while refusing the > kernel update. I may have missed the announcement that the issue was > resolved and the the update is now approved. > > -- > _ > °v° >/(_)\ > ^ ^ Mark LaPierre > Registered Linux user No #267004 > https://linuxcounter.net/ > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Dumb Centos 8 DNF mirror question...
Hi! Might "dnf clean X" be the command you are looking for? //JD On Wed, Aug 12, 2020 at 2:10 PM Tom Bishop wrote: > On Wed, Aug 12, 2020 at 9:02 AM Tom Bishop wrote: > > > I have several Centos 8 machines that I update and every now and again I > > will go through and update all of them and one of them will get a slow > > mirror, like downloading the kernel at 50kb etc. With the newer version > I > > am unable to figure out how to force it to update the mirror list and > > hopefully change to a faster mirror. I have searched but must not be > using > > the right verbiage since I am unable to find the easy solution to dump > the > > mirrors and re-select. > > > > Thanks :) > > > > I enabled fastestmirror in dnf.conf and that seems to have done the > trick...if there are better ways of handling let me know. > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
