My homelab PDU suddenly died! It’s dead, D-E-D, dead! There are few things worse than a server rack suddenly going completely silent…

The PDU has had an error since the power outage last summer — F11 means Power fail on auxiliary 1. Which is an odd error for a PDU with only one input. And; it wasn’t possible to clear or reset it it 😕

In my new home office — I never got around to set up an organized system for my tools. I’ve had some in tool cases, others in boxes — with lids. Not a good system…

I’ve found that if something is out of arm’s reach, I’m far less likely to put it back when I’m done with it. So I’ve accumulated tools; on the bench, and on the floor.

But — with my new tool trolley; I’m hoping to solve all these issues 😎

Comments. I’ve written about them before, two times — but here we go again.

Long story short; I’ve spent some time thinking about adding comments, and think it might be time to give it another try. Why now? As my traffic numbers have gone up, so has the emails from readers. I don’t get a lot — by any measure, but I do get some with very good insight about the post.

I’d like to share that knowledge, but reworking it into the article is not always so easy. With a comment section; they could be put on display 🙂

I’m using a Raspberry Pi to communicate with the power equipment in my homelab rack; the UPS, ATS and PDU. For the UPS, I’m using NUT (Network UPS Tools), and for the ATS and PDU; my own PowerWalker Python library.

In this post I’ll be going through how I’ve set up the NUT server to communicate with my PowerWalker VI 1500 RT HID UPS, and NUT clients running on all other physical machines in the rack.

In 2021 I wrote 69 blog posts, which is an all time record for me. In 2022 — I’m going to try and keep it going 🙂