Ftp Troubleshooting Scenarios

Packages advent2025 ai ansible apache aws cli bash c caddy clickhouse cron csv data processing disk volumes dns docker elk envoy etcd financial finops ftp git gitea golang gunicorn hack haproxy harbor hashicorp vault helm java jenkins json kubernetes linux-other mongodb mysql nginx node.js php podman postgres prometheus python rabbitmq redis sql sqlite ssh ssl supervisord systemd terraform traefik

realistic / interviews new pro business

Ftp

TFP scenarios

#	Name	Level	Time	Type
1	"Edinburgh": FTP catalog sync failure	Easy	10 m	Fix	"Edinburgh": FTP catalog sync failure Scenario: "Edinburgh": FTP catalog sync failure Level: Easy Type: Fix Access: Email Description: The warehouse API on this host should answer on `http://127.0.0.1:9178/` with a body containing `OK`. It depends on a catalog file pulled from the internal FTP mirror at `127.0.0.1`. The sync job at /home/admin/edinburgh-sync.sh is failing; edinburgh-sync is in a failed state and the API never comes up healthy. Fix the sync so the catalog is downloaded and the API works again. Test: /var/lib/edinburgh/catalog.txt exists with the correct inventory data, the service edinburgh-api is active, and `curl http://127.0.0.1:9178/` returns a response whose body contains `OK`. The "Check My Solution" button runs the script /home/admin/agent/check.sh, which you can see and execute. Time to Solve: 10 minutes.

Ftp Troubleshooting Scenarios

Ftp

TFP scenarios

"Edinburgh": FTP catalog sync failure

Send Us Feedback or Get Notified