rhel

This evening I’m trying to enable EPEL repository on a RHEL 9 server, by following instruction is taken from How to install EPEL on RHEL and CentOS Stream article [1] by Red Hat Enable Sysadmin. Enable the CodeReady Linux Builder repository. $ sudo subscription-manager repos --enable \ codeready-builder-for-rhel-9-$(arch)-rpms Repository 'codeready-builder-for-rhel-9-x86_64-rpms' is enabled for this system. Install the EPEL RPM. $ sudo dnf install \ https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ...snip... Installed: epel-release-9-7.el9.noarch Complete! Let’s try to install htop (available from the EPEL repo) to verify that everything is working: $ sudo dnf install htop -y ....

Well, if you know you know, otherwise, you could have wasted the whole evening trying to upgrade RHEL 7.9 with High Availability to RHEL 8.x, and failed! If you read this post, head to the link at [1] and you’d see that Red Hat does not support i-place upgrades or rolling-upgrades of cluster nodes from one major release of RHEL to another. Here is an extract from [1]: Red Hat does not support in-place upgrades or rolling-upgrades of cluster nodes from one major release of RHEL to another....

Recently, I decided to pick up learning Kubernetes again after completely being absent from this world for many years. In this post, I’ll document how to install Helm CLI on AlmaLinx 9. Helm is like a package manager for Kubernetes. Helm CLI can be installed on your local machine, it does not to be installed on the Kubenetes node. However, in order to interact with your Kubernetes cluster, you’ll need to also have kubectl command as well as properly configured it to interact with your Kubernetes cluster....

If you’re reading this post, it’s quite likely that you’re fully aware that Red Hat provide a no-cost Red Hat Developer Subscription for individuals. With this subscript you can use it run RHEL for free. The subscription only lasts one year, and when it expires it can’t be renewed. You must re-register. I have a test RHEL vm, but I hardly use. So today when I turned it on and logged into it, the following message came up when i tried to update the system:...

On RHEL 7/8, CentOS 7/8 and even Ubuntu (??), by default the journal log data is stored only in memory (/run/log/journal/ directory). There are 2 ways to retain the journal log messages. The first one is to set the variable Storage to persistent in the /etc/systemd/journald.conf. [Journal] Storage=persistent Then restart the systemd-journald service. Another solution is simpler and it looks like it’s the recommended way of achieving this. All we have to do is to create a directory, /var/log/journal (with correct ownership and permission), and journald will automatically store the log messages there....