PDQ: Server Running 11 Years with No Reboots or Patches

Name: PDQ: Server Running 11 Years with No Reboots or Patches
Uploaded: 2026-08-11T09:08:45-04:00
Duration: 1 min 1 s
Description: Story originally posted on Reddit. #sysadmin #informationtechnology #pdq #microsoft #server Can't get enough PDQ? Subscribe and enable notifications! • Join us on Discord!: https://discord.gg/pdq • Our blog: https://www.pdq.com/blog/ • PDQ Connect fre...

PDQ

08/11/2026

0 (0%)

Report Like Favorite

TL;DR

A sysadmin discovered a Linux server with 4,018 days of uptime running an undocumented, unpatched Python 2.6 billing script that processed every company invoice for 11 years.
The original developer, who left in 2015, was tracked down but no longer remembered writing the 4,000-line uncommented script, leaving the team with no documentation or owner.
After six weeks of reverse engineering and 37 staged reboot tests, the team successfully rebooted the server — it came back up in 40 seconds with everything working perfectly.

Summary

This short-form video, sourced from a Reddit sysadmin story, recounts the discovery of a Linux server with 4,018 days of uninterrupted uptime — nearly 11 years — running a critical billing process that generated 1,200 invoices per month. The server ran CentOS 6.4 (end of life since 2020) on a 2012 kernel, executing a 4,000-line uncommented Python 2.6 script written by a developer who had left the company in 2015 and no longer remembered writing it. With no patches, no documentation, no owner, and no understanding of what the script actually did, the sysadmin faced an impossible dilemma: the server was an unacceptable security risk, but touching it risked breaking the company's entire invoicing operation. After six weeks of reverse engineering and 37 staged reboot tests, the team rebooted the server on a Saturday morning with the CEO present. It came back up in 40 seconds and worked perfectly — resolving over a decade of institutional fear in under a minute.

Chapters

0:00 - The Discovery
0:07 - The Technical Debt
0:26 - The Impossible Dilemma
0:40 - The Resolution

Key Quotes

0:05 "Nobody knew what would happen if it rebooted."
0:29 "I can't leave it. It's an unpatched security risk that's been sitting exposed since 2020."
0:34 "I can't touch it. It's 4,000 lines of uncommented Python 2 and nobody alive knows what it does."
0:53 "... 11 years of fear for 40 seconds."

FAQ

Why didn't anyone reboot or patch the server sooner?

Nobody knew what would happen if the server rebooted, and the script had no documentation or living owner. The risk of breaking the company's entire invoicing operation outweighed the perceived urgency — until the security exposure became undeniable.

How did the team finally feel confident enough to reboot it?

They spent six weeks reverse engineering the 4,000-line Python 2.6 script and tested the reboot 37 times in a staging environment before proceeding on a Saturday morning with the CEO aware and present.

Categories:

» Data Protection

Tags:

Show more Show less

TL;DR

Summary

Chapters

Key Quotes

FAQ

Bridging the SaaS Protection Gap: Preventing Data Loss and AI Missteps

The Automation Escalation: Discovering the AI-Driven Underground Revolution

Invisible Data: Understanding What You Can't Safeguard