Discuss

discuss@lists.centos.org

34729 discussions

Installing devtoolset-6 on CentOS 8
by Eric Gervais-Despres 18 Aug '20

18 Aug '20

Has anybody tried (and succeeded) to get gcc 6.3.1 (or devtoolset-6) to work on CentOS 8? In the Animation and Visual Effect industry, gcc 6.3.1 is still the current recommended compiler (see www.vfxplatform.com), and is required to build many plugins. Unfortunately, it is not a "minimum requirement"... It is THE requirement. So I tried to get it from the vault: -- sudo dnf config-manager --add-repo= http://vault.centos.org/7.6.1810/sclo/x86_64/rh/ sudo dnf install devtoolset-6 -- but I get these messages: -- Error: Problem: package devtoolset-6-6.1-1.el7.x86_64 requires devtoolset-6-runtime, but none of the providers can be installed conflicting requests nothing provides policycoreutils-python needed by devtoolset-6-runtime-6.1-1.el7.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages -- All options fail. I hate having to install something not officially supported anymore, but still officially required for many current software. Thank you. -- *Éric Gervais-Després* President 4270 St-Laurent #300 Montréal, Qc, Canada, H2W 1Z3 +1-514-705-4946 *www.ngeniousstudio.com <http://www.ngeniousstudio.com>*

2 1

Replacement for KMail V1
by Gary Stainburn 17 Aug '20

17 Aug '20

Last week my trusty Fedora 9 file and print server failed on me. Not bad for 12 years trusty service. I have now replaced it with a C7 server and found that lots have changed in those 12 years. Thankfully many things haven't, named-chroot, dhcpd, etc pretty much copied across and Samba wasn't a major rewrite. However I feel like my right arm has been chopped off. My work life revolves around my emails which were in KMail version 1.x. My first thought was to move to the current KMail which is version 4.x. The problem is that it's cr*p. It appears to be the same as V1, but just more up to date - perfect. Unfortunately it is so slow that it is completely unusable, even on a brand new server. As a GUI it is unusable, and functionally fails with connections time out etc. Some research has found that KMail was stuffed as far back as V2 when they moved to using an embedded MYSQL engine to drive it. What I would really like is advice on how to make KMail V4 usable. As I doubt that is possible can anyone please recommend a decent email client with good keyboard short-cuts and filtering processes. I am currently limping along using Thunderbird but I find the lack of useful keystroke functions (such as next unread message, next folder with an unread message) annoying. Having to move my hand from keyboard to mouse is more exercise than I'm used to.

3 2

Samba rpms now available from Storage SIG
by Anoop C S 17 Aug '20

17 Aug '20

Hi all, This is to announce the availability of Samba(and CTDB) rpms from Storage SIG[1] on CentOS 7 and 8. Visit Samba's CentOS Storage SIG wiki page[2] for more details on installation steps. [1] https://wiki.centos.org/SpecialInterestGroup/Storage [2] https://wiki.centos.org/SpecialInterestGroup/Storage/Samba Regards, Anoop C S.

2 3

Teo En Ming's Learning Achievements on 14 August 2020 Friday
by Turritopsis Dohrnii Teo En Ming 15 Aug '20

15 Aug '20

Subject: Teo En Ming's Learning Achievements on 14 August 2020 Friday [1] Activate Cisco AnyConnect SSL VPN License on Cisco ASA 5506-X Firewall Today I discovered that the base license for Cisco ASA 5506-X Firewall only allows maximum 2 SSL VPN users. I had to login to https://www.cisco.com/go/license, assign the PAK/token to the serial number of Cisco ASA 5506-X firewall and perform a license request to Cisco. After receiving the Product Authorization Key from Cisco, I had to activate it on the Cisco ASA 5506-X firewall using the following CLI commands: enable config t activation-key 12345678 12345678 12345678 12345678 12345678 The number of AnyConnect Premium Peers has been increased from 2 to 50 after license activation. [2] Configuring NIC teaming/bonding on CentOS 8.2 (2004) Linux Server Today I had to configure NIC teaming/bonding on CentOS 8.2 (2004) Linux Server. The server hardware is Dell PowerEdge R640 with 2x 10GE NIC ports and 6x 1GE NIC ports. NIC teaming/bonding was configured using 2x 10GE NIC ports. All I had to do is to follow the following reference guide. Reference Guide: How to Configure NIC Teaming on CentOS 8 / RHEL 8 Link: https://www.linuxtechi.com/configure-nic-teaming-centos-8-rhel-8/ In my situation, the network interfaces used in the NIC teaming/bonding are eno1 and eno2. Both are 10 Gigabit per second. -- -----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-----

3 2

Dumb Centos 8 DNF mirror question...
by Tom Bishop 14 Aug '20

14 Aug '20

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 :)

2 2

After update to 8 (2004) ... system is unbootable - UEFI Secure boot
by Leon Fauster 13 Aug '20

13 Aug '20

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

3 7

kvm & external snapshots
by Gregory P. Ennis 13 Aug '20

13 Aug '20

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/ht… 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

2 1

[Sharing] CentOS 8.2 (2004) Linux Server is Compatible with Dell PowerEdge R640 1U Server
by Turritopsis Dohrnii Teo En Ming 13 Aug '20

13 Aug '20

Subject: [Sharing] CentOS 8.2 (2004) Linux Server is Compatible with Dell PowerEdge R640 1U Server 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-----

2 3

Testing
by Turritopsis Dohrnii Teo En Ming 13 Aug '20

13 Aug '20

Testing

1 0

Docker swarm service misconfigured in FirewallD / CentOS 7
by Nicolas Kovacs 13 Aug '20

13 Aug '20

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 <?xml version="1.0" encoding="utf-8"?> <service> <short>Docker integrated swarm mode</short> <description>Natively managed cluster of Docker Engines (>=1.12.0), where you deploy services.</description> <port port="2377" protocol="tcp"/> <port port="7946" protocol="tcp"/> <port port="7946" protocol="udp"/> <port port="4789" protocol="udp"/> <protocol value="esp"/> </service> 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 : info(a)microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12

2 1

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