The mouse did not survive interrogation.
Also mouse not pictured.
Submitted 3 days ago by Gekkonen@sopuli.xyz to selfhosted@lemmy.world
https://sopuli.xyz/pictrs/image/046aadff-4943-4a89-94ef-cf9c0f92c45d.webp
The mouse did not survive interrogation.
Also mouse not pictured.
Darkassassin07@lemmy.ca 3 days ago For a while, the windows machine I was using kept randomly becoming unresponsive (both via network, as well as the keyboard+mouse) and I just could not figure out why. Everytime it did, I’d have to force a shutdown by holding the power button until it shutoff, then press it again to start back up. Sometimes this happened while I wasn’t home, so it had to just stay offline until I was.
I got sick of having to do this; so I replaced the power button with a transistor and a RPI. The PI would ping the server every 5min; if it failed to get a response 3 times in a row, it would trigger the transistor for 10sec, release for 3sec, then press and release again; forcing a poweroff then starting the machine again. It’d also write these events to a log file. I think it was around twice a week ish.
Never did figure out what the cause of the lockup was; but it stopped when I replaced windows with Debian.
Had a zyxel nas that got unresponsive after 10-15days of uptime, thankfully it hat a scheduled shutdown/reboot setting. Runs since 2014 with a reboot every Mondy 3am.
Heh, my router is on one of those timer plug things. No matter how frozen, it will reboot.
I have NAS that had a similar problem, but from the logs it was clear that the machine was running fine after going non-responsive, but either the NIC or something else network related was crashing. However, the logs weren’t capturing the exact issue. I wrote a script to ping Google every 10 minutes, write a bunch of debug data to disc, and then reboot.
And it has never happen since. I have no idea what the root cause was, but sending those pings out seems to have fixed it.
A_norny_mousse@piefed.zip 3 days ago Never did figure out what the cause of the lockup was
the mysteries of closed-source software
I also had a machine that would randomly crash on Windows, but not on Linux.
I’m pretty sure it was some sort of hardware failure, as it also sometimes failed to boot Linux. But if it booted Linux, it would be stable until I shut it down.
Sometimes Linux handles faults better than Windows
Typically dmesg shows error when the hardware is acting up
1. Rule out unswitched (non-chipset, direct CPU lanes) PCI connectivity and power issues by testing without specific PCI components. Unstable PCI errors can be missed during post and present later after boot, and Windows is especially bad at handling it transparently. Common culprits include GPU sag, dubious riser extensions, and anemic PSUs 2. If there is a “high bandwidth” feature toggle for RAM in your BIOS settings that is currently on, try turning it off 3. If your system drive is an NVMe blade with a Phizon controller, check if the manufacturer software has a firmware update available. 4. If the freeze is regular but not persistent, try turning the polling rate down on your mouse, and if it’s wired, try to make sure it’s plugged into one of the board’s SOC-hosted USB 2.0 ports
I just wrote a comment about a very similar setup! Glad I wasn’t the only one haha
Using an RPi with a transistor almost seems professional… ITAPPMONROBOT
Yeah getting rid of windows solves many issues, LOL. I have always refused to run any server with windows, outside of being forced to at work. 😁
No mouse problem, but I’ve had to take measures to prevent cat-related downtime. Cats and power-button at the top is not a good combination.
When I had this problem I disconnected the power button on the motherboard.
16mhz@lemmy.ml 3 days ago Cant you just assign a different action to that power button instead of messing with it internally?
Did you reconnect it everytime you had to power it on?
They make sprung flip-top covers specifically for this reason. It’s just a little adhesive square/circle that you stick over the power/reset button, and it has a flip-top that automatically springs closed again.
Instead of cat proofing, you were supposed to get a server room dog…
irmadlad@lemmy.world 3 days ago I have two server room dogs. An English pit, which is my seizure dog, and a Jack Russel. They shed, especially in the summer months, and the floor sweeper gets a daily work out, as well as keeping it out of equipment enclosures. It’s not that I hate cats, they are nice as a pet in your house, just not mine. LOL
Meowy Guard. en.wiktionary.org/wiki/molly-guard
I have a small piece of acrylic sheet taped over the power and reset buttons on my server for that reason. At least I don’t have to worry about mice.
Oh, my housemates’ cat hits the front power button when he leaps off my tower. I’ve got some leather taped over it. My uptime approaches 1! I love your little weight setup, too!
My radiator is on top so they’ve learned that’s about the only surface in the house where they’re not allowed to sleep
Aha, I disabled the LEDs by unplugging them from the motherboard, you could do the same with the power sw plugs
I hosted shit for about ten years before really understanding how local dns worked.
Imagine a primitive society that discovered literally every major modern scientific achievement, but somehow missed the wheel. That’s basically how my first setup went lol.
I have heard of local DNS multiple times now and been selfhosting for many years, but I’m good with my 192.168.178.39 :)
It opened the door to pihole and unbound, then dns certs, man… everything’s so nice now lol
Well hello there, fellow Fritz-Box user :D
I have a feeling there’s a point in time where most non-it self-hosters got fed up with ads and installed pihole, then learned about DNS. I have a feeling that started about five years ago.
Now it’s probably hand in hand with how necessary a pihole is.
I do not self host. I just wandered in here. Do you have suggested resources to learn more about DNS? I feel like generally searching shit sucks to get an answer like that lately.
A dns server knows what and where things are. That’s its only real job, to tell who’s asking where say, eff.org is.
“Ay homie, where’s eff.org?”
over here - 173.239.79.200
“thanks, bud!”
The issue is, the dns server you use by default is under the control of whoever your provider is, and as a result, they get all of your dns lookups like the example above as well as every porn site, every piracy site, everywhere.
Installing your own, or simply moving to one your provider has no business with like 9.9.9.9 can help keep your dns queries more private, go a step further and use encrypted dns, as many providers supply, and you’ll be even further covered.
Installing your own, however, comes with the added perk of being able to apply your own dns entries. Suddenly local addresses can have custom names without ever touching a hosts file. Neat! Use DNS certs and you’ve got local SSL!
I would go find something applicable to feed you for a dns 101, but my old resources don’t exist. I just know stuff from years of doing it and failing over and over until things work.
One day, our internet just stopped working entirely. Our ISP was fine, router good, but no outside connection and I couldn’t access local devices. I have two Unraid servers. I took a quick glance at them, they were powered on, all looked ok. I decide to power cycle everything. Still no internet. Then I realize that I can still access Google from my phone when on WiFi… hmm. That would mean… an issue with pi-hole!
I begin to try to diagnose from my phone with a hotspot to my computer. I’m getting warmer but some things just aren’t making sense. I go back and stare at the server running pi-hole. Then it fucking hits me.
I have the pretty odd and totally not ideal home network. I have plans to upgrade everything but currently I have two wifi networks tied to the same WAN. One network is run off of access points so I can get Ethernet to odd areas of the property. The Unraid server hosting pi-hole was connected to an AP and the Ethernet cable I used didn’t have a clip, so it just barely unseated itself from it, breaking the connection. The router+pi-hole config meant also breaking the internet if anything happened to pi-hole or that server. I swapped it for a better cable and it all instantly started working.
Spent that weekend sorting out the network so it doesn’t happen again. It was definitely a head-scratcher.
rimu@piefed.social@piefed.social 3 days ago It’s always dns at least half the time
Pihole is cool, but fucked me over as well more than once. It’s on its own hardware now, but I plan to add a second one to reduce the single point of failure.
Haven’t thought of that tbh. Would they both just share configuration? Curious how leasing would be split/shared between them. Off to research!
Yep I’ve had it randomly stop working if it has to serve clients outside it’s subnet
I keep one Physical Pihole and one in a container, be sure yeah, this happens.
Then you tell people about it on IRC and become known as “the dead mouse guy”.
But the maximum nickname length on the IRC server is limited, so you settle for “deadmau5” as your nick.
also mouse not pictured
😤😤😤
Also mouse not pictures
I was frantically searching for it, then i opended the post to See if the comments found it …
I’m sorry. Have this picture of a lime-hawk moth caterpillar I saw the other day.
Optical or roller ball?
Forester@pawb.social 3 days ago I have a strong suspicion that the answer is mammilion
That sounds like a lot. Is it more than a bajillion, or less?
At my first-ever tech job back in 2000, I was given a little Celeron desktop computer to do my work: mostly writing some ColdFusion and cutting up images in Photoshop. For the most part, the machine worked fine, except whenever I scrolled down on a webpage in Netscape, the box’s PC speaker would start screaming. I tried to ignore it, but I was in a small room with two other nerds and it was getting really annoying.
One day, my frustrated colleague decided it was time to investigate. As part of the process, he noticed that there was very little air coming out of the power supply fan port. “Must be a busted fan and that’s causing an overheating alarm” he declared. We unplugged the box, popped it onto my desk, and opened it up. The internals were pristine. No dust, nothing. The computer was practically brand new after all.
We were just about to crack open the power supply (not recommended, but we were getting desperate) when my colleague noticed that something was wedged inside the fan… it was the biggest (dead, thankfully) cockroach I have ever seen, at least 10cm long. For context, this was in Vancouver, Canada. Those just don’t exist there.
My colleague jammed his screwdriver in there to grind up the cockroach carcass, then plugged the box back in. After a shittone of dessicated cockroach guts spewed out the back, my little computer was operating normally.
As best we could guess, the monster crawled into the fan in Malaysia when as was assembled and somehow got pinned in there, died of starvation, and then stowed away to Canada.
And this is the way bioinvasor species spread - most of the time they don’t come delivered inside of PSUs but simple crates, which improves their survivability lol
Cat vomit… my cat hit my raspberry pi.
Sounds like a cat. The entire place to vomit and it finds the most expensive/inconvenient thing to lay that stomach lasagna.
You don’t need a mouse for a server. Just SSH into it, duh.
wreckedcarzz@lemmy.world 3 days ago Now now don’t sshush the server, it’s doing the best it can, okay? It gets hot in that box…
Well, if it could think outside the box every once in a while, that would be great y’know.
Not exactly self-hosting, but I’ve worked at two different academic labs that had unique issues and small budgets.
The first was on top of a mountain at 3km elevation. The low air pressure meant that all hard drives had a lifespan of no more than a year before starting to have issues. This was in the pre-SSD days. The “solution” was to boot from a floppy, never compress data, and have a student return the drives to a low elevation and swap them for the prior ones every six months.
The second was at a place that was using old Datacube MaxVideo hardware that we would never have the budget to replace. It would crash if the room temperature got above about 18C, so we set the thermostat to 15C. Which doesn’t sound too bad until you’ve tried sitting at a desk for 8 hours where everything is 15C and the heat is just slowly leaving your body into the chair, the desk, and the keyboard. And then you walk outside where it is 32C and instantly start sweating because you’re still in several layers and fingerless gloves.
Bebopalouie@lemmy.ca 3 days ago Back in the day of BBS’ my buddy had a wonky modem. If I picked up phone , pursed my lips and did a squeaky sound the modem worked and I could log into BBS.
Not selfhosting, but I remember standing in a server room with a hands’ width of water on the ground (and rising), and hastily shutting down servers where the water was already in the case. It were big towers (Compaq Proliant, if anyone remembers), and luckily the board, drives, and PSU were in the top part of the big tower cases, the drive bays at the bottom were empty.
We got all equipment out safely, and we did not get electrocuted, either. We left with the last equipment when the water level was approaching the knees.
Reminds me of a time at my old job. It was a small office and this was before “the cloud” was a buzzword, so we had a little server room running a few boxes for AD, Exchange, and the thick end of our thin clients.
This “server room” was basically a large closet behind my office, retrofitted with its own AC.
We had residential units on the higher floors of our building. Residents occasionally thought to themselves “you know what makes a great hanging rack? Sprinkler pipes!” Hijinks ensued.
That was a fun call to get at 10PM.
Shoutout to the facilities guy who immediately thought to run a makeshift tarp over the server rack, fashioned from trash bags. No permanent damage.
Did you try turning the faucet off first to stop the water from rising while you were working?
The “faucet” was water literally streaming in through the broken window during a thunderstorm. One of my coworkers went outside and shielded the window with a wooden board to reduce the flow.
I got a little fanless atom PC from work that was being tossed because it “didn’t work.” It did work you would just have to apply pressure to it before boot because the CPU must have been coming unsoldered. I just stuck it on the bottom of like 30 pounds of gear and never had a problem.
How on earth did you diagnose that one?
There was an era where the BGA chips giving up the ghost was a common enough occurrence and pushing on things was a relatively normal troubleshooting step
Goddamn I hate mice. I just had to tear out the entire contents of a combine cab to get rid of their piss and shit, and fix the wiring they chewed off.
DrunkAnRoot@sh.itjust.works 3 days ago Fail2ban crashing on 3 seperate days i tried setting it up then one day i did the exact same thing an it worked
I had a screen get burn in (forgot to turn it off, oops) removed it from the laptop, waited 3 days, put it back in and it was flawless again.
I had a laptop that refused ethernet and would only ever use wifi… When the ethernet was connected. No wifi unless that cord was connected. Confirmed it was, indeed, wifi by using a dummy connector.
Bought a 10tb hdd that refused to read anything at all, opened it for giggles/curiosity and found a piece of scotch tape stuck to one of the disks and one of 4 disks completely shattered. The disk was still factory sealed (by appearance, anyways; they still had the antitamper stickers)
tenchiken@anarchist.nexus 3 days ago Mine would be when I had a 48 bay disk array / JBOD fail on me… badly. After a storm, it killed the larger card that allowed for me to get many of the drives into a PCIe 16x slot, and I was relegated down to only getting ~8 disks per box made from spare hardware. A single box I got 16 going. Add to this mix an SSD for mid-line caching.
These were all running bcache on top of mdraid… One single mount.
Yes I understand how obnoxiously stupid it was to run RAID6 on a 48 disk volume. It was almost all just stuff I could re-acquire over time, not irreplaceable things.
I just HAD to solve this one though.
In come several spare chassis / mobo etc…. get a bunch of drives powered and on /dev/ , move to the next.
A couple spare gigabit switches…
several gigabit NICs…
two explicit paths for each machine…
a bit of iSCSI magic, and one machine now had the physical disks all exposed to it… mdadm –assemble blah blah, bit of UUID chaos…
It’s surprising that while a bit speed limited (I think I got just around 110MB/sec reads), it was nicely performant for what a huge mess of wires and disks just strewn out around my rack.
Managed to evacuate all I needed without much issue once I got that going. Now, I try to keep my arrays under 16 drives at a time, or keep a very rigid policy of “I can lose this and don’t care” vs “this box gets RAID10 and/or offsite backups nightly”.
back up your critical stuff people!
Well at home i only have problems with spiders in my racks, not like the racks i have seen at work. Highlights are toiletpaper, chipmunks+nuts and worst in a school server rack a gun.
“not enough space in the used server for a standard power unit”
I wanted to put a dedicated graphics card in there for interference experiments - but the server is, well, a server - and those high availability PUs are expensive and a hell to cable manage
But a Dremel I had at hand … And a second PU as well. Now my server has a second power unit which is only powering the graphics card and is short circuited to be always-on.
self-made problems require self-made solutions.
Had a problem where my ports would suddenly close. At first I thought it was Telekom, then the modem, then the NAS.
After much investigation I discovered that restarting my router would solve it.
After some more weeks I discovered that the crawling bots were triggering some stateful tplink firewall that would close everything until rebooted.
So the router in the middle of the setup was the problem, not the edges.
I’ve got Pfsense installed on a device with 6 RJ45 ports. 0 is wan, 1 is lan0, 2 is lan1, etc up to 4. Why I have multiple lans is somewhat tangential.
One day it rebooted due to a power outage and WAN worked but lan1 and 2 and 3+ were messed up. I’m still not entirely sure what happened, but the second physical Ethernet port was non responsive at boot and Pfsense just assigned the ports as if it never existed. I moved all the cables over one except LAN and it worked just fine. Except that of course in the troubleshooting i had moved all the assignments around and broke it thoroughly, so it took a while.
I used to have a Ryzen 2700X based system as a server. At the time (no clue if it’s still an issue), there was a bug in the interaction between early Ryzen chips and Linux that caused the OS to lock up intermittently. I used a ATmega32u4 board to connect to the reset switch on the PC and as a USB device with a systemd unit that sends a ping to the board every 30 seconds. If the board doesn’t see a ping for a minute, it reboots the PC. It was janky as hell, but it worked for 2+ years!
My WAN connection would just randomly start losing packets and would not recover, not full disconnect just lots of retries. Didn’t impact LAN just WAN. Unplugged the cable or disabling then re-enabling the interface would fix it for a coupe of days to a week then it would come back.
Time consuming to diagnose as switching cables, ports, etc would require waiting days to see if it fixed it.
Eventually had the ISP come out and swap the fiber media converter and fiber integrity. But again it came back.
After several weeks I stumbled on a FreeBDS bug that was exactly my issue…I was running OpnSense and my gateway had I225s. Applied the scripts and it worked.
it is frying here during summer in Australia. I have to buy a seperate airconditioner for the server room and pipe it into the intake of my home lab/nas so it would not shut down on me
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| AP | WiFi Access Point |
| ISP | Internet Service Provider |
| NAS | Network-Attached Storage |
| PCIe | Peripheral Component Interconnect Express |
| RPi | Raspberry Pi brand of SBC |
| SBC | Single-Board Computer |
| SSD | Solid State Drive mass storage |
| SSH | Secure Shell for remote terminal access |
[Thread #80 for this comm, first seen 18th Aug 2026, 08:10] [FAQ] [Full list] [Contact] [Source code]
Not self hosted but at work: after an update to both our firewall cluster nodes they both acted wonky, restarted 5 min after booting, ssh connection wasn’t working half the time, dropped packages… the problem persisted through multiple reboots, support had no idea.
the fix was to pull the plug entirely, wait 10 seconds then power them on again. on both nodes we had this behavior and both worked again after losing power for a few seconds.
seems that even for business appliances “have you tried to turn it off and on again” is a viable solution.
Not on a computer but I had a JVC TV that started blanking a few times a minute whenever my dvd player was connected. Whilst trying to fix this I attempted to update the TV firmware. That didn’t fix a thing but I noticed that the blanking went away when the USB drive with the firmware update was plugged in. So I just plugged a cheapo USB drive in and left it there for as long as I owned that TV and dvd player.
KairuByte@lemmy.dbzer0.com 3 days ago
Got my hopes up for nothing!
Crozekiel@lemmy.zip 2 days ago
I stared at that picture like it was a Where’s Wally for like 10 minutes before I came to check the comments and saw this note in OP’s message…
KairuByte@lemmy.dbzer0.com 2 days ago
We are cut of the same cloth.
conorab@lemmy.conorab.com 3 days ago
It’s OK I gotchu
Image
Fun fact - he’s called that because this same thing happened to him with a dead mouse in the pc case.