I'm trying to migrate the storage of a virtual machine to a different datastore. (on the same san)

When I start the job I see the task :

Relocating virtual machine / Status 'In Progress'

After 10 minutes I get 2 popups :

-

Error

-

Cannot connect to host.

-

OK

-

I tried to move the storage from a different virtual machine, but I got the same error.

Also tried from a different vmhost (but same cluster) but also the same error.

When trying from a host in a different cluster It works without problems (same san/datastore used in the cluster where I got the errors)

There are no difference in the security profile on the hosts.

Any hints ?

Attached logfile (vpxd-353.log) when I was running the migrate storage.

Error part :

2009-11-03 16:49:07.035 02464 info 'App' (1257263347020035) VMotion started

2009-11-03 16:58:35.903 02464 error 'App' (1257263347020035) VMotion failed: vim.fault.HostConnectFault

When it runs ok :

2009-11-03 17:29:49.470 02456 info 'App' (1257265789470153) VMotion started

I am stumped. At first, I was able to at least login to vsphere and do operations. The client would close like every 15 minutes so it got really annoying. Now I am stuck with no launch to vsphere. I must log into each host individually. ESXi hosts without a vsphere is so limited. Please advise.

Here is the /var/log/messages

vsphere-fmrif:~ # tail -f /var/log/messages
May 31 09:50:32  vsphere-fmrif watchdog-vpxd: [4773] Begin '/usr/sbin/vpxd', min-uptime =  30, max-quick-failures = 5, max-total-failures = 1000000, bg_pid_file =  ''
May 31 09:50:32 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'
May  31 09:50:34 vsphere-fmrif kernel: [   59.780777] warning: process  `vpxd-worker' used the deprecated sysctl system call with 1.1.
May 31 09:50:40 vsphere-fmrif sshd[4944]: Accepted password for root from 128.231.212.117 port 51160 ssh2
May 31 09:50:44 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 12 seconds (quick failure 1) 134
May 31 09:50:44 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'
May 31 09:50:45 vsphere-fmrif kernel: [   70.438974] warning: process `vpxd' used the deprecated sysctl system call with 1.1.
May 31 09:50:51 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 7 seconds (quick failure 2) 134
May 31 09:50:51 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'
May 31 09:50:52 vsphere-fmrif kernel: [   77.370397] warning: process `vpxd' used the deprecated sysctl system call with 1.1.
May 31 09:50:58 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 7 seconds (quick failure 3) 134
May 31 09:50:58 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'
May 31 09:50:58 vsphere-fmrif kernel: [   83.923261] warning: process `vpxd' used the deprecated sysctl system call with 1.1.
May 31 09:51:05 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 7 seconds (quick failure 4) 134
May 31 09:51:05 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'
May  31 09:51:06 vsphere-fmrif kernel: [   91.720959] warning: process  `vpxd-worker' used the deprecated sysctl system call with 1.1.
May 31 09:51:12 vsphere-fmrif auditd[3012]: Audit daemon rotating log files
May 31 09:51:13 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 8 seconds (quick failure 5) 134
May 31 09:51:13 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'
May 31 09:51:19 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 6 seconds (quick failure 6) 134
May 31 09:51:19 vsphere-fmrif watchdog-vpxd: End '/usr/sbin/vpxd', failure limit reached

/var/log/warn

May 31 02:40:23 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:41:26 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:42:28 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:43:31 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:44:33 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:45:36 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:46:38 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:47:41 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:48:44 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:49:46 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:50:49 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:51:51 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:52:54 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:53:56 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:54:59 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:56:01 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:57:04 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 02:58:06 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 02:59:09 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:00:12 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:01:14 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:01:52 vsphere-fmrif portmap[25177]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:01:52 vsphere-fmrif portmap[25178]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:01:53 vsphere-fmrif portmap[25179]: connect from 128.231.212.121 to callit(390109): request from unauthorized host
May 31 03:02:17 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:03:07 vsphere-fmrif portmap[25275]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:03:19 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:04:04 vsphere-fmrif portmap[25358]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:04:19 vsphere-fmrif portmap[25368]: connect from 128.231.212.121 to callit(390109): request from unauthorized host
May 31 03:04:22 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:05:25 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:06:01 vsphere-fmrif portmap[25531]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:06:27 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:06:31 vsphere-fmrif portmap[25603]: connect from 128.231.212.121 to callit(390109): request from unauthorized host
May 31 03:07:00 vsphere-fmrif portmap[25618]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:07:30 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:08:32 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:09:35 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:10:38 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:11:40 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:12:20 vsphere-fmrif portmap[26072]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:12:43 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:12:54 vsphere-fmrif portmap[26144]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:13:45 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:13:48 vsphere-fmrif portmap[26227]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:14:17 vsphere-fmrif portmap[26242]: connect from 128.231.212.121 to callit(390109): request from unauthorized host
May 31 03:14:48 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:15:09 vsphere-fmrif portmap[26348]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:15:17 vsphere-fmrif portmap[26354]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:15:51 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:16:03 vsphere-fmrif portmap[26435]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:16:53 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:16:53 vsphere-fmrif portmap[26472]: connect from 128.231.212.177 to callit(390109): request from unauthorized host
May 31 03:16:59 vsphere-fmrif portmap[26519]: connect from 128.231.212.121 to callit(390109): request from unauthorized host
May 31 03:17:56 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:18:30 vsphere-fmrif portmap[26621]: connect from 128.231.212.121 to callit(390109): request from unauthorized host
May 31 03:18:58 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:20:01 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:21:03 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:21:37 vsphere-fmrif portmap[26897]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:22:06 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:23:09 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:24:11 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:24:22 vsphere-fmrif portmap[27146]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:25:14 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:26:16 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:26:40 vsphere-fmrif portmap[27330]: connect from 128.231.212.168 to callit(390109): request from unauthorized host
May 31 03:27:19 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:28:21 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:29:24 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:30:27 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:31:29 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:32:32 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:33:35 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1
May 31 03:34:37 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1
May 31 03:35:40 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1

/var/log/vmware/vpx/vpxd.log

 

From earlier:

vsphere-fmrif:~ # tail -f -n 100 /var/log/vmware/vpx/vpxd.log

Section for VMware VirtualCenter, pid=25488, version=5.0.0, build=build-455964, option=Release

 

------ In-memory logs start --------

2012-05-31T09:11:29.623-04:00 [7FFFF3B09700 info 'Hooks'] Hooks Initialized

 

------ In-memory logs end   --------

2012-05-31T09:11:29.633-04:00 [7FFFF3B09700 info 'Default'] Initialized channel manager

2012-05-31T09:11:29.641-04:00 [7FFFF3B09700 info 'Default'] Current working directory: /storage/log/vmware/vpx

2012-05-31T09:11:29.642-04:00 [7FFFF3B09700 info 'Default'] Log path: /var/log/vmware/vpx

2012-05-31T09:11:29.642-04:00 [7FFFF3B09700 info 'Default'] Initializing SSL

2012-05-31T09:11:29.645-04:00  [7FFFF3B09700 info 'Default'] Vmacore::InitSSL: doVersionCheck = true,  handshakeTimeoutUs = 120000000

2012-05-31T09:11:29.646-04:00 [7FFFF3B09700 info 'Default'] Changed working directory to /var/log/vmware/vpx

2012-05-31T09:11:29.666-04:00 [7FFFF3B09700 info 'Default'] Starting VMware VirtualCenter 5.0.0 build-455964

2012-05-31T09:11:29.666-04:00 [7FFFF3B09700 info 'Default'] Log directory: /var/log/vmware/vpx.

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] Account name: root

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:835] Calling: InfoDeclSchema(gDB)

2012-05-31T09:11:29.667-04:00  [7FFFF3B09700 info 'Default'] [Init:837] Calling:  VpxCallbackDesc::Init(MakeFunctor(this,  &ServerApp::RequestShutdown))

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:838] Calling: VpxCryptInit()

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:839] Calling: VpxLRO::Init()

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:840] Calling: VpxLroList::Init(ltud)

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 640 max LROs

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 12 reserved internal LROs

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 12 reserved blocker LROs

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 12 reserved short LROs

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 8 reserved long LROs

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 600-second completed task lifetime

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 60-second minimum completed task lifetime

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 200 maximum completed tasks

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 600-second unregistered task lifetime

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:841] Calling: VpxdCharacterizeThreadpool(ltud)

2012-05-31T09:11:29.667-04:00  [7FFFF3B09700 info 'ThreadPool'] [SetConfig] Thread info: IoMin: 2,  IoMax: 1990, TaskMin: 59, TaskMax: 1990, Max Thread: 3980, Keepalive:  61, thread kill: 600, max fds: -1

2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:842] Calling: VpxdCertificate_Load(gDB, CERTIFICATE_VMDBPATH )

2012-05-31T09:11:29.668-04:00  [7FFFF3B09700 info 'Default'] [Init:843] Calling:  VpxdVdb::Init(VpxdVdb::GetVcVdbInstId(), false, false, NULL)

2012-05-31T09:11:29.668-04:00 [7FFFF3B09700 info 'Default'] Registry Item DB 5 value is ''

2012-05-31T09:11:32.078-04:00  [7FFFF3B09700 info 'Default'] [VdbSchemaLoader::LookupSchemaFromDB]  Loaded schema and index information from DB

2012-05-31T09:11:32.099-04:00 [7FFFF3B09700 info 'Default'] [Init:844] Calling: VpxdDbSchemaHash::CheckSchema()

2012-05-31T09:11:32.100-04:00  [7FFFF3B09700 info 'Default'] [VpxdDbSchemaHash::CheckSchema]: schema  file: /usr/lib/vmware-vpx/VCDB_db2.sql

2012-05-31T09:11:32.104-04:00 [7FFFF3B09700 info 'Default'] [Init:845] Calling: VpxdDbMonitoring::Init()

2012-05-31T09:11:32.120-04:00 [7FFFF3B09700 info 'Default'] [Init:848] Calling: VpxdLdap::Init()

2012-05-31T09:11:32.121-04:00 [7FFFF3B09700 info 'Default'] [LdapBackup] Making sure LDAP instance VMwareVCMSDS is running

2012-05-31T09:11:32.121-04:00 [7FFFF3B09700 info 'Default'] [LdapBackup] Checking service ldap for running

2012-05-31T09:11:32.179-04:00 [7FFFF3B09700 info 'Default'] [Init:849] Calling: VpxResultFilter::Init()

2012-05-31T09:11:32.179-04:00  [7FFFF3B09700 info 'Default'] Looking for vpx result filter at  /usr/lib/vmware-vpx/vpxResultFilter.xml

2012-05-31T09:11:32.184-04:00 [7FFFF3B09700 info 'Default'] [Init:853] Calling: VpxdLock::Init(gDB)

2012-05-31T09:11:32.184-04:00 [7FFFF3B09700 info 'Default'] [Init:854] Calling: VpxdMoLock::Init()

2012-05-31T09:11:32.184-04:00 [7FFFF3B09700 info 'Default'] [Init:855] Calling: VpxdStateLock::Init()

2012-05-31T09:11:32.184-04:00 [7FFFF3B09700 info 'Default'] [Init:856] Calling: VpxdMoDataTable::Init()

2012-05-31T09:11:32.184-04:00  [7FFFF3B09700 info 'Default'] [Init:858] Calling:  VpxdHeartbeat::Init(MakeFunctor(this, &ServerApp::RequestShutdown))

2012-05-31T09:11:32.184-04:00 [7FFFF3B09700 info 'Default'] [Init:859] Calling: VpxdHostCnx::Init(gDB)

2012-05-31T09:11:32.189-04:00 [7FFFEAA06710 info 'Default' opID=SWI-75fe915a] Pre-loading symbols...

2012-05-31T09:11:32.190-04:00 [7FFFEAA06710 info 'Default' opID=SWI-75fe915a] Done pre-loading symbols.

2012-05-31T09:11:32.196-04:00 [7FFFF3B09700 info 'Default'] [Init:861] Calling: VpxdVmomi::Init()

2012-05-31T09:11:32.198-04:00  [7FFFF3B09700 info 'Default'] Looking for vpx result filter at  /usr/lib/vmware-vpx/vpxResultFilter.xml

2012-05-31T09:11:32.200-04:00 [7FFFF3B09700 info 'Default'] [Init:862] Calling: QueryServiceProviderHelper::Init()

2012-05-31T09:11:32.201-04:00 [7FFFF3B09700 info 'QueryServiceProvider'] Initializing QueryServiceProviderHelperImpl

2012-05-31T09:11:32.240-04:00 [7FFFF3B09700 info 'QueryServiceProvider'] Starting with generation number: 5230290

2012-05-31T09:11:32.240-04:00 [7FFFF3B09700 info 'Default'] [Init:863] Calling: ServiceDirectory_Init()

2012-05-31T09:11:32.240-04:00  [7FFFF3B09700 info 'Default'] [ServiceDirectory] Local instance UUID:  DB25B17D-3703-4779-BAFB-845B64AC33AA

2012-05-31T09:11:32.245-04:00 [7FFFF3B09700 warning 'VpxProfiler'] ServerApp::Init [TotalTime] took 2578 ms

2012-05-31T09:11:32.246-04:00 [7FFFF3B09700 error 'Default'] [VpxdMain] Failed to initialize: Name or service not known

2012-05-31T09:11:32.246-04:00 [7FFFF3B09700 error 'Default'] Failed to intialize VMware VirtualCenter. Shutting down...

2012-05-31T09:11:32.246-04:00 [7FFFF3B09700 info 'Default'] Wrote uptime information

2012-05-31T09:12:32.701-04:00 [7FFFF3B09700 info 'Default'] Forcing shutdown of VMware VirtualCenter now

and the process itself

vsphere-fmrif:~ # service vmware-vpxd status
vmware-vpxd is stopped
tomcat is stopped
vsphere-fmrif:~ # service vmware-vpxd start
Waiting for embedded DB2 database to startup: .success
Cleaning session lock table: success
Verifying EULA acceptance: success
Shutting down ldap-server..done
Starting ldap-server..done
Starting vmware-vpxd: success
Waiting for vpxd to initialize: ....failed

I have a separate PSC and VCSA at version 6.5 U2.  I have upgraded both to version 6.7 U2 from the ISO and am now trying to converge to one VM.  I have mounted the VCSA ISO on the VCSA 6.7 VM as I don't have internet access from these machines.  The converge process is started succesfully from the GUI but then fails.  looking at the converge.log on the VCSA I see the first error is 'ERROR converge Unable to run ldapsearch'

then it later says 'ERROR converge Failed to run white listed firstboot scripts'

I have checked the converge_status.json file and it indicates firstboot stage 1 of 4 failed.

All DNS is working correctly and I am unsure what to check next with this.  It is a lab environment so I can try things out without affecting any prod systems.  Any suggestions on how to resolve this?

Thanks

Chris

Dear Team

How can we reset password on Vcenter 6.0 ?

Hi Guys,

Hopefully something you can assist me with to stop me from ripping anymore of my hair out   For the last few days, I have been trying to add our VCSA to our domain so that I can setup the SSO domain.

This is a brand new deployment - 6.0 all around.  We are using the embedded VCSA with an embedded deployment.  When I go to join the domain, I get the following error:

Idm client exception: Error trying to join AD, error code [11], user [Administrator@mydomain], domain [mydomain], orgUnit []

I have replaced our domain name with 'mydomain' above - any ideas?

We plan to deploy a new vCenter appliance as an initial step to executing embedded linked mode between the new appliance and the existing one.

This will be followed by moving some of the hosts with their VMs from the original vCenter to the new vCenter. Running VMs must not be impacted and VMs across the two vCenters are reachable to each other the same before they moved out.

still determining the approach to achieve this, the considered steps

Deploy new appliance

Join to existing SSO

Create identical VLAN/Port Groups in new vCenter

(This host which planned to be moved later to new vCenter)

Create a new empty host cluster in new vCenter

Evacuate target host and move it from source vCenter to new vCenter under new host cluster

Mount a new datastore to the moved host

SVmotion VMs to new datastore and moved host

Repeat the same for the second host.

Not sure if this plan is doable or missing pieces or order is not quite right, I am open to any idea or recommendations for achieving this task. Thanks

While upgrading vCSA 6.0U3 to 6.5U1, the pre-upgrade check shows the following warning.

User vdcs does not have the expected uid 1006

Suggested Resolution: Please refer to the corresponding KB article.

The vdcs user indeed has UID 1007 (UID 1006 is in use for another user), but it's a default installation, i.e. all users were created automatically.

I also cannot find any KB article for this.

Does this need to be fixed (how)? Will it cause any issues if this user has a uid other than 1006?

André

Hi experts,

I tried to install vCenter 6.0, and got the following error:

• Installation of component VCSServiceManager failed with error code '1603'. Check the logs for more details.

Checked the release notes, ipv4 stack is all fine.

I tried a couple of times, couldn't overcome this. Also tried to upgrade from 5.5 to 6.0, failed with the same error.

How can I overcome this?

Thanks a lot for your help!

Forget to mention: I am installing this on Windows Server 2008 R2 Standard

Hello.

Have big problem with vSphere client

Today i press button Clear SSL certificate in IE on my Windows 7 OS

Then i faced with strange issue

I'm trying connect to vm console (client connected to vCenter) and i have an error ssl verification failure for "ip" due to a host thumbprint mismatch.

It's happend again then i trying to connect directly to ESXI

vCenter version 5.0,ESXi 5.0

What I tried to do - clear SSL ignore by regedit, reinstall vSphere client - it's not resolve a problem

I'm still not able to connect to any VM console

I'm trying connect from websphere - no luck,same error

Then i install client on different machine - all running ok

I'm trying to create a gold template for provisioning guests from using current version of CentOS 8, however, VMware Customzation Specification seems to be just completely broken for it. I have the latest version of open-vm-tools and perl packages installed. If I try to customize the OS and give it the network configuration, the VM starts up without hostname being changed (to the VM name) and the NIC has no IP at all. What am I missing? I'm also using EFI boot, which is recommended for CentOS 8.

Here are the environment information:

- ESXi 6.7u3

- vCenter 6.7u3

- CentOS 8.0.1905

- open-vm-tools 10.3.0-2.el8

- perl 5.26.3-416.el8

Hello.

We are thinking about to upgrade our vSphere environment to the following version mix (from VMware site OK?!):

ESXi     5.5U3 (Upgrade to 6.5 is not possible due Storage)

vCSA     6.5

Does anybody have experience with this mix in an production environment?

Thanks.

K

Hey all,

I just wanted to update a vCSA appliance. Unfortunately it hangs in the status "Checking for aivailable updates..." as has no internet access.

I changed the settings to CD-ROM  updates, mounted the update-repo iso and restarted the appliance, but no luck, it's still in the checking for updates mode.

Anyone has an idea how to stop this process? As the check and install update buttons are disabled during the update search.

Thanks

Tim

Hello. Can anybody help me, please. When i`m resetting passoword for administrator@vsphere.local in my Vsphere 6, i get such error:

"VmDirForceResetPassword failed (5)"

What am i doing wrong?

For resetting `ve used KB manual: VMware KB: Unlocking and resetting the VMware vCenter Single Sign-On administrator password

Please help.

When installing a second vCenter I keep running into the errors:

1. Firstboot script execution error.

2. The supplied System Name vcenter-01.domain.local is not valid.

3. If the supplied system name is a FQDN, then make sure the DNS forward lookup results in at least one valid IP address in the system. If the supplied system name is an IP address, then it should be one of the valid IP address(es) in the system.

This is a second vCenter install I am working on. I installed a vCenter 6 appliance with the psc and vCenter in our DR creating creating the vsphere.local (we are installing new hardware and moving from 5.0) just fine. At our Prod site I am running the appliance iso using a newly setup esxi 6 u1 host. I join the SSO site and create a new site name or join the existing, I am using a dvgroup with a Ephemeral port on the dvSwitch. I have triple checked the DNS settings. There is a host and pointer record for the esxi 6 host and appliance, I can run a nslookup from multiple machines with no issues.

Any thoughts as I am stuck.

Hi Team, I'm trying to install vcsa 6.7 and I'm having issues with my DNS is there a way I can install without a DNS. I do have a DNS but when I'm in the server room I'm unbale to ping any machines its probably the network connection?

launched with the shell command shell but the pi still reset password does not work

==================

Please select:

0. exit

1. Test LDAP connectivity

2. Force start replication cycle

3. Reset account password

4. Set log level and mask

5. Set vmdir state

==================

3

  Please enter account UPN : cn=administrator,cn=users,dc=vSphere,dc=local

VmDirForceResetPassword failed (9106)

==================

Please select:

0. exit

1. Test LDAP connectivity

2. Force start replication cycle

3. Reset account password

4. Set log level and mask

5. Set vmdir state

==================

3

  Please enter account UPN : Administrator@vSphere.local

VmDirForceResetPassword failed (9106)

vcenter VMware vCenter Server Appliance 6.0.0.20000

Hi,

from time to time the VCSA 6.5e statsmonitor service stops unexpectedly. This breaks the ability to backup VCSA data via PowerCLI script. Another consequence is that there are no CPU/Memory/Database Statistics collected in VCSA management backend.

vRealize LogInsight Log excerpt is attached for the considered timeframe and filtered by "statsmonitor". I cannot tell from this log why it tried to add this service, tried to start it and then failed.

So the stop occurred on June, 13th for the last time. It remained stopped since then. Before June, 13th, I realized it and fixed it on June, 8th.

I see this problem occurring one one of our VCSA 6.5 instances but not on the other ones.

Does anyone else see this behavior or any idea what's wrong?

Hello. After rebooting, I could not connect to Vcentr every time I received a 503 error When I start vmware-vpxd manually, I get the following error. What is Stderr = Key not found: vpxd / secureSoapPort? How to fix  and what to do? Help me please! Thank!

service-control --start vmware-vpxd

INFO:root:Service: vmware-vpxd, Action: start

Service: vmware-vpxd, Action: start

2019-01-28T19:29:57.828Z   Running command: ['/sbin/chkconfig', u'vmware-vpxd']

2019-01-28T19:29:57.958Z   Done running command

2019-01-28T19:29:57.958Z   Running command: ['/sbin/service', u'vmware-vpxd', 'status']

2019-01-28T19:29:58.532Z   Done running command

2019-01-28T19:29:58.532Z   Running command: ['/sbin/chkconfig', '--force', u'vmware-vpxd', 'on']

2019-01-28T19:29:58.595Z   Done running command

2019-01-28T19:29:58.595Z   Running command: ['/sbin/service', u'vmware-vpxd', 'start']

2019-01-28T19:30:01.535Z   Done running command

2019-01-28T19:30:01.536Z   Invoked command: ['/sbin/service', u'vmware-vpxd', 'start']

2019-01-28T19:30:01.536Z   RC = 1

Stdout = Key not found: vpxd/secureSoapPort

vmware-vpxd: VC SSL Certificate does not exist, it will be generated by vpxd

Waiting for the embedded database to start up: success

Executing pre-startup scripts...

vmware-vpxd: Starting vpxd by administrative request.

success

vmware-vpxd: Waiting for vpxd to start listening for requests on

Waiting for vpxd to initialize: Usage: wait_for_vpxd.py [options]

wait_for_vpxd.py: error: -p option requires an argument

failed

failed

vmware-vpxd: vpxd failed to initialize in time.

vpxd is already starting up. Aborting the request.

Stderr = Key not found: vpxd/secureSoapPort

2019-01-28T19:30:01.536Z   {

    "resolution": null,

    "detail": [

        {

            "args": [

                "Command: ['/sbin/service', u'vmware-vpxd', 'start']\nStderr: Key not found: vpxd/secureSoapPort\n"

            ],

            "id": "install.ciscommon.command.errinvoke",

            "localized": "An error occurred while invoking external command : 'Сommand: ['/sbin/service', u'vmware-vpxd', 'start']\nStderr: Key not found: vpxd/                                                                      secureSoapPort\n'",

            "translatable": "An error occurred while invoking external command :'%(0)s'"

        }

    ],

    "componentKey": null,

    "problemId": null

}

ERROR:root:Unable to start service vmware-vpxd, Exception: {

    "resolution": null,

    "detail": [

        {

            "args": [

                "vmware-vpxd"

            ],

            "id": "install.ciscommon.service.failstart",

            "localized": "An error occurred while starting service 'vmware-vpxd'                                                                      ",

            "translatable": "An error occurred while starting service '%(0)s'"

        }

    ],

    "componentKey": null,

    "problemId": null

}

Unable to start service vmware-vpxd, Exception: {

    "resolution": null,

    "detail": [

        {

            "args": [

                "vmware-vpxd"

            ],

            "id": "install.ciscommon.service.failstart",

            "localized": "An error occurred while starting service 'vmware-vpxd'                                                                      ",

            "translatable": "An error occurred while starting service '%(0)s'"

        }

    ],

    "componentKey": null,

    "problemId": null

}

I deployed a Vm from template using a customization template. I made sure the Vm deployed had NIC connected when i selected finished. But after the clone, the VM came up with nic disconnected

any idea?

I installed a new copy of vCenter 6.5.0. One host added. While installing VDP appliance, vSphereDataProtection-6.1.3.ova, I get the following error

  Failed to deploy OVF package.

  Cause:
  A specified parameter was not correct:
  The checksum(s) from the provided manifest file do not match the content of file(s): vSphereDataProtection-0.0TB-disk1.vmdk.

The deploy asked for all the deployment details, where, DNS, IPs, etc. then ran a few minutes to about 65% completion when error occurred.