Hi Gurus

I have the following problem, my vcenter was upgraded to 5.1 but once the server was rebooted the following service did not start and I cant get them to start.

VmWare Virtualcenter server

VmWare Virtualcenter Management webservies

VmWare Virtualcenter server service which throws me the following error

   " The vmware virtualcenter server service on local computer started and then stopped.Some services stops automatically if they are not in use by other services or program"

VmWare Virtualcenter Management webservices services throws the error

"  error 1068:the dependency service or group failed to start  "

  I take once the virtualcenter server gets up and running the next service will work.

  1) I have  checked log on account

  2) I have checked connection to database

  3) Restarted SSO services

Gurus I  need help so any would be appreciated

Thanks a bunch

I've got three hosts in a DRS cluster.  Two of them set up HA without any problems, but the 3rd node has been having issues.  I've verified DNS (less than 30 characters) and that the gateway is set up correctly.  There are no VM's on this server right now, so I know there isn't anything inside there that would cause a problem. 

The only thing I can find in the addnode.log is that its complaining that prot 8042 is not available, but I can't find any processes that are using this port.

Output of the log:

CMD: /opt/LGTOaam512/bin/ft_setup -domain=vmware -upgrade=n -noprompt=y -hostname=dtc-vmesx2 -port1=8042 -licensekey=AMCFNEET-4YRDDN53CTHMBDSJ -mailserver=none -primaryagent=dtc-vmesx3

RESULT:

\----

Legato Automated Availability Manager setup script.

Setting environment from /opt/LGTOaam512/config/agent_env.Linux

Setting up the Legato Automated Availability Manager agent for domain vmware

            Welcome to Automated Availability Manager.  (Release 5.1 )

Configuring Agent for current node: dtc-vmesx2

Enter the name of your domain \[vmware]:

Using comand line argument domain of :  vmware

A previous installation has been detected in this directory.

Is this a software upgrade? (y/n) :

Upgrade command line argument: n

WARNING: your previous configuration and database will be overwritten.

Do you want to continue? (y/n) :

Configuration requires the node name of a primary agent. If you

are configuring the first node in the domain, enter the name

of this node. (i.e. dtc-vmesx2)  If this is a subsequent installation

enter the name of an existing primary agent node.

Enter the name of a Primary Agent Node:

Using input argument of dtc-vmesx3 for Primary Agent

Agents require the use of 4 network ports through which to

communicate.  These port numbers must be available and consistent

across each of the nodes in the domain. If you are unsure about

specifying port numbers or defining primary nodes please read the

appropriate sections of the user documentation provided with this

product.

Specify the first of the 4 port numbers: \[8042]

Using argument for port1: 8042

Bind info: Cannot assign requested address

That port 8042 is currently in use, please select again

Enter the starting port number: Error: Port currently in use! at /opt/LGTOaam512/bin/ft_setup.pl line 638,  line 13.

Copying /opt/LGTOaam512/config/vmware-sites to /opt/LGTOaam512/log/aam_config_util_addnode.log

Total time for script to complete:  0 minute(s) and 0 second(s)

output of netstat

Active Internet connections (w/o servers)

Proto Recv-Q Send-Q Local Address               Foreign Address             State     

tcp        0      0 127.0.0.1:199               127.0.0.1:33344             TIME_WAIT  

tcp        0      0 127.0.0.1:199               127.0.0.1:33345             TIME_WAIT  

tcp        0      0 127.0.0.1:199               127.0.0.1:33346             TIME_WAIT  

tcp        0      0 127.0.0.1:199               127.0.0.1:33347             TIME_WAIT  

tcp        0      0 127.0.0.1:199               127.0.0.1:33348             TIME_WAIT  

tcp        0      0 127.0.0.1:199               127.0.0.1:33349             TIME_WAIT  

tcp        0      0 127.0.0.1:199               127.0.0.1:33350             TIME_WAIT  

tcp        0      0 127.0.0.1:199               127.0.0.1:33351             TIME_WAIT  

tcp        0      0 127.0.0.1:199               127.0.0.1:33352             TIME_WAIT  

tcp        0      0 10.0.130.196:32823          10.0.130.196:8402           ESTABLISHED

tcp        0      0 127.0.0.1:32788             127.0.0.1:32787             ESTABLISHED

tcp        0      0 127.0.0.1:32787             127.0.0.1:32788             ESTABLISHED

