Linux Security

Debugging Local Networks with resolvectl and ss

When I’m dealing with local network issues, I always reach for two essential tools: resolvectl and ss. These utilities provide valuable insights into DNS resolution and network socket connections, making it easier to identify and troubleshoot common network problems.

resolvectl for DNS Troubleshooting

I’ve seen this go wrong when DNS resolution fails, and resolvectl is a lifesaver. This command-line utility lets you query and control the systemd-resolved service, which handles DNS resolution on many modern Linux distributions. With resolvectl, you can perform DNS lookups, check the status of DNS servers, and even override default DNS settings for troubleshooting purposes.

Introduction to SSH Connection Issues

I’ve seen my fair share of SSH connection issues over the years, especially when dealing with new servers or changes in network configurations. Secure Shell (SSH) is a fundamental tool for remote access and management in Linux, but issues with unknown hosts and missing host keys can be a real headache. Understanding how to troubleshoot and resolve these issues is crucial for efficient system administration and security.

Introduction to Systemd Service Restart Policies

Systemd is the backbone of most modern Linux distributions, and one of its key features is managing service restart policies. I’ve seen this go wrong when a service fails and takes down the entire system with it. In this article, we’ll dive into the world of systemd service restart policies and explore how to configure them to prevent cascading failures.

Understanding Systemd Service Restart Policies

Systemd provides several restart policies that can be applied to services. The real trick is understanding when to use each one:

Introduction to Log Noise

I’ve seen this go wrong when dealing with system logs - the sheer amount of unnecessary or redundant log messages can make it difficult to identify real issues. As a Linux administrator, managing log noise is essential for efficient system maintenance and troubleshooting. In this article, I’ll share how to tame log noise using jq and systemd journal filters.

Understanding systemd Journal

Systemd journal is a powerful centralized logging system that collects and stores log messages from various system components. It provides a robust and flexible way to manage logs, including filtering, prioritization, and storage. The real trick is to leverage the journalctl command to work with systemd journal.

Introduction to Journalctl

I’ve been working with Linux systems for years, and one tool that’s become essential to my workflow is journalctl. As of 2026, most modern Linux distributions have adopted systemd as their default init system, making journalctl a must-know tool for system administrators and users alike. In this article, I’ll share how to use journalctl to filter out unnecessary log noise and focus on meaningful errors.

Understanding Journalctl Basics

Before diving into advanced filtering techniques, let’s cover the basics of journalctl. The command journalctl can be used to view system logs, and by default, it will show you the most recent log entries. You can use the -n option to specify the number of log entries to display, for example, journalctl -n 10 will show you the last 10 log entries. Don’t bother with sudo unless you need to access system logs - journalctl will automatically use your current user’s permissions.

Introduction to rsync and snapshotting

Dealing with large ext4 filesystems can make backups a real challenge. I’ve seen this go wrong when using traditional backup methods like tar or cp - they can be slow and resource-intensive. That’s where rsync and snapshotting come in - they can simplify the backup process and reduce the strain on your system.

What is rsync?

rsync is a fast and versatile command-line utility that synchronizes files and directories across different locations. The real trick is that it uses a delta-transfer algorithm, which only transfers the differences between the source and destination, making it an efficient tool for backups. You can use rsync to synchronize files locally or over a network.

Introduction to Efficient Backups

I’ve seen this go wrong when dealing with large Ext4 volumes: creating inefficient backups can lead to data integrity issues and disrupt business continuity. One approach I’ve found useful is combining rsync with snapshot capabilities. rsync is a powerful tool for synchronizing files and directories across different locations, while snapshots provide a point-in-time view of the file system, allowing for consistent backups even on active systems.

Introduction to Debugging Connectivity Issues

I’ve seen this go wrong when dealing with connectivity issues on Linux systems: not knowing where to start. Two essential tools can save you a lot of time - resolvectl and ss. These tools help in identifying and troubleshooting DNS and routing problems. Let’s dive into a step-by-step guide on how to use them, focusing on practical examples and security considerations where relevant.

Understanding resolvectl

resolvectl is a command-line utility provided by systemd for querying and configuring the DNS resolver. It’s incredibly useful for controlling the DNS resolver, including setting DNS servers, querying the DNS cache, and configuring DNS over TLS (DoT) or DNS over HTTPS (DoH). To get started with resolvectl, you can use the following command to status the current DNS configuration:

Introduction to Efficient Disk Backups

I’ve seen many Linux users struggle with backups, whether they’re sysadmins, self-hosters, or homelab enthusiasts. One approach that’s worked well for me is combining rsync with snapshots, particularly when using the btrfs filesystem. In this article, I’ll share how to leverage rsync and btrfs snapshots for robust and space-efficient backups. Don’t bother with other filesystems if you’re serious about snapshots - btrfs is the way to go.

Introduction to Disk Full Errors

I’ve seen disk full errors bring Linux systems to a grinding halt, and they can be a real challenge to troubleshoot. One approach that’s worked for me is using btrfs snapshots and the du command to identify the cause of these errors. In this article, we’ll explore how to use these tools to diagnose and resolve disk full issues.

Understanding btrfs Snapshots

btrfs is a powerful file system that offers some great features, including snapshotting, which lets you create a read-only copy of a subvolume at a given point in time. This is super useful for troubleshooting disk full errors, as it allows you to examine the file system without modifying its current state. To create a btrfs snapshot, you can use the following command: