Discuss July 2021

discuss@lists.centos.org

69 participants
37 discussions

Microsoft Teams on CentOS 7. Does the latest version work?
by Toralf Lund 03 Dec '21

03 Dec '21

Does anyone else run Microsoft Teams on CentOS 7? I've used it for a while now, and it's generally worked reasonably well. However, after upgrading to the latest version from the Microsoft repos, it doesn't start up properly. Processes start and remain active until I give up and kill them, but I can't see a window or a tray icon or anything. Has anyone else seen this? Is there anything I can do to make the GUI appear? This is not a big deal as everything just works fine if I revert to the previous release, but it would be interesting to know if this is a general problem with the software, or I have some weird issue with my system. The release that doesn't work is 1.4.00.13653. The one that does is 1.4.00.7556. - Toralf

14 31

MATE 1.20 test build for CentOS 7 available
by Greg Bailey 14 Oct '21

14 Oct '21

Hi everyone, There's been discussions in the past about updating MATE RPMs in EPEL-7: https://bugzilla.redhat.com/show_bug.cgi?id=1436260 https://lists.centos.org/pipermail/centos/2019-August/173154.html (and lots of others...) As a proof-of-concept, I've written some scripts that clone specific commits from the Fedora master branches, and then runs a tool to re-apply RPM scriptlets that are required by EL7 but removed from the Fedora .spec files. The scripts are available at: https://github.com/gebailey/mate-rpms/tree/master/1.20/el7 There's also instructions there if you want to try upgrading to MATE 1.20 w/o rebuilding them yourself. If these packages work for others, perhaps we can revisit the idea of updating the epel7 branches of the Fedora git repos and submitting an official update. There's nothing here (yet) about building MATE 1.22 (which might require a newer gcc for EL7), or building anything on CentOS 8, but thought the CentOS 7 users might find this helpful. -Greg

6 17

Transition test report going from CentOS8 to Debian 10.
by Lamar Owen 06 Aug '21

06 Aug '21

Sorry for the length.... I'm posting this here since this particular transition has been mentioned on-list as one possibility for a path forward for current CentOS Linux users. AlmaLinux, the Developer Subscription RHEL, Rocky, CentOS Stream, Springdale, upgrading to full RHEL; all these are also possibilities, too, and all have different strengths and weaknesses. The transition to Debian has a lot of strengths, including a long track-record of support (even if the support time for a particular release is shorter), a fully-open development model with no 'corporate overlord' that I know of, a large set of supported packages, and a huge community of developers and users. For the CentOS user the main weakness is having to learn a few areas of difference in the way the system is setup and maintained; of course, if a ten-year 'stable' timeframe is really that important to you the lack of that is also a weakness. So, last week I transitioned, as a test of sorts, my working CentOS 8 main laptop to Debian 10. I kept a complete backup of the C8 install should I wish to go back to it, and installed Buster to a new mSATA SSD, but ported the two SATA drives (Dell Precision M6700 - has an mSATA slot plus two SATA bays) straight over after making full backups. I posted a pretty complete rundown on the scientific linux users mailing list, so I won't recap it all here. The bottom line was the the transition was not any more difficult, really, than moving from CentOS 7 to CentOS 8. The software versions in Buster are pretty close to what is in CentOS 8, although I have yet to need any third-party repository (PPA) for anything I've needed to install. All the packages I have worked with so far have worked fine with a little bit of massaging. These include commercial (and costly) software such as Harrison Consoles' Mixbus32C, Qoppa's PDFStudio2019 Professional, and others. So if you were to decide that this is the route for you to take, it does work and I found it to be not nearly as hard as I had thought it might be. If you install GNOME 3 you get GNOME 3; it feels pretty much the same as a non-Classic CentOS GNOME 3, just with a different set of extensions installed by default. That's on the workstation. On the server side, I'm evaluating Proxmox for the virtualization solution, and so far I'm finding it to be a pretty easy migration. I'm using the 'non-subscription' repository, so this is a no-cost option. Even getting the box registered to our EMC Clariion SAN was relatively easy; EMC provides the Unisphere Server Utility for Linux x64 in RPM form; the latest I have is "ServerUtil-Linux-64-x86-en_US-1.0.55.1.0044-1.x86_64.rpm" (which is fairly old, but I did say Clariion arrays, so they're pretty old, too). Debian has provided the 'alien' tool for some time; after installing alien, a simple 'alien -i ServerUtil-Linux-64-x86-en_US-1.0.55.1.0044-1.x86_64.rpm' installed the EMC RPM in the correct place. Proxmox already included everything that serverutilcli requires; on a plain Buster install I had to install dm-multipath and the device mapper libraries and tools before serverutilcli would find the arrays; but it ran just like it did on CentOS 8 (and 7). I haven't decided whether to stay on Debian or not; too early to tell. I have time to test and evaluate. My CentOS 7 installs aren't goin anywhere, though, at least until late 2023. And I've registered for a Developer subscription of RHEL so that I can properly evaluate that option, too. This is the beauty of open source: we have OPTIONS.

11 23

hosts.deny, fail2ban etc.
by H 04 Aug '21

04 Aug '21

|Running CentOS 7. I was under the impression - seemingly mistaken - that by adding a rule to /etc/hosts.deny such as ALL: aaa.bbb.ccc.* would ban all attempts from that network segment to connect to the server, ie before fail2ban would (eventually) ban connection attempts. This, however, does not seem correct and I could use a pointer to correct my misunderstanding. How is hosts.deny used and what have I missed? Is it necessary to run: iptables -I INPUT -s aaa.bbb.ccc.0/24 -j DROP to drop incoming connection attempts from that subnet? Thank you! |

