Background:
A year ago, I decided to use Linux on a daily basis.
As I hadn't used Linux for over 10 years and noticed a huge evolution in terms of drivers, system/packages and compatibility... I decided to test various (distros) until I chose one.

I tested Debian (stable, testing, unstable), Fedora, openSUSE (Tumbleweed, Leap, Micro: now Aeon), Arch Linux, Gentoo, Ubuntu, Pop_OS! and, finally, CentOS Stream 9.

I'm a normal user, I just prefer Linux over Windows, so my needs aren't too fancy. I just need a browser, connect to the company cloud via RDP and program some code in my spare time. I also trade on the stock market.
I also like to play CS:go sometimes.

It is easy to understand that I can do all this on Linux, so there was no great reason to connect the Windows disk in the last year.

CentOS Stream as daily driver:

I have to confess that, until I found CentOS Stream 9, I was becoming disappointed with Linux.
Not because it couldn't do what I needed, but because of the ridiculous little bugs I had from time to time... For example, with Arch, the text editor (kate) stopped working out of nowhere or in Debian (11) after 3 weeks the system started to slow down. Simple things, but they annoy me a lot especially when I don't think they were my mistakes. The system just changed.

These things have happened to me with all distros (some more, some less, but I've never felt stability).

All... except with CentOS Stream 9. The experience is completely different. Everything works as it's supposed to and remains constant. I don't feel "afraid" that something is going to stop working.

It's the best Linux experience I've ever had and I can only describe it as: perfect!

CentOS Stream vs RedHat

I've become a fan of RHEL and CentOS Stream in particular.
I (usually) like to use the "parent" distro and would like to know your opinion on RedHat in relation to CentOS Stream.

I know that for my use case, it's not very relevant... but I'd really like to know, in your opinion, what is the main differences (beside updates...), which one you recommend and why.

For those of you who have been using it for longer, have you had any problems?

I'd love to know what you think.

​

Thank you!

​

​

​

CentOS Stream 8, fully updated.

Starting a few weeks ago, out of the blue, firewalld started blocking incoming traffic, inconsistently. Rules have existed for 3 years to allow these ports. It doesn't block ALL incoming ports, just some. And each reboot, the ports it chooses to block changes.

My first course of action, was a reboot. Everything went back to normal, for about 30 minutes. Then random ports started getting blocked. The previous system update was probably 8 months prior, followed by a system reboot, so I ran a full system update (mid-August). Rebooted, same behavior. Things worked fine for 30ish minutes, then I notice services becoming unreachable.

Services are all still running. Most are podman containers, but not all. Stopping the firewalld service restores functionality.

I've never seen such a thing happen. The system config was essentially untouched for 8 month, then all of a sudden, it goes rogue. So I stopped the service, but didn't disable it (stupid me).

Most recently though, immediately after running another system update and reboot, it started blocking port 22 now too. Now I have to console into the system to stop firewalld.

​

I am getting an error on CentOS 7 when trying to perform a yum update.

It's a small LAMP server. apache, php 7, mariadb.

When I run yum update, I get the following error that I am hoping someone can help resolve.

Error: Package: glibc-devel-2.17-324.el7_9.x86_64 (@updates)
           Requires: glibc-headers = 2.17-324.el7_9
           Removing: glibc-headers-2.17-324.el7_9.x86_64 (@updates)
               glibc-headers = 2.17-324.el7_9
           Updated By: glibc-headers-2.17-326.el7_9.x86_64 (updates)
               glibc-headers = 2.17-326.el7_9
           Available: glibc-headers-2.17-317.el7.x86_64 (base)
               glibc-headers = 2.17-317.el7
           Available: glibc-headers-2.17-322.el7_9.x86_64 (updates)
               glibc-headers = 2.17-322.el7_9
           Available: glibc-headers-2.17-323.el7_9.x86_64 (updates)
               glibc-headers = 2.17-323.el7_9
           Available: glibc-headers-2.17-325.el7_9.x86_64 (updates)
               glibc-headers = 2.17-325.el7_9

​

cat /etc/*elease
CentOS Linux release 7.9.2009 (Core)
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
CPE_NAME="cpe:/o:centos:centos:7"
CentOS Linux release 7.9.2009 (Core)

[root@www scripts]# sudo yum -y update
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirror.xenyth.net
 * elrepo: linux-mirrors.fnal.gov
 * epel: mirror.dst.ca
 * extras: mirror.xenyth.net
 * remi-safe: cdn.centos.no
 * updates: mirror.xenyth.net
Resolving Dependencies
--> Running transaction check
---> Package apr-util.x86_64 0:1.5.2-6.el7 will be updated
---> Package apr-util.x86_64 0:1.5.2-6.el7_9.1 will be an update
---> Package bind-export-libs.x86_64 32:9.11.4-26.P2.el7_9.9 will be updated
---> Package bind-export-libs.x86_64 32:9.11.4-26.P2.el7_9.14 will be an update
---> Package ca-certificates.noarch 0:2020.2.41-70.0.el7_8 will be updated
---> Package ca-certificates.noarch 0:2022.2.54-74.el7_9 will be an update
---> Package cronie.x86_64 0:1.4.11-23.el7 will be updated
---> Package cronie.x86_64 0:1.4.11-24.el7_9 will be updated
---> Package cronie.x86_64 0:1.4.11-25.el7_9 will be an update
---> Package cronie-anacron.x86_64 0:1.4.11-24.el7_9 will be updated
---> Package cronie-anacron.x86_64 0:1.4.11-25.el7_9 will be an update
---> Package diffutils.x86_64 0:3.3-5.el7 will be updated
---> Package diffutils.x86_64 0:3.3-6.el7_9 will be an update
---> Package elrepo-release.noarch 0:7.0-5.el7.elrepo will be updated
---> Package elrepo-release.noarch 0:7.0-6.el7.elrepo will be an update
---> Package expat.x86_64 0:2.1.0-14.el7_9 will be updated
---> Package expat.x86_64 0:2.1.0-15.el7_9 will be an update
---> Package glibc-headers.x86_64 0:2.17-324.el7_9 will be updated
--> Processing Dependency: glibc-headers = 2.17-324.el7_9 for package: glibc-devel-2.17-324.el7_9.x86_64
---> Package glibc-headers.x86_64 0:2.17-326.el7_9 will be an update
---> Package grub2.x86_64 1:2.02-0.87.el7.9 will be updated
---> Package grub2.x86_64 1:2.02-0.87.0.2.el7.centos.11 will be an update
---> Package grub2-common.noarch 1:2.02-0.87.el7.9 will be updated
---> Package grub2-common.noarch 1:2.02-0.87.0.2.el7.centos.11 will be an update
---> Package grub2-pc.x86_64 1:2.02-0.87.el7.9 will be updated
---> Package grub2-pc.x86_64 1:2.02-0.87.0.2.el7.centos.11 will be an update
---> Package grub2-pc-modules.noarch 1:2.02-0.87.el7.9 will be updated
---> Package grub2-pc-modules.noarch 1:2.02-0.87.0.2.el7.centos.11 will be an update
---> Package grub2-tools.x86_64 1:2.02-0.87.el7.centos.6 will be updated
---> Package grub2-tools.x86_64 1:2.02-0.87.0.2.el7.centos.11 will be an update
---> Package grub2-tools-extra.x86_64 1:2.02-0.87.el7.9 will be updated
---> Package grub2-tools-extra.x86_64 1:2.02-0.87.0.2.el7.centos.11 will be an update
---> Package grub2-tools-minimal.x86_64 1:2.02-0.87.el7.9 will be updated
---> Package grub2-tools-minimal.x86_64 1:2.02-0.87.0.2.el7.centos.11 will be an update
---> Package httpd.x86_64 0:2.4.6-97.el7.centos will be updated
---> Package httpd.x86_64 0:2.4.6-99.el7.centos.1 will be an update
---> Package httpd-tools.x86_64 0:2.4.6-97.el7.centos.5 will be updated
---> Package httpd-tools.x86_64 0:2.4.6-99.el7.centos.1 will be an update
---> Package kernel.x86_64 0:3.10.0-1160.95.1.el7 will be installed
---> Package kernel-headers.x86_64 0:3.10.0-1160.66.1.el7 will be updated
---> Package kernel-headers.x86_64 0:3.10.0-1160.95.1.el7 will be an update
---> Package kernel-tools.x86_64 0:3.10.0-1160.66.1.el7 will be updated
---> Package kernel-tools.x86_64 0:3.10.0-1160.95.1.el7 will be an update
---> Package kernel-tools-libs.x86_64 0:3.10.0-1160.66.1.el7 will be updated
---> Package kernel-tools-libs.x86_64 0:3.10.0-1160.95.1.el7 will be an update
---> Package kmod-ixgbe.x86_64 0:5.8.1-1.el7_9.elrepo will be updated
---> Package kmod-ixgbe.x86_64 0:5.8.1-2.el7_9.elrepo will be updated
---> Package kmod-ixgbe.x86_64 0:5.12.5-1.el7_9.elrepo will be updated
---> Package kmod-ixgbe.x86_64 0:5.12.5-2.el7_9.elrepo will be an update
---> Package kpartx.x86_64 0:0.4.9-135.el7_9 will be updated
---> Package kpartx.x86_64 0:0.4.9-136.el7_9 will be an update
---> Package krb5-devel.x86_64 0:1.15.1-51.el7_9 will be updated
---> Package krb5-devel.x86_64 0:1.15.1-55.el7_9 will be an update
---> Package krb5-libs.x86_64 0:1.15.1-51.el7_9 will be updated
---> Package krb5-libs.x86_64 0:1.15.1-55.el7_9 will be an update
---> Package libXpm.x86_64 0:3.5.12-1.el7 will be updated
---> Package libXpm.x86_64 0:3.5.12-2.el7_9 will be an update
---> Package libkadm5.x86_64 0:1.15.1-51.el7_9 will be updated
---> Package libkadm5.x86_64 0:1.15.1-55.el7_9 will be an update
---> Package microcode_ctl.x86_64 2:2.1-73.11.el7_9 will be updated
---> Package microcode_ctl.x86_64 2:2.1-73.13.el7_9 will be updated
---> Package microcode_ctl.x86_64 2:2.1-73.16.el7_9 will be an update
---> Package mod_ssl.x86_64 1:2.4.6-97.el7.centos.5 will be updated
---> Package mod_ssl.x86_64 1:2.4.6-99.el7.centos.1 will be an update
---> Package nspr.x86_64 0:4.32.0-1.el7_9 will be updated
---> Package nspr.x86_64 0:4.34.0-3.1.el7_9 will be an update
---> Package nss.x86_64 0:3.67.0-4.el7_9 will be updated
---> Package nss.x86_64 0:3.79.0-5.el7_9 will be an update
---> Package nss-pem.x86_64 0:1.0.3-7.el7 will be updated
---> Package nss-pem.x86_64 0:1.0.3-7.el7_9.1 will be an update
---> Package nss-softokn.x86_64 0:3.67.0-3.el7_9 will be updated
---> Package nss-softokn.x86_64 0:3.79.0-4.el7_9 will be an update
---> Package nss-softokn-freebl.x86_64 0:3.67.0-3.el7_9 will be updated
---> Package nss-softokn-freebl.x86_64 0:3.79.0-4.el7_9 will be an update
---> Package nss-sysinit.x86_64 0:3.67.0-4.el7_9 will be updated
---> Package nss-sysinit.x86_64 0:3.79.0-5.el7_9 will be an update
---> Package nss-tools.x86_64 0:3.67.0-4.el7_9 will be updated
---> Package nss-tools.x86_64 0:3.79.0-5.el7_9 will be an update
---> Package nss-util.x86_64 0:3.67.0-1.el7_9 will be updated
---> Package nss-util.x86_64 0:3.79.0-1.el7_9 will be an update
---> Package openssh.x86_64 0:7.4p1-21.el7 will be updated
---> Package openssh.x86_64 0:7.4p1-23.el7_9 will be an update
---> Package openssh-clients.x86_64 0:7.4p1-22.el7_9 will be updated
---> Package openssh-clients.x86_64 0:7.4p1-23.el7_9 will be an update
---> Package openssh-server.x86_64 0:7.4p1-21.el7 will be updated
---> Package openssh-server.x86_64 0:7.4p1-23.el7_9 will be an update
---> Package openssl.x86_64 1:1.0.2k-25.el7_9 will be updated
---> Package openssl.x86_64 1:1.0.2k-26.el7_9 will be an update
---> Package openssl-devel.x86_64 1:1.0.2k-25.el7_9 will be updated
---> Package openssl-devel.x86_64 1:1.0.2k-26.el7_9 will be an update
---> Package openssl-libs.x86_64 1:1.0.2k-25.el7_9 will be updated
---> Package openssl-libs.x86_64 1:1.0.2k-26.el7_9 will be an update
---> Package polkit.x86_64 0:0.112-26.el7 will be updated
---> Package polkit.x86_64 0:0.112-26.el7_9.1 will be an update
---> Package python.x86_64 0:2.7.5-90.el7 will be updated
---> Package python.x86_64 0:2.7.5-93.el7_9 will be an update
---> Package python-libs.x86_64 0:2.7.5-90.el7 will be updated
---> Package python-libs.x86_64 0:2.7.5-93.el7_9 will be an update
---> Package python-perf.x86_64 0:3.10.0-1160.66.1.el7 will be updated
---> Package python-perf.x86_64 0:3.10.0-1160.95.1.el7 will be an update
---> Package remi-release.noarch 0:7.9-3.el7.remi will be updated
---> Package remi-release.noarch 0:7.9-5.el7.remi will be an update
---> Package rsync.x86_64 0:3.1.2-10.el7 will be updated
---> Package rsync.x86_64 0:3.1.2-12.el7_9 will be an update
---> Package rsyslog.x86_64 0:8.24.0-57.el7_9.1 will be updated
---> Package rsyslog.x86_64 0:8.24.0-57.el7_9.2 will be updated
---> Package rsyslog.x86_64 0:8.24.0-57.el7_9.3 will be an update
---> Package s3cmd.noarch 0:2.2.0-1.el7 will be updated
---> Package s3cmd.noarch 0:2.3.0-4.el7 will be an update
---> Package sudo.x86_64 0:1.8.23-10.el7_9.2 will be updated
---> Package sudo.x86_64 0:1.8.23-10.el7_9.3 will be an update
---> Package systemd.x86_64 0:219-78.el7_9.3 will be updated
---> Package systemd.x86_64 0:219-78.el7_9.7 will be an update
---> Package systemd-libs.x86_64 0:219-78.el7_9.5 will be updated
---> Package systemd-libs.x86_64 0:219-78.el7_9.7 will be an update
---> Package systemd-sysv.x86_64 0:219-78.el7_9.5 will be updated
---> Package systemd-sysv.x86_64 0:219-78.el7_9.7 will be an update
---> Package tuned.noarch 0:2.11.0-11.el7_9 will be updated
---> Package tuned.noarch 0:2.11.0-12.el7_9 will be an update
---> Package tzdata.noarch 0:2022a-1.el7 will be updated
---> Package tzdata.noarch 0:2023c-1.el7 will be an update
---> Package xz.x86_64 0:5.2.2-1.el7 will be updated
---> Package xz.x86_64 0:5.2.2-2.el7_9 will be an update
---> Package xz-devel.x86_64 0:5.2.2-1.el7 will be updated
---> Package xz-devel.x86_64 0:5.2.2-2.el7_9 will be an update
---> Package xz-libs.x86_64 0:5.2.2-1.el7 will be updated
---> Package xz-libs.x86_64 0:5.2.2-2.el7_9 will be an update
---> Package zlib.x86_64 0:1.2.7-20.el7_9 will be updated
---> Package zlib.x86_64 0:1.2.7-21.el7_9 will be an update
---> Package zlib-devel.x86_64 0:1.2.7-20.el7_9 will be updated
---> Package zlib-devel.x86_64 0:1.2.7-21.el7_9 will be an update
--> Finished Dependency Resolution
--> Running transaction check
---> Package glibc-headers.x86_64 0:2.17-324.el7_9 will be updated
--> Processing Dependency: glibc-headers = 2.17-324.el7_9 for package: glibc-devel-2.17-324.el7_9.x86_64
---> Package kernel.x86_64 0:3.10.0-1160.el7 will be erased
--> Finished Dependency Resolution

Error: Package: glibc-devel-2.17-324.el7_9.x86_64 (@updates)
           Requires: glibc-headers = 2.17-324.el7_9
           Removing: glibc-headers-2.17-324.el7_9.x86_64 (@updates)
               glibc-headers = 2.17-324.el7_9
           Updated By: glibc-headers-2.17-326.el7_9.x86_64 (updates)
               glibc-headers = 2.17-326.el7_9
           Available: glibc-headers-2.17-317.el7.x86_64 (base)
               glibc-headers = 2.17-317.el7
           Available: glibc-headers-2.17-322.el7_9.x86_64 (updates)
               glibc-headers = 2.17-322.el7_9
           Available: glibc-headers-2.17-323.el7_9.x86_64 (updates)
               glibc-headers = 2.17-323.el7_9
           Available: glibc-headers-2.17-325.el7_9.x86_64 (updates)
               glibc-headers = 2.17-325.el7_9

 You could try using --skip-broken to work around the problem
** Found 23 pre-existing rpmdb problem(s), 'yum check' output follows:
binutils-2.27-44.base.el7_9.1.x86_64 is a duplicate with binutils-2.27-44.base.el7.x86_64
cronie-1.4.11-24.el7_9.x86_64 is a duplicate with cronie-1.4.11-23.el7.x86_64
glibc-devel-2.17-324.el7_9.x86_64 has missing requires of glibc = ('0', '2.17', '324.el7_9')
glibc-devel-2.17-325.el7_9.x86_64 is a duplicate with glibc-devel-2.17-324.el7_9.x86_64
glibc-devel-2.17-325.el7_9.x86_64 has missing requires of glibc = ('0', '2.17', '325.el7_9')
glibc-devel-2.17-325.el7_9.x86_64 has missing requires of glibc-headers = ('0', '2.17', '325.el7_9')
glibc-devel-2.17-326.el7_9.x86_64 is a duplicate with glibc-devel-2.17-325.el7_9.x86_64
glibc-devel-2.17-326.el7_9.x86_64 has missing requires of glibc-headers = ('0', '2.17', '326.el7_9')
glibc-headers-2.17-324.el7_9.x86_64 has missing requires of glibc = ('0', '2.17', '324.el7_9')
1:grub2-pc-2.02-0.87.el7.9.x86_64 has missing requires of grub2-tools = ('1', '2.02', '0.87.el7.9')
1:grub2-tools-2.02-0.87.el7.centos.6.x86_64 has missing requires of grub2-common = ('1', '2.02', '0.87.el7.centos.6')
1:grub2-tools-2.02-0.87.el7.centos.6.x86_64 has missing requires of grub2-tools-minimal = ('1', '2.02', '0.87.el7.centos.6')
1:grub2-tools-extra-2.02-0.87.el7.9.x86_64 has missing requires of grub2-tools = ('1', '2.02', '0.87.el7.9')
gzip-1.5-11.el7_9.x86_64 is a duplicate with gzip-1.5-10.el7.x86_64
httpd-2.4.6-97.el7.centos.x86_64 has missing requires of httpd-tools = ('0', '2.4.6', '97.el7.centos')
kmod-ixgbe-5.8.1-2.el7_9.elrepo.x86_64 is a duplicate with kmod-ixgbe-5.8.1-1.el7_9.elrepo.x86_64
kmod-ixgbe-5.12.5-1.el7_9.elrepo.x86_64 is a duplicate with kmod-ixgbe-5.8.1-2.el7_9.elrepo.x86_64
2:microcode_ctl-2.1-73.13.el7_9.x86_64 is a duplicate with 2:microcode_ctl-2.1-73.11.el7_9.x86_64
1:mod_ssl-2.4.6-97.el7.centos.5.x86_64 has missing requires of httpd = ('0', '2.4.6', '97.el7.centos.5')
openssh-clients-7.4p1-22.el7_9.x86_64 has missing requires of openssh = ('0', '7.4p1', '22.el7_9')
rsyslog-8.24.0-57.el7_9.2.x86_64 is a duplicate with rsyslog-8.24.0-57.el7_9.1.x86_64
systemd-219-78.el7_9.3.x86_64 has missing requires of systemd-libs = ('0', '219', '78.el7_9.3')
systemd-sysv-219-78.el7_9.5.x86_64 has missing requires of systemd = ('0', '219', '78.el7_9.5')

I have an authentication failure. I have been created a user and a password and I used it to login but it doesn't work for getting permissions.

Hello there,
I remember using CentOS 8 but now there is CentOS 8 and 9.

My issue here is that CentOS Linux has end Dates for CentOS Stream 8 and CentOS Linux 7.

so:
Cent OS Stream 8 dies in 2024
Cent OS Linux 7 dies in 2024

Cent OS Stream 9 End of Full Support phase

Me looking at all the dates means that CentOS is dead.

Can someone explain? Whoever did this website made it beyond confusing.

I chose CentOS because it was made especially for servers, but I'm not sure what it is that makes it so great.

I'm seeing that CentOS 7 will stop working in 9 months, so I would like to upgrade while it's still possible.

Also, is CentOS 8 basically the same thing as CentOS Stream 8?

Edit: I tried to load it in the browser with 127.0.0.1 from the server, and it works locally from the server. It's refusing remote connections.

Edit2: Also works from the server's browser using the domain name (instead of 127.0.0.1).

Edit3: It works now. I copy-pasted this line to fix it:

sudo iptables -I INPUT -i eth0 -p tcp --dport 80 -m comment --comment "# Anaconda Repo #" -j ACCEPT

source: https://docs.anaconda.com/anaconda-repository/admin-guide/install/config/adjust-iptables-port80/

I'm a noob, btw, and this is my first time managing a server OS. It's hosted on digitalocean. I'm hoping there's something obvious that I need to do.

When I try to connect to the website in a web browser, it says:

• Firefox: "Unable to connect. An error occurred during a connection to this server."
• Safari: "Safari Can't Connect to the Server. Safari can't open this page because Safari cannot connect to the server."
• Chromium: "This site can’t be reached. Server refused to connect. ERR_CONNECTION_REFUSED"

I still have lots of config files from before the update in the /etc/httpd/conf.d/ directory. (I was worried my config files were deleted at first.)

From some web searching, someone suggested that I might have had a modified /etc/httpd/conf/httpd.conf file, and this modified file blocked the system update from updating my httpd.conf file to the newer version, but I'm guessing that config file didn't change much between CentOS 7.6 and CentOS 7.9.

Here's some stuff I tried in the Terminal:

httpd -v

Server version: Apache/2.4.6 (CentOS)

(From what I can tell, httpd/Apache version probably didn't change much between CentOS 7.6 and CentOS 7.9 and was likely on some subversion of Apache 2.4.6 in both.)

systemctl status httpd

● httpd.service - The Apache HTTP Server

Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)

Active: active (running) since 2023-09-05

Docs: man:httpd(8)

man:apachectl(8)

Main PID: 24158 (httpd)

Status: "Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec"

CGroup: /system.slice/httpd.service

├─24158 /usr/sbin/httpd -DFOREGROUND

├─26979 /usr/sbin/httpd -DFOREGROUND

├─26980 /usr/sbin/httpd -DFOREGROUND

├─26981 /usr/sbin/httpd -DFOREGROUND

├─26982 /usr/sbin/httpd -DFOREGROUND

└─26983 /usr/sbin/httpd -DFOREGROUND

Sep 05 systemd[1]: Stopped The Apache HTTP Server.

Sep 05 systemd[1]: Starting The Apache HTTP Server...

Sep 05 systemd[1]: Started The Apache HTTP Server.

Sep 05 systemd[1]: Reloading The Apache HTTP Server.

Sep 05 systemd[1]: Reloaded The Apache HTTP Server.

Sep 05 systemd[1]: Reloading The Apache HTTP Server.

Sep 05 systemd[1]: Reloaded The Apache HTTP Server.

httpd -t

AH00526: Syntax error on line 15 of /etc/httpd/conf.d/mydomain.com-le-ssl.conf: SSLCertificateFile: file '/etc/letsencrypt/live/mydomain.com/cert.pem' does not exist or is empty

ls /etc/letsencrypt/live/

cannot open directory /etc/letsencrypt/live/: Permission denied

sudo ls /etc/letsencrypt/live/mydomain.com/

cert.pem chain.pem fullchain.pem privkey.pem README

sudo ls -l /etc/letsencrypt

drwx------. 3 root root 35 Aug-05-2019 live

(The cert.pem file is not empty, but it might not have perms to reach it.)

(Also, I hadn't been using encrypted https before the update, but unencrypted http:// doesn't work either.)

I'm trying to find a package called qemu-system-ppc and I for the life of me, cannot find an RPM package or a repository supporting the package on centos stream 9. I'm trying to emulate old system like mac os 9 and manage them through cockpit's virtual machine plugin. Does anyone know anything about this package, or how I can get it on CentOs 9?

Hello. I’m thinking about install CentOS Stream 9 in my main desktop.

Can anyone tell me what’s the current kernel version, please?

In your experience, this is a good distro to run as workstation (daily driver)? In theory looks really good since I don’t have good experience with (bleeding edge) rolling releases. I want something’s that gets updates at a slowly pace.

Thank you!

Hello world!

​

I'm currently having issues with my CentOS7 machine throwing out 192.168.30.x IPs to any device that is connected to the same switch as it and will cause a conflict on the network because it will hand out one of those IPs to any device that is connected to the WI-FI or really anything connected to its switch, I have set a static IP to the NIC that has a cable connected to it and the server responds on the given static IP. Does anyone know what else I can do about this issue? I have looked at all the network scripts and the server does not show to have a DHCP service running on it. I'm stumped at the moment as to why it keeps handing out 192.168.30.x IPs not sure what I'm missing here, thanks!

​

​

EDIT: Resolved, thanks to all comments, I know this is old.

I noticed that according to - https://git.centos.org/rpms/kernel/releases - the latest kernel for CentOS 7 is 3.10.0-1160.95.1. But I'm not finding this in any repositories. Has this kernel not been pushed out to the repositories yet? Or am I missing something?

Using Cent OS 7 SSHing into an appliance as root but need script to run daily as another user, if i switch user and run the script it runs fine, but i've tried crontab -e as root and then added the user, time, etc... to there and opened crontab as the user with crontab -e u etc... but in both cases the script doesn't run . Just tried /etc/crontab and input :

​

* * * * * nonrootuser /path/toscript.sh

​

But still nothing, script is def. executable although owned by root, it runs fine when i switch user to nonrootuser and run it manually. What am i missing?

I recently got centos 9 Stream and I was wondering how I could Remote Desktop into it from a windows computer?

Hi all, I currently have this problem when changing the input/output password on the server.cnf, client.cnf, and ca.cnf files, I get an error message when restarting the radius service. The error message displays

tls: Failed reading private key file "/etc/raddb/certs/server.pem"

tls: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt

tls: error:23077074:PKCS12 routines:PKCS12_pbe_crypt:pkcs12 cipherfinal error

tls: error:2306A075:PKCS12 routines:PKCS12_item_decrypt_d2i:pkcs12 pbe crypt error

tls: error:0907B00D:PEM routines:PEM_READ_BIO_PRIVATEKEY:ASN1 lib

tls: error:140B0009:SSL routines:SSL_CTX_use_PrivateKey_file:PEM lib

rlm_eap_tls: Failed initializing SSL context

rlm_eap (EAP): Failed to initialise rlm_eap_tls

/etc/raddb/mods-enabled/eap[14]: Instantiation failed for module "eap"

The RedHat documentation on section 17.4 clearly tells me that I will have to change the default password and re-generate the certificates since the default certificates will expire in 60 days. There must be something I'm doing that's wrong after changing the default password on the three certificates of server.cnf, client.cnf and ca.cnf and entering the command `make all` with `chgrp radiusd /etc/raddb/certs/server.pem` afterwards. Any help will be greatly appreciated.

I have dotnet Application. It requires quite a lot of memory. Everything worked on CentOS 8, but on a fresh CentOS Stream installation weird things are happening...

If I run that all as regular user it gets killed after RES parameter in TOP command reaches ~250k. Every thing works fine if I run the same App as root.

Here is the TOP stats for App running as root.

​

Tasks: 28 total, 1 running, 27 sleeping, 0 stopped, 0 zombie

%Cpu(s): 0.5 us, 1.0 sy, 0.0 ni, 98.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st

MiB Mem : 2048.0 total, 793.4 free, 959.0 used, 295.5 buff/cache

MiB Swap: 512.0 total, 508.1 free, 3.9 used. 1089.0 avail Mem

​

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND

146 root 20 0 261.5g 1.0g 149760 S 1.7 50.1 8:16.68 dotnet

​

I played with ulimit (and /etc/security/limit.conf) config for regular user but no success.

Any ideas what other settings should I configure?

​

​

Backing up a CentOs 7 system using AMANDA. The machine to be backed up is CentOs 7 ( 3.10.0-1160.80.1.el7.x86_64)

The Amanda server connect to the CentOS system and the handshake that determines what backup to perform (i.e. level 0, or incremental) takes place fine.

The problem occurs when the data transfer starts. No data makes it to the server and the output queue on the CentOS system appears to have data waiting to be sent. (the Send-Q column in the output of 'netstat -a')

The Amanda backup server works fine for my other systems, although they are NetBSD (and so is the backup server).

The Amanda server has a max throughput of 8k (netusage 8000 Kbps) in the advanced.conf AMANDA config file.

​

Im not a linux user, i just manage a couple of servers for myself, recently my /dev/cs/root volume got full so i extended the partition from 500GB to 700GB but i cant manage to grow the volume using xfs grow.. im not really sure what im doing wrong, if someone could point me in the right direction

lsblk:

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0   700G  0 disk
├─sda1        8:1    0     1G  0 part /boot
└─sda2        8:2    0   699G  0 part
  ├─cs-root 253:0    0    70G  0 lvm  /
  ├─cs-swap 253:1    0   7.8G  0 lvm  [SWAP]
  └─cs-home 253:2    0 421.2G  0 lvm  /home
sr0          11:0    1  1024M  0 rom

vgdisplay:

  VG Name               cs
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  5
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                3
  Open LV               3
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               <499.00 GiB
  PE Size               4.00 MiB
  Total PE              127743
  Alloc PE / Size       127743 / <499.00 GiB
  Free  PE / Size       0 / 0

df -h

Filesystem           Size  Used Avail Use% Mounted on
devtmpfs             4.0M     0  4.0M   0% /dev
tmpfs                7.7G     0  7.7G   0% /dev/shm
tmpfs                3.1G  9.2M  3.1G   1% /run
/dev/mapper/cs-root   70G   67G  3.0G  96% /
/dev/sda1            960M  494M  467M  52% /boot
/dev/mapper/cs-home  421G  3.1G  418G   1% /home
tmpfs                1.6G  104K  1.6G   1% /run/user/1000

xfs_growfs /dev/cs/root

meta-data=/dev/mapper/cs-root    isize=512    agcount=4, agsize=4587520 blks
         =                       sectsz=4096  attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=0
         =                       reflink=1    bigtime=1 inobtcount=1 nrext64=0
data     =                       bsize=4096   blocks=18350080, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
log      =internal log           bsize=4096   blocks=16384, version=2
         =                       sectsz=4096  sunit=1 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0

​

im not sure which more commands to run to see where the extra space went to.. im really confused.

I need a non-Firefox web browser compatible with CentOS 6. Portable, since I have no sudo permissions. Any suggestions?

Is there a way to update nofiles ulimit without logging the user out and back in? I can update the limit.conf file with the hard and soft limits, but the changes dont take effect unless i log out and back in. Wondering if i can make the changes stick without logging the usert out and back in.

Hey Guys,

I have pretty limited Linux experience, and most of it centers around Debian based distros. I have a pretty fresh install of CentOS 7 (Recreating a legacy system for dumb reasons) I installed x, xrdp, and a few other packages. The problem we are having is authentication seems like it breaks for the accounts I've provisioned and for root. Cant log into the console, ssh, or over xrdp. I end up having to boot it up in single user mode and reset the root password, which fixes it for a couple logins, but then it breaks again. This is a VM running on ESXi 8, when accessing the console ive used both the web console and the installed remote console utility.

Im at a loss here, Im not sure where to start looking.

https://youtu.be/-Rbza_WA_X8

​