Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Showcase


Channel Catalog


Channel Description:

Latest Forum Threads in VMware Communities

older | 1 | .... | 6724 | 6725 | (Page 6726) | 6727 | 6728 | .... | 6759 | newer

    0 0

    I have been a Fusion Pro user for many years.  I frequently run Debian or Ubuntu 64-bit guests on a MacOS host.  Sometimes I run just one VM at a time, other times I run a few.  Everything has been pretty great for the past few years ...until either MacOS Mojave or Fusion Pro 11 came along (or both).  Now I'm having a really tough time.

     

    I currently have a 2018 MacBook Pro Core i9 with 32GB RAM, a 1TB SSD and Radeon Pro 560X.  I also have a 2012 iMac Core i7 with 32GB RAM and Nvidia GTX 680MX.  Both run MacOS Mojave (10.14)

     

    My iMac (and previous MacBook Pro) had been running MacOS High Sierra and Fusion Pro 10 for the past few months without issue and my new MacBook only ran Fusion Pro 10 for a few days before Fusion Pro 11 came out.  It has been downhill ever since.

     

    Both computers are now running MacOS Mojave with Fusion Pro 11 and my VMs are really hard to work with on both machines.  The guests behave otherwise normally unless I let them sit idle for several minutes and then I get the spinning beach ball when trying to interact with them again.  It takes anywhere from 30-40 seconds to a few minutes for the VMs to start responding to me again.

     

    Most of the time it takes so long for them to respond that I end up force-quitting Fusion.  When I open it back up, the VMs are still running and are responsive again (which I find odd because they aren't resuming; they are just still there running)... until a I let them sit idle again and then it's back to beach ball time.

     

    I have tinkered with the guest RAM and processor settings on several different VMs.  I have also tinkered with the sleep and automatic suspend settings on the guests.  All to no avail.  I have been running VMs like this for years with few to no problems and certainly nothing like this.

     

    I have tried open-vm-tools and the VMWare Tools on different VMs to see if they offered any differences (uninstalling the other each time before switching).  They don't help.  In previous versions of Fusion I have been using open-vm-tools with great success but now it's buggy (I had to write a script to restart open-vm-tools at login in order to get the screen to resize when dragging by the corners).  VMWare Tools hasn't worked for me in a long time and when I tried it again with Fusion Pro 11 I met the same lack of success.  It installs fine but my screen won't resize and I can't get an actual full-screen mode to work (with VMWare Tools).

     

    Is anyone else experiencing this slow performance with Fusion Pro 11 and MacOS Mojave combined?

     

    If anyone has any suggestions on how I might fix the problem I'll be incredibly grateful.  The situation I've got now has me wondering if I need to try falling back to Fusion Pro 10 or High Sierra.  I really don't want to do that.

     

    Thanks, in advance, for any help you can offer.

     

    CW.

     

    Message was edited by: ITdojo - corrected a typo.


    0 0

    Hello. I have an Alienware 17 R5 laptop with Windows 10 Pro x64 installed. I recently installed VMware Workstation 15 Pro and then I installed Linux Mint 19 Cinnamon x64 as a new VM. Everything is fine and shared folders work, but, both copy and paste and drag and drop do not work, no matter the direction ( ie. to/from guest/host ).

     

    I'm using VMware Workstation 15 Pro version 15.0.2 build 10952284 and I have the latest, I believe, VMware Tools installed with a version of 10.3.2-9925305.

     

    In the VM's setting under "Guest isolation" I have both "drag and drop" and "copy and paste" checked.

     

    Any help would be appreciated.

     

    Thanks,

     

    jdb2


    0 0

    Hello,

     

    I have NSX-T 2.3 env managing a vSphere env of ESXi 6.5. All hosts in the cluster are prepared as transport nodes and all are in Overlay TZ. I have created a logical switch on NNSX manager which i can see conveyed to NSX controllers(if i check on controllers via cli) however i don't see those logical switches on ESXi hosts when i run "get logical-switches" command on nsxcli shell of ESXi host.

     

    Output from controller:

    ----------------------------

    nsxt-ctlr1> get logical-switch

    VNI      UUID                                   Name

    67584    xxxxxxx-xxxxx-x-xx-xxx   switch1

    67586    xxxxx-xxxxx-xxxx-xxxxx   test1

     

     

    nsxt-ctlr1> get logical-switch 67586 transport-node-table

    nsxt-ctlr1>

     

    I am following the NSX-T2.3 troubleshooting guide and i have confirmed on host that the following services are running:

     

    1- nsx-mpa

    2- nsx-opsagent

    3- netcpad

     

    I also checked the controllers and manager output from host:

     

    host> get managers

    - 192.168.0.11     Connected

     

     

    host> get controllers

    Controller IP    Port     SSL         Status       Is Physical Master   Session State  Controller FQDN

    192.168.0.250    1235   enabled      not used            false              null              NA

    192.168.0.252    1235   enabled     connected             true               up               NA

    192.168.0.251    1235   enabled      not used            false              null              NA

     

    host# esxcli network ip connection list | grep 1235

    tcp         0       0  192.168.0.16:20410               192.168.0.252:1235  ESTABLISHED     89665  newreno  nsx-proxy . <--- As per troubleshooting guide this should be netcpa but in my output it is nsx-proxy??

     

    host# esxcli network ip connection list | grep 5671

    tcp         0       0  192.168.0.16:61104               192.168.0.11:5671   ESTABLISHED     91052  newreno  mpa

    tcp         0       0  192.168.0.16:22875               192.168.0.11:5671   ESTABLISHED     91052  newreno  mpa

     

    Not sure why logical switches are not seen on hosts:

     

    Output from host:

    --------------------

     

    Host> get logical-switch

                      Logical Switches Summary

    ------------------------------------------------------------

     

     

                        Overlay Kernel Entry

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

      VNI                    DVS name                 VIF num

     

     

                         Overlay LCP Entry

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

      VNI              Logical Switch UUID

     

     

                         VLAN Backed Entry

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

              Logical Switch UUID            VLAN ID

     

     

    Any help would be highly appreciated.

     

    Thanks,

    Amit


    0 0

    I'm trying to use Windows file sharing (SMB) on Windows 10 (v1809) host / Linux guest running in VMware Workstation Player 15.0.2.

    However, I'm not able connect to 192.168.121.1:445 (connection refused) neither from the host, nor from the guest.

     

    192.168.121.1 is the IP address of VMware Virtual Ethernet Adapter for VMnet8 (NAT).

    The adapter is up, and ping 192.168.121.1 works fine.

    The host is listening on TCP 0.0.0.0:445.

    Windows firewall is off, antivirus software is disabled.

     

    Both "Client for Microsoft Networks" and "File and Printer Sharing for Microsoft Networks" are checked in the adapter properties.

    If I disable "File and Printer Sharing for Microsoft Networks" in the properties of "VMware Virtual Ethernet Adapter for VMnet8" and then enable it again, everything gets right, and I can connect to 192.168.121.1:445. However, after reboot it does not work again.

     

    This problem appeared after upgrade from Workstation Player 14 to Workstation Player 15.0.2.


    0 0
  • 01/06/19--12:53: sql cluster desing
  • I have vCenter 6.5 u2 and vplex metro cluster with 2 vnx 5400 . now I want to install Microsoft 2016 server with Microsoft 2017 SQL Server Always On. I have read some articles but I would like to ask experts here again. I need the share disk for MS SQL Server Always On. the sharing disk must be the physical mode or virtual rdm mode. each of the virtual machines will run on 6.5 u2 with different ESXi .

     

    it also supports vmotion virtual machines not storage vmotion ?


    0 0

     

     

    is not validating the license.
    what  could be happening?

     

    your help, please


    0 0

    I have been using VMware Fusion for a number of years to access hospital websites through Windows via Citrix Receiver and now Workspace. I keep Fusion up to date, as I do Windows (now Windows 10), and my Macs. Using Citrix on my Mac (without Fusion and Windows) never worked very well, and I was never able to print from a Citrix connection using a Mac.

     

    For a long time Fusion/Windows worked well in every respect. But then I began having trouble with one of the hospital sites, trouble which progressively worsened, and then with the others. Now I can't access any of the 3 hospitals usefully through Citrix. Either I can't connect, the connection drops soon after access, or the connection is way too slow to work. The Citrix access works fine for all three hospitals on Windows machines. Also, Fusion on my Mac works well for everything else including a clinic that I access through FortiClient.

     

    Interestingly, Citrix seems to often work pretty well on iOS devices (I haven’t tried printing.), but the screens are too small for the kind of work I do, so I haven't used Citrix on iOS much.

     

    The hospitals all use different versions of Receiver/Workspace, some more up to date than others, but if I have a recent Workspace client installed on my Windows computer, it works well with all of the hospitals. The attitudes of the hospital IT departments vary, but the most important hospital won't support Macs at all, VM or directly.

     

    I'm on the road a lot and much prefer my Mac over a Windows computer. I've developed a workaround, accessing my Windows computer through a remote desktop, but that is clunky.

     

    I doubt that I'm the only one having this problem, but I can't find it mentioned in Google searches or in searches on the WMware support site. I know that Citrix and WMware are competitors, but it is difficult to believe that the products would be made incompatible intentionally. Does anyone have any insight in to what the problem may be?


    0 0

    We have 3 VMWare hosts, with shared and direct attached storage.  We have been moving things around, and temporarily moved some VM's to a Windows 2012r2 Storage server.  We setup the storage as NFS 4.1 in VMWare, and setup following the many guides on the internet on the 2012r2 server.

     

    I'm not sure what happened, but we can no longer extend or create storage.  I have tried many many things on both the VMware side and the server 2012r2 server, but am at a loss.  None of the 3 hosts can create disks on the 2012 datastore.  I can create disks on my OpenSuse NFS storage, as well as the local direct attached storage.  All 3 vmware hosts are acting the same. 

     

    The error message I get when trying to create a disk:

    A general system error occurred: Error creating disk Device or resource busy

    File system specific implementation of LookupAndOpen[file] failed

    File system specific implementation of LookupAndOpen[file] failed

    File system specific implementation of LookupAndOpen[file] failed

    File system specific implementation of LookupAndOpen[file] failed

    File system specific implementation of Lookup[file] failed

    File system specific implementation of Lookup[file] failed

    File system specific implementation of Lookup[file] failed

    File system specific implementation of Lookup[file] failed

    File system specific implementation of Lookup[file] failed

    File system specific implementation of LookupAndOpen[file] failed

    File system specific implementation of LookupAndOpen[file] failed

    File system specific implementation of Lookup[file] failed

    File system specific implementation of LookupAndOpen[file] failed

    File system specific implementation of LookupAndOpen[file] failed

    File system specific implementation of Unlink[file] failed

    File system specific implementation of Lookup[file] failed

    File system specific implementation of LookupAndOpen[file] failed

    File system specific implementation of Ioctl[file] failed

    File system specific implementation of RenameFile[file] failed

     

    I can browse the data store, and I can create folders, edit files, etc..  I can mount existing disks and the vm works.  I just can't create new, or extend the size of existing. 

     

    Any ideas? 

    Thanks!


    0 0

    OK. Here is a bonus question....

     

    Having successful implemented Touch ID with IOS 12.1.1 and Horizon View 7.7, connecting to a Windows Server 2019 [as Desktop] machine.

     

    How can I do the same thing using the Direct Connect Plugin (bypassing the Connection Server)? I've gotten as far as getting IOS to Trust the Certificate of the Desktop but emulating the effect of adding

     

    "BioMetricsTimeout=-1"

     

    to the Connection Server ADAM database is another thing.

     

    A clever solution may not be supported but when has that ever stopped anyone from wanting to do something.

     

     

    Kind Regards

     

    ps. I logged in with direct connect and logged out but no button showed to enable Touch ID and it still works immediately when I connect to the Connection Server (I get the finger ID prompt right away). So the problem is definitely, getting the local CS to see that BioMetricsTimeout=-1, some how. Adding that line to the ADAM database serves to 'enable/turn-on the feature. How can I turn it on inside of a machine running the direct connect plugin?

     

     

     


    0 0

    The script:

    1.PNG

     

    Installing is OK. But I  want after installing has been completed auto eject CD.

     

    What should I do?


    0 0

    I have installed the appliance, changed the root password, setup a static IP and tried to log in only to be greeted with the digital middle finger, "Request took too long to respond".

     

    I've Googled and reviewed the forum for clues to crack this code, but find myself reaching for my magic 8 ball to seek wisdom after all site point to <null>.

     

    Any help would be greatly appreciated.

     

    PS: I downloaded and parsed through the log.  Couldn't find the culprit, but it looks like a error 500.


    0 0
  • 01/06/19--19:19: vSAN witness on EC2 instance
  • Hi team,

     

    I need to know if it is possible to launch the vSan witness and Tie Breaker server on AWS EC2 instance?

     

    Regards

    Pravesh


    0 0

    2019-01-07T03:28:49.788Z - info: installerLogFile: C:\Users\ADMINI~1\AppData\Local\Temp\vcsaUiInstaller\installer-20190107-112849784.log

    2019-01-07T03:28:49.808Z - info: networkLogFile: C:\Users\ADMINI~1\AppData\Local\Temp\vcsaUiInstaller\network-20190107-112849784.log

    2019-01-07T03:28:53.144Z - debug: wizardTitle: Upgrade - Stage 1: Deploy appliance

    2019-01-07T03:29:33.776Z - info: getDeploymentType() on source VC:192.168.2.9

    2019-01-07T03:29:33.777Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:29:35.191Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:29:35.216Z - debug: session does not exist: 192.168.2.9,

    2019-01-07T03:29:35.216Z - debug: Logging in to 192.168.2.9:443 as

    2019-01-07T03:29:39.235Z - error: Failed to login to 192.168.2.9:443 as : ServerFaultCode: Cannot complete login due to an incorrect user name or password.

    2019-01-07T03:30:07.629Z - debug: Source Host IP address in DOM input value is: 192.168

    2019-01-07T03:30:07.629Z - debug: Source Host IP Value in data model is: 192.168

    2019-01-07T03:30:07.630Z - debug: Source Host IP Value in data model after correction is: 192.168

    2019-01-07T03:31:35.003Z - debug: Source Host IP address in DOM input value is: 192.168.2.5

    2019-01-07T03:31:35.003Z - debug: Source Host IP Value in data model is: 192.168.2.5

    2019-01-07T03:31:35.003Z - debug: Source Host IP Value in data model after correction is: 192.168.2.5

    2019-01-07T03:31:41.243Z - debug: Source Host IP address in DOM input value is: 192.168.2.5

    2019-01-07T03:31:41.243Z - debug: Source Host IP Value in data model is: 192.168.2.5

    2019-01-07T03:31:41.244Z - debug: Source Host IP Value in data model after correction is: 192.168.2.5

    2019-01-07T03:32:06.336Z - info: THUMBPRINT(vCenterAppliance): 8D:AF:E8:D5:31:1B:4E:63:FE:E6:2F:EC:3A:A0:31:C6:E0:EC:53:2B

    2019-01-07T03:32:06.342Z - info: THUMBPRINT(esxiHost): 7D:3B:E5:5E:4C:5B:95:D8:A6:CD:A7:7E:5E:36:6C:40:58:13:63:40

    2019-01-07T03:32:06.631Z - info: THUMBPRINT(vCenterAppliance): 8D:AF:E8:D5:31:1B:4E:63:FE:E6:2F:EC:3A:A0:31:C6:E0:EC:53:2B

    2019-01-07T03:32:06.635Z - info: THUMBPRINT(esxiHost): 7D:3B:E5:5E:4C:5B:95:D8:A6:CD:A7:7E:5E:36:6C:40:58:13:63:40

    2019-01-07T03:32:08.826Z - info: attemptHttpsConnToSourceVc

    2019-01-07T03:32:08.855Z - info: login() to source VC:192.168.2.9

    2019-01-07T03:32:08.856Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:32:09.836Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:32:09.859Z - debug: session does not exist: 192.168.2.9, administrator@vsphere.local

    2019-01-07T03:32:09.859Z - debug: Logging in to 192.168.2.9:443 as administrator@vsphere.local

    2019-01-07T03:32:09.941Z - info: Logged in to 192.168.2.9:443 as administrator@vsphere.local, session: 5201b1c8-c53e-1c5c-24b6-8654882044c4

    2019-01-07T03:32:09.942Z - info: Login successful to source VC, IP: 192.168.2.9

    2019-01-07T03:32:09.942Z - info: login() to host managing the source VC:192.168.2.5

    2019-01-07T03:32:09.942Z - info: initializing vsphere API connection to 192.168.2.5:443

    2019-01-07T03:32:11.027Z - info: vimService apiType: HostAgent, version: 6.5.0

    2019-01-07T03:32:11.057Z - debug: session does not exist: 192.168.2.5, root

    2019-01-07T03:32:11.057Z - debug: Logging in to 192.168.2.5:443 as root

    2019-01-07T03:32:11.116Z - info: Logged in to 192.168.2.5:443 as root, session: 5239dc4d-b36d-f605-326a-f9979ec53f57

    2019-01-07T03:32:11.116Z - info: Login successful to host for source VC, IP: 192.168.2.5:443

    2019-01-07T03:32:11.117Z - info: sourceVcService: Source VC Version=6.5, minVersion=6, maxVersion=6.7

    2019-01-07T03:32:11.117Z - info: Source VC, version: 6.5.0, isOSLinux: true

    2019-01-07T03:32:11.117Z - debug: isIp: 192.168.2.9: true

    2019-01-07T03:32:11.125Z - debug: getVmWithIPFQDN: hostName 192.168.2.9 is associated with [ '192.168.2.9' ]

    2019-01-07T03:32:11.193Z - debug: token:undefined, length:11, running total:11

    2019-01-07T03:32:11.193Z - debug: vm found by IP: 192.168.2.9

    2019-01-07T03:32:11.195Z - info: VM with hostName 192.168.2.9: { _type: 'VirtualMachine',

      _moid: '27',

      config: { template: false },

      guest:

       { hostName: 'photon-machine',

         ipAddress: '192.168.2.9',

         net: [ [Object] ] },

      name: '009vcsa(192.168.2.9)',

      parent: { value: 'ha-folder-vm', type: 'Folder' },

      runtime: { host: { value: 'ha-host', type: 'HostSystem' } },

      summary:

       { storage:

          { committed: 63540112898,

            uncommitted: 194009636242,

            unshared: 63540112898,

            timestamp: 2018-11-25T22:08:36.178Z } } }

    2019-01-07T03:32:11.195Z - info: VM Identifier for Source VC: 27

    2019-01-07T03:32:11.544Z - debug: initiateFileTransferFromGuest error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:32:11.545Z - debug: Failed to get fileTransferInfo:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:32:11.545Z - debug: Failed to get url of file in guest vm:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:32:11.545Z - error: Error in getting fileData for nodeType. Error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:32:11.545Z - error: Failed to read the nodetype, Error: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:32:11.545Z - info: Checking if password expired

    2019-01-07T03:32:12.559Z - info: Error trying sshing directly, Error: connect ECONNREFUSED 192.168.2.9:22

    2019-01-07T03:32:12.560Z - error: Root login failed for source VC: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:32:26.934Z - info: THUMBPRINT(vCenterAppliance): 8D:AF:E8:D5:31:1B:4E:63:FE:E6:2F:EC:3A:A0:31:C6:E0:EC:53:2B

    2019-01-07T03:32:26.938Z - info: THUMBPRINT(esxiHost): 7D:3B:E5:5E:4C:5B:95:D8:A6:CD:A7:7E:5E:36:6C:40:58:13:63:40

    2019-01-07T03:32:28.110Z - info: attemptHttpsConnToSourceVc

    2019-01-07T03:32:28.134Z - info: login() to source VC:192.168.2.9

    2019-01-07T03:32:28.134Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:32:28.226Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:32:28.241Z - debug: session exists: 192.168.2.9, administrator@vsphere.local, 5201b1c8-c53e-1c5c-24b6-8654882044c4

    2019-01-07T03:32:28.257Z - info: successfully logged out from 192.168.2.9, administrator@vsphere.local, 5201b1c8-c53e-1c5c-24b6-8654882044c4

    2019-01-07T03:32:28.257Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:32:28.340Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:32:28.340Z - debug: Logging in to 192.168.2.9:443 as administrator@vsphere.local

    2019-01-07T03:32:28.393Z - info: Logged in to 192.168.2.9:443 as administrator@vsphere.local, session: 521ca946-4962-f7f8-67a0-5a98baed87b7

    2019-01-07T03:32:28.393Z - info: Login successful to source VC, IP: 192.168.2.9

    2019-01-07T03:32:28.393Z - info: login() to host managing the source VC:192.168.2.5

    2019-01-07T03:32:28.393Z - info: initializing vsphere API connection to 192.168.2.5:443

    2019-01-07T03:32:28.467Z - info: vimService apiType: HostAgent, version: 6.5.0

    2019-01-07T03:32:28.485Z - debug: session exists: 192.168.2.5, root, 5239dc4d-b36d-f605-326a-f9979ec53f57

    2019-01-07T03:32:28.499Z - info: successfully logged out from 192.168.2.5, root, 5239dc4d-b36d-f605-326a-f9979ec53f57

    2019-01-07T03:32:28.499Z - info: initializing vsphere API connection to 192.168.2.5:443

    2019-01-07T03:32:28.559Z - info: vimService apiType: HostAgent, version: 6.5.0

    2019-01-07T03:32:28.559Z - debug: Logging in to 192.168.2.5:443 as root

    2019-01-07T03:32:28.618Z - info: Logged in to 192.168.2.5:443 as root, session: 520e23ca-595d-de6d-e0fa-d9fa00bdd88b

    2019-01-07T03:32:28.618Z - info: Login successful to host for source VC, IP: 192.168.2.5:443

    2019-01-07T03:32:28.618Z - info: sourceVcService: Source VC Version=6.5, minVersion=6, maxVersion=6.7

    2019-01-07T03:32:28.618Z - info: Source VC, version: 6.5.0, isOSLinux: true

    2019-01-07T03:32:28.618Z - debug: isIp: 192.168.2.9: true

    2019-01-07T03:32:28.618Z - debug: getVmWithIPFQDN: hostName 192.168.2.9 is associated with [ '192.168.2.9' ]

    2019-01-07T03:32:28.673Z - debug: token:undefined, length:11, running total:11

    2019-01-07T03:32:28.673Z - debug: vm found by IP: 192.168.2.9

    2019-01-07T03:32:28.673Z - info: VM with hostName 192.168.2.9: { _type: 'VirtualMachine',

      _moid: '27',

      config: { template: false },

      guest:

       { hostName: 'photon-machine',

         ipAddress: '192.168.2.9',

         net: [ [Object] ] },

      name: '009vcsa(192.168.2.9)',

      parent: { value: 'ha-folder-vm', type: 'Folder' },

      runtime: { host: { value: 'ha-host', type: 'HostSystem' } },

      summary:

       { storage:

          { committed: 63540112898,

            uncommitted: 194009636242,

            unshared: 63540112898,

            timestamp: 2018-11-25T22:08:36.178Z } } }

    2019-01-07T03:32:28.673Z - info: VM Identifier for Source VC: 27

    2019-01-07T03:32:28.740Z - debug: initiateFileTransferFromGuest error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:32:28.740Z - debug: Failed to get fileTransferInfo:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:32:28.740Z - debug: Failed to get url of file in guest vm:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:32:28.740Z - error: Error in getting fileData for nodeType. Error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:32:28.740Z - error: Failed to read the nodetype, Error: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:32:28.740Z - info: Checking if password expired

    2019-01-07T03:32:29.749Z - info: Error trying sshing directly, Error: connect ECONNREFUSED 192.168.2.9:22

    2019-01-07T03:32:29.749Z - error: Root login failed for source VC: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:32:52.160Z - info: THUMBPRINT(vCenterAppliance): 8D:AF:E8:D5:31:1B:4E:63:FE:E6:2F:EC:3A:A0:31:C6:E0:EC:53:2B

    2019-01-07T03:32:52.167Z - info: THUMBPRINT(esxiHost): 7D:3B:E5:5E:4C:5B:95:D8:A6:CD:A7:7E:5E:36:6C:40:58:13:63:40

    2019-01-07T03:32:53.692Z - info: attemptHttpsConnToSourceVc

    2019-01-07T03:32:53.722Z - info: login() to source VC:192.168.2.9

    2019-01-07T03:32:53.722Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:32:53.813Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:32:53.831Z - debug: session exists: 192.168.2.9, administrator@vsphere.local, 521ca946-4962-f7f8-67a0-5a98baed87b7

    2019-01-07T03:32:53.845Z - info: successfully logged out from 192.168.2.9, administrator@vsphere.local, 521ca946-4962-f7f8-67a0-5a98baed87b7

    2019-01-07T03:32:53.845Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:32:53.927Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:32:53.928Z - debug: Logging in to 192.168.2.9:443 as administrator@vsphere.local

    2019-01-07T03:32:53.989Z - info: Logged in to 192.168.2.9:443 as administrator@vsphere.local, session: 52e2c00c-6b5e-5f11-8320-cbd124ae0bf1

    2019-01-07T03:32:53.989Z - info: Login successful to source VC, IP: 192.168.2.9

    2019-01-07T03:32:53.989Z - info: login() to host managing the source VC:192.168.2.5

    2019-01-07T03:32:53.989Z - info: initializing vsphere API connection to 192.168.2.5:443

    2019-01-07T03:32:54.087Z - info: vimService apiType: HostAgent, version: 6.5.0

    2019-01-07T03:32:54.106Z - debug: session exists: 192.168.2.5, root, 520e23ca-595d-de6d-e0fa-d9fa00bdd88b

    2019-01-07T03:32:54.121Z - info: successfully logged out from 192.168.2.5, root, 520e23ca-595d-de6d-e0fa-d9fa00bdd88b

    2019-01-07T03:32:54.121Z - info: initializing vsphere API connection to 192.168.2.5:443

    2019-01-07T03:32:54.167Z - info: vimService apiType: HostAgent, version: 6.5.0

    2019-01-07T03:32:54.167Z - debug: Logging in to 192.168.2.5:443 as root

    2019-01-07T03:32:54.214Z - info: Logged in to 192.168.2.5:443 as root, session: 520042d5-08fb-e187-7df8-aa0cc716b942

    2019-01-07T03:32:54.215Z - info: Login successful to host for source VC, IP: 192.168.2.5:443

    2019-01-07T03:32:54.215Z - info: sourceVcService: Source VC Version=6.5, minVersion=6, maxVersion=6.7

    2019-01-07T03:32:54.215Z - info: Source VC, version: 6.5.0, isOSLinux: true

    2019-01-07T03:32:54.215Z - debug: isIp: 192.168.2.9: true

    2019-01-07T03:32:54.215Z - debug: getVmWithIPFQDN: hostName 192.168.2.9 is associated with [ '192.168.2.9' ]

    2019-01-07T03:32:54.273Z - debug: token:undefined, length:11, running total:11

    2019-01-07T03:32:54.274Z - debug: vm found by IP: 192.168.2.9

    2019-01-07T03:32:54.274Z - info: VM with hostName 192.168.2.9: { _type: 'VirtualMachine',

      _moid: '27',

      config: { template: false },

      guest:

       { hostName: 'photon-machine',

         ipAddress: '192.168.2.9',

         net: [ [Object] ] },

      name: '009vcsa(192.168.2.9)',

      parent: { value: 'ha-folder-vm', type: 'Folder' },

      runtime: { host: { value: 'ha-host', type: 'HostSystem' } },

      summary:

       { storage:

          { committed: 63540112898,

            uncommitted: 194009636242,

            unshared: 63540112898,

            timestamp: 2018-11-25T22:08:36.178Z } } }

    2019-01-07T03:32:54.275Z - info: VM Identifier for Source VC: 27

    2019-01-07T03:32:54.423Z - debug: initiateFileTransferFromGuest error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:32:54.423Z - debug: Failed to get fileTransferInfo:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:32:54.424Z - debug: Failed to get url of file in guest vm:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:32:54.424Z - error: Error in getting fileData for nodeType. Error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:32:54.424Z - error: Failed to read the nodetype, Error: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:32:54.424Z - info: Checking if password expired

    2019-01-07T03:32:55.435Z - info: Error trying sshing directly, Error: connect ECONNREFUSED 192.168.2.9:22

    2019-01-07T03:32:55.436Z - error: Root login failed for source VC: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:33:16.343Z - info: THUMBPRINT(vCenterAppliance): 8D:AF:E8:D5:31:1B:4E:63:FE:E6:2F:EC:3A:A0:31:C6:E0:EC:53:2B

    2019-01-07T03:33:16.356Z - info: THUMBPRINT(esxiHost): 7D:3B:E5:5E:4C:5B:95:D8:A6:CD:A7:7E:5E:36:6C:40:58:13:63:40

    2019-01-07T03:33:17.310Z - info: attemptHttpsConnToSourceVc

    2019-01-07T03:33:17.338Z - info: login() to source VC:192.168.2.9

    2019-01-07T03:33:17.338Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:33:17.436Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:33:17.454Z - debug: session exists: 192.168.2.9, administrator@vsphere.local, 52e2c00c-6b5e-5f11-8320-cbd124ae0bf1

    2019-01-07T03:33:17.467Z - info: successfully logged out from 192.168.2.9, administrator@vsphere.local, 52e2c00c-6b5e-5f11-8320-cbd124ae0bf1

    2019-01-07T03:33:17.467Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:33:17.542Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:33:17.542Z - debug: Logging in to 192.168.2.9:443 as administrator@vsphere.local

    2019-01-07T03:33:17.592Z - info: Logged in to 192.168.2.9:443 as administrator@vsphere.local, session: 52859d94-d826-897b-19c9-8d62fc31c855

    2019-01-07T03:33:17.592Z - info: Login successful to source VC, IP: 192.168.2.9

    2019-01-07T03:33:17.592Z - info: login() to host managing the source VC:192.168.2.5

    2019-01-07T03:33:17.592Z - info: initializing vsphere API connection to 192.168.2.5:443

    2019-01-07T03:33:17.665Z - info: vimService apiType: HostAgent, version: 6.5.0

    2019-01-07T03:33:17.688Z - debug: session exists: 192.168.2.5, root, 520042d5-08fb-e187-7df8-aa0cc716b942

    2019-01-07T03:33:17.709Z - info: successfully logged out from 192.168.2.5, root, 520042d5-08fb-e187-7df8-aa0cc716b942

    2019-01-07T03:33:17.710Z - info: initializing vsphere API connection to 192.168.2.5:443

    2019-01-07T03:33:17.784Z - info: vimService apiType: HostAgent, version: 6.5.0

    2019-01-07T03:33:17.784Z - debug: Logging in to 192.168.2.5:443 as root

    2019-01-07T03:33:17.836Z - info: Logged in to 192.168.2.5:443 as root, session: 524bacb3-9b4e-92c6-6928-1c87be542a5e

    2019-01-07T03:33:17.836Z - info: Login successful to host for source VC, IP: 192.168.2.5:443

    2019-01-07T03:33:17.836Z - info: sourceVcService: Source VC Version=6.5, minVersion=6, maxVersion=6.7

    2019-01-07T03:33:17.836Z - info: Source VC, version: 6.5.0, isOSLinux: true

    2019-01-07T03:33:17.836Z - debug: isIp: 192.168.2.9: true

    2019-01-07T03:33:17.836Z - debug: getVmWithIPFQDN: hostName 192.168.2.9 is associated with [ '192.168.2.9' ]

    2019-01-07T03:33:17.896Z - debug: token:undefined, length:11, running total:11

    2019-01-07T03:33:17.896Z - debug: vm found by IP: 192.168.2.9

    2019-01-07T03:33:17.897Z - info: VM with hostName 192.168.2.9: { _type: 'VirtualMachine',

      _moid: '27',

      config: { template: false },

      guest:

       { hostName: 'photon-machine',

         ipAddress: '192.168.2.9',

         net: [ [Object] ] },

      name: '009vcsa(192.168.2.9)',

      parent: { value: 'ha-folder-vm', type: 'Folder' },

      runtime: { host: { value: 'ha-host', type: 'HostSystem' } },

      summary:

       { storage:

          { committed: 63540112898,

            uncommitted: 194009636242,

            unshared: 63540112898,

            timestamp: 2018-11-25T22:08:36.178Z } } }

    2019-01-07T03:33:17.897Z - info: VM Identifier for Source VC: 27

    2019-01-07T03:33:17.992Z - debug: initiateFileTransferFromGuest error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:33:17.992Z - debug: Failed to get fileTransferInfo:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:33:17.993Z - debug: Failed to get url of file in guest vm:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:33:17.993Z - error: Error in getting fileData for nodeType. Error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:33:17.993Z - error: Failed to read the nodetype, Error: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:33:17.993Z - info: Checking if password expired

    2019-01-07T03:33:19.000Z - info: Error trying sshing directly, Error: connect ECONNREFUSED 192.168.2.9:22

    2019-01-07T03:33:19.000Z - error: Root login failed for source VC: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:33:29.167Z - info: THUMBPRINT(vCenterAppliance): 8D:AF:E8:D5:31:1B:4E:63:FE:E6:2F:EC:3A:A0:31:C6:E0:EC:53:2B

    2019-01-07T03:33:29.178Z - info: THUMBPRINT(esxiHost): 7D:3B:E5:5E:4C:5B:95:D8:A6:CD:A7:7E:5E:36:6C:40:58:13:63:40

    2019-01-07T03:33:30.631Z - info: attemptHttpsConnToSourceVc

    2019-01-07T03:33:30.662Z - info: login() to source VC:192.168.2.9

    2019-01-07T03:33:30.662Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:33:30.756Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:33:30.770Z - debug: session exists: 192.168.2.9, administrator@vsphere.local, 52859d94-d826-897b-19c9-8d62fc31c855

    2019-01-07T03:33:30.783Z - info: successfully logged out from 192.168.2.9, administrator@vsphere.local, 52859d94-d826-897b-19c9-8d62fc31c855

    2019-01-07T03:33:30.783Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:33:30.869Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:33:30.869Z - debug: Logging in to 192.168.2.9:443 as administrator@vsphere.local

    2019-01-07T03:33:30.924Z - info: Logged in to 192.168.2.9:443 as administrator@vsphere.local, session: 522383dd-493a-cd96-037e-f43901e64363

    2019-01-07T03:33:30.924Z - info: Login successful to source VC, IP: 192.168.2.9

    2019-01-07T03:33:30.924Z - info: login() to host managing the source VC:192.168.2.5

    2019-01-07T03:33:30.924Z - info: initializing vsphere API connection to 192.168.2.5:443

    2019-01-07T03:33:31.005Z - info: vimService apiType: HostAgent, version: 6.5.0

    2019-01-07T03:33:31.025Z - debug: session exists: 192.168.2.5, root, 524bacb3-9b4e-92c6-6928-1c87be542a5e

    2019-01-07T03:33:31.042Z - info: successfully logged out from 192.168.2.5, root, 524bacb3-9b4e-92c6-6928-1c87be542a5e

    2019-01-07T03:33:31.042Z - info: initializing vsphere API connection to 192.168.2.5:443

    2019-01-07T03:33:31.088Z - info: vimService apiType: HostAgent, version: 6.5.0

    2019-01-07T03:33:31.088Z - debug: Logging in to 192.168.2.5:443 as root

    2019-01-07T03:33:31.135Z - info: Logged in to 192.168.2.5:443 as root, session: 52f7497a-edea-7b78-e312-4183ef0bc8e5

    2019-01-07T03:33:31.135Z - info: Login successful to host for source VC, IP: 192.168.2.5:443

    2019-01-07T03:33:31.135Z - info: sourceVcService: Source VC Version=6.5, minVersion=6, maxVersion=6.7

    2019-01-07T03:33:31.135Z - info: Source VC, version: 6.5.0, isOSLinux: true

    2019-01-07T03:33:31.135Z - debug: isIp: 192.168.2.9: true

    2019-01-07T03:33:31.135Z - debug: getVmWithIPFQDN: hostName 192.168.2.9 is associated with [ '192.168.2.9' ]

    2019-01-07T03:33:31.192Z - debug: token:undefined, length:11, running total:11

    2019-01-07T03:33:31.192Z - debug: vm found by IP: 192.168.2.9

    2019-01-07T03:33:31.193Z - info: VM with hostName 192.168.2.9: { _type: 'VirtualMachine',

      _moid: '27',

      config: { template: false },

      guest:

       { hostName: 'photon-machine',

         ipAddress: '192.168.2.9',

         net: [ [Object] ] },

      name: '009vcsa(192.168.2.9)',

      parent: { value: 'ha-folder-vm', type: 'Folder' },

      runtime: { host: { value: 'ha-host', type: 'HostSystem' } },

      summary:

       { storage:

          { committed: 63540112898,

            uncommitted: 194009636242,

            unshared: 63540112898,

            timestamp: 2018-11-25T22:08:36.178Z } } }

    2019-01-07T03:33:31.193Z - info: VM Identifier for Source VC: 27

    2019-01-07T03:33:33.658Z - debug: initiateFileTransferFromGuest error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:33:33.658Z - debug: Failed to get fileTransferInfo:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:33:33.658Z - debug: Failed to get url of file in guest vm:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:33:33.658Z - error: Error in getting fileData for nodeType. Error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:33:33.658Z - error: Failed to read the nodetype, Error: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:33:33.658Z - info: Checking if password expired

    2019-01-07T03:33:34.669Z - info: Error trying sshing directly, Error: connect ECONNREFUSED 192.168.2.9:22

    2019-01-07T03:33:34.669Z - error: Root login failed for source VC: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:33:49.941Z - info: THUMBPRINT(vCenterAppliance): 8D:AF:E8:D5:31:1B:4E:63:FE:E6:2F:EC:3A:A0:31:C6:E0:EC:53:2B

    2019-01-07T03:33:49.955Z - info: THUMBPRINT(esxiHost): 7D:3B:E5:5E:4C:5B:95:D8:A6:CD:A7:7E:5E:36:6C:40:58:13:63:40

    2019-01-07T03:33:52.342Z - info: attemptHttpsConnToSourceVc

    2019-01-07T03:33:52.371Z - info: login() to source VC:192.168.2.9

    2019-01-07T03:33:52.371Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:33:52.461Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:33:52.478Z - debug: session exists: 192.168.2.9, administrator@vsphere.local, 522383dd-493a-cd96-037e-f43901e64363

    2019-01-07T03:33:52.491Z - info: successfully logged out from 192.168.2.9, administrator@vsphere.local, 522383dd-493a-cd96-037e-f43901e64363

    2019-01-07T03:33:52.491Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:33:52.575Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:33:52.575Z - debug: Logging in to 192.168.2.9:443 as administrator@vsphere.local

    2019-01-07T03:33:52.632Z - info: Logged in to 192.168.2.9:443 as administrator@vsphere.local, session: 52676050-b36d-8160-3fb8-b39473d5219b

    2019-01-07T03:33:52.632Z - info: Login successful to source VC, IP: 192.168.2.9

    2019-01-07T03:33:52.632Z - info: login() to host managing the source VC:192.168.2.5

    2019-01-07T03:33:52.633Z - info: initializing vsphere API connection to 192.168.2.5:443

    2019-01-07T03:33:52.714Z - info: vimService apiType: HostAgent, version: 6.5.0

    2019-01-07T03:33:52.730Z - debug: session exists: 192.168.2.5, root, 52f7497a-edea-7b78-e312-4183ef0bc8e5

    2019-01-07T03:33:52.741Z - info: successfully logged out from 192.168.2.5, root, 52f7497a-edea-7b78-e312-4183ef0bc8e5

    2019-01-07T03:33:52.741Z - info: initializing vsphere API connection to 192.168.2.5:443

    2019-01-07T03:33:52.790Z - info: vimService apiType: HostAgent, version: 6.5.0

    2019-01-07T03:33:52.790Z - debug: Logging in to 192.168.2.5:443 as root

    2019-01-07T03:33:52.843Z - info: Logged in to 192.168.2.5:443 as root, session: 52542bbc-ac1a-438d-d2b4-ce4a8aa3bf3b

    2019-01-07T03:33:52.843Z - info: Login successful to host for source VC, IP: 192.168.2.5:443

    2019-01-07T03:33:52.843Z - info: sourceVcService: Source VC Version=6.5, minVersion=6, maxVersion=6.7

    2019-01-07T03:33:52.843Z - info: Source VC, version: 6.5.0, isOSLinux: true

    2019-01-07T03:33:52.843Z - debug: isIp: 192.168.2.9: true

    2019-01-07T03:33:52.843Z - debug: getVmWithIPFQDN: hostName 192.168.2.9 is associated with [ '192.168.2.9' ]

    2019-01-07T03:33:52.912Z - debug: token:undefined, length:11, running total:11

    2019-01-07T03:33:52.912Z - debug: vm found by IP: 192.168.2.9

    2019-01-07T03:33:52.912Z - info: VM with hostName 192.168.2.9: { _type: 'VirtualMachine',

      _moid: '27',

      config: { template: false },

      guest:

       { hostName: 'photon-machine',

         ipAddress: '192.168.2.9',

         net: [ [Object] ] },

      name: '009vcsa(192.168.2.9)',

      parent: { value: 'ha-folder-vm', type: 'Folder' },

      runtime: { host: { value: 'ha-host', type: 'HostSystem' } },

      summary:

       { storage:

          { committed: 63540112898,

            uncommitted: 194009636242,

            unshared: 63540112898,

            timestamp: 2018-11-25T22:08:36.178Z } } }

    2019-01-07T03:33:52.912Z - info: VM Identifier for Source VC: 27

    2019-01-07T03:33:54.898Z - debug: initiateFileTransferFromGuest error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:33:54.899Z - debug: Failed to get fileTransferInfo:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:33:54.899Z - debug: Failed to get url of file in guest vm:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:33:54.899Z - error: Error in getting fileData for nodeType. Error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:33:54.899Z - error: Failed to read the nodetype, Error: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:33:54.899Z - info: Checking if password expired

    2019-01-07T03:33:55.912Z - info: Error trying sshing directly, Error: connect ECONNREFUSED 192.168.2.9:22

    2019-01-07T03:33:55.912Z - error: Root login failed for source VC: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:04.705Z - info: THUMBPRINT(vCenterAppliance): 8D:AF:E8:D5:31:1B:4E:63:FE:E6:2F:EC:3A:A0:31:C6:E0:EC:53:2B

    2019-01-07T03:34:04.717Z - info: THUMBPRINT(esxiHost): 7D:3B:E5:5E:4C:5B:95:D8:A6:CD:A7:7E:5E:36:6C:40:58:13:63:40

    2019-01-07T03:34:05.874Z - info: THUMBPRINT(vCenterAppliance): 8D:AF:E8:D5:31:1B:4E:63:FE:E6:2F:EC:3A:A0:31:C6:E0:EC:53:2B

    2019-01-07T03:34:05.887Z - info: THUMBPRINT(esxiHost): 7D:3B:E5:5E:4C:5B:95:D8:A6:CD:A7:7E:5E:36:6C:40:58:13:63:40

    2019-01-07T03:34:07.152Z - info: THUMBPRINT(vCenterAppliance): 8D:AF:E8:D5:31:1B:4E:63:FE:E6:2F:EC:3A:A0:31:C6:E0:EC:53:2B

    2019-01-07T03:34:07.165Z - info: THUMBPRINT(esxiHost): 7D:3B:E5:5E:4C:5B:95:D8:A6:CD:A7:7E:5E:36:6C:40:58:13:63:40

    2019-01-07T03:34:07.985Z - debug: Source Host IP address in DOM input value is: 192.168.2.5

    2019-01-07T03:34:07.985Z - debug: Source Host IP Value in data model is: 192.168.2.5

    2019-01-07T03:34:07.985Z - debug: Source Host IP Value in data model after correction is: 192.168.2.5

    2019-01-07T03:34:10.139Z - info: attemptHttpsConnToSourceVc

    2019-01-07T03:34:10.174Z - info: login() to source VC:192.168.2.9

    2019-01-07T03:34:10.174Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:34:11.173Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:34:11.200Z - debug: session exists: 192.168.2.9, administrator@vsphere.local, 52676050-b36d-8160-3fb8-b39473d5219b

    2019-01-07T03:34:11.212Z - info: successfully logged out from 192.168.2.9, administrator@vsphere.local, 52676050-b36d-8160-3fb8-b39473d5219b

    2019-01-07T03:34:11.212Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:34:11.266Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:34:11.267Z - debug: Logging in to 192.168.2.9:443 as administrator@vsphere.local

    2019-01-07T03:34:11.328Z - info: Logged in to 192.168.2.9:443 as administrator@vsphere.local, session: 52fd4ada-0041-01bb-cffc-5f54321bac46

    2019-01-07T03:34:11.328Z - info: Login successful to source VC, IP: 192.168.2.9

    2019-01-07T03:34:11.328Z - info: login() to host managing the source VC:192.168.2.5

    2019-01-07T03:34:11.328Z - info: initializing vsphere API connection to 192.168.2.5:443

    2019-01-07T03:34:12.378Z - info: vimService apiType: HostAgent, version: 6.5.0

    2019-01-07T03:34:12.473Z - debug: session exists: 192.168.2.5, root, 52542bbc-ac1a-438d-d2b4-ce4a8aa3bf3b

    2019-01-07T03:34:12.493Z - info: successfully logged out from 192.168.2.5, root, 52542bbc-ac1a-438d-d2b4-ce4a8aa3bf3b

    2019-01-07T03:34:12.493Z - info: initializing vsphere API connection to 192.168.2.5:443

    2019-01-07T03:34:12.595Z - info: vimService apiType: HostAgent, version: 6.5.0

    2019-01-07T03:34:12.596Z - debug: Logging in to 192.168.2.5:443 as root

    2019-01-07T03:34:12.660Z - info: Logged in to 192.168.2.5:443 as root, session: 5227a1d8-3dbc-2452-b204-08bc81289d73

    2019-01-07T03:34:12.660Z - info: Login successful to host for source VC, IP: 192.168.2.5:443

    2019-01-07T03:34:12.660Z - info: sourceVcService: Source VC Version=6.5, minVersion=6, maxVersion=6.7

    2019-01-07T03:34:12.660Z - info: Source VC, version: 6.5.0, isOSLinux: true

    2019-01-07T03:34:12.660Z - debug: isIp: 192.168.2.9: true

    2019-01-07T03:34:12.660Z - debug: getVmWithIPFQDN: hostName 192.168.2.9 is associated with [ '192.168.2.9' ]

    2019-01-07T03:34:12.723Z - debug: token:undefined, length:11, running total:11

    2019-01-07T03:34:12.723Z - debug: vm found by IP: 192.168.2.9

    2019-01-07T03:34:12.724Z - info: VM with hostName 192.168.2.9: { _type: 'VirtualMachine',

      _moid: '27',

      config: { template: false },

      guest:

       { hostName: 'photon-machine',

         ipAddress: '192.168.2.9',

         net: [ [Object] ] },

      name: '009vcsa(192.168.2.9)',

      parent: { value: 'ha-folder-vm', type: 'Folder' },

      runtime: { host: { value: 'ha-host', type: 'HostSystem' } },

      summary:

       { storage:

          { committed: 63540112898,

            uncommitted: 194009636242,

            unshared: 63540112898,

            timestamp: 2018-11-25T22:08:36.178Z } } }

    2019-01-07T03:34:12.724Z - info: VM Identifier for Source VC: 27

    2019-01-07T03:34:14.740Z - debug: initiateFileTransferFromGuest error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:14.740Z - debug: Failed to get fileTransferInfo:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:14.740Z - debug: Failed to get url of file in guest vm:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:14.740Z - error: Error in getting fileData for nodeType. Error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:14.740Z - error: Failed to read the nodetype, Error: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:14.740Z - info: Checking if password expired

    2019-01-07T03:34:15.748Z - info: Error trying sshing directly, Error: connect ECONNREFUSED 192.168.2.9:22

    2019-01-07T03:34:15.748Z - error: Root login failed for source VC: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:20.343Z - info: THUMBPRINT(vCenterAppliance): 8D:AF:E8:D5:31:1B:4E:63:FE:E6:2F:EC:3A:A0:31:C6:E0:EC:53:2B

    2019-01-07T03:34:20.354Z - info: THUMBPRINT(esxiHost): 7D:3B:E5:5E:4C:5B:95:D8:A6:CD:A7:7E:5E:36:6C:40:58:13:63:40

    2019-01-07T03:34:21.652Z - info: attemptHttpsConnToSourceVc

    2019-01-07T03:34:21.676Z - info: login() to source VC:192.168.2.9

    2019-01-07T03:34:21.676Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:34:21.759Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:34:21.775Z - debug: session exists: 192.168.2.9, administrator@vsphere.local, 52fd4ada-0041-01bb-cffc-5f54321bac46

    2019-01-07T03:34:21.790Z - info: successfully logged out from 192.168.2.9, administrator@vsphere.local, 52fd4ada-0041-01bb-cffc-5f54321bac46

    2019-01-07T03:34:21.790Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:34:21.866Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:34:21.866Z - debug: Logging in to 192.168.2.9:443 as administrator@vsphere.local

    2019-01-07T03:34:21.921Z - info: Logged in to 192.168.2.9:443 as administrator@vsphere.local, session: 5250230f-cf47-f494-7648-4398a62a4b1c

    2019-01-07T03:34:21.921Z - info: Login successful to source VC, IP: 192.168.2.9

    2019-01-07T03:34:21.921Z - info: login() to host managing the source VC:192.168.2.5

    2019-01-07T03:34:21.921Z - info: initializing vsphere API connection to 192.168.2.5:443

    2019-01-07T03:34:21.972Z - info: vimService apiType: HostAgent, version: 6.5.0

    2019-01-07T03:34:21.986Z - debug: session exists: 192.168.2.5, root, 5227a1d8-3dbc-2452-b204-08bc81289d73

    2019-01-07T03:34:21.998Z - info: successfully logged out from 192.168.2.5, root, 5227a1d8-3dbc-2452-b204-08bc81289d73

    2019-01-07T03:34:21.998Z - info: initializing vsphere API connection to 192.168.2.5:443

    2019-01-07T03:34:22.048Z - info: vimService apiType: HostAgent, version: 6.5.0

    2019-01-07T03:34:22.048Z - debug: Logging in to 192.168.2.5:443 as root

    2019-01-07T03:34:22.106Z - info: Logged in to 192.168.2.5:443 as root, session: 523f4cfd-9c31-0782-d150-560d1a39873a

    2019-01-07T03:34:22.106Z - info: Login successful to host for source VC, IP: 192.168.2.5:443

    2019-01-07T03:34:22.106Z - info: sourceVcService: Source VC Version=6.5, minVersion=6, maxVersion=6.7

    2019-01-07T03:34:22.106Z - info: Source VC, version: 6.5.0, isOSLinux: true

    2019-01-07T03:34:22.107Z - debug: isIp: 192.168.2.9: true

    2019-01-07T03:34:22.107Z - debug: getVmWithIPFQDN: hostName 192.168.2.9 is associated with [ '192.168.2.9' ]

    2019-01-07T03:34:22.166Z - debug: token:undefined, length:11, running total:11

    2019-01-07T03:34:22.166Z - debug: vm found by IP: 192.168.2.9

    2019-01-07T03:34:22.167Z - info: VM with hostName 192.168.2.9: { _type: 'VirtualMachine',

      _moid: '27',

      config: { template: false },

      guest:

       { hostName: 'photon-machine',

         ipAddress: '192.168.2.9',

         net: [ [Object] ] },

      name: '009vcsa(192.168.2.9)',

      parent: { value: 'ha-folder-vm', type: 'Folder' },

      runtime: { host: { value: 'ha-host', type: 'HostSystem' } },

      summary:

       { storage:

          { committed: 63540112898,

            uncommitted: 194009636242,

            unshared: 63540112898,

            timestamp: 2018-11-25T22:08:36.178Z } } }

    2019-01-07T03:34:22.167Z - info: VM Identifier for Source VC: 27

    2019-01-07T03:34:24.308Z - debug: initiateFileTransferFromGuest error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:24.308Z - debug: Failed to get fileTransferInfo:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:24.308Z - debug: Failed to get url of file in guest vm:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:24.308Z - error: Error in getting fileData for nodeType. Error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:24.309Z - error: Failed to read the nodetype, Error: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:24.309Z - info: Checking if password expired

    2019-01-07T03:34:25.324Z - info: Error trying sshing directly, Error: connect ECONNREFUSED 192.168.2.9:22

    2019-01-07T03:34:25.324Z - error: Root login failed for source VC: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:31.665Z - info: THUMBPRINT(vCenterAppliance): 8D:AF:E8:D5:31:1B:4E:63:FE:E6:2F:EC:3A:A0:31:C6:E0:EC:53:2B

    2019-01-07T03:34:31.680Z - info: THUMBPRINT(esxiHost): 7D:3B:E5:5E:4C:5B:95:D8:A6:CD:A7:7E:5E:36:6C:40:58:13:63:40

    2019-01-07T03:34:32.873Z - info: attemptHttpsConnToSourceVc

    2019-01-07T03:34:32.898Z - info: login() to source VC:192.168.2.9

    2019-01-07T03:34:32.898Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:34:32.996Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:34:33.021Z - debug: session exists: 192.168.2.9, administrator@vsphere.local, 5250230f-cf47-f494-7648-4398a62a4b1c

    2019-01-07T03:34:33.052Z - info: successfully logged out from 192.168.2.9, administrator@vsphere.local, 5250230f-cf47-f494-7648-4398a62a4b1c

    2019-01-07T03:34:33.052Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:34:33.164Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:34:33.164Z - debug: Logging in to 192.168.2.9:443 as administrator@vsphere.local

    2019-01-07T03:34:33.231Z - info: Logged in to 192.168.2.9:443 as administrator@vsphere.local, session: 52e669fc-c748-d692-61e5-93f0a53d9845

    2019-01-07T03:34:33.231Z - info: Login successful to source VC, IP: 192.168.2.9

    2019-01-07T03:34:33.231Z - info: login() to host managing the source VC:192.168.2.5

    2019-01-07T03:34:33.231Z - info: initializing vsphere API connection to 192.168.2.5:443

    2019-01-07T03:34:33.277Z - info: vimService apiType: HostAgent, version: 6.5.0

    2019-01-07T03:34:33.292Z - debug: session exists: 192.168.2.5, root, 523f4cfd-9c31-0782-d150-560d1a39873a

    2019-01-07T03:34:33.304Z - info: successfully logged out from 192.168.2.5, root, 523f4cfd-9c31-0782-d150-560d1a39873a

    2019-01-07T03:34:33.304Z - info: initializing vsphere API connection to 192.168.2.5:443

    2019-01-07T03:34:33.357Z - info: vimService apiType: HostAgent, version: 6.5.0

    2019-01-07T03:34:33.357Z - debug: Logging in to 192.168.2.5:443 as root

    2019-01-07T03:34:33.420Z - info: Logged in to 192.168.2.5:443 as root, session: 52e1a0dc-49e1-394e-85df-9d943c512a94

    2019-01-07T03:34:33.420Z - info: Login successful to host for source VC, IP: 192.168.2.5:443

    2019-01-07T03:34:33.421Z - info: sourceVcService: Source VC Version=6.5, minVersion=6, maxVersion=6.7

    2019-01-07T03:34:33.421Z - info: Source VC, version: 6.5.0, isOSLinux: true

    2019-01-07T03:34:33.421Z - debug: isIp: 192.168.2.9: true

    2019-01-07T03:34:33.421Z - debug: getVmWithIPFQDN: hostName 192.168.2.9 is associated with [ '192.168.2.9' ]

    2019-01-07T03:34:33.485Z - debug: token:undefined, length:11, running total:11

    2019-01-07T03:34:33.485Z - debug: vm found by IP: 192.168.2.9

    2019-01-07T03:34:33.485Z - info: VM with hostName 192.168.2.9: { _type: 'VirtualMachine',

      _moid: '27',

      config: { template: false },

      guest:

       { hostName: 'photon-machine',

         ipAddress: '192.168.2.9',

         net: [ [Object] ] },

      name: '009vcsa(192.168.2.9)',

      parent: { value: 'ha-folder-vm', type: 'Folder' },

      runtime: { host: { value: 'ha-host', type: 'HostSystem' } },

      summary:

       { storage:

          { committed: 63540112898,

            uncommitted: 194009636242,

            unshared: 63540112898,

            timestamp: 2018-11-25T22:08:36.178Z } } }

    2019-01-07T03:34:33.486Z - info: VM Identifier for Source VC: 27

    2019-01-07T03:34:35.473Z - debug: initiateFileTransferFromGuest error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:35.473Z - debug: Failed to get fileTransferInfo:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:35.474Z - debug: Failed to get url of file in guest vm:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:35.474Z - error: Error in getting fileData for nodeType. Error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:35.474Z - error: Failed to read the nodetype, Error: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:35.474Z - info: Checking if password expired

    2019-01-07T03:34:36.489Z - info: Error trying sshing directly, Error: connect ECONNREFUSED 192.168.2.9:22

    2019-01-07T03:34:36.490Z - error: Root login failed for source VC: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:47.168Z - info: THUMBPRINT(vCenterAppliance): 8D:AF:E8:D5:31:1B:4E:63:FE:E6:2F:EC:3A:A0:31:C6:E0:EC:53:2B

    2019-01-07T03:34:47.180Z - info: THUMBPRINT(esxiHost): 7D:3B:E5:5E:4C:5B:95:D8:A6:CD:A7:7E:5E:36:6C:40:58:13:63:40

    2019-01-07T03:34:48.539Z - info: attemptHttpsConnToSourceVc

    2019-01-07T03:34:48.561Z - info: login() to source VC:192.168.2.9

    2019-01-07T03:34:48.562Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:34:48.644Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:34:48.659Z - debug: session exists: 192.168.2.9, administrator@vsphere.local, 52e669fc-c748-d692-61e5-93f0a53d9845

    2019-01-07T03:34:48.673Z - info: successfully logged out from 192.168.2.9, administrator@vsphere.local, 52e669fc-c748-d692-61e5-93f0a53d9845

    2019-01-07T03:34:48.673Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:34:48.738Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:34:48.738Z - debug: Logging in to 192.168.2.9:443 as administrator@vsphere.local

    2019-01-07T03:34:48.791Z - info: Logged in to 192.168.2.9:443 as administrator@vsphere.local, session: 5285cde1-3267-b5b9-64a7-5f45b01ee91c

    2019-01-07T03:34:48.791Z - info: Login successful to source VC, IP: 192.168.2.9

    2019-01-07T03:34:48.791Z - info: login() to host managing the source VC:192.168.2.5

    2019-01-07T03:34:48.791Z - info: initializing vsphere API connection to 192.168.2.5:443

    2019-01-07T03:34:48.838Z - info: vimService apiType: HostAgent, version: 6.5.0

    2019-01-07T03:34:48.851Z - debug: session exists: 192.168.2.5, root, 52e1a0dc-49e1-394e-85df-9d943c512a94

    2019-01-07T03:34:48.863Z - info: successfully logged out from 192.168.2.5, root, 52e1a0dc-49e1-394e-85df-9d943c512a94

    2019-01-07T03:34:48.863Z - info: initializing vsphere API connection to 192.168.2.5:443

    2019-01-07T03:34:48.915Z - info: vimService apiType: HostAgent, version: 6.5.0

    2019-01-07T03:34:48.915Z - debug: Logging in to 192.168.2.5:443 as root

    2019-01-07T03:34:48.963Z - info: Logged in to 192.168.2.5:443 as root, session: 522c9baa-8339-5894-a497-490d44e03b3a

    2019-01-07T03:34:48.963Z - info: Login successful to host for source VC, IP: 192.168.2.5:443

    2019-01-07T03:34:48.963Z - info: sourceVcService: Source VC Version=6.5, minVersion=6, maxVersion=6.7

    2019-01-07T03:34:48.964Z - info: Source VC, version: 6.5.0, isOSLinux: true

    2019-01-07T03:34:48.964Z - debug: isIp: 192.168.2.9: true

    2019-01-07T03:34:48.964Z - debug: getVmWithIPFQDN: hostName 192.168.2.9 is associated with [ '192.168.2.9' ]

    2019-01-07T03:34:49.027Z - debug: token:undefined, length:11, running total:11

    2019-01-07T03:34:49.027Z - debug: vm found by IP: 192.168.2.9

    2019-01-07T03:34:49.028Z - info: VM with hostName 192.168.2.9: { _type: 'VirtualMachine',

      _moid: '27',

      config: { template: false },

      guest:

       { hostName: 'photon-machine',

         ipAddress: '192.168.2.9',

         net: [ [Object] ] },

      name: '009vcsa(192.168.2.9)',

      parent: { value: 'ha-folder-vm', type: 'Folder' },

      runtime: { host: { value: 'ha-host', type: 'HostSystem' } },

      summary:

       { storage:

          { committed: 63540112898,

            uncommitted: 194009636242,

            unshared: 63540112898,

            timestamp: 2018-11-25T22:08:36.178Z } } }

    2019-01-07T03:34:49.028Z - info: VM Identifier for Source VC: 27

    2019-01-07T03:34:51.522Z - debug: initiateFileTransferFromGuest error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:51.522Z - debug: Failed to get fileTransferInfo:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:51.522Z - debug: Failed to get url of file in guest vm:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:51.522Z - error: Error in getting fileData for nodeType. Error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:51.522Z - error: Failed to read the nodetype, Error: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:34:51.522Z - info: Checking if password expired

    2019-01-07T03:34:52.530Z - info: Error trying sshing directly, Error: connect ECONNREFUSED 192.168.2.9:22

    2019-01-07T03:34:52.531Z - error: Root login failed for source VC: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:35:22.663Z - info: THUMBPRINT(vCenterAppliance): 8D:AF:E8:D5:31:1B:4E:63:FE:E6:2F:EC:3A:A0:31:C6:E0:EC:53:2B

    2019-01-07T03:35:22.676Z - info: THUMBPRINT(esxiHost): 7D:3B:E5:5E:4C:5B:95:D8:A6:CD:A7:7E:5E:36:6C:40:58:13:63:40

    2019-01-07T03:35:24.885Z - info: attemptHttpsConnToSourceVc

    2019-01-07T03:35:24.913Z - info: login() to source VC:192.168.2.9

    2019-01-07T03:35:24.914Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:35:25.008Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:35:25.024Z - debug: session exists: 192.168.2.9, administrator@vsphere.local, 5285cde1-3267-b5b9-64a7-5f45b01ee91c

    2019-01-07T03:35:25.039Z - info: successfully logged out from 192.168.2.9, administrator@vsphere.local, 5285cde1-3267-b5b9-64a7-5f45b01ee91c

    2019-01-07T03:35:25.039Z - info: initializing vsphere API connection to 192.168.2.9:443

    2019-01-07T03:35:25.119Z - info: vimService apiType: VirtualCenter, version: 6.5.0

    2019-01-07T03:35:25.120Z - debug: Logging in to 192.168.2.9:443 as administrator@vsphere.local

    2019-01-07T03:35:25.177Z - info: Logged in to 192.168.2.9:443 as administrator@vsphere.local, session: 52cfd3ef-a51c-2684-c49f-c0b5d3965ea1

    2019-01-07T03:35:25.178Z - info: Login successful to source VC, IP: 192.168.2.9

    2019-01-07T03:35:25.178Z - info: login() to host managing the source VC:192.168.2.5

    2019-01-07T03:35:25.178Z - info: initializing vsphere API connection to 192.168.2.5:443

    2019-01-07T03:35:25.226Z - info: vimService apiType: HostAgent, version: 6.5.0

    2019-01-07T03:35:25.239Z - debug: session exists: 192.168.2.5, root, 522c9baa-8339-5894-a497-490d44e03b3a

    2019-01-07T03:35:25.251Z - info: successfully logged out from 192.168.2.5, root, 522c9baa-8339-5894-a497-490d44e03b3a

    2019-01-07T03:35:25.251Z - info: initializing vsphere API connection to 192.168.2.5:443

    2019-01-07T03:35:25.318Z - info: vimService apiType: HostAgent, version: 6.5.0

    2019-01-07T03:35:25.318Z - debug: Logging in to 192.168.2.5:443 as root

    2019-01-07T03:35:25.374Z - info: Logged in to 192.168.2.5:443 as root, session: 52b4fd33-0d36-50b4-75e5-d97084d2f5ca

    2019-01-07T03:35:25.374Z - info: Login successful to host for source VC, IP: 192.168.2.5:443

    2019-01-07T03:35:25.374Z - info: sourceVcService: Source VC Version=6.5, minVersion=6, maxVersion=6.7

    2019-01-07T03:35:25.374Z - info: Source VC, version: 6.5.0, isOSLinux: true

    2019-01-07T03:35:25.374Z - debug: isIp: 192.168.2.9: true

    2019-01-07T03:35:25.374Z - debug: getVmWithIPFQDN: hostName 192.168.2.9 is associated with [ '192.168.2.9' ]

    2019-01-07T03:35:25.428Z - debug: token:undefined, length:11, running total:11

    2019-01-07T03:35:25.428Z - debug: vm found by IP: 192.168.2.9

    2019-01-07T03:35:25.429Z - info: VM with hostName 192.168.2.9: { _type: 'VirtualMachine',

      _moid: '27',

      config: { template: false },

      guest:

       { hostName: 'photon-machine',

         ipAddress: '192.168.2.9',

         net: [ [Object] ] },

      name: '009vcsa(192.168.2.9)',

      parent: { value: 'ha-folder-vm', type: 'Folder' },

      runtime: { host: { value: 'ha-host', type: 'HostSystem' } },

      summary:

       { storage:

          { committed: 63540112898,

            uncommitted: 194009636242,

            unshared: 63540112898,

            timestamp: 2018-11-25T22:08:36.178Z } } }

    2019-01-07T03:35:25.429Z - info: VM Identifier for Source VC: 27

    2019-01-07T03:35:25.576Z - debug: initiateFileTransferFromGuest error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:35:25.576Z - debug: Failed to get fileTransferInfo:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:35:25.576Z - debug: Failed to get url of file in guest vm:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:35:25.576Z - error: Error in getting fileData for nodeType. Error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:35:25.576Z - error: Failed to read the nodetype, Error: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:35:25.576Z - info: Checking if password expired

    2019-01-07T03:35:26.590Z - info: Error trying sshing directly, Error: connect ECONNREFUSED 192.168.2.9:22

    2019-01-07T03:35:26.590Z - error: Root login failed for source VC: Failed to authenticate with the guest operating system using the supplied credentials.

    2019-01-07T03:35:36.442Z - info: Log file was saved at: D:\BaiduNetdiskDownload\VMware-VCSA-all-6.7.0-10244745\vcsa-ui-installer\win32\installer-20190107-112849784.log

    在更新VCSA6.5的时候出现了该报错信息!


    0 0

    I have no space left on my XP VM in 8.5.10 and it now starts to a jam. No error messages, but also no reclaimable space in the pre-start screen.

     

    It is so full that it wont even run reclaim properly or if it does, it doesnt show anything as having been reclaimed.There must have been 12 gb of it when I last looked??  trying to reclaim 10-12 times did once show 12.3 gb of reclaimable space but reclaim wouldnt reclaim anything and all bars now show as completely full.

     

    The VM also wont do an F8 boot (or a Fn-F8 boot) and the only symptom I can identify is that XP starts to a hand=cursor, which wont do anything, it wont even bring up the menu! I can only close the vm by shutting down in the Fusion menu.

     

    I can get into settings in the VMs desktop but cant do much once I get there. 

     

    i would love to identify what suddenly filled all that space!


    0 0
  • 01/03/19--23:45: schedule Remove-snapshot
  • Hi, I'm New User for PowerCLI,I have a question for schedule Remove-snapshot:

     

    for example:

    I have been created a snapshot in PowerCLI for my vm:

    $Date = Get-Date -UFormat %Y%m%d

    $timechop = Get-Date -Format g

    get-vm | where {$_.PowerState -eq "PoweredOn"} | where {$_.Name -match "Linux"} | New-Snapshot -Name "$Date" -Description "PowerCLI Weekly Snapshot at $timechop"

     

    get-vm | where {$_.PowerState -eq "PoweredOn"} | where {$_.Name -match "Linux"} | Get-Snapshot

    Name                 Description                    PowerState

    ----                 -----------                    ----------

    20190104             PowerCLI Weekly Snapshot at... PoweredOn

     

    Now the question:

    I need to Schedule Remove the Snapshot Before 7 days ago (according the snapshot create day,for example:20190104,autoremove the named"20190104" when the current date is change to 20190111),how to write the scripts?

     

    thanks a lot!


    0 0
  • 01/06/19--19:05: OVF deployment issue
  • Hi

     

    When I deployed VMs through vCenter, and found a dynamic disk appearing , and why?Thanks


    0 0

    Author : Joseph Sciallo

    URL : http:////docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.psc.doc/GUID-98B36135-CDC1-435C-8F27-5E0D0187FF7E.html

    Topic Name : Active Directory LDAP Server and OpenLDAP Server Identity Source Settings

    Publication Name : Platform Services Controller Administration

    Product/Version : VMware vSphere/6.5

    Question :

    LdaP authentication is done ,but still im unable to access.domain is also added. it is 6.7 version


    0 0

    Hello.

    I don't like my ESXi host see the internet but VMs can. How can I block ESXi host?

     

    Thank you.


    0 0

    Hello,

    I currently have the following setup:

    VMs are sometimes being provisioned in networks, where other VMs, not provisioned by vRA, reside. The IPs in these networks are handed out by DHCP (on a NSX-V edge).

    I need to be able to provision and add new adapters to the vm in this DHCP-provisioned network.

     

    The deployment itself seems to work fine. I have created a new external network profile, that has no IP ranges set, only the basic options. I had no other ooption but to select the vRA IPAM endpoint, even though I do not want to use it in this case. This profile is attached to some reservations, then it is mapped to the dvs port group (network), where DHCP hands out the adresses. During provisiong, the network adapter of the vm gets connected to this portgorup and after power-on an IP gets assigned.

     

    However, when I want to add a new adapter to the VM and select the DHCP-provisioned network during the Reconfigure Action in the Network Tab, the request fails:

    java.lang.RuntimeException: [Error code: 42000 ] - [Error Msg: Infrastructure service provider error: The list of unallocated IP addresses for the network profile [MyProfileName] has been exhausted.]

     

    What would be an elegant solution to this problem? Is it possible to create a network profile that would not be tied to the vRA IPAM? The only purpose of this profile would be to attach the adapter to the selected port group. Similar how you could do it back in vRA 6 with a private network profile.

     

    Edit: I've managed to solve this last week. Now I just assign a network without the profile to reservations for groups that need it. During provisioning a user can also choose this dhcp-provisioned network from a drop down using a friendly name, or just choose a network profile which has an IPAM-provisioned assigned.


    0 0
  • 01/06/19--16:30: upgrade 6.5 U1 to 6.5 U2
  • Hello,

     

    I'm upgrading vcenter with external psc from 6.5 U1 to 6.5 U2.

     

    The first step of PSC upgrade was OK but i had an issue in step 2. The issue was appeared during the pre-upgrade check.

    When i looked into the log files I saw that there was an issue with ntp service.

     

    2019-01-06T23:37:26.510Z INFO service_manager Service vmware-stsd: STARTED

    2019-01-06T23:37:26.510Z INFO sdk_utils Appliance has version 6.5.0.0

    2019-01-06T23:37:26.517Z ERROR transport Command ['/sbin/chkconfig', 'ntp'] exit-code=1, stdout=, stderr=ntp: unknown service

     

    I ran the command /sbin/chkconfig ntp on the psc server. These were the results.

     

     

    root@psc [ ~ ]# /sbin/chkconfig ntp

    ntp: unknown service

    root@psc [ ~ ]# /sbin/chkconfig ntpd

    Note: Forwarding request to 'systemctl is-enabled ntpd.service'.

    enabled

    root@psc [ ~ ]#

     

    You will find attached the log files.

     

    Can someone help me solve this?


    Thanks


older | 1 | .... | 6724 | 6725 | (Page 6726) | 6727 | 6728 | .... | 6759 | newer