Skip to content

Month: February 2011

A general system error occurred: internal error

I recently tried to export the system logs from an ESXi via the vSphere client. Instead of receiving the generated bundled the host returned:

A general system error occurred: internal error

Very informative error message, no? I looked at the logs visible from the vSphere client and realized they were all dated before ESXi was installed. What was going on?

invalid request: domain is not configured for preauth

I was recently playing around with my Zimbra installation and was specifically trying to figure out how to configure administrator accounts. By default, a single global administrator is configured during installation. While this is good, I needed the following:

  • Change the global administrator to a different domain / account
  • Add multiple administrators, one per domain
  • Grant certain administrators administrator access to multiple domains

While playing around with the Zimbra configuration, I navigated to https://<FQDN>:5480 (I am running the appliance version) and logged in with the vmware user account. Upon selecting the Zimbra Administration tab, I was greeted by:

Problem accessing /service/preauth. Reason:
invalid request: domain is not configured for preauth

I had no issues in the past so I knew it had to have been something I changed. So what was causing the problem?

Cannot complete the configuration of the HA agent on the host

I enabled HA on a new cluster the other day and one of the hosts came back with the following error:

Cannot complete the configuration of the HA agent on the host. Misconfiguration in the host network setup.

On ocassion, I have seen weird HA errors where simply selecting the ‘Reconfigure for HA’ on the host fixed the issue. I tried this, but the same error was seen. I next selected the host and went to Tasks & Events – Events. From there, I found the following error message:

HA agent on <host> in cluster <cluster> in <datacenter> has an error: Cannot complete the HA configuration.

Selecting the message and under Related Events selecting Show displayed:

Host <host> has the following extra networks not used by other hosts for HA communication: <IP>,.
Consider using HA advanced option ads.allowNetworkto control network usage.

Looking at the VMkernel interface, everything appeared to be configured correctly. I ensured the IP configuration was correct and that no duplicate IP issue was being experienced. So what was causing the problem?

Bug in PowerCLI 4.1.1: Set-VIRole

I was trying to set up some permissions on vCenter Server using PowerCLI. Here is an example of a command I was running:

foreach ($role in 'Host','Virtual Machine','VMware vCenter Update Manager') {
Set-VIRole Role (Get-VIRole -Name ) -AddPrivilege (Get-VIPrivilege -Name 'Virtual machine')

PowerCLI returned the following:

WARNING: There were one or more problems with the server certificate:
* The X509 chain could not be built up to the root certificate.
* The certificate’s CN name does not match the passed value.
Name IsSystem
—- ——–
newTestRole False
newTestRole False
newTestRole False

This looks like it worked, however upon looking at the permissions on vCenter Server, the checkboxes for these three options were not selected. If you attempt the command with any other permissions it works as expected (i.e. the checkboxes are selected).
Why was this not working?