centos

The awscli package is available from the EPEL repository, which is not enabled by default on RockyLinux. Enable the EPEL repo by installing epel-release pacakge. $ sudo dnf install epel-release Once the EPEL repo is successfully enabled, we can install awscli package. $ sudo dnf install awscli Enable and verify that the awscli is installed on the system. $ aws --version aws-cli/1.18.156 Python/3.6.8 Linux/4.18.0-425.10.1.el8_7.x86_64 botocore/1.18.15 As a bonus, here is how to configure the AWS credential....

I just setup a new server with a minimal installation of AlmaLinux 8. AlmaLinux is a variant of free Red Hat Enterprise Linux 8. It’s like a CentOS 8, but will have a full support until the end of RHEL 8 life cycle. This server is to serve as a new proxy for all VMs inside my home lab. I want to use tinyproxy which is need to be compiled from source as the RPM package is not available as of the time writing....

This is a quick note to list failed services on systemd system. [root@zilla ~]# systemctl status ● zilla State: degraded Jobs: 0 queued Failed: 1 units Since: Fri 2020-09-04 02:20:47 AEST; 3 months 11 days ago CGroup: / ├─1 /usr/lib/systemd/systemd --system --deserialize 22 └─system.slice ├─httpd.service │ ├─21860 /usr/sbin/httpd -DFOREGROUND │ ├─21861 /usr/sbin/httpd -DFOREGROUND │ ├─21862 /usr/sbin/httpd -DFOREGROUND │ ├─21863 /usr/sbin/httpd -DFOREGROUND │ ├─21864 /usr/sbin/httpd -DFOREGROUND │ └─21865 /usr/sbin/httpd -DFOREGROUND ... [root@zilla ~]# systemctl list-units --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● ipmi....

I need to have an iSCSI storage to be used by my oVirt lab. The last time I had to create an iSCSI target was during the preparation of the RHCE 7 exam. Therefore, I think this is an opportunity to practice doing this again. First, install the required package. Then enable the target service, otherwise the target won’t work on the next reboot. [root@utility ~]# dnf install targetcli -y [root@utility ~]# systemctl enable target Run the targetcli command to create an iSCSI target/storage using the storage block (/dev/mapper/data_iscsi LVM volume)....

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....