Updated Raspberry Pi OS "bookworm" from 5.4 to 5.9, and also did a sudo iiab-update. Everything was working great until the system was shut down for the weekend. After boot up, the Admin Console suddenly started giving "Invalid Login" errors, despite entering the same login/pw that we've always used. Oddly enough, the admin password still works with SSH and SFTP.
First thing I did to fix the problem was SSH using login "iiab-admin", and running sudo passwd iiab-admin but that didn't work. I checked /etc/default/locale and it showed:
# File generated by update-locale
LANG=en_GB.UTF-8
Tried changing it to "LANG=en_US.UTF-8", and also tried running sudo passwd iiab-admin, and sudo scripts/ansible (Ansible --version says "core 2.19.9"), and ran sudo iiab-update another time, and even tried reinstalling the Admin Console. None of these had any affect on the issue. I was able to recreate the issue by booting up my secondary MicroSD and performing the same updates. How does this happen?
The only good news is that I had enough sense to save an image of my production microSD prior to doing any updates. This coming week I expect to wait the typical 7+ hrs to write a new microSD. It's likely that I will also overwrite a secondary microSD, and carefully try to update RPi OS and IIAB again. Is there something that I should be doing differently, other than what's in the IIAB wiki?
Updated Raspberry Pi OS "bookworm" from 5.4 to 5.9, and also did a
sudo iiab-update. Everything was working great until the system was shut down for the weekend. After boot up, the Admin Console suddenly started giving "Invalid Login" errors, despite entering the same login/pw that we've always used. Oddly enough, the admin password still works with SSH and SFTP.First thing I did to fix the problem was SSH using login "iiab-admin", and running
sudo passwd iiab-adminbut that didn't work. I checked/etc/default/localeand it showed:Tried changing it to "LANG=en_US.UTF-8", and also tried running
sudo passwd iiab-admin, andsudo scripts/ansible(Ansible --version says "core 2.19.9"), and ransudo iiab-updateanother time, and even tried reinstalling the Admin Console. None of these had any affect on the issue. I was able to recreate the issue by booting up my secondary MicroSD and performing the same updates. How does this happen?The only good news is that I had enough sense to save an image of my production microSD prior to doing any updates. This coming week I expect to wait the typical 7+ hrs to write a new microSD. It's likely that I will also overwrite a secondary microSD, and carefully try to update RPi OS and IIAB again. Is there something that I should be doing differently, other than what's in the IIAB wiki?