![]() These are the last few lines of the wmkernal.log file I am know stuck at adding a host to VSHERE web client.Īnd all i get is "A general system error occurred: Timed out waiting for vpxa to start"Īdding host to cluster: "Timed waiting for vpxa to start" where the time is changed. Installed esxi 6.5 vcenter server Appliance (although installation was not smooth (stuck at 80% and other - however manage to get it installed.)) This is my first installation of a VM-Ware environment and I am hoping someone can point me in the right direction. Is this a bug? I know I'm not running the latest ESXi version, or even the latest build of ESXi 6.0, but I'm not quite ready for that yet. I thought initially it was out of date VMware Tools, and it certainly looked more promising when tools was updated to 10.0.9 (build 10249), but then it all seemed to revert back and the same things happen. The message pre-migration will always show 'Compatability checks succeeded'. Sometimes I will see all the migration hosts, but not all the time and very inconsistently It happens in both the Flash and HTML UI's. This method of migrating the VM will work, but I have to 'fake' a datastore change selection. If though, I select 'Change both compute resource and storage', I can expand the cluster and see all hosts. One very strange observation is that when I try and vmotion a VM to another host, if I select 'Change compute resource only', invariably the only destination host I'll see is the host the VM is currently running on - no other cluster hosts will show. I upgraded the licenses and applied them to the new setup ok. I've just completed an upgrade from 3 x ESXi 5.0 hosts and a vCenter 5.1 appliance (Essentials Plus) to ESXi 593 and VCSA 321. Anything we can provide within the command differently perhaps? We know the password, we even tested it separately. When we run the command though ("viewdbchk -removeMachine -machineName Xyz -noErrorCheck"), and are prompted for our service account password for vCenter ( ) and for Composer ( ), when we enter, no characters show not even masked (this might be by design), and when we hit enter to confirm anyway, we are greeted with "ERROR: Cannot get password for user "service_account". This is fine, we know what credentials to use. In Horizon 7 version 7.2 or later, the viewDBChk tool will not have access to vCenter or View Composer credentials and will prompt for this information when needed. ![]() However, since the move to 7.3.2, we can't seem to run it.Īccording to the release notes there was a change: ![]() We use viewdbchk every now and again to cleanup pools in Horizon, when the View Admin console is having issues doing such.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |