Lab catalog

found 7 of 777 of 77loading…

Sort

hard

Loading…

Site unreachable from another host The site on node2 answers itself but does not open from node1. There may be several causes — find them all and keep nginx healthy. Networking ~40 min not started
Networking ~40 min not started
A site and its database on two machines The orders site moved to node1 while its database stayed on node2, and the site stopped opening. Find every cause and leave the database open to the site only. ~50 min not started
— ~50 min not started
Cleaning up exports on a schedule The cleanup script run by cron deletes the wrong files, gets in the way of the backup and stays silent. Fix it and move it to a systemd timer with a log and a lock. ~40 min not started
— ~40 min not started
A compose stack after the move The orders service was moved from hand-made docker run commands to compose, and the stack won't come up. Find every cause and bring the service back with its existing orders. ~40 min not started
— ~40 min not started
A slow server: triaging three complaints The catalog site answers slowly, the server keeps running short of available memory, and under a rush of visitors requests fail with an error. Find the culprit behind each complaint, remove the causes so that they do not come back after a reboot, and write the triage down in a report. ~45 min not started
— ~45 min not started
A server ready for publication A new ticket server is about to go public, but the security review sent it back. Leave key-only login without root, close the extra ports, turn on brute-force protection and confine the service — so that all of it holds after a reboot. ~60 min not started
— ~60 min not started
A site on node2, by a playbook from node1 A colleague's playbook is meant to bring up a status page on node2 from node1, yet it finishes without errors and there is no page. Fix the project so that the playbook configures node2 and a second run changes nothing. ~50 min not started
— ~50 min not started