journalctl -b -1 -n 500 # < the number of lines to go backSince I was a little tardy in scanning and checking the logs, I had to go back around 2000 lines to see what was up
journalctl -b -1 -n 2000Solution is to install fail2ban and fix the service under duress. Not going to explain any further as I would like to keep the egg off my face 🍳 🤓
sudo apt install fail2ban
# to check fail2ban events:
fail2ban-client status <daemon/process name>