Conversation

Notices

1. Embed this notice
   Miakoda (hellomiakoda@pdx.social)'s status on Saturday, 19-Apr-2025 05:20:24 JST Miakoda

   Bah, I was going to sit here and work on my server, but I forgot I hadn't fixed the SSH issue. Trying to log-in over ssh gives me "POWER FAILURE" and "Too many failed login attempts".
   I have no idea how to reset that, but it obviously requires I be at it's keyboard.

   #Linux

   • Embed this notice
     Miakoda (hellomiakoda@pdx.social)'s status on Saturday, 19-Apr-2025 05:24:39 JST Miakoda

     in reply to

     • MuhammadFree🇵🇸

     @MuhammadFreeSoftware Well... When I attempt to login with ssh, it says "POWER FAILURE" and "Too many failed login attempts"

   • Embed this notice
     MuhammadFree🇵🇸 (muhammadfreesoftware@fosstodon.org)'s status on Saturday, 19-Apr-2025 05:24:40 JST MuhammadFree🇵🇸

     in reply to

     @hellomiakoda Help us to help you!
     Can you give more informations about the issue you're facing? By giving more info, more people can help you
     https://dontasktoask.com

   • Embed this notice
     Miakoda (hellomiakoda@pdx.social)'s status on Saturday, 19-Apr-2025 05:27:26 JST Miakoda

     in reply to

     • MuhammadFree🇵🇸

     @MuhammadFreeSoftware Ah, I see. Judging by the link you included, you have mistaken my rambling about my frustrating issue as a request for assistance. While I welcome assistance, I haven't posted it as a request because I have not yet had the moment to sit at that keyboard and attempt the repair myself. If I can't figure it out, then I'll ask and include the details, such as distro.

   • Embed this notice
     Miakoda (hellomiakoda@pdx.social)'s status on Saturday, 19-Apr-2025 05:29:21 JST Miakoda

     in reply to

     • MuhammadFree🇵🇸

     @MuhammadFreeSoftware I'm sure with 5 minutes on SearX, or perhaps even just 10 minutes with only the bash shell on that server, minus the remote connection, I'll be able to find what needs to be cleared. I'll probably even find the settings to change to relax that security a little bit, or maybe even make an additional user I can SSH with when my account gets locked.

   • Embed this notice
     Miakoda (hellomiakoda@pdx.social)'s status on Saturday, 19-Apr-2025 05:32:49 JST Miakoda

     in reply to

     • MuhammadFree🇵🇸

     @MuhammadFreeSoftware No worries. You're not the first. I'm autistic. My rambling often gets mistaken for requests, or insults, or whatever else.

     Though if you're open to help, I'll keep you in mind if I can't figure out when I'm back at that machine.

   • Embed this notice
     MuhammadFree🇵🇸 (muhammadfreesoftware@fosstodon.org)'s status on Saturday, 19-Apr-2025 05:32:50 JST MuhammadFree🇵🇸

     in reply to

     @hellomiakoda Oh ok, sorry for that.

   • Embed this notice
     Miakoda (hellomiakoda@pdx.social)'s status on Saturday, 19-Apr-2025 05:35:13 JST Miakoda

     in reply to

     • Rob Williamson

     @eswag We did recently have a power failure, and it (hopefully) shutdown via UPS - which I then later manually powered it on once grid power was back.
     I don't remember what set off the "too many failed", but I was on local net when that problem started. I hadn't thought about it cause power failure happened, and I'm surprised the reboot didn't clear that.

   • Embed this notice
     Rob Williamson (eswag@dju.social)'s status on Saturday, 19-Apr-2025 05:35:14 JST Rob Williamson

     in reply to

     @hellomiakoda

     "Too many failed login attempts" makes me think you've made your server suspicious. "POWER FAILURE" makes me think it's trying to fake its own death. What on earth are you doing with it?

   • Embed this notice
     Steve's Place (steter@mastodon.stevesworld.co)'s status on Saturday, 19-Apr-2025 05:48:18 JST Steve's Place

     in reply to

     @hellomiakoda Your account is locked after either 3 or 5 failed attempts. It should relent in 10 minutes.

   • Embed this notice
     Miakoda (hellomiakoda@pdx.social)'s status on Saturday, 19-Apr-2025 08:12:31 JST Miakoda

     in reply to

     • Steve's Place

     @steter
     It's been many days and a reboot.

   • Embed this notice
     Steve's Place (steter@mastodon.stevesworld.co)'s status on Saturday, 19-Apr-2025 09:16:13 JST Steve's Place

     in reply to

     @hellomiakoda Okay, I hope this helps. Probably the easiest way to fix it is to boot up on a rescue/install medium. Mount the misbehaving boot disk, e.g., to /mnt. Then (add /mnt to all file paths) (from superuser.com):

     Navigate to /var/run/faillock (*), this folder should contain a file with the locked username

     # ls /var/run/faillock
     myUsername

     Remove the file with the username to unlock

     # rm /var/run/faillock/myUsername

     * This is called 'tally directory' and its location depends on your system's configuration, which is likely to be found at /etc/security/faillock.conf

   • Embed this notice
     Miakoda (hellomiakoda@pdx.social)'s status on Saturday, 19-Apr-2025 16:53:07 JST Miakoda

     in reply to

     • Steve's Place

     @steter
     Well, before I got to try that, it ended up in a none potable state. It complains about not being able to load apparmor profiles and then goes to emergency shell

   • Embed this notice
     Steve's Place (steter@mastodon.stevesworld.co)'s status on Saturday, 19-Apr-2025 17:12:19 JST Steve's Place

     in reply to

     @hellomiakoda That's in /etc/apparmor and /etc/apparmor.d.. On an install/rescue disk it should not happen.

     Well, you could pull the drive out and install it as a non-boot drive in a system that boots and see what you have. Maybe make the changes there and put it back.

     Maybe run e2fsck on it, too. I'm assuming that's in ext4 format.

     What fun.

   • Embed this notice
     Miakoda (hellomiakoda@pdx.social)'s status on Saturday, 19-Apr-2025 18:30:57 JST Miakoda

     in reply to

     • Steve's Place

     @steter
     / is in btrfs

     Only /boot and the content drives are in ext4 on this system