A comprehensive guide to diagnosing and resolving server disk space alerts, covering root cause analysis, evidence-based cleanup procedures, automated safety-guarded scripts, and monitoring strategies for Linux systems with systemd and Docker.
This article walks through essential Nginx command‑line tools—including version checks, configuration testing, graceful and fast shutdowns, reloads, log reopening, and specifying custom configuration files—showing concrete examples and explaining when each command should be used in development and production environments.
This guide walks through locating disk‑space hogs on a Linux server, safely cleaning APT caches, logs, and Docker artifacts, configuring Docker log limits, migrating Docker data to a separate disk, and verifying that root‑partition usage drops from 84% to around 60%, while emphasizing verification before deletion and long‑term growth prevention.
This guide explains how to use systemd's journalctl for reading, configuring persistent storage, limiting log size, setting up automatic cleanup, and verifying integrity of Linux logs, providing practical commands and configuration snippets for reliable log management.
This guide explains why removing large log files on Linux often leaves disk usage unchanged, reveals the hidden “ghost” processes that keep deleted files open, and provides step‑by‑step commands to identify, release, and prevent such space leaks.
This guide explains how Nginx’s access_log and error_log work, details the log_format directive for customizing access logs, shows how to configure log paths, formats, buffering, compression, and conditional logging, and provides a Bash script with a cron job to automatically rotate daily log files.
This article examines common log‑management anti‑patterns—such as copy‑truncate rotation, NAS storage, multi‑process writes, file‑hole creation, frequent overwrites, and Vim edits—explains why they cause data loss or duplicate collection, and offers practical best‑practice recommendations for reliable log handling in cloud‑native environments.
Effective log management is crucial for cloud‑native observability, yet common practices like copy‑truncate rotation, NAS storage, multi‑process writes, file‑hole creation, frequent overwrites, and vim edits can cause data loss or duplicate collection; adopting create‑mode rotation, local disks, append‑only writes, and proper tools mitigates these risks.
This guide explains why default Nginx logging can fill disks, then walks through disabling logging, clearing old files, re‑enabling logging, using a shell script to rotate logs by date, and scheduling the script with cron to keep server storage healthy.
This guide walks through why nginx logs need daily rotation, demonstrates manual log splitting, provides a complete shell script for automated daily log rotation, explains logrotate configuration, and shows how to test and schedule the process with cron, ensuring clean and manageable log files.
This guide explains how to configure Nginx access and error logs, customize log formats with log_format, manage log files using access_log and error_log directives, and automate daily log rotation with a Bash script and cron job.
This article presents two Bash scripts that automate MySQL multi‑database backups with per‑table dumps and rotate Nginx access logs daily by moving them into month‑based directories and signaling Nginx to reopen its logs.
This guide explains why nginx logs need regular rotation, shows how to manually split logs using a shell script that backs up, renames, and signals nginx to reopen log files, and demonstrates configuring and testing the logrotate utility for automated daily log rotation and compression.
This guide explains why nginx logs need regular rotation, demonstrates manual log backup and rotation using shell commands, provides a complete Bash script for daily log splitting, and shows how to configure and use the logrotate tool for automated, compressed log management.
When adding a ZooKeeper observer to a Codis cache cluster, the election port (3888) was unreachable because the QuorumCnxManager listener thread vanished, prompting telnet and log checks, and leading to a successful recovery by rolling upgrade to ZooKeeper 3.4.13, rebuilding the data directory, performing a rolling restart, and decommissioning the temporary node, thereby restoring full cluster quorum and normal Codis‑Proxy operation.
This article explains how to improve PHP logging performance by controlling log levels, batching writes, using asynchronous processes, and implementing log rotation, providing clear code examples for each technique in real-world PHP applications.
This guide explains how to use Python's config module to load log levels, set output paths per environment, dynamically update logging settings, control log formats, and configure file backup, providing five practical code examples for robust API automation logging.
This article explains how to configure Nginx to split access logs by day using the $time_iso8601 variable, align log timestamps with the local timezone via Docker‑Compose or Dockerfile settings, and introduces the GoAccess tool for visual log analysis.
This guide explains why rotating Nginx access logs is essential for maintainability and demonstrates a straightforward shell script plus a cron job to split logs by day, ensuring smooth log management and easy analysis.
This guide explains how logrotate automates log rotation, detailing its configuration files, common directives such as rotate, daily, size, compress, postrotate, and sharedscripts, and provides practical examples for managing large log files efficiently on Linux servers.
This guide explains how logrotate automates log rotation, configures rotation intervals, size limits, compression, and post‑rotation scripts, helping you manage growing log files, conserve disk space, and maintain system performance on Linux servers.
This article explains how to troubleshoot fragmented log files caused by the Supervisor process manager on Linux, covering configuration details, log‑rotation constraints, diagnostic commands, and the eventual resolution by restarting the supervisord service.
The article details a MongoDB 3.4 sharded cluster incident where a sudden connection storm overwhelmed the primary, leading to replication lag, automatic failover, and how monitoring, log analysis with mtools, and a custom log‑rotation script were used to diagnose and resolve the issue.
This article investigates MySQL binlog numbering, discovers that the maximum sequence number is 2^31‑1 (2147483647), shows through three experiments how MySQL behaves when approaching or hitting this limit, and explains the resulting warnings and server shutdown.
A MongoDB shard node’s logs unexpectedly turned into PCX image files due to improper log rotation using echo, causing CPU spikes and slow‑query analysis failures; the investigation reproduces the issue, explains the header corruption, and presents a SIGUSR1‑based solution to restore proper ASCII logs and retrieve the needed time‑range data.
This article presents a detailed overview of Nginx performance optimizations, module types, load‑balancing algorithms, log rotation scripting, custom error page setup, smooth restart procedures, configuration checks, and a comparative analysis with Apache and LVS for backend server administrators.
This guide explains how to automatically rotate Nginx logs each day by renaming the current log file at midnight, creating dated backup directories, and signaling the Nginx master process with USR1 using a simple Bash script scheduled via a cron job.
The article explains how the Linux top command reveals filesystem cache usage, why large log files can waste cache memory, and proposes hourly log rotation with compression, using lsof to identify cached files and tools like zless to view compressed logs.
This article explains how to use the Linux tail command to monitor log files in real time, filter errors, and reliably continue following logs after rotation by using the -F option, providing practical guidance for system administrators and developers.
