I renently upgraded vcenter from 4.1 to 5.1 and one of the upgrades we wanted to get host profiles working. I attempted to get a profile from an existing host and this is the error:
A general system error occurred:
Any ideas?
Are you using the vSphere Web Client 5.1, or the classic vSphere Client (Thick / C# app)?
I have used both clients actually
Can you edit the hostprofile and check if the configuration details are correct , if any thing is left blank .
Best Regards,
Shashi
HI,
I believe it is unable to get properties of some devices / components.
Can you please check the below logs.
ESXi Host: /var/log/hostd.log
vCenter: C:\ProgramData \vmware\infrastructure\Virtualcenter\logs\vpxd.log
We running into the same issue, but only on some ESXi 5.1 hosts.
Did you ever find a cause or solution for this?
Regards,
Harold
Hi 🙂
I had the same problem with the error message, but this was solved as follows:
When I had the problem:
The problem with the error message: "A general system error" - "argument of type 'NoneType' is not iterable" does appear on servers that have been updated from 5.0 to 5.1, when the system was not new installed with version 5.1.
Solution:
The problem causes the file "/etc/vmware/snmp.xml". This file looks after the update not right.
My snmp.xml looked after the update from 5.0 to 5.1 as follows:
<?xml version="1.0" ?>
<config>
<snmpSettings>
<enable>
false
</enable>
<port>
161
</port>
<syscontact>
not set
</syscontact>
<syslocation>
not set
</syslocation>
<communities>
</communities>
<targets>
</targets>
</snmpSettings>
</config>
and the snmp.xml should looks like:
"<config><snmpSettings><enable>false</enable><port>161</port><EnvEventSource>indications</EnvEventSource><loglevel>info</loglevel><communities></communities><targets></targets></snmpSettings></config>" (In one Line without Spaces!)
Login to the host (customize security settings and to start the SSH service) with putty.
Now executes the following command:
"esxcli system snmp get"
This allows you to show the configuration file of the SNMP service. Should an error occur, look at the snmp.xml file ("/etc/vmware/snmp.xml). If this looks like them above, then changes the content of snmp.xml to the following:
"<config><snmpSettings><enable>false</enable><port>161</port><EnvEventSource>indications</EnvEventSource><loglevel>info</loglevel><communities></communities><targets></targets></snmpSettings></config>"
again check the file with the command:
"esxcli system snmp get"
Now the settings should be correct.
Try again a host profiles Check and it should work .
Excuse my Denglish 🙂
Greetings from Bremen,Germany
Alex