This article describes how to troubleshooting the issue.
Issue: A general system occurred: internal error
I recently encountered the issue, I was unable to enable lock down mode and getting this error on this.
To fix the issue, I followed the below steps.
- Schedule a downtime for this ESXi and migrate the VMs
     off the host.
 - Place the host into maintenance mode and run the below
     commands on ESXi putty in succession: 
 - # Stop hostd 
 - $ /etc/init.d/hostd
       stop
 - # Dump the default host
      permissions from the config store to a json file 
 - $ /bin/configstorecli
       config default get -c esx -g authorization -k permissions -outfile
       /tmp/tmp.json
 - # Delete all
      permissions from config store 
 - $ /bin/configstorecli
       config current delete --all -c esx -g authorization -k permissions
 - # Update the config
      store with the previous json file. 
 - $ /bin/configstorecli
       config current set -c esx -g authorization -k permissions -infile
       /tmp/tmp.json
 - # Start hostd 
 - $ /etc/init.d/hostd
       start
 - Post this you may exit the maintenance mode and attempt
     enabling the lockdown mode on the ESXi.
 
 
        Reviewed by Virtulization
        on 
        
December 26, 2023
 
        Rating: 

This worked. Thank you!
ReplyDeleteThank you! This fixed my issue as well. About a dozen of my hosts would not let me enable lockdown mode without doing these steps. The others let me turn it on no problem.
ReplyDeleteThank you
ReplyDelete