Red Hat Certified System Administrator (RHCSA 9) Practice.

You've forgotten the root password for node1. Securely reset the root password to regain access to the system. Remember, resetting a root password should only be done as a last resort and strong password practices should be followed after regaining access.

• Configure a NetworkManager connection profile named "myprofile1" on node1 for the ens160 device with the following static settings:

• Static IPv4 Address: 192.168.1.2

• Subnet Mask: 255.255.255.0

• IPv4 Default Gateway: 192.168.1.1

• IPv4 DNS Servers: 192.168.1.209

• DNS Search Domain: 3etechsolution.com

• Configure node1 and node2 to use the following local repositories:

• http://rhel-repos.3etechsolution.com:/rhel-9-for-x86_64-appstream-rpms.

• gpgkey=http://rhel-repos.3etechsolution.com:/RPM-GPG-KEY-redhat-release

• http://rhel-repos.3etechsolution.com:/rhel-9-for-x86_64-baseos-rpms.

• gpgkey=http://rhel-repos.3etechsolution.com:/RPM-GPG-KEY-redhat-release

• Configure node1 and node2 to automatically mount the home directories of users tom and sam from nfs-server.3etechsolution.com using NFS. The home directories on nfs-server are located at "/rhome/tom" and "/rhome/sam," with user IDs 1010 and 1020, respectively. The mount should be established in the local "/users" directory on node1 and node2, ensuring read and write permissions, efficient resource usage, and seamless user experience.

• On node1, as user ewi, create a persistent, rootless mariadb server container using the "registry.redhat.io/rhel9/mariadb-1011" image, ensuring it adheres to best practices for security and efficiency. Apply the following specifications:

• Container name: "mydb"

• Registry credentials: Your red hat login.

• Mount a persistent storage volume from "~/mydb/" to "/var/lib/mysql/" within the container

• Map host port 3306 to container port 3306

• Set environment variables: MYSQL_USER=mysql, MYSQL_PASSWORD=password@123, MYSQL_DATABASE=mydb,

• Manage the container using systemd for persistence and automatic startup.

• On node1, use /dev/sda to do the following:

• 1. Create a 2GiB volume group named “myvg”with physical extent size of 16MiB.

• 2. Create a 500MiB logical volume named “mylv” inside the “myvg” volume group.

• 3. The “mylv” logical volume should be formatted with the ext4 filesystem and mounted persistently on the "/mylv" directory.

• Create a 5GB partition from /dev/sda and use it to extend the root filesystem ensuring file integrity.

• On node1, create a 2GiB swap partition using /dev/sda that automatically activates at boot.

• Create the following users and groups on node1, configure their permissions for specific directories, and ensure appropriate file ownership for newly created files.All user passwords: school1
  

• Users:

• ami and biko (members of the "admins" group)

• carlos and david (members of the "developers" group)

• Directories:

• /admins (accessible only to owner and admins group members, owned by biko)

• /developers (accessible only to developers group members, owned by carlos)

• File Ownership:

• New files in /developers or /admins should be owned by the respective group owner.

• Only file creators should be allowed to delete their files.
  

• Node1 runs the Apache HTTP Server and needs to access files in the directory /var/my_web. However, SELinux is currently preventing this access. Also, the server is configured to run on non-default port 88/tcp.

• Task: Modify the SELinux policy on node1 to grant Apache HTTP Server access to files in /var/my_web securely, and to allow web traffic through tcp port 88.

• Additional Considerations:

• This modification should persist after a server reboot.

• Minimize the impact on other applications or directories.

• On node2, schedule a cron job to append the message "Ended on $(date) by $LOGNAME" to the "/var/log/messages" file with root privileges everyday at 5am. Specify a tag "my_script" for the log message.

• Configure node1 to automatically boot into the multi-user.target, ensuring a non-graphical, multi-user environment for command-line administration.

• On node1, allow full permissions for biko on directory /engineers/projects.

• Note that /engineers/projects is owned by root user and engineers group. Biko is not a member of engineers group.

• On node1, create a compressed archive of the "/home" directory using tar and bzip2. Store the archive under "/mnt" with the filename "local-home.tar.bz2". Verify the contents of the archive.