tcp        0      0 10.0.130.196:8402           10.0.130.196:32823          ESTABLISHED

tcp        0     48 10.0.130.196:22             10.0.145.101:4321           ESTABLISHED

tcp        0      0 127.0.0.1:199               127.0.0.1:33335             TIME_WAIT  

tcp        0      0 127.0.0.1:199               127.0.0.1:33336             TIME_WAIT  

tcp        0      0 127.0.0.1:199               127.0.0.1:33337             TIME_WAIT  

tcp        0      0 127.0.0.1:199               127.0.0.1:33338             TIME_WAIT  

tcp        0      0 127.0.0.1:199               127.0.0.1:33339             TIME_WAIT  

tcp        0      0 127.0.0.1:199               127.0.0.1:33340             TIME_WAIT  

tcp        0      0 10.0.130.196:32778          10.0.130.22:8401            ESTABLISHED

tcp        0      0 10.0.130.196:32780          10.0.130.22:8401            ESTABLISHED

tcp        0      0 127.0.0.1:199               127.0.0.1:33341             TIME_WAIT  

tcp        0      0 10.0.130.196:902            10.0.130.191:2182           ESTABLISHED

tcp        0      0 127.0.0.1:199               127.0.0.1:33342             TIME_WAIT  

tcp        0      0 127.0.0.1:199               127.0.0.1:33343             TIME_WAIT  

Active UNIX domain sockets (w/o servers)

Proto RefCnt Flags       Type       State         I-Node Path

unix  9               DGRAM                    1416   /dev/log

unix  2               DGRAM                    78576 

unix  3               STREAM     CONNECTED     17583 

unix  3               STREAM     CONNECTED     17582 

unix  2               DGRAM                    17520 

unix  2               DGRAM                    13368 

unix  2               DGRAM                    9865  

unix  2               DGRAM                    8214  

unix  2               DGRAM                    7611  

unix  2               DGRAM                    2096  

unix  2               DGRAM                    1427 

Any thoughts?

This is the first time I've used a VCSA appliance, and I just find it strange that I have 11 virtual disks assigned to this appliance. Is this a normal occurrence? Here's what I see when I got to Manage Hard Disks in the VM settings.

Hard disk 1 - 12.00 GB

Hard disk 2 - 1.27 GB

Hard disk 3 - 25.00 GB

Hard disk 4 - 25.00 GB

Hard disk 5 - 10.00 GB

Hard disk 6 - 10.00 GB

Hard disk 7 - 5.00GB

Hard disk 8 - 10.00 GB

Hard disk 9 - 1.00 GB

Hard disk 10 - 10.00GB

Hard disk 11 - 5.00 GB

Hi All

I have a problem with the peformance tab not showing any data for VMs & hosts. I have done a fair bit of searching on this problem and not found an answer yet. My thoughts is that its a vCenter database problem because when I login directly to an ESXi host I can get the performance stats from the tab in question.

I have recently upgraded our three ESXi hosts from 5.0 to 5.1 build 838463 and created an new copy of vCenter 5.1 and connected the hosts to the new copy of vCenter. As far as I know the performace stats were working on 5.0 and looks like they have stopped working after the upgrade. I upgraded the hosts using update manager and installed the ISO image from Dell that included the VIB for hardware monitoring.

Environment:

3x Dell R710, 128GB RAM each

ESXi 5.1 Build 838463 Enterprise Plus

vCenter 5.1 build 880146 Standard

Please let me know if you have any ideas or suggestions, I have attached a screenshot of the graphs showing no data.

Regards,

Andrew

Hi people,

I have implemented vCenter Server 6 WEB appliance and tried to import self signed SSL Machine certificate, in order to access on vCenter web interface using that certificate for HTTPS. Certificate was signed by Windows Server 2008 CA with template configured using these instrustions: Creating a Microsoft Certificate Authority Template for SSL certificate creation in vSphere 6.0 (2112009) | VMware KB. Also, I tried to import Comodo Trial Positive SSL certificate with same issue - couldn't import it.

I used the VMCA script for certificate management and also tried to import them manually using this procedure: vSphere 6.0 Documentation Center. In both cases, process crashed during vmware-vpxd service restarting process. VMCA script exited with rolling-back old certificates. After trying to manual replace certificates using commands certool and vecs-cli, I tried to start vmware-vpxd service using command service vmware-vpxd start. It produced following output:

virtual:~ # service vmware-vpxd start

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 8089

