RH134 - ch14s02

Bookmark this page

Lab: Fixing Boot Issues and Maintaining Servers

In this review, you will troubleshoot and repair boot problems and update the system default target. You will also schedule tasks to run on a repeating schedule as a normal user.

Outcomes

You should be able to:

Diagnose issues and recover the system from emergency mode.
Change the default target from graphical.target to multi-user.target.
Schedule recurring jobs to run as a normal user.

Copy any files or work you wish to keep to other systems before resetting. Reset the workstation, servera, and serverb systems now.

On workstation, run lab rhcsa-compreview1 start to start the comprehensive review. This script creates the necessary files to set up the environment correctly.

[student@workstation ~]$ lab rhcsa-compreview1 start

Instructions

Perform the following tasks on serverb to complete the comprehensive review:

On workstation, run the lab rhcsa-compreview1 break1 command. This break script causes the boot process to fail on serverb. It also sets a longer timeout on the GRUB2 menu to help interrupt the boot process, and reboots serverb.
Troubleshoot the possible cause and repair the boot failure. The fix must ensure that serverb reboots without intervention. Use redhat as the password of the superuser, when required.
On workstation, run the lab rhcsa-compreview1 break2 command. This break script causes the default target to switch from the multi-user target to the graphical target on serverb. It also sets a longer timeout for the GRUB2 menu to help interrupt the boot process, and reboots serverb.
On serverb, fix the default target to use the multi-user target. The default target settings must persist after reboot without manual intervention.
Use the sudo command, as the student user with student as the password, for performing privileged commands.
Schedule a recurring job as the student user that executes the /home/student/backup-home.sh script on an hourly basis between 7 p.m. and 9 p.m. on all days except Saturday and Sunday.
Download the backup script from http://materials.example.com/labs/backup-home.sh. The backup-home.sh backup script backs up the /home/student directory from serverb to servera in the /home/student/serverb-backup directory. Use the backup-home.sh script to schedule the recurring job as the student user on serverb.
Reboot the system and wait for the boot to complete before grading.

On workstation, run the lab rhcsa-compreview1 break1 command.
[student@workstation ~]$ lab rhcsa-compreview1 break1
After serverb boots up, access the console and notice that the boot process stopped early. Take a minute to speculate about a possible cause for this behavior.
Locate the icon for the serverb console, as appropriate for your classroom environment. Open the console.
Looking at the error, it appears that at least parts of the system are still functioning.
Press Ctrl+Alt+Del to reboot serverb.
When the boot-loader menu appears, press any key except Enter to interrupt the countdown.
Edit the default boot-loader entry, in memory, to log in to emergency mode.
Press e to edit the current entry.
Use the cursor keys to navigate to the line that starts with linux. Append systemd.unit=emergency.target to the end of the line.
Press Ctrl+x to boot using the modified configuration.
Log in to emergency mode. The root password is redhat.
Give root password for maintenance (or press Control-D to continue): redhat [root@serverb ~]#
Remount the / file system read/write. Use the mount -a command to attempt to mount all the other file systems.
Remount the / file system read/write to edit the file system.
[root@serverb ~]# mount -o remount,rw /
Use the mount -a command to attempt to mount all the other file systems. Notice that one of the file systems cannot be mounted.
[root@serverb ~]# mount -a mount: /FakeMount: can't find UUID=fake.
Edit /etc/fstab to fix the issue. Remove or comment out the incorrect line.
[root@serverb ~]# vim /etc/fstab ...output omitted... #UUID=fake /FakeMount xfs defaults 0 0
Update systemd for the system to register the new /etc/fstab configuration.
[root@serverb ~]# systemctl daemon-reload [ 206.828912] systemd[1]: Reloading.
Verify that /etc/fstab is now correct by attempting to mount all entries.
[root@serverb ~]# mount -a
Reboot serverb and wait for the boot to complete. The system should now boot normally.
[root@serverb ~]# systemctl reboot
On workstation, run the lab rhcsa-compreview1 break2 command.
Wait for the reboot to complete before proceeding.
[student@workstation ~]$ lab rhcsa-compreview1 break2

On serverb, switch to the multi-user target. Set the default target to multi-user. Use the sudo command to run any required administrative command and if prompted, use student as the password.

From workstation, open an SSH session to serverb as the student user.

[student@workstation ~]$ ssh student@serverb
...output omitted...
[student@serverb ~]$

As the student user on serverb, determine the default target.

[student@serverb ~]$ systemctl get-default
graphical.target

Switch to the multi-user target. Use the sudo command and if prompted, use student as the password.
```
[student@serverb ~]$ sudo systemctl isolate multi-user.target
[sudo] password for student: student
```

Set serverb to use the multi-user target as the default target.

[student@serverb ~]$ sudo systemctl set-default multi-user.target
Removed /etc/systemd/system/default.target.
Created symlink /etc/systemd/system/default.target -> /usr/lib/systemd/system/multi-user.target.

