Hello,
We had a very similar issue after our VCSA had a memory allocation error and crashed. We rebooted it and the PSC but then lost any connectivity via the web client (thick client worked on some things).
The main issue = PSC lost it's AD connection
The verification:
- VCSA
- SSh session
- Drop to the shell
- run
- /opt/likewise/bin/domainjoin-cli query
- The return should say your domain and distinguished name
- PSC
- SSh session
- Drop to the shell
- run
- /opt/likewise/bin/domainjoin-cli query
- The return should say your domain and distinguished name
- My case was blank
The fix:
- On either system that does not show you the AD information
- run
- /opt/likewise/bin/domainjoin-cli join YOURDOMAINNAME.COM %AD user account%
- enter password
- run
- Reboot the PSC and VCSA
- Once they are back up
- run
- /opt/likewise/bin/domainjoin-cli query
- You might initially receive a "time skew" error with AD
- This happens as the service has not fully updated. Might take a 1-2 minute to fully update
- You can keep running the above command to verify. It will eventually update to the correct time
- run
- Login to the web client and check your permissions
In my case I did lose some of my 3rd party plugins which I had to re-register.
Hopefully this helps someone else.
Thanks
B