Waiting for vpxd to initialize: ..........................................................Fri Jun 17 14:19:51 CEST 2016 Captured live core: /var/core/live_core.vpxd.7892.06-17-2016-14-19-51

[INFO] writing vpxd process dump retry:2 Time(Y-M-D H:M:S):2016-06-17 12:19:48

.Fri Jun 17 14:20:13 CEST 2016 Captured live core: /var/core/live_core.vpxd.7892.06-17-2016-14-20-13

[INFO] writing vpxd process dump retry:1 Time(Y-M-D H:M:S):2016-06-17 12:20:01

.failed

failed

vmware-vpxd: vpxd failed to initialize in time.

End of the /var/log/messages log file contains following:

2016-06-17T14:10:04.149368+02:00 virtual vmware-vpxd: VC SSL Certificate does not exist, it will be generated by vpxd

2016-06-17T14:10:04.158972+02:00 virtual root: RHTTPPROXY_HTTP_PORT = 80

2016-06-17T14:10:04.168334+02:00 virtual root: RHTTPPROXY_HTTPS_PORT = 443

2016-06-17T14:10:04.748884+02:00 virtual vmware-vpxd: Starting vpxd by administrative request.

2016-06-17T14:10:05.811146+02:00 virtual vmware-vpxd: Waiting for vpxd to start listening for requests on 8089

2016-06-17T14:10:11.068787+02:00 virtual kernel: [ 8262.100377] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=32356 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:10:41.045286+02:00 virtual kernel: [ 8292.062481] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=32645 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:11:11.392806+02:00 virtual kernel: [ 8322.396547] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=280 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:11:41.380687+02:00 virtual kernel: [ 8352.368229] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=593 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:12:11.508805+02:00 virtual kernel: [ 8382.477595] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=905 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:12:41.124668+02:00 virtual kernel: [ 8412.078362] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=1173 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:13:11.068788+02:00 virtual kernel: [ 8442.006593] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=1480 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:13:41.052756+02:00 virtual kernel: [ 8471.975786] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=1805 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:14:10.948713+02:00 virtual kernel: [ 8501.859385] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=2068 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:14:41.048793+02:00 virtual kernel: [ 8531.942485] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=2336 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:15:01.102632+02:00 virtual /usr/sbin/cron[6935]: (root) CMD ( /usr/sbin/iiad.sh >/dev/null 2>&1)

2016-06-17T14:15:10.976770+02:00 virtual kernel: [ 8561.853765] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=2622 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:15:41.220689+02:00 virtual kernel: [ 8592.076813] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:fc:4d:d4:d2:e5:a9:08:00 SRC=192.168.0.23 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=5745 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:16:10.988809+02:00 virtual kernel: [ 8621.836572] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:3c:97:0e:32:f7:1c:08:00 SRC=192.168.0.80 DST=192.168.0.255 LEN=229 TOS=0x00 PREC=0x00 TTL=128 ID=16631 PROTO=UDP SPT=138 DPT=138 LEN=209

2016-06-17T14:16:41.200814+02:00 virtual kernel: [ 8652.031163] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=3292 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:17:11.040715+02:00 virtual kernel: [ 8681.856944] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=3595 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:17:41.012706+02:00 virtual kernel: [ 8711.812066] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=3808 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:18:10.948718+02:00 virtual kernel: [ 8741.730820] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=4046 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:18:40.936986+02:00 virtual kernel: [ 8771.705858] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=4360 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:19:11.024790+02:00 virtual kernel: [ 8801.777535] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=4647 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:19:41.144770+02:00 virtual kernel: [ 8831.881485] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=5909 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:20:01.147104+02:00 virtual /usr/sbin/cron[13172]: (root) CMD ( /usr/sbin/iiad.sh >/dev/null 2>&1)

2016-06-17T14:20:01.153980+02:00 virtual /usr/sbin/cron[13171]: (root) CMD ([ -x /usr/lib64/sa/sa1 ] && exec /usr/lib64/sa/sa1 -S ALL 1 1)

2016-06-17T14:20:01.157092+02:00 virtual /usr/sbin/cron[13175]: (root) CMD ( test -x /usr/sbin/vpxd_periodic && /usr/sbin/vpxd_periodic >/dev/null 2>&1)

2016-06-17T14:20:01.163979+02:00 virtual /usr/sbin/cron[13170]: (root) CMD ( test -x /usr/sbin/cloudvm_ram_size_periodic && /usr/sbin/cloudvm_ram_size_periodic >/dev/null 2>&1)

