My main day-to-day machine is a 2018 Mac Mini. Over the last year, and especially the last 6 months, it’s been a struggle to keep adequate space free. About two weeks ago, I’d had enough, and went on a deep dive to figure out what was wrong. In my last post, I described the journey I took to identify the likely problem.
Simply identifying a “likely” culprit wasn’t enough, though. I needed to take a methodical approach to testing different settings and recording the results.
My everyday desktop is a 2018 Mac Mini. Last summer, I started noticing that some apps would crash overnight, mostly Ivory (my Mastodon client).
I assumed it was a memory thing. My disk space wasn’t great, but I had like 5 gigabytes or so free on the 256 gig drive, and wasn’t seeing any “your disk is full” errors. I wasn’t getting crazy “Your system is out of memory!” errors, either, but memory pressure seemed like a good explanation. I tried a few lazy tricks to get some data, try to collect logs, etc., but got nowhere.
Nine years ago, I migrated all my local house storage from a massive Dell with Debian and software RAID, onto a tiny little Synology NAS. Well, not exactly tiny, but probably 1/3 of the volume of the Dell. It serves as a file server, Time Machine target, and destination for various rsync and other low-level backup tasks from the rest of the network. At other times, it’s run a Plex server, the Channels DVR, and…I honestly don’t remember what else I’ve experimented with here. It’s a pretty capable little box.
A few days ago, I wrote about what GreyNoise have been calling “Noise Storms,” extended periods of high-volume ping traffic detected by many of their sensors, coming from…many different sources. The most intriguing of these were packets with the word “LOVE” in plaintext in the ping payload, and in my post, I offered a possible explanation of that traffic. At least, at a technical level – what they’re doing with those packets, well, that’s a different puzzle.
Earlier this month, I attended BSidesNoVA in Arlington, where the keynote was presented by Andrew Morris of GreyNoise. Using sensors distributed all over the world, GreyNoise collects…background noise…on the Internet. Basically, they watch and monitor activity that hits lots of hosts randomly – network mapping, port scanning, doorknob rattling. If you see someone trying to break into your SSH server, you can check GreyNoise to see if that person (well, their IP, anyway) has been seen doing such things in the past.
Feb 24, 2025 - 2800 Words -
