---
title: "Discussion on \"[Day 10] journalctl — Finding Problems Through Logs\" | Hashnode"
description: "Discussion on \"[Day 10] journalctl — Finding Problems Through Logs\". Day 9 covered systemd managing services. Unit files, service registration, auto-restart on failure.\nBut when something breaks on a server running 50 services, you can't run systemctl status on each on"
url: "https://hashnode.com/posts/day-10-journalctl-finding-problems-through-logs/69fc3e203d9a9c101979d539"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [\[Day 10\] journalctl — Finding Problems Through Logs](https://frogsdevlog.hashnode.dev/day-10-journalctl-finding-problems-through-logs?utm_source=hashnode&utm_medium=feed)

Day 9 covered systemd managing services. Unit files, service registration, auto-restart on failure. But when something breaks on a server running 50 services, you can't run systemctl status on each on

May 7 · 5 min read · frogsdevlog.hashnode.dev  
Read the article

## Written by

[Seung Joo Ahn](https://hashnode.com/@seungjoo)

@seungjoo · Seoul, South Korea

  
[View profile](https://hashnode.com/@seungjoo)

Backend Engineer

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