2016-06-17T14:20:11.664891+02:00 virtual kernel: [ 8862.387284] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=6251 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:20:23.877678+02:00 virtual vmware-vpxd: vpxd failed to initialize in time.

2016-06-17T14:20:41.260666+02:00 virtual kernel: [ 8891.967607] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=6551 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:21:10.940726+02:00 virtual kernel: [ 8921.632250] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=6906 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:21:41.452588+02:00 virtual kernel: [ 8952.121422] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:8d:f4:26:08:00 SRC=192.168.0.51 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=22577 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:22:11.080638+02:00 virtual kernel: [ 8981.739467] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=7505 PROTO=UDP SPT=137 DPT=137 LEN=58

Please help me, tell me where I made mistake. Thank you in advance.

Has anyone seen this error when trying to remove a replication agreement?

I have 6 PSCs in my domain and was removing some excess agreements. It seems like I am only getting this error when trying to remove agreements from a particular PSC

have an interesting situation in our VMware Infrastructure.   We have what appears to be 2 DataCenters observed in our vCenter Server 5.5.  All hosts are ESXi5.5.

I have always worked vMotion under the belief that I could not vMotion a VM in one DataCenter into a host on another DataCenter.   Each DataCenter supports different vLan subnets.  However, in our situation that appears NOT to be true.   We have been able to vMotion a VM from DataCenter2 to DataCenter1.   The odd thing is that we CAN NOT vMotion the other way around.  So, vMotion is only one way. 

I thought this might be explained by looking at the way the switches are setup in each DataCenter.  

DataCenter1:   Hosts on this DataCenter are setup with standard virtual switches. 

DataCenter2.   Hosts on this DataCenter are setup with dvSwitches

I don't see any VMports or management network assigned to the IP addresses on either DataCenter. 

The shared storage also is different and that is what I would expect since each DataCenter hosts its own SAN.

So, I'm confused.  How is it that a VM can vMotion across DataCenters?

Here is what I have:

- ESXi4.1

- vCenter 4.1, brand new install

- I created a new VM (Virtual Hardware v. 7, VMXNET3 NIC) which I am going to use as a template and installed Windows Server 2008 R2 from an ISO image I downloaded from Microsoft.

- Installed Windows updates and made a couple minor customization i.e. disabled UAC, firewall, IE ESC etc.

- created new guest customization specification for Windows 2008 R2 with standard parameters

     Registration info...

     Computer name - use Virtual Machine name

     Product Key - blank (tried to use KMS key as well which did not make any difference)

     Server license mode - per Seat. (tried without it as well)

     Admin Password - Standard local admin password for my company

     Time Zone - GMT

     Run Once - empty

     Join Workgroup (the template server is not on the domain)

     Generate SID.

- powered off VM

When I clone VM and use customization template it does not work. According to Tasks & Events it gets stuck at:

Started customization of VM test4. Customization log located at
C:\Windows\TEMP\vmware-imc\guestcust.log in the guest OS.

Exactly the same customization template works fine for Windows Server 2008 SP2.

What am I doing wrong?

Hi all,

I have some problems with my vcenter. version is 6.0.0.10200

First, one service is on critical warning. the vmware syslog-service reports that /storage/log has less than 15% of free space.

Second, I can't see my esxi hosts in vsphere web client, even not with vsphere.local admin. in the normal client i can see se esxi servers.

Third, I see a warning in the vsphere client: appliance management health alarm

Fourth, alert in vCenter "VMware common logging service health alarm"

I already opened a call at vmware, but i wait already 2 weeks for a response.

Thank for any advices.

Hello,

I have been trying to install a PSC inside my embedded vCenter 6 so I can move to a seperated model. The first install of the 2nd PSC failed and it is showing up in the webclient yet I cannot remove it. When i run vdcleavefed I get "leave federation cleanup failed. error 13 - confidentiality required"

See the pic I am trying to remove the highlighted PSC.

It seems as though the Content Library Service has up and vanished from my vCenter Services. I created a content library back in April. I went to delete and add an online library I built and it wouldn't work. I dug around and did some homework and found where the core services were. I used a BASH shell command to try and start it. I figured it wouldn't work, but here is what it spit back.

Has anyone had issues with their content library before?

service-control --start vmware-vdcs

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

Service: vmware-vdcs, Action: start

