The upgrade started, but at some point before the first reboot the UI appeared to log itself out (instead of the "rebooting .." message I had seen on previous upgrade). It seemed to be suggesting that I had a session timeout, but I had only just logged in and started the upgrade immediately.
So I just waited, and TOS rebooted itself as normal, and I could refresh the page myself and log in to the new version, all data intact.
I was glad to see what appears to be improved file permissions control, so thanks TM for that.
However .... now I can no longer join my domain. Now I have had to rejoin the domain after every single upgrade, which is irritating but not really a huge problem. This time though, rejoining did not work. It just complains about an "Incorrect username or password". I have tried several users with permissions to join the domain, but none work.
I can't find any logs on my domain controller (Samba) that suggest the DC is even being contacted. And I can't find anything that looks relevant in TOS logs either.
The only sign of anything untoward I can find is by tailing /var/log/syslog. The following text just keeps repeating infinitely. Windows file sharing on TOS itself appears to be working, just without any domain integration.
Code: Select all
.
Sep 20 16:18:49 terra systemd[1]: Started trigger-samba.service.
Sep 20 16:18:49 terra systemd[1]: Condition check resulted in Kernel Security Modules - SMACK being skipped.
Sep 20 16:18:49 terra systemd[1]: Condition check resulted in Security Spcack being skipped.
Sep 20 16:18:49 terra systemd[1]: Starting trigger-samba.service...
Sep 20 16:18:51 terra systemd[1]: trigger-samba.service: Deactivated successfully.
Sep 20 16:18:51 terra systemd[1]: Started trigger-samba.service.
Sep 20 16:18:51 terra systemd[1]: Condition check resulted in Kernel Security Modules - SMACK being skipped.
Sep 20 16:18:51 terra systemd[1]: Condition check resulted in Security Spcack being skipped.
Sep 20 16:18:51 terra systemd[1]: Starting trigger-samba.service...



