Orthevs Orthevs Fathom new horizons
Menu

Workshop wiki · German and English

Troubleshooting Ubuntu

This example is a controlled Ubuntu workshop lab. It is safe for local execution and does not change system configuration.

Content language · German and EnglishSize · 34.4 KBexamples/30-troubleshooting-ubuntu/README.md
Workshop examples as ZIP files
Learning progress in the web app

Mark chapters as read, view reading progress and check off practice modules after enabling the optional web app. Workshop progress is calculated from chapters across all document pages. Your choices stay on this device; there is no account or server sync. Installation is not required. Withdrawing your choice in Privacy settings deletes the progress.

Reading progress0%
0%
0 / 6 chapters read

Troubleshooting Ubuntu

Focus: Boot-, Paket-, Netzwerk-, Storage- und Servicefehler.

Purpose

This example is a controlled Ubuntu workshop lab. It is safe for local execution and does not change system configuration.

01 / 06

Documentation

02 / 06

Files

03 / 06

Run

bash
./run.sh

The script writes temporary evidence below work/. The directory is ignored by Git.

04 / 06

Review Questions

    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
    1. How does this example demonstrate Boot-, Paket-, Netzwerk-, Storage- und Servicefehler with safe Ubuntu operations?
05 / 06

Practice Appendix: Example Troubleshooting Ubuntu

This appendix is a working backlog for longer trainings, reviews and repetitions. Each task can be checked locally with sample configuration, shell commands and a Git repository.

A001. Boot-, Paket-, Netzwerk-, Storage- und Servicefehler

  • Task: check release and support status and connect the observation explicitly to Boot-, Paket-, Netzwerk-, Storage- und Servicefehler.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A002. Ubuntu

  • Task: evaluate package and repository risk and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A003. Operations

  • Task: explain service status and logs and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A004. Security

  • Task: document network assumption and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A005. Boot-, Paket-, Netzwerk-, Storage- und Servicefehler

  • Task: review user and sudo rule and connect the observation explicitly to Boot-, Paket-, Netzwerk-, Storage- und Servicefehler.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A006. Ubuntu

  • Task: evaluate firewall rule and exposure and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A007. Operations

  • Task: describe storage and backup path and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A008. Security

  • Task: record patch and reboot window and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A009. Boot-, Paket-, Netzwerk-, Storage- und Servicefehler

  • Task: mark security baseline and connect the observation explicitly to Boot-, Paket-, Netzwerk-, Storage- und Servicefehler.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A010. Ubuntu

  • Task: name monitoring or alert rule and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A011. Operations

  • Task: record rollback or recovery path and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A012. Security

  • Task: write team rule and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A013. Boot-, Paket-, Netzwerk-, Storage- und Servicefehler

  • Task: check release and support status and connect the observation explicitly to Boot-, Paket-, Netzwerk-, Storage- und Servicefehler.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A014. Ubuntu

  • Task: evaluate package and repository risk and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A015. Operations

  • Task: explain service status and logs and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A016. Security

  • Task: document network assumption and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A017. Boot-, Paket-, Netzwerk-, Storage- und Servicefehler

  • Task: review user and sudo rule and connect the observation explicitly to Boot-, Paket-, Netzwerk-, Storage- und Servicefehler.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A018. Ubuntu

  • Task: evaluate firewall rule and exposure and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A019. Operations

  • Task: describe storage and backup path and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A020. Security

  • Task: record patch and reboot window and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A021. Boot-, Paket-, Netzwerk-, Storage- und Servicefehler

  • Task: mark security baseline and connect the observation explicitly to Boot-, Paket-, Netzwerk-, Storage- und Servicefehler.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A022. Ubuntu

  • Task: name monitoring or alert rule and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A023. Operations

  • Task: record rollback or recovery path and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A024. Security

  • Task: write team rule and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A025. Boot-, Paket-, Netzwerk-, Storage- und Servicefehler

  • Task: check release and support status and connect the observation explicitly to Boot-, Paket-, Netzwerk-, Storage- und Servicefehler.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A026. Ubuntu

  • Task: evaluate package and repository risk and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A027. Operations

  • Task: explain service status and logs and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A028. Security

  • Task: document network assumption and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A029. Boot-, Paket-, Netzwerk-, Storage- und Servicefehler

  • Task: review user and sudo rule and connect the observation explicitly to Boot-, Paket-, Netzwerk-, Storage- und Servicefehler.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A030. Ubuntu

  • Task: evaluate firewall rule and exposure and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A031. Operations

  • Task: describe storage and backup path and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A032. Security

  • Task: record patch and reboot window and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A033. Boot-, Paket-, Netzwerk-, Storage- und Servicefehler

  • Task: mark security baseline and connect the observation explicitly to Boot-, Paket-, Netzwerk-, Storage- und Servicefehler.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A034. Ubuntu

  • Task: name monitoring or alert rule and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A035. Operations

  • Task: record rollback or recovery path and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A036. Security

  • Task: write team rule and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A037. Boot-, Paket-, Netzwerk-, Storage- und Servicefehler

  • Task: check release and support status and connect the observation explicitly to Boot-, Paket-, Netzwerk-, Storage- und Servicefehler.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A038. Ubuntu

  • Task: evaluate package and repository risk and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A039. Operations

  • Task: explain service status and logs and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A040. Security

  • Task: document network assumption and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A041. Boot-, Paket-, Netzwerk-, Storage- und Servicefehler

  • Task: review user and sudo rule and connect the observation explicitly to Boot-, Paket-, Netzwerk-, Storage- und Servicefehler.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A042. Ubuntu

  • Task: evaluate firewall rule and exposure and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A043. Operations

  • Task: describe storage and backup path and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A044. Security

  • Task: record patch and reboot window and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A045. Boot-, Paket-, Netzwerk-, Storage- und Servicefehler

  • Task: mark security baseline and connect the observation explicitly to Boot-, Paket-, Netzwerk-, Storage- und Servicefehler.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A046. Ubuntu

  • Task: name monitoring or alert rule and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A047. Operations

  • Task: record rollback or recovery path and connect the observation explicitly to Operations.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A048. Security

  • Task: write team rule and connect the observation explicitly to Security.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A049. Boot-, Paket-, Netzwerk-, Storage- und Servicefehler

  • Task: check release and support status and connect the observation explicitly to Boot-, Paket-, Netzwerk-, Storage- und Servicefehler.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.

A050. Ubuntu

  • Task: evaluate package and repository risk and connect the observation explicitly to Ubuntu.
  • Evidence: Record at least one Ubuntu-related command, expected output and a boundary of that evidence.
  • Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
  • Security question: Which accounts, services, packages, ports, logs or secrets would be critical?
  • Recovery: Describe whether rollback, restore, package downgrade, reboot, key rotation or manual correction would be needed.
06 / 06

UBU · Orthevs Academy

31 modules as one continuous learning path.

The sequence remains unchanged: from the lab skeleton through technical foundations and operating models to final troubleshooting. The technical directory names are deliberately preserved.

Practice modules

Orthevs as an app

Install Orthevs

The Orthevs web app can be installed on supported mobile devices and desktop browsers.

iPhone and iPad

Open Orthevs in Safari. Tap Share, then Add to Home Screen. Enable Open as Web App if offered, then tap Add.

Android

For the web app, open the browser menu and choose Install app or Add to Home screen. Confirm the installation.

Desktop browser

Open the browser menu or the install icon in the address bar, then choose Install app or Add to Dock.

Web app installation depends on your browser. If no install prompt appears, follow the browser steps shown above.