2015-12-30T00:00:40.321Z   Running command: ['/sbin/chkconfig', u'vmware-vdcs']

2015-12-30T00:00:40.362Z   Done running command

2015-12-30T00:00:40.363Z   Running command: ['/sbin/service', u'vmware-vdcs', 'status']

2015-12-30T00:00:40.453Z   Done running command

2015-12-30T00:00:40.454Z   Running command: ['/sbin/chkconfig', '--force', u'vmware-vdcs', 'on']

2015-12-30T00:00:40.486Z   Done running command

2015-12-30T00:00:40.486Z   Running command: ['/sbin/service', u'vmware-vdcs', 'start']

2015-12-30T00:00:56.294Z   Done running command

2015-12-30T00:00:56.294Z   Invoked command: ['/sbin/service', u'vmware-vdcs', 'start']

2015-12-30T00:00:56.294Z   RC = 1

Stdout = Starting VMware Content Library Service...

wrapper  | An encoding declaration is missing from the top of configuration file, /etc/vmware/wrapper_common.conf, trying the system encoding.

wrapper  | An encoding declaration is missing from the top of configuration file, /etc/vmware/wrapper_linux.conf, trying the system encoding.

wrapper  | Spawning intermediate process...

Waiting for VMware Content Library Service..................

WARNING: VMware Content Library Service may have failed to start.

Last login: Tue Dec 29 23:04:21 UTC 2015 on console

Stderr =

2015-12-30T00:00:56.294Z   {

    "resolution": null,

    "detail": [

        {

            "args": [

                "Command: ['/sbin/service', u'vmware-vdcs', 'start']\nStderr: "

            ],

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

            "localized": "An error occurred while invoking external command : 'Command: ['/sbin/service', u'vmware-vdcs', 'start']\nStderr: '",

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

        }

    ],

    "componentKey": null,

    "problemId": null

}

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

    "resolution": null,

    "detail": [

        {

            "args": [

                "vmware-vdcs"

            ],

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

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

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

        }

    ],

    "componentKey": null,

    "problemId": null

}

Unable to start service vmware-vdcs, Exception: {

    "resolution": null,

    "detail": [

        {

            "args": [

                "vmware-vdcs"

            ],

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

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

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

        }

    ],

    "componentKey": null,

    "problemId": null

}

Hello,

A brief idea of my test lab environment:

vCenter Servers:

vc1 - Registered to psc1 in Site1

vc2 - Registered to psc2 in Site2

External Platform Services Controllers:

psc1 - Site1

psc2 - Site2

SSO Domain: vsphere.local

I upgraded from vCenter Server 5.5 Update 3d to vCenter Server 6.0 Update 2. The vCenter servers in 5.5 had integrated / embedded SSO's and all the services running on the same machine and were in linked mode before the upgrade and I removed them from linked mode before the upgrade. They were upgraded to vCenter Server 6.0 with Embedded PSC and they automatically entered Enhanced Linked Mode (ELM).

After the step above, I deployed 2 external PSC's psc1 and psc2 in replication mode with vc1 and vc2 in the same site's Site1 and Site2 respectively. I then migrated the embedded psc's of both the vCenter Servers to their respective external psc replication partners by running the command cmsso-util reconfigure --repoint-psc "psc1/psc2" --username administrator --domain-name "vsphere.local" --passwd "administrator_password". This operation completed successfully and my vCenter's were reconfigured as vCenter Server with External PSC.

After this, I followed VMware KB article 2127057 (Determining replication agreements and status with the Platform Services Controller 6.0 (2127057) | VMware KB) to make the 2 external psc's psc1 and psc2 replication partners of each other by running the command vdcrepadmin -f createagreement -2 -h psc2.clifford.local -H psc1.clifford.local -u administrator -w "administrator_password". I ran this command from psc2. This operation also completed successfully and when I query the replication status of the replication partners psc1 and psc2, there is nothing wrong. However after restarting my vSphere Infrastructure, I see that vc1, psc1 and psc2 have all their services started successfully.

vc2 services seem to be failing to start, especially the VMware Component Manager service which is required for many other services to start. The VMware HTTP Reverse Proxy service starts successfully and I don't have any IIS role / feature installed on my machine. The error message that occurs while trying to manually start the service is as attached as file Error2.JPG in the discussion. The error from the Windows Event Log is as attached as file Error3.JPG in the discussion.

Please let me know how do I resolve this issue at the earliest.

Hi,

