>_ IzzyLab

Topic breakdown

Services run in the background and have no screen to write to, so everything that happens to them goes into a log. When a service won't start, the first thing to do is read its log — the cause is almost always written there in plain words.

Where to find the log:

  • on a server with systemd — journalctl -u name: for example, journalctl -u nginx -n 50 shows nginx's last 50 entries;
  • many services also write to their own files in /var/log: /var/log/nginx/error.log, /var/log/postgresql/….

The sandbox has no systemd, so here logs are just files.

A log line usually looks like this: the date and time, the program name with its process number, the level and the message:

2026-03-02 09:15:01 backupd[812]: ERROR: cannot connect to storage: Connection refused

A log is appended at the end, so the fresh entries are at the bottom. You read it from the end: tail -n 20 file shows the last 20 lines, tail -f file follows new lines as they appear (Ctrl+C to quit).

What's checked

  1. The reportd service is running
  2. The cause is fixed and the service logged a successful launch

What it looks like