Proxmox, MikroTik, Docker, Linux, and the occasional rabbit hole. Written by a homelab gremlin. Start here.
Audit an Infrastructure Tutorial Before You Trust It
Use the GNTECH Infrastructure Series to see what a publishing check proves and how to record the remaining lab work.
Test What Happens to Your Logs During a Destination Outage
Use a temporary HTTP receiver and numbered events to measure delivery gaps, replay, and recovery time.
Did Your Log Shipper Keep Reading After Rotation?
Follow a short sequence of numbered log events across a renamed file, its replacement, and a collector restart.
Rotate NGINX Logs and Verify the Workers Reopened Them
Rotate a disposable access log, ask NGINX to reopen it, and trace a unique request into the new file.
Linux Has Free Disk Space but Cannot Create Files? Check Inodes
Check the filesystem’s file capacity alongside free bytes, locate directories with many entries, and recover through application-aware retention.
Deleted a Large Linux File but Disk Space Did Not Return?
Find the process still holding an unlinked file, distinguish filesystem usage from visible directory usage, and choose an application-aware recovery.
Keep Linux Logs Across Reboots Without Letting the Journal Fill the Disk
Keep the evidence needed for the next incident while setting an explicit storage budget for the systemd journal.
GNTECH Infrastructure Part 12: Validate the Boundaries and Hand Over Operations
Build an evidence-based acceptance matrix for network isolation, authenticated administration, restore readiness, and alert delivery.
GNTECH Infrastructure Part 11: Alert When Backup Evidence Goes Stale
Use a synthetic backup timestamp to test freshness and missing-data alerts before connecting real backup automation.
GNTECH Infrastructure Part 10: Restore a Proxmox VM Using Only the Off-Site Backup
Prove that a recovery node can restore and boot a VM from the off-site datastore using credentials and keys kept outside the primary site.