I've searched all over the internet and been working with VMware tech support, but I am unable to find a solution.  I am running vSphere 4.1 on Windows 2008 R2 and all is working well, except I am unable to import any physical machine into vCenter.  No matter if I use IP, host name, host:port, I always get the error "Unable to contact the specified host..." when trying to install the converter agent remotely.

If I use converter standalone or manually install the agent on the source, the conversion works fine.

Conversions worked fine in 3.5 but now on 4.1, it is broken.  I have verified that all the ports are open and I can connect to all shares on the source machine from my vCenter server.  UAC is off and the windows firewall is off.  Does anybody have any clues on what may be going on?

Thanks for any help you guys can offer.

Can anyone please describe to me what the difference is between Health Status Changed and Health Status Monitoring?  They both seem to be alerts for vCenter "service".  Any help greatly appreciated.  Thanks.

Health Status Changed

Default alarm to monitor changes to service and extension health status

Health Status Monitoring

Default alarm to monitor changes in overall health status. See vCenter Service Status on the Home view for more details.

BigD

We recently updated our vSphere Server 5.5 to 6.0 and the NetApp VSC Plugin from 5.0 to 6.0.

Now the Plugin won't show up in the WebClient as it did before the upgrade.

Has anyone the same issue? Is there a solution for it?

The backup jobs defined before the upgrade are running.

Thanks

Hello

I have recently upgraded our VMware estate to 5.5, however we use a virtual machine as the VSphere server. This has caused an issue because I have upgraded the VMware hardware to V10 and I would like to change the VM's settings...however if you power off the vm (to change the settings) I lose web management (because it is hosted from the VSphere server) and I cant use the Windows "fat client" to change the settings because you get the following error message "You cannot use the VSphere client to edit the settings of virtual machines of version 10 or higher, use the VSphere Web Client to edit the settings of this machine"

It is a complete catch 22

Any advice?

I have a possible solution to this but wondering if anyone had a better idea?

I have a vCenter server which is a virtual machine hosted on a VMware 5.0 U3 platform (4 Host HA cluster). The SCSI controller for this server is an 'LSI Logic SAS' and I would like to change this to 'Paravirtual'.

Now the procedure for this is to add a 1MB (VM best practice says 1GB why?) disk on a different iscsi bus using the paravirtual SCSI controller, then shutdown the VM, remove 1MB disk and change the original SCSI controller type to Paravirtual. Simples Right?

Ok, so you add you 1MB disk on a paravirtual SCSI controller and shutdown the VM but wait a minute... its running you vcentre! DOH! now you cant make any changes and your vcentre is down... mmmm. OK log into the host running the vCenter server and make the changes there right? wrong! The host is being controlled by the vcentre server and VMware gives you a lovely error message that "resources for this virtual machine can only be done from <Ip_address of vcentre server you just shut down>.... How infuriating! At least you can power-on you vCenter server I guess

So your vCenter server is now backup at least and you just spent ten minutes and caused a brief outage to you vCenter server with no result.

The only way I can get arround this is by creating a clone of my vCenter server and during the process use the 'Edit Hardware Settings' Experimental to change the SCSI controller. But really?

Can anyone else help me think around this issue?

All help greatly appreciated

ALF4

Hello

I have two vCenter Servers, Production and Recovery Site, both Windows boxes, apart of same SSO domain, in linked mode and both at the latest build of 5.5. I am trying to upgrade my recovery site first to 6.0U2 using the migration assistant to create an appliance. The upgrade is failing in the pre-upgrade checker with the below errors in the migration-assistant.log:

2016-11-02 13:16:27.406Z| migration-assistant-4191364| E: LaunchUpgradeRunnerCommon: Failed to run pre-upgrade phase: "C:\mig58D2.tmp\PFiles\VMware\CIS\python\python.exe" "C:\mig58D2.tmp\PFiles\VMware\CIS\cis_upgrade_runner\UpgradeRunner.py" --mode=requirements --configFile="C:\Users\MS_VCE~1\AppData\Local\Temp\UpgradeRunnerInput.json" --logDir="C:\Users\MS_VCE~1\AppData\Local\Temp\vcsMigration"  --locale=en --outputFile="C:\Users\MS_VCE~1\AppData\Local\Temp\UpgradeRunnerPreupgradeOutput.json"

2016-11-02 13:16:27.406Z| migration-assistant-4191364| I: RemoveDirectoryIfEmpty: Successfully deleted empty directory C:\mig58D2.tmp.

