factroy's Posts

Hi, what does a syslog message like this mean: Hostd: [LikewiseGetDomainJoinInfo:354] QueryInformation(): ERROR_FILE_NOT_FOUND (2/0): We get a lot of them from all different ESXi servers. Which file was not found? Why? Any method for debugging this? Thanks for any insights here. Best. PS: This is ESXi 6.5 updated from 6.0/5.x etc.

Hi, there were a couple of discussions about configuring the syslog logging level of an ESXi server. So, I we all know these links: Enabling trivia logging in VMware vCenter Server (1001584) | VMware KB and vSphere Documentation Center But I still have some issues in reducing the 'verbosity' of an ESXi 6.5 host: In my config.xml in /etc/vmware/hoistd I have this code. My understanding: "Only syslog messages 'error' or more severe"       <!-- default log level -->      <level>error</level><!-- <level/> -->       <!-- If true, logs to syslog -->       <outputToSyslog>true</outputToSyslog>       <!-- syslog configuration.  Only used if outputToSyslog is true. -->       <syslog>          <!-- syslog identifier to use when logging -->          <ident>Hostd</ident>          <!-- syslog facility to use when logging -->          <facility>local4</facility> But I still get syslog messages like this: 2016-11-23T18:40:48.222Z vmh-01.samos Hostd: trivia hostd[9E40B70] [Originator@6876 sub=Snmpsvc.http.HTTPService] HTTP Response: .... 2016-11-23T18:40:01.722Z vmh-01.samos hostd-probe: info -[7F9E980] So, any explanation why this is the case?  Any other configuration file? Or are these options overwritten somewhere? Thanks for refreshing the discussion here. Best.

Hi, we would like to move a small (essentials) dev network from 6.0 vCenter Windows to the new 6.5 vCenter Appliance. Unfortunately, the automatic migration does not work because of  FATAL error "vmonapi" while migrating from Windows 6.0 to Appliance 6.5 So, our idea was to setup a new 6.5 appliance and move some config manually as we only need the three 'essentials' host and we do not need any records or older logs. Any tips what would be the best way to do such a thing? Whch files or config to bring over? Anyone did this before? At which point do we need to shut down the old vCenter Windows server in this manual process? Thanks for any comments PS: Reason for doing it this way is because we are not expecting any help solving  FATAL error "vmonapi" while migrating from Windows 6.0 to Appliance 6.5 without a commercial support ticket.

Hi, we would like to move from our Windows vCenter 6.0 installation to the new vCenter Appliance 6.5 as documented. All went well until the new instance is goging to start where we get an error: "An error occurred while starting service "vmonapi" (Failed to start VMware Service lifecycle manager API service)" There was some hint in the release notes: "vmon-api firstboot" Workaround: Verify that the source vCenter Server SSL certificate SAN field contains the valid IP address of the source vCenter Server instance. but I really dont understand how or what to fix on the original vCenter Windows server if this is really causing the issue. a) Any additional help would be great. Could this really be the issue. But how do I fix this "SAN field"? b) How can I verify that this is really the issue? I have inspected the "vm-supported.tgz", but dont know where to look? Anyone else seeing this? Thanks for any help. PS: Of course a new installation of the  6.5 appliance works just fine.