The Missing Configuration
The application says its configuration is missing. But is the file actually gone?
Your goal is not simply to make a missing pathname exist. Your goal is to learn how an administrator enters an unfamiliar Linux machine, understands where things normally belong, gathers evidence before changing anything, identifies the authoritative configuration, repairs the expected path safely, and proves that the application works again.
In this investigation, you'll learn how Linux organizes files, how programs locate configuration, how to search for evidence, and how to restore an expected path without creating a second source of truth.
Before fixing anything: understand the machine
Every Linux machine organizes its files the same basic way: one tree, starting at /. Before you can find anything, you need a rough map of what normally lives where.
Command reference
pwd — prints your current directory ("print working directory").
ls / — lists everything directly under filesystem root.
ls -la /etc — lists the contents of /etc, including hidden entries.
Common mistakes
Typing /root when you meant /. — They look related but are completely different locations — one is the whole tree, the other is one user's home.
Assuming a directory's name fully describes its contents. — /etc is a strong convention, not a law. Software can (and does) store configuration elsewhere.
/ is the root of the entire filesystem. /root is the home directory that belongs to the user literally named "root" — the machine's superuser account. They share four letters and nothing else. /root is just another directory hanging off /, the same way /home/alex is.
inventory-api cannot find its machine-wide configuration.
Which directory would you investigate first?