Just a quick post regarding the following message:
You have reached the maximum number of connected consoles: X. Please contact your administrator
I've been getting this question frequently after reducing the maximum number of connected consoles down to 1 a while back. We've been having issues with Hung Sessions.
To resolve this issue, just vMotion the affected VM to another ESXi host. This will sever the hung console session and allow a user to connect.
We've been moving resource around in Azure and one of the tools we've been using is Microsoft Azure Storage Explorer. One question I get asked frequently is how to resolve the following Certificate error when logging in:
{
"message":
"\"{\\n
\\\"name\\\": \\\"Error\\\",\\n \\\"message\\\": \\\"self signed
certificate in certificate chain\\\",\\n
\\\"stack\\\": \\\"Error: self signed certificate in
certificate chain\\\\n at
TLSSocket.onConnectSecure (node:_tls_wrap:1530:34)\\\\n at TLSSocket.emit
(node:events:390:28)\\\\n at
TLSSocket._finishInit (node:_tls_wrap:944:8)\\\\n at TLSWrap.ssl.onhandshakedone
(node:_tls_wrap:725:12)\\\",\\n
\\\"code\\\":
\\\"SELF_SIGNED_CERT_IN_CHAIN\\\"\\n}\""
}
While updating one of my vCSAs from Update 3j to 3l, the update process would abruptly stop at “Converting Data 80%”.
The following 2 logs should be used to determine if the update was successfully completed:
1. /var/log/vmware/applmgmt/update_microservice.log
2021-03-17 18:13:09,367 - update_script_day0_patching - DEBUG - Patching completed successfully
2021-03-17 18:13:09,368 - vmware.update.extensions - DEBUG - The component script returned 'None'
2021-03-17 18:13:09,374 - vmware.appliance.update.update_b2b - DEBUG - update script result file '{\n "error": null,\n "info": [],\n "progress": 100,\n "progress_message": null,\n "status": "success",\n "warning": []\n}
'
2021-03-17 18:13:09,374 - vmware.appliance.update.update_functions - DEBUG - /var/vmware/applmgmt/patch-history directory created successfully
2021-03-17 18:13:09,388 - vmware.appliance.update.update_b2b - INFO - Setting appliance version 6.7.0.46000 build 17138064
2021-03-17 18:13:09,391 - vmware.appliance.update.update_b2b - DEBUG - Appliance version is updated for login banner
2021-03-17 18:13:09,394 - vmware.appliance.update.update_functions - DEBUG - Running /usr/bin/banner_ctrl reset
2021-03-17 18:13:16,146 - /usr/lib/applmgmt/update/py/vmware/appliance/update/task_manager.py - DEBUG - UpdateTask: status=SUCCEEDED, progress=100, message={'id': 'com.vmware.appliance.install_complete', 'default_message': 'Installation
complete', 'args': []}
2021-03-17 18:13:16,153 - vmware.appliance.update.update_b2b - DEBUG - Installation completed successfully!
2021-03-17 18:13:16,153 - vmware.appliance.update.update_functions - DEBUG - Running reboot
2021-03-17 18:13:21,928 - __main__ - DEBUG - Event callback succeeded
2. /var/log/vmware/applmgmt/upgrade_hook_PatchHook
{
"info": [],
"progress_message": null,
"warning": [],
"status": "success",
"error": null,
"progress": 100
}
This appears to be a "cosmetic" issue and the upgrade completed successfully.
This was the best $14 I've spent on my Homelab.
The processor and memory specs on my Dell PowerEdge R820 running VMWare ESXi 7 are completely fine. Unfortunately, the storage performance was lacking... So, I used a generic $14 PCIe card that allowed me to use an existing M.2 SSD drive as a VMWare datastore. IOPs went from 1K to 54K and power consumption went down by 40W.
Quick video on the process:
One of the limitations of Azure Migrate is that each Azure Migrate Appliance can only be associated with one Migrate project.
After successfully migrating a VM from on-prem to Azure, here’s a quick and easy way to reset the appliance.
1. Open the following JSON file:
C:\ProgramData\Microsoft Azure\Config\appliance.json
Update "IsApplianceRegistered" from "True" to “False” and save the JSON file.
2. Restart the server. Upon restart, the appliance has now been reset.
3. That's it! The appliance is now ready to be used for your next migration project.
Well, that didn't go as planned...
I had a VMWare vCSA that was running version 7.0 GA that was in need of an update. The pre-update check ran successfully, the update was staged (5GB) and I began the installation.
After an hour, the progress was still 0%, I clicked "Cancel Installation" and received the following error:
Error in method invocation [Errno 2] No such file or directory
 |
"Update installation is in progress"
To resolve this issue I SSH'd into the appliance and performed the following:
1. Create a copy of the software_update_state.conf file. The file is located in the /etc/applmgmt/appliance/ directory
cp software_update_state.conf software_update_state_backup.conf
2. Stop the applmgmt service.
service-control --stop applmgmt
3. Delete the software_update_state.conf file.
rm software_update_state.conf
4. Confirm the applmgmt service starts successfully.
service-control --start applmgmt
I was then able to successfully log into the VAMI and complete the install.
5. I un-staged the update. (Neat, reboot not required)
6. This time, I selected "Stage and Install"
7. The update installed successfully and the vCSA is now running the latest release.
This appears to be an issue when a vCSA update is unsuccessful. Deleting the original software update state config file and having the vCSA create a fresh one looks to resolve the issue.
