Linux Advanced About 40 min +320 XP

Forgeline Returns 500 on Every Page

forgeline.dev answers 500 on the web UI and API, and its readiness probe fails from every region.

Briefing

forgeline.dev started answering 500 on every page at 09:07, about twenty-five minutes after the database team began rebuilding the standby that fell behind during this morning's spam wave.

The main PostgreSQL cluster on pg-core-01 will not start, writes are frozen at the load balancer, and git pushes over SSH still work only.

Dev wants to reuse the standby's half-finished copy.

Inspired by a real outage: Postmortem of database outage of January 31 (GitLab, 2017). Names and details are fictionalized.

The fix is yours to find: hints, the recovery checks and the debrief unlock inside the incident.

How it plays

  1. 01

    Get paged

    The alert fires and the clock starts. Read the page and the briefing.

  2. 02

    Investigate

    Work in a simulated shell with realistic output: logs, configs, services.

  3. 03

    Fix it

    Change the system the way you would in production. Hints are there if you get stuck.

  4. 04

    Prove it

    Automated checks verify the recovery, then the debrief explains what happened.

Your pager is ready.

Free, instant, and it works on your phone. No signup: start as a guest and save your progress later.