The mouse did not survive interrogation.

Also mouse not pictured.

  • Ebby@lemmy.ssba.comEnglish
    19·
    10 days ago

    I lost a raspberry pi for a couple months. Just couldn’t find the darn thing. It was working fine serving away.

    Turns out it was in the basement. I forgot I moved it to be closer to my tilt Hydrometer.

  • Sir. Haxalot@nord.pubEnglish
    17·
    10 days ago

    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.

    pPRfvOP0JoofIAQ.jpg

  • Darkassassin07@lemmy.caEnglish
    15·
    10 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.

    • ÚwÙ-Passwort@lemmy.worldEnglish
      6·
      10 days ago

      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.

      • BartyDeCanter@piefed.socialEnglish
        2·
        10 days ago

        I have a NAS that had a similar problem, every week or two it would stop responding. 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 if it failed, and then reboot.

        And it has never happened in the year since. I have no idea what the root cause was, but sending those pings out seems to have fixed it.

      • vaionko@sopuli.xyzEnglish
        2·
        10 days ago

        Heh, my router is on one of those timer plug things. No matter how frozen, it will reboot.

        • LincolnsDogFido@lemmy.zipEnglish
          2·
          10 days ago

          I’ve got an extra and don’t know what to do with it. I feel like its bad to pull power unexpectedly once a week though. Especially with a single HDD storage setup. I’d like to setup a RAID config, but its a 28TB drive and additional drives would cost me about $$$$$$$.

    • black0ut@pawb.socialEnglish
      3·
      10 days ago

      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.

      • Possibly linux@lemmy.zipEnglish
        2·
        10 days ago

        Sometimes Linux handles faults better than Windows

        Typically dmesg shows error when the hardware is acting up

    • Jul@piefed.blahaj.zoneEnglish
      2·
      9 days ago

      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. 😁

    • Septimaeus@infosec.pubEnglish
      1·
      10 days ago
      Note to any future lemmings who find this thread troubleshooting the same symptom…
      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
  • kfh@lemmy.worldEnglish
    10·
    10 days ago

    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.

  • BeBopALouie@lemmy.caEnglish
    10·
    10 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.

  • Daniel Quinn@lemmy.caEnglish
    7·
    10 days ago

    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.

    • Wildmimic@anarchist.nexusEnglish
      5·
      10 days ago

      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

  • Scipitie@lemmy.dbzer0.comEnglish
    6·
    9 days ago

    “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.

  • BartyDeCanter@piefed.socialEnglish
    6·
    10 days ago

    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.

  • Super Mega Ultra Edition DX Unleashed 64@sh.itjust.worksEnglish
    6·
    10 days ago

    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.

    • cenzorrll@piefed.caEnglish
      5·
      9 days ago

      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.

    • eco_game@discuss.tchncs.deEnglish
      4·
      10 days ago

      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 :)

    • greatwhitebuffalo41@piefed.socialEnglish
      2·
      9 days ago

      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.

      • Super Mega Ultra Edition DX Unleashed 64@sh.itjust.worksEnglish
        7·
        9 days ago

        A dns server knows what and where things are. That’s its only real job, to tell who’s asking where say, http://eff.org/ is.

        “Ay homie, where’s https://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.

  • somenonewho@feddit.orgEnglish
    6·
    10 days ago

    Also mouse not pictures

    I was frantically searching for it, then i opended the post to See if the comments found it …

  • Ascend910@lemmy.mlEnglish
    5·
    9 days ago

    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

    • glitch1985@lemmy.worldEnglish
      1·
      9 days ago

      My last home I put the server in the closet with my heat pump water heater. They pretty much balanced each other out.

  • Treczoks@lemmy.worldEnglish
    5·
    10 days ago

    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.

    • hersh@literature.cafeEnglish
      2·
      10 days ago

      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.

    • blueduck@piefed.socialEnglish
      1·
      10 days ago

      Did you try turning the faucet off first to stop the water from rising while you were working?

      • Treczoks@lemmy.worldEnglish
        3·
        9 days ago

        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.