Reboot serverb to verify that the multi-user target is set as the default target.

[student@serverb ~]$ sudo systemctl reboot
Connection to serverb closed by remote host.
Connection to serverb closed.
[student@workstation ~]$

After reboot, open an SSH session to serverb as the student user. Verify that the multi-user target is set as the default target.
```
[student@workstation ~]$ ssh student@serverb
...output omitted...
[student@serverb ~]$ systemctl get-default
multi-user.target
```

Schedule a recurring job as the student user that executes the /home/student/backup-home.sh script on an hourly basis between 7 p.m. and 9 p.m. on all days except Saturday and Sunday.
Use the backup-home.sh script to schedule the recurring job. Download the backup script from http://materials.example.com/labs/backup-home.sh.
On serverb, download the backup script from http://materials.example.com/labs/backup-home.sh. Use chmod to make the backup script executable.
[student@serverb ~]$ wget http://materials.example.com/labs/backup-home.sh ...output omitted... [student@serverb ~]$ chmod +x backup-home.sh
Use the crontab -e command to open the crontab file using the default text editor.
[student@serverb ~]$ crontab -e
Edit the file to add the following line:
0 19-21 * * Mon-Fri /home/student/backup-home.sh
Save the changes and exit the editor.
Use the crontab -l command to list the scheduled recurring jobs.
[student@serverb ~]$ crontab -l 0 19-21 * * Mon-Fri /home/student/backup-home.sh

Reboot serverb and wait for the boot to complete before grading.

[student@serverb ~]$ sudo systemctl reboot
[sudo] password for student: student
Connection to serverb closed by remote host.
Connection to serverb closed.
[student@workstation ~]$

Evaluation

On workstation, run the lab rhcsa-compreview1 grade script to confirm success on this exercise. Correct any reported failures and rerun the script until successful.

[student@workstation ~]$ lab rhcsa-compreview1 grade

Finish

On workstation, run lab rhcsa-compreview1 finish to complete this exercise. This script deletes the files and resources created throughout the exercise and ensures that the environment is clean.

[student@workstation ~]$ lab rhcsa-compreview1 finish

Save any files or work you want to keep to other systems, and then reset workstation, servera, and serverb before the next exercise.

This concludes the comprehensive review.

Discuss Red Hat System Administration II

Go to community

Is It possible to reset root password when the system is on multi-user.target?

jennifer1987

27 lip 2023

Hi thereWell, i have a question, Is It possible to reset root password when the system is on multi-user.target? I was not be able to found a foro o some information related with this and another question that I have, If the grub menu dont show up, is it posible to reset the root password?

991

Red Hat System Administration II (RH134)

Haley_Ruccio

21 lip 2023

Build the skills to perform the key tasks needed to become a full-time Linux administratorRed Hat System Administration II (RH134) is the second part of the RHCSA training track for IT professionals who have already attended Red Hat System Administration I. The course goes deeper into core Linux system administration skills in storage configuration and management, installation and deployment of Red Hat Enterprise Linux, management of security features such as SELinux, control of recurring system tasks, management of the boot process and troubleshooting, basic system tuning, and command-line automation and productivity. This course assumes that students have attended Red Hat System Administration I (RH124).Experienced Linux administrators who seek rapid preparation for the RHCSA certification should instead start with RHCSA Rapid Track (RH199).This course is based on Red Hat Enterprise Linux 9.0.Course summaryInstall Red Hat Enterprise Linux using scalable methodsAccess security files, file systems, and networksExecute shell scripting and automation techniquesManage storage devices, logical volumes, and file systemsManage security and system accessControl the boot process and system servicesRun containersAudience for this courseThis course is geared toward Windows system administrators, network administrators, and other system administrators who are interested in supplementing current skills or backstopping other team members, in addition to Linux system administrators who are responsible for these tasks:Configuring, installing, upgrading, and maintaining Linux systems using established standards and proceduresProviding operational supportManaging systems for monitoring system performance and availabilityWriting and deploying scripts for task automation and system administrationRecommended trainingSuccessful completion of Red Hat System Administration I (RH124) is recommended.Experienced Linux administrators seeking to accelerate their path toward becoming a Red Hat Certified System Administrator should start with the RHCSA Rapid Track course (RH199).Take our free assessment to gauge whether this offering is the best fit for your skills.Technology considerationsThere are no special technology requirements.This course is not designed for bring your own device (BYOD).Internet access is not required, but is recommended to allow students to research and access Red Hat online resources.

Welcome to the Red Hat System Administration II (RH134) group in the Red Hat Learning Community!

Deanna

18 lip 2023

We are excited to launch a space dedicated to the Red Hat Training course Red Hat System Administration II! To gain the most value from this group - click the "Join Group" button in the upper right hand corner.We encourage group members to collaborate in this group to discuss topics, ask questions, share best practices and tips, provide course feedback, and share their accomplishments as it relates to RH134.Read more about Red Hat System Administration II here.

417

Revision: rh134-8.2-f0a9756