2016-11-02 13:16:27.407Z| migration-assistant-4191364| I: LaunchUpgradeRunnerCommon: Successfully deleted file: C:\Users\MS_VCE~1\AppData\Local\Temp\UpgradeRunnerInput.json

2016-11-02 13:16:27.407Z| migration-assistant-4191364| I: Leaving function: LaunchUpgradeRunnerCommon

2016-11-02 13:16:27.407Z| migration-assistant-4191364| I: ParseExportEstimatesFromPreUpgradeOutput: Component 'upgrade_framework': Export disk req [0 MB], Export time estimate [0 mins] and Import time estimate [0 mins].

Error: Failed to discover a system name that is compatible with both your VMware vCenter Server certificate and your VMware Single Sign-On certificate that can be used to migrate to a VMware vCenter Server Appliance with an embedded Platform Services Controller.

2016-11-02 13:16:27.439Z| migration-assistant-4191364| I: ParsePreUpgradeOutput: Resolution: Regenerate your VMware vCenter Server SSL certificate and your VMware Single Sign-On SSL certificate to have a common system name that can be used to migrate your system to VMware vCenter Server Appliance with Platform Services Controller. DHCP IP Address cannot be used as a system name to migrate to a VMware vCenter Server Appliance.

So I have done my due diligence and replaced the certs on the vCenter (Embedded deployment with external/remote SQL DB) but I am still getting the same error. I can confirm the certificates have been regenerated and applied successfully. Also did a complete uninstall and re-install to no avail.

Thoughts?

Has anyone seen this error when trying to remove a replication agreement?

I have 6 PSCs in my domain and was removing some excess agreements. It seems like I am only getting this error when trying to remove agreements from a particular PSC

I've been struggling with this- ensuring that our users have the minumum permissions on our ESX VC system. When we first set up our first ESX cluster and VC, we gave everyone VM Admin permissions on their own folders and VM's, as well as VM Admin privs on the datacenter, cluster and host server (without propagating thos permissions past past the host server).  This allows users to mess with VM advanced settings, like CPU affinity, which screws up Vmotion on the ESX cluster.  So, what I've done is clone the VM Admin role and remove anything that allows the user to edit advanced settings on the VM, or anything on the host except create/remove VM's.  So far, All of the users can edit their VM's (but not the advanced settings), take and manage snapshots- they can do everything they need except clone a VM.

The way permissions are set up: put the most permissions at the top of the heiarchy, and then limiting them as you drill down the ladder (something VMware tech support had us do when we initially set up our system two years ago).  For the sake of the explaination, we'll call my altered VM Admin role as Company User.

On the Hosts and Clusters view, the typical user has Company User privs On the Hosts and Clusters object, which is propogated down to the datacenter object, cluster object and host server objects.  At the Host server, the role is changed to not propogate any further.  On any datacenterthat the user is not supposed to access, the permissions are change to "no access".

  On the Folders and Templates view, the Company User role is assigned to the user at the Folder and Templates object, and allowed to propogate down through the datacenter object.  On each of the folders under the datacenter object, the user is either change to "no access" if they're not supposed to access that folder, or the permission is allowed to propogate.

Here's the permissions I have set up on the Company User role:

• Global

• Cancel Task

• Host

• Local Operations

• Create Virtual Machine

• Delete Virtual Machine

• Virtual Machine

• Inventory

• Create

• Remove

• Move

• Interaction

• Power On

• Power Off

• Suspend

• Reset

• Answer Question

• Console Interaction

• Device Connection

• Configure CD Media

• Configure Floppy Media

• Tools Install

• Configuration

• Rename

• Add Existing Disk

• Add New Disk

• Remove Disk

• Change CPU COunt

• Memory

• Add/Remove Device

• Modify Device Settings

• Settings

• Upgrade Virtual Hardware

• Reset Guest Information

• State

• Create Snapshot

• Revert Snapshot

• Remove Snapshot

• Rename Snapshot

• Provisioning

• Custommize Clone

• Clone

• Create Template from VM

• Deply Template

• Clone Template

• Mark as template

• Mark as virtual machine

• read customization specifications

• Allow Disk Access

• Resource

• Migrate

• Relocate

• Scheduled Task

• Create Tasks

• Remove Task

• Run Task

• Modify Task

Finally, this is a VirtualCenter 2.5.0 build 104215, and the ESX servers are running ESX 3.5.0 build 120512