9 17

how do I get an OLD Version like 6.3
by Jerry Geis 04 Aug '21

04 Aug '21

I need to example a really old version like 6.3. Where can I get a download for that ? Thanks Jerry

3 3

CentOS 8: two external network adapters, two ISPs - routing problems
by Konstantin Boyandin 02 Aug '21

02 Aug '21

Hello! Given: a CentOS 8-powered computer with three network adapters. eth0, eth2: external, connected to two different ISPs eth1: faces home network (intranet) The task: allow accessing certain internal services from either ISP. There are several services, I only mention SSH below. In the configs below: IP1: external IP at first ISP (ISP1), assigned to eth0 Gateway1: IP of gateway provided by ISP1 Network1,Netmask1: related to IP1 IP2: external IP at second ISP (ISP2), assigned to eth2 Gateway2: IP of gateway provided by ISP2 Network2,Netmask2: related to IP2 LocalSSHIP: IP in intranet (eth1) where SSH server is running Current configs follow. Routing tables: echo "200 isp1" >> /etc/iproute2/rt_tables echo "201 isp2" >> /etc/iproute2/rt_tables Routing policies: /etc/sysconfig/network-scripts/route-eth0 Network1 dev eth0 src IP1 table isp1 default via Gateway1 dev eth0 table isp1 /etc/sysconfig/network-scripts/route-eth2 Network2 dev eth2 src IP2 table isp2 default via Gateway2 dev eth2 table isp2 Routing rules: /etc/sysconfig/network-scripts/rule-eth0 from IP1/32 table isp1 /etc/sysconfig/network-scripts/rule-eth2 from IP2/32 table isp2 iptables snippets. External traffic forwarded to local SSH server from both interfaces: iptables -A PREROUTING -t nat -i eth0 -p tcp -d IP1 --dport 22 -j DNAT --to LocalSSHIP:22 iptables -A PREROUTING -t nat -i eth2 -p tcp -d IP2 --dport 22 -j DNAT --to LocalSSHIP:22 iptables -A FORWARD -p tcp -d LocalSSHIP --dport 22 -j ACCEPT eth0 is default gateway: $ ip route default via Gateway1 dev eth0 proto static metric 100 default via Gateway2 dev eth2 proto static metric 101 ... $ ip rule 0: from all lookup local 32764: from IP2 lookup isp2 32765: from IP1 lookup isp1 32766: from all lookup main 32767: from all lookup default SNAT is applied for the traffic originating from eth1: iptables -t nat -A POSTROUTING -i eth1 -o eth0 -j SNAT --to-source IP1 Current situation: - All services forwarded from eth0 are working normally. - All traffic originating from intranet passes out and back normally. - All the attempts to access services from eth2 time out. There are no obvious hints in /var/log/messages (such as complaints about "martian IPs"). I am somewhat at a loss here, all the pieces of advice would be very welcome. -- Sincerely, Konstantin Boyandin

3 2

It's been six days since CVD-2021-33909 was patched in RHEL, what's the holdup for Stream 8?
by Steven Rosenberg 29 Jul '21

29 Jul '21

This bug in the kernel was patched in RHEL on 7/20. Every other mainstream Linux distro patched it that day or the day after. That includes Rocky and Alma. https://access.redhat.com/security/cve/CVE-2021-33909 It's still not patched six days later in CentOS Stream 8. This Bugzilla entry makes it clear that when it comes to security, CentOS Stream falls behind RHEL. But this far behind? https://bugzilla.redhat.com/show_bug.cgi?id=1975182 This doesn't make a good argument for Stream being a viable CentOS Linux replacement.

3 5

Old CentOS 6.3 grub.conf
by Jerry Geis 28 Jul '21

28 Jul '21

I am trying to "add" an entry to grub.conf on CentOS 6.3 - and change the default=0 to default=1 # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You do not have a /boot partition. This means that # all kernel and initrd paths are relative to /, eg. # root (hd0,0) # kernel /boot/vmlinuz-version ro root=/dev/sda1 # initrd /boot/initrd-[generic-]version.img #boot=/dev/sda default=1 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.32-279.el6.x86_64) root (hd0,0) kernel /boot/vmlinuz-2.6.32-279.el6.x86_64 ro root=UUID=09337d96-de39-43f1-99c2-8a6a1fadd465 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet initrd /boot/initramfs-2.6.32-279.el6.x86_64.img title Boot Other root (hd0,0) kernel /boot/vmlinuz initrd /boot/initrd I then run "grub-install /dev/sda" and reboot. If I cursor down - my new title is present - but the default is still the first title. What did I miss ? Thanks, jerry

1 0

heads up: stream8 cloud-init rebase 20 to 21
by Leon Fauster 26 Jul '21

26 Jul '21

FYI and everyone on C8S: cloud-init does run on deployed cloud vm's anymore succesfully after update (it was rebased from 20. to 21.). Fix: before rebooting run "cloud-init clean" -- Leon

1 0

Folio Infobase
by J Martin Rushton 26 Jul '21

26 Jul '21

Does anyone know any way to read .nfo files from Folio infobases. The best suggestion I've seen so far is to run up a VM with Windows 98 on it, does anyone know where I can get a copy of that! BTW, these are not the .nfo files used to describe scenes. -- J Martin Rushton MBCS

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss July 2021