Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Troubleshooting

Linux journal troubleshooting: use systemd logs to trace a failure

Published August 2026 · 2 min read · Updated 2026-09-05

The systemd journal is most useful when you approach it with a service name and time window. Dumping the entire journal after an incident often buries the first relevant error under retries, follow-on failures, and unrelated background noise.

Anchor the investigation to time and unit

Record when the symptom began, then query the affected service unit around that window. Include a few minutes before the visible failure so dependency errors, restarts, resource pressure, or configuration reloads are not missed.

Use boot selection when a problem appeared after reboot; logs from the previous boot may contain the shutdown or crash clue.

Read the first failure before the cascade

A database becoming unavailable can generate hundreds of application errors. The earliest dependency failure is often more actionable than the last request that failed.

Note exit status, signal, restart count, and any referenced file, port, user, permission, or environment variable.

Pair journal output with unit configuration

Inspect the effective unit, drop-ins, environment files, dependencies, restart policy, working directory, and service user. A process that works from a shell can fail under systemd because its environment and permissions are intentionally different.

Use systemd-analyze verify or application-specific config tests where available before restarting repeatedly.

Preserve useful logs

Set journal retention appropriate to available disk and incident needs. Forward or back up critical logs when local loss would erase the only evidence after a filesystem or server failure.

  • Filter by unit and time.
  • Read the earliest dependency error.
  • Inspect the effective unit environment.
  • Retain enough history for incident review.

Next step

Use journalctl by unit, boot and time range, correlate service errors with system events, and preserve the evidence needed to diagnose recurring failures.

Explore DotMoose VPS hosting

Keep reading

Related guides.

HTTP 500, 502 and 503 errors explained for website owners

Learn what HTTP 500, 502 and 503 errors usually indicate, which layer to investigate, what evidence to collect, and when restarting a service is not the real fix.

Read the guide

Linux file permissions: ownership, modes, groups and ACLs explained

Understand Unix ownership and rwx modes, then use groups and ACLs where needed so services can access files without opening them to every user.

Read the guide

Moving a DreamHost VPS to Canadian hosting

Inventory the server, copy it safely, test it, and cut DNS over with a rollback plan.

Read the guide

More vps & linux guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move