Archive for the ‘virtualization’ Category

source:
VMware vCenter Server 5.5.0 (Windows 2012R2, MSSQL 2012 Express), 12GB RAM

target:
VMware vCenter 6.0 U3 Appliance (Linux, PostgreSQL), 16 GB RAM

 

Error:

  • Firstboot script execution error
  • This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request
  • /var/log/firstboot/vpostgres-firstboot.py_16503_stderr.log
  • install.ciscommon.internal.error
  • This vCenter Server has extensions registered that cannot be upgraded to or may not work with the new vCenter Server. Extensions: VR Management (by VMware, Inc.) on http://vcenter:80/|https://appliancevr:8043 VMware vSphere Update Manager Extension on https://vcenter:8084/vci/sdk vCenter Operations Manager (by VMware, Inc.) on https://new_vcenter/vcops-vsphere/viClientConfig.xml

 

Znalezione obrazy dla zapytania vcenter fastboot failed

 

on logs:

csd.txt :
[2018-05-23 15:28:44] [INFO] Web Socket Server [50100] Terminated With no error code
[2018-05-23 15:28:44] [INFO] CSD Server Exited.
[2018-05-23 15:28:44] [INFO] Lookup: stop called…
[2018-05-23 15:28:44] [INFO] Lifetime: join…
[2018-05-23 15:28:47] [INFO] Lifetime Timer stopped.
[2018-05-23 15:28:47] [INFO] Lifetime: Exited.
[2018-05-23 15:28:47] [INFO] Lookup: Exited.
[2018-05-23 15:28:47] [INFO] ~MigrationApi
[2018-05-23 15:28:47] [INFO] Process exiting.
vcsa_0001.txt:
2018-05-23 14:47:23.065316 CIP Service [VCSA INFO] nfc.vmGetFile: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5509″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”cQk5-Fj2d-VuiB-e1PL”,”result”:”{\n \”status\”: \”error\”, \n \”info\”: [], \n \”question\”: null, \n \”progress_message\”: {\n \”args\”: [\n \”VMware Postgres\”\n ], \n \”id\”: \”install.ciscommon.component.starting\”, \n \”localized\”: \”Starting VMware Postgres…\”, \n \”translatable\”: \”Starting %(0)s…\”\n }, \n \”warning\”: [], \n \”error\”: {\n \”resolution\”: {\n \”id\”: \”install.default.failure.resolution\”, \n \”localized\”: \”This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request.\“, \n \”translatable\”: \”This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request.\”\n }, \n \”detail\”: [\n {\n \”args\”: [\n \”see /var/log/firstboot/vpostgres-firstboot.py_16503_stderr.log\”\n ], \n \”id\”: \”install.ciscommon.internal.error\”, \n \”localized\”: \”Encountered an internal error.\\n\\nsee /var/log/firstboot/vpostgres-firstboot.py_16503_stderr.log\“, \n \”translatable\”: \”Encountered an internal error.\\n\\n%(0)s\”\n }\n ], \n \”componentKey\”: \”vpostgres\”, \n \”problemId\”: null\n }, \n \”progress\”: 48\n}”,”isFinal”:”true”}
2018-05-23 14:47:23.068319 Progress Page: [VCSA ERROR] – First Boot error
2018-05-23 14:47:28.784075 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5515″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”D2ER-tpuj-51BF-Unl0″,”result”:””,”isFinal”:”false”,”item”:[“{\”error\”:\”vim.fault.FileNotFound\”}”]}
2018-05-23 14:47:30.187195 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5515″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”D2ER-tpuj-51BF-Unl0″,”result”:””,”isFinal”:”true”}
2018-05-23 14:47:30.191199 Progress Page: [VCSA ERROR] Error in downloading support bundle
2018-05-23 14:48:10.911286 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5521″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”fNmx-IuPq-78cR-k5BZ”,”result”:””,”isFinal”:”false”,”item”:[“{\”error\”:\”vim.fault.FileNotFound\”}”]}
2018-05-23 14:48:12.316936 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5521″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”fNmx-IuPq-78cR-k5BZ”,”result”:””,”isFinal”:”true”}
2018-05-23 14:48:12.320941 Progress Page: [VCSA ERROR] Error in downloading support bundle
2018-05-23 14:48:53.037021 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5527″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”u4fv-YEyW-ODJE-aHO5″,”result”:””,”isFinal”:”false”,”item”:[“{\”error\”:\”vim.fault.FileNotFound\”}”]}
2018-05-23 14:48:54.440281 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5527″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”u4fv-YEyW-ODJE-aHO5″,”result”:””,”isFinal”:”true”}
2018-05-23 14:48:54.443297 Progress Page: [VCSA ERROR] Error in downloading support bundle
2018-05-23 14:49:38.771027 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5534″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”tfqA-CRMH-XOIh-bOXA”,”result”:””,”isFinal”:”false”,”item”:[“{\”data\”:\”\”}”]}
2018-05-23 14:49:39.573271 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5534″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”tfqA-CRMH-XOIh-bOXA”,”result”:””,”isFinal”:”true”}
2018-05-23 14:49:39.577275 Progress Page: [USER INFO] Support bundle created successfully – {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5534″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”tfqA-CRMH-XOIh-bOXA”,”result”:””,”isFinal”:”true”}
2018-05-23 15:14:49.825467 Progress Footer: Closing the installation wizard

 

what to check:

  1. Check DNS, forward and reverse resolution
  2. Check NTP server, try to sync time
  3. Plug-in not compatible is better to unregister/uninstall:  how to.
    I uninstalled: Update Manager, Operations Manager, UCS Plugin, VR Plugin
  4. In our environment Replication Appliance was incompatible with new version of vCenter. I stopped all replication jobs, unregistered Appliance (how to). Stopped VR Appliance.
  5. Check the database size…

 

Resolution:

In my situation, 8GB database (MSSQL) on Win2012R2 with 12GB RAM (small vCenter, 1000VM), was migrated to the same, small vCenter on Linux (1000 VM), with 16 GB RAM.

… it was to small.
I modified: vCenter Server to 32GB RAM,
on migration step I choose Large vCenter (32GB RAM) to create large vCenter Appliance

Success :)

ps. after this, I downsized RAM to 16GB :)

 

VMware Appliance size

 

RESULT:

VMware Migration result

 

 

Advertisements

Problem:

Type: Consistency check Status: Failed Description: DPM cannot continue protection for VMware <vm_name> on <vCenter_server/ESX host IP>  (ID 30184) More information End time: 2018-03-12 23:48:37 Start time: 2018-03-12 23:48:37 Time elapsed: 00:00:00 Data transferred: 0 MB Cluster node – Source details: <vm_name> Protection group: Protection Group 1 Items scanned: 0 Items fixed: 0

 

Resolution:

Problem with VM *.vmx file.

  • Delete vmx and recreate VM
    or
  • create new VM and bind hdd from old VM.

Problem:

Recently I noticed running out of space on one of Hyper-V host. There was only ~10% free space. Couple of VM was placed out of clustered storage, on local RAID.

But what was strange, this VM has ~100 AVHDX files and 1 main VHDX file, but there was no checkpoints!

Automerge should start automatically, but it doesn’t. So let’s try on my own.

 there are about 100 AVHDX files!

 

but there is no any checkpoint in Hyper-V MMC

 

Resolution:

  1. Automerge : should start automatically. Delete checkpoints, then poweroff VM.
    In my situation, there was not any checkpoint, so automerge didn’t start.
  2. Merge files manually through Hyper-V : Hyper-V MMC -> edit disk -> locate latest AVHDX file (by date modification). Repeat procedure until you achieve one VHDX file.
    In my situation (~100 AVHDX files) it would take too long :) 
  3. Merge files manually – without Hyper-V :
    a) download VHDUtils from here
    b) extract makevhd.exe file to VM AVHDX files localization
    c) on cmd or PS run command:
    makevhd -d   merged-disk.vhd   0   latest-modified-avhdx-file.avhd
    d) wait, there will be no progress bar
    e) when merging has completed – attach VHDX to VM.
    You may have “Cannot change disk since a disk merging is pending” warning – just remove HDD from VM, apply VM settings, and then re-add newly merged VDHX file to VM.

That’s it.

Scenario:
3-node cluster has access to one disk with GFS/GFS2 filesystem.

  • node1 – offline
  • node2 – offline
  • node3 – online

Node3 waits for other nodes to connect. Unfortunately, node2 and node 3 are phisically damaged.


Problem:
Cluster cannot start and mount GFS/GFS2 filesystem.
Console shows errors:

can't connect to gfs_controld: Connection refused  
can't connect to gfs_controld: Connection refused  
gfs_controld not running  
error mounting lockproto lock_dlm

or

gfs_controld join connect error: Connection refused
error mounting lockproto lock_dlm


Resulution:
Convert GFS/GFS2 cluster to work as a standalone server.
To do this we need to change superblock locking protocol of GFS/GFS2 filesystem.


Check what is current type of locking protocol:

 

gfs_tool sb <device> proto
gfs2_tool sb <device> proto

ex.:
gfs_tool sb /dev/sdb proto
gfs2_tool sb /dev/sdb proto


Change superblock locking protocol to lock_nolock:

gfs_tool sb <device> proto lock_nolock
gfs2_tool sb <device> proto lock_nolock

ex.:
gfs_tool sb /dev/sdb proto lock_nolock
gfs2_tool sb /dev/sdb proto lock_nolock

Restart cluster service or whole server. Disk should mount successfully.
Now you may start to run backup :)


To revert superblock to previous settings, lock_dml, set:

gfs_tool sb <device> proto lock_dlm
gfs2_tool sb <device> proto lock_dlm

ex.:
gfs_tool sb /dev/sdb proto lock_dlm
gfs2_tool sb /dev/sdb proto lock_dlm

 

Helpful commands:

mount -t gfs2 /dev/sdb /mnt/storage
service cman start
service gfs2 start