Morning everybody. I’ve got a server at home running Debian and I handle everything over SSH aside from file transfers for which I use webmin. I’d be trying to get Frigate working on it using Podman but couldn’t get it to find the hardware I was passing to it and got pissed off and gave up, that was a few weeks ago and everything was fine. The Podman container had its own user and I’d set it up so I couldn’t access the containers with any other users, even with sudo. I’ve gone back to it this morning and found that when i try to sudo su in (which is what I normally do) i get “This account is currently not available”. I checked everything my friendly AI hero suggested but I couldn’t figure out why it had locked. The last reference in journalctl was me closing the session and there was no records of failed logins or fail2ban being triggered. I had the ! in the shadow file and passwd was showing me an L to say it was locked. In the end I gave up trying to figure out why it had locked because I couldn’t see evidence of anything dodgy so I just went to unlock it. I’ve tried passwd -u and I’ve remember the ! and rebooted but it still won’t unlock.
I suspect Podman may have done something but I’m pretty sure I stopped the containers before I last logged off because I got sick of them filling the log files up, and though I’ve rebooted at least once in the last three weeks I don’t know if my containers are auto starting, or what that would do. I can’t even check until I’ve got the user logging on.
Anyone have any ideas?
I'm not sure how you'd be able to sudo su (user name) if that users shell was /usr/sbin/nologin. Maybe you were doing something else if that was indeed the assigned shell.