Hi community,
I have a problem with my VC2.5 and ESX3.5.
50% of all actions results in "An error occurred while communicating with the remote host". The 2nd try mostly works, sometimes i have to do another try.
I start an action, the host disconnects and a few seconds later the host is back and i can give it another try. The error occures on every host i have.
Can anyone help me, please?
TIA,
Sascha
Hello
Since we have updatet from ESXi 4.1 to Update 1 we have problems with taking quiesced snapshot. Before we have installed the update 1 quiesced snapshot worked witout problems.
When we take a quiesced snapshot, Windows 2008 R2 mount a new volumes and remove them after the snapshot is taken.
In the Eventlog i can see following errors and infos:
multiple entrys from this 2 event:
Log Name: System
Source: Virtual Disk Service
Date: 11.04.2011 22:40:26
Event ID: 3
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Description:
Service started.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Virtual Disk Service" />
and
Log Name: System
Source: Service Control Manager
Date: 11.04.2011 22:40:26
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: TESTTEMPLATE.gef.be.ch
Description:
The Virtual Disk service entered the running state.
and
Log Name: System
Source: Ntfs
Date: 11.04.2011 22:20:57
Event ID: 57
Task Category: (2)
Level: Warning
Keywords: Classic
User: N/A
Description:
The system failed to flush data to the transaction log. Corruption may occur.
and
Log Name: System
Source: Ntfs
Date: 11.04.2011 22:20:57
Event ID: 137
Task Category: (2)
Level: Error
Keywords: Classic
User: N/A
Description:
The default transaction resource manager on volume \\?\Volume{d533451f-6478-11e0-94e8-005056ae007a} encountered a non-retryable error and could not start. The data contains the error code.
and
Log Name: Application
Source: VSS
Date: 11.04.2011 18:05:48
Event ID: 12289
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: G3110SRV014APL.gef.be.ch
Description:
Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\fdc#generic_floppy_drive#6&2bc13940&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} - 0000000000000418,0x00560000,0000000000000000,0,000000000027CDB0,4096,[0]). hr = 0x80070001, Incorrect function.
.
Operation:
Exposing Recovered Volumes
Locating shadow-copy LUNs
PostSnapshot Event
Executing Asynchronous Operation
Context:
Device: \\?\fdc#generic_floppy_drive#6&2bc13940&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
Examining Detected Volume: Existing - \\?\fdc#generic_floppy_drive#6&2bc13940&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
Execution Context: Provider
Provider Name: VMware Snapshot Provider
Provider Version: 1.0.0
Provider ID: {564d7761-7265-2056-5353-2050726f7669}
Current State: DoSnapshotSet
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">12289</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-04-11T16:05:48.000000000Z" />
<EventRecordID>6430</EventRecordID>
<Channel>Application</Channel>
<Security />
</System>
<EventData>
<Data>DeviceIoControl(\\?\fdc#generic_floppy_drive#6&2bc13940&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} - 0000000000000418,0x00560000,0000000000000000,0,000000000027CDB0,4096,[0])</Data>
When we remove the snapshot the vm freeze for about 30second (no Ping no RDP)
Have anyone the same issue?
I have try to install a new clean server 2008 r2 but have the same problem.
Best Regards
Simon
When running VI Client 4 or 4 U1, on Vista SP1 x64, I get the following error message.
The type initializer for threw an exception for 'VirtualInfrastructure.Utils.ClientsXml' threw an exception.
and the VI Client exists.
Any ideas, I've found similiar with users running on Windows 7, I've followed those treads, but it still gives me the error message, VI Client used to work, but has stopped.
e.
Hi
I'm using vCenter 5.5 with WEB vSphere GUI to take a snapshot of a RHEL 5.4 32 based VM on a ESXi 5.5. When I choose the "Quiesce the guest file system" instead of the "snapshot the virtual machine memory", the snapshot creation failed at 90% with "An error occurred while taking a snapshot: Failed to quiesce the virtual machine" .
I have no problem using the "snapshot the virtual machine memory" option to create the snapshot.
Your help is appreciated
Ren Wong
Hi,
I have been testing out the latest vSphere, and have ran in to an issue with the vCenter Server Appliance.
I was able to access it via its web address as well as by the vSphere Client but after I rebooted the host that it was running on I can no longer access it.
This is for both the web address and client.
When I go to the address i get the usual certificate warning but after that I get:
A server error occurred.
[500] SSO error: Cannot connect to the VMware Component Manager
The vCenter Server Appliance is a virtual instance on the host.
I am able to connect directly to the host and the VM is running, as I can open the console session to it.
All this occurred after I rebooted the host to complete the install of the Mega RAID CLI and LSI Provider .VIB's
Any ideas?
Thanks,
Marcus
Hi everyone
We had a scheduled maintenance window over the weekend while some work was carried out elsewhere in the building. As a precaution we shutdown the infrastructure that we we still keep onsite (the rest is in colo). So all we have is a 2 node ESXi cluster, managed by vCenter Server Appliance (Novell SUSE Linux Enterprise 11 64bit). It only has 6 VMs running on it as most of them have been migrated offsite.
This morning we started up the OpenFiler NFS storage box and the ESXi nodes. All VMs started ok, including the vCenter Server Appliance.
However I was unable to connect to the vCenter Appliance using vSphere Client. I could connect to the ESXi nodes directly without problems. DNS hostnames all resolve to the IP addresses without problems.
Looking at the vSphere Client logs I see the following message each time I tried to connect:
System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.10.0.205:443
So I connected to the vCenter Appliance over SSH and it looks like it's run out of disk space. Here's the df and mount output:
vlevcenter01:/ # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 9.8G 9.8G 0 100% /
devtmpfs 4.0G 104K 4.0G 1% /dev
tmpfs 4.0G 4.0K 4.0G 1% /dev/shm
/dev/sda1 130M 18M 105M 15% /boot
/dev/sdb1 20G 3.8G 15G 21% /storage/core
/dev/sdb2 20G 717M 18G 4% /storage/log
/dev/sdb3 20G 19G 0 100% /storage/db
vlevcenter01:/ # mount -l
/dev/sda3 on / type ext3 (rw,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
devtmpfs on /dev type devtmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,mode=1777)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/sda1 on /boot type ext3 (rw,acl,user_xattr)
/dev/sdb1 on /storage/core type ext3 (rw)
/dev/sdb2 on /storage/log type ext3 (rw)
/dev/sdb3 on /storage/db type ext3 (rw)
So the database and root partitions have run out of space. Looking in /var/log/localmesages:
Jul 15 10:10:51 vlevcenter01 startproc: startproc: Empty pid file /var/run/slapd/slapd.pid for /usr/lib/openldap/slapd
Jul 15 10:10:51 vlevcenter01 startproc: startproc: exit status of parent of /usr/lib/openldap/slapd: 1
Jul 15 10:10:52 vlevcenter01 checkproc: checkproc: Empty pid file /var/run/slapd/slapd.pid for /usr/lib/openldap/slapd
It looks like it can't create the pid files for the services because there is no disk space.
We already have 60GB of vmdks allocated to this VM though we do have space on our datastore to add more. But I'm concerned that the vCenter Appliance will just grow and grow.
1) Is there any scheduled maintenance that runs on the vCenter Appliance to keep disk usage under control? This is what I would expect from an enterprise product, I'm very surprised to see such a problem happen.
2) Where should I start looking to clear some disk space so we can get the vCenter service back up and running?
I'd like to find a longer term solution to this otherwise we might have to just keep adding vmdks until our datastore runs out of space.
Cheers, B
I cannot open the vcsa-setup.html file, it claims it needs a "Client Integration Plug-In".
I successfully installed the Client Integration Plug-In from the vsca directory on the CD.
However, neither Internet Explorer nor Chrome "detected" the plug-in when I tried to open the file again.
I uninstalled the plug-in again (because I installed it before Chrome the first time and thought maybe it needed installing after the browser).
Now it won't install again.
VMware-ClientIntegrationPlugin-6.0.0.exe fails with an alert
"There is a problem with this Windows installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor."
Before clicking OK I checked the directory "C:\Program Files (x86)\VMware\Client Integration Plug-in 6.0" and the plug-in appears to be fully installed. However, after confirming the alert, the installer undoes the installation performed so far.
VMware-ClientIntegrationPlugin-6.0.0.exe /l c:\tmp\integration.log creates a log file that tells me that the error is rather unclear. This is what it says in the last few lines before confirming the alert box:
MSI (s) (1C:4C) [22:04:17:004]: Executing op: CustomActionSchedule(Action=CsdServiceInstall,ActionType=3090,Source=C:\Program Files (x86)\VMware\Client Integration Plug-in 6.0\vmware-csd.exe,Target=--install,)
CustomAction CsdServiceInstall returned actual error code 3 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (1C:4C) [22:04:17:050]: Note: 1: 1722 2: CsdServiceInstall 3: C:\Program Files (x86)\VMware\Client Integration Plug-in 6.0\vmware-csd.exe 4: --install
MSI (s) (1C:4C) [22:04:17:050]: Note: 1: 2205 2: 3: Error
MSI (s) (1C:4C) [22:04:17:050]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1722
After clicking OK, it continues:
Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action CsdServiceInstall, location: C:\Program Files (x86)\VMware\Client Integration Plug-in 6.0\vmware-csd.exe, command: --install
MSI (s) (1C:4C) [22:12:29:202]: Note: 1: 2205 2: 3: Error
MSI (s) (1C:4C) [22:12:29:202]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (1C:4C) [22:12:29:202]: Product: VMware Client Integration Plug-in 6.0.0 -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action CsdServiceInstall, location: C:\Program Files (x86)\VMware\Client Integration Plug-in 6.0\vmware-csd.exe, command: --install
Action ended 22:12:29: InstallFinalize. Return value 3.
What do I do now?
Hi Guys,
We are currently backing up our exchange server with the bog standard backup which comes with windows (windows backup), which is saving to the hyper-v vhdx file type, what is the best way to go about converting the file from vhdx to vmdk?
While in vcenter, the summary tab for a host displays this message:
"This host currently has no management network redundancy"
I attached pictures of the Host > Configuration > Networking and Host > Configuration > Networking Adapters pages. It looks to me like the management network is behind 2 nics teamed together.
What am I doing wrong? How can I fix this?
Thanks
How do you view older tasks/events? The client only allows you to go back 1000 items? how do you see older than that ?
Thanks
When selecting a VM to migrate the option to migrate is greyed out. In fact, Power On, Migrate, Revert to Current Snapshot are greyed out. I would like to migrate this VM to another host and datastore.
ESXi version 5.1.0 build 1021289
VMware vCenter Server, 5.1.0 build 947673
I've migrated 154 VMs and out of the 154 VMs migrated approximately a dozen VMs would not allow for live migrations(migrate... option greyed out). I could not identify any commonality between the dozen VMs that did not allow for live migrations.
I really need to migrate this VM in a live state if at all possible.
When vCenter checks to see if a VM is a valid candidate to migrate, what does it check for because the migrate option is NOT grey for about a second before it becomes greyed out?
I'm trying to import an OVA via the vSphere Flash Client. The VCSA is running 6.5 GA, however I@m getting the following error.
The SSL certificate is imported and as you can see from the attached screenshot, there are no SSL warnings in the browser.
The VCSA was configured with the IP as it's system name. I think there is another issue and the SSL warning is just a guess at the problem.
Has anyone else seen this behavior before? The particular OVA file imported fine with 6.0. I'm unable to import it via ESXi because it needs to be done via the VC due to an error trying it that way earlier.
The operation failed for an undetermined reason. Typically this problem occurs due to certificates that the browser does not trust. If you are using self-signed or custom certificates, open the URL below in a new browser tab and accept the certificate, then retry the operation.
Screenshot attached
I am testing vSphere 5.5 in our lab and I am experiencing some issues with vCenter Server or SSO. After a fresh install all works about fine, I can add AD authentication to SSO and AD login works to vSphere Client. I was having issues with vCenter Orchestator login so I rebooted vCenter Server VM. After a Windows reboot vCenter Server is no longer starting, it tries to start but SSO fails and vCenter Server process shuts down. Below is a snippet from vpxd.log with relevant output.
Domain Controller is Windows Server 2012.
vCenter Server and SSO is on Windows Server 2008 R2.
2013-09-28T12:49:09.679+03:00 [04988 info 'dbdbPortgroup'] [VpxdInvtDVPortGroup::PreLoadDvpgConfig] loaded [0] dvpg config objects
2013-09-28T12:49:09.685+03:00 [04988 info '[SSO][SsoFactory_CreateFacade]'] Solution user set to: vCenterServer_2013.09.26_125138
2013-09-28T12:49:09.685+03:00 [04988 info '[SSO][SsoFactory_CreateFacade]'] VC's ServiceId in LookupService: Default-First-Site:b0f86720-9fa6-42b5-aaf4-26d700d6152a
2013-09-28T12:49:09.685+03:00 [04988 info '[SSO][SsoFactory_CreateFacade]'] STS URI set to: https://vCenter.vclass.local:7444/sts/STSService/vsphere.local
2013-09-28T12:49:09.685+03:00 [04988 info '[SSO][SsoFactory_CreateFacade]'] Admin URI set to: https://vCenter.vclass.local:7444/sso-adminserver/sdk/vsphere.local
2013-09-28T12:49:09.685+03:00 [04988 info '[SSO][SsoFactory_CreateFacade]'] Groupcheck URI set to: https://vCenter.vclass.local:7444/sso-adminserver/sdk/vsphere.local
2013-09-28T12:49:09.685+03:00 [04988 info '[SSO][SsoFactory_CreateFacade]'] VC SSL certificate location: C:\ProgramData\VMware\VMware VirtualCenter\ssl\rui.crt
2013-09-28T12:49:09.685+03:00 [04988 info '[SSO][CreateSsoFacade]'] [CreateUserDirectory] STS URI set to: https://vCenter.vclass.local:7444/sts/STSService/vsphere.local
2013-09-28T12:49:09.685+03:00 [04988 info '[SSO][CreateSsoFacade]'] [CreateUserDirectory] Admin URI set to: https://vCenter.vclass.local:7444/sso-adminserver/sdk/vsphere.local
2013-09-28T12:49:09.685+03:00 [04988 info '[SSO][CreateSsoFacade]'] [CreateUserDirectory] Groupcheck URI set to: https://vCenter.vclass.local:7444/sso-adminserver/sdk/vsphere.local
2013-09-28T12:49:09.737+03:00 [04988 warning 'Default'] Closing Response processing in unexpected state: 3
2013-09-28T12:49:09.740+03:00 [04988 error '[SSO][SsoFactory_CreateFacade]'] Unable to create SSO facade: Invalid response code: 404 Not Found.
2013-09-28T12:49:09.741+03:00 [04988 error 'vpxdvpxdMain'] [Vpxd::ServerApp::Init] Init failed: Vpx::Common::Sso::SsoFactory_CreateFacade(sslContext, ssoFacadeConstPtr)
--> Backtrace:
--> backtrace[00] rip 000000018018cd7a
--> backtrace[01] rip 0000000180106c48
--> backtrace[02] rip 000000018010803e
--> backtrace[03] rip 00000001800907f8
--> backtrace[04] rip 00000000003f5bac
--> backtrace[05] rip 0000000000416722
--> backtrace[06] rip 000000014075dd5a
--> backtrace[07] rip 00000001407578bc
--> backtrace[08] rip 000000014098800b
--> backtrace[09] rip 000007feff17a82d
--> backtrace[10] rip 0000000076ef652d
--> backtrace[11] rip 000000007712c541
-->
2013-09-28T12:49:09.742+03:00 [04988 warning 'VpxProfiler'] ServerApp::Init [TotalTime] took 3520 ms
2013-09-28T12:49:09.742+03:00 [04988 error 'Default'] Failed to intialize VMware VirtualCenter. Shutting down...
I am running the most current versions of eveything.
ESX 4.0 Update 1
and the latest builds of vcenter server and client.
My workstation is running server 2008 x64
I am using remote desktop (RDP) to go from my client workstation into a VM that is running vcenter client.
The VM is server 2008 R2.
When trying to work inside any console session from within the vi client my mouse disappears as soon as I click inside the console window. The mouse still works. If I right click somewhere I see menus pop up, etc. It's just that the pointer completely vanishes. (the cursor is visible during the ctrlaltdel logon screen)
Through means of troubleshooting here are the things that I have found out.
When VMware tools is not installed the problem does not occur (but the mouse is choppy so this isn't a fix)
When VMware tools IS installed, but the pointing device driver is changed from "vmware pointing device" to "PS/2 compatible mouse" the problem does not occur
When VMware tools IS installed and the pointing device driver is the default "vmware pointing device" and "enable pointer shadow" is enabled in the mouse properties the problem does not occur. However by enabling the pointer shadow it makes my mouse rather choppy, so this still isn't a solution.
It looks as though there is something funky going on when using 2008 in conjuction with RDP and working inside VM consoles.
Has anyone else seen this behavior?
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?
Hi,
I have successfully migrated from VC 6.0 for Windows to VCSA 6.5 as I wanted to get freed Windows Server license. All is working correctly except Update Manager. I'm still getting error "VMware vSphere Update Manager had an unknown error. Check the events and log files for details." when I tried to scan for updates. I'm new to VCSA, so please which logs exactly I need to look in? on VCSA ? or ESXi itself?
Thanks
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
can anybody help me , I am facing some problem related to v center server 5.5 connectivity . we are using esxi 5.5 and on this esxi5.5 we are running VM . On this single vm we have installed v center server , single sign on , inventory services (without any error) . when I am trying to connect vcenter server through v center client one error occurred vsphere client could not connect to ip add .you don't have a permission to login to the server ip.
Hello ,
Below vCenter 6.0 U1 alarm frequently changing, any idea ?
alarm.VsphereClientHealthAlarm - Event: Status change (7582963) Summary: vsphere-client status changed from green to yellow Date: 9/21/2015 12:05:53 PM Arguments: componentId = vsphere-client componentName = vsphere-client newStatus = yellow oldStatus = green serviceId = vsphere-client
regards
Surya
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