Hi all
Trying to upload a VM to ESXi 6.0 using VMware vCenter Converter Standalone version 6.2.0 but the task will not start giving the message "Invalid configuration for device '0'."
I don't know what this pertains to. The source VM came from Workstation 15 and I thought it may have to do with compatibility level. I tried changing the source VM level to 12 and to 11 but the same message appear. Anyone know what the solution might be?
Thanks
HI,
We have just migrated from a Windows VCenter to a VCSA 6.7 (update 2), OLD VCenter was integrated with the ADirectory and We were able to join without troubles. Migration ended succesfully.
Our question is for the new configuration, new VCSA keeps old network settings, including DNS client settings, but old Windows VCenter record were dynamically registred on the AD DNS servers.
The new VCSA will continue be registered dynamically on the DNS record ? or should we create static entries for it in DNS ?
Best Regards
Hi,
Are the predefined Critical Host Patches and vSAN Cluster baselines applicable when using custom vendor ESXi images?
(They show as non compliant but are these really meant to work/tested with vendor custom ESXi?)
If not how should one check for updates when using custom vendor ESXi images and can these checks/downloads be integrated in VUM?
Dell/HP are typical examples where custom images are used so not sure if VUM is still applicable to patch such vendor ESXi images.
Thanks
Hello everyone,
since a week we recognize that the Skyline Health in our VCSA 6.7U3 seems to have some issues.
We see only three tests under Skyline Health and "Under Online Health Availability" "Online health checks execution" has a yellow mark. The "Online health connectivity" and "Customer experience improvement program (CEIP)" are green.
When we click "Retest" it will work für some time and shows us the tests but then it goes back in the faulty state. A restart of the Appliance changed nothing.
The Ask VMware link is useless. It leeds only to this page VMware Support Offerings & Services.
So where can i look what the problem is or have anyone a suggestion what to do ?
Best regards Sven
Hi, I tried to add my vSphere Host to vCenter, but This error occurred. vSphere says "Failed - Cannot change the host configuration." How to fix this?
I have created a SMB and NFS share to contain the Vcenter Management server backup and i cannot connect to the share via the Management interface. The interface give the error "Access to the backup server is denied - Check your credentials" .
Both shares have been tested, as i can connected to each of them via NFS and SMB by mouting them on a linux machine with the following commands
#SMB Share
//IP Address/backup /mnt/backup cifs vers=2.0,username=admin,password=adminpaassword,uid=1024,gid=100,iocharset=utf8,rw
OR
#NFS Shares
IP address:/volume1/backup /mnt/backup nfs rsize=8192,wsize=8192,timeo=14,intr
I am also able to connect to these shares via Windows.
Can someone let me know of how i can fix this? ans also the filename and location of the log that records theses attempts. maybe there is more info there.
Thank you in advance.
Hello all,
I have a customer who has two vCenter Servers, version 6.0, running in Enhanced Linked Mode. Due to organizational changes, we need to separate the two vCenter Servers from each other, that is, break the Enhanced Linked Mode.
We would like to keep both vCenter Servers running as is due to integration with other products and not have to kill one of them and install a new instance.
Is there any (supported) way to split the servers in Enhanced Linked Mode?
Thanks!
// Matts
Hello All,
My vSphere Client suddenly can't connect to vCenter Server.
Use command to login, but receive a "Error in service module” error message
This Error is vCenter Server web.
Immediate session timeout when logging into vCenter Server Appliance.
Restart vCenter Server with a lot of error messages.
I don't know what happened..
We have to decomission a vcenter with embedded PSC from an ELM configuration
The main Vcenter with its embedded PSC will remain in HQ site .
Following the kb VMware Knowledge Base we performed the below steps
On the vcenter/PSC to be decomissioned we first run the command to unregister the vcenter
cmsso-util unregister --node-pnid prdvcsadr.xxx.com --username administrator@vsphere.local --passwd xxxx
the command reported
020-07-15T12:58:55.651Z Running command: ['/usr/lib/vmware-vmafd/bin/dir-cli', 'service', 'list', '--login', 'administrator@vsphere.local']
2020-07-15T12:58:55.754Z Done running command
2020-07-15T12:58:56.124Z RC = 1
Stdout = vdcleavefd offline for server prdvcsadr.xxx.com
Leave federation cleanup failed. Error[1] - Operations error
Stderr = password:
ERROR unregistering computer account.
Success
2020-07-15T12:58:56.125Z Running command: ['/usr/bin/sed', '-i', '-e', 's/cmsso-util.*/cmsso-util/g', '/var/log/vmware/procstate']
2020-07-15T12:58:59.972Z Done running command
After that we checked the main Vcenter and we found that the remote vcenter was correctly removed
So we went through the step to unregister the remote's PSC from the main site
We shut down the DR appliance ( PSC) and performed the following command on the main site's appliance
root@prdvcsa [ ~ ]# cmsso-util unregister --node-pnid prdvcsadr.xxxx.com - -username administrator@vsphere.local--passwd xxxx
and got the following error
Could not find a host id which maps to prdvcsadr.xxxx.com in Component Manage r
Failed!!!
2020-07-15T13:22:17.609Z Running command: ['/usr/bin/sed', '-i', '-e', 's/cmss o-util.*/cmsso-util/g', '/var/log/vmware/procstate']
2020-07-15T13:22:17.709Z Done running command
Can anyone explain if this expected since we already unregister the DR's vcenter or if there's something wrong in the procedure ?
thanks
I can log in with putty as root user into vcenter server and execute DCLI commands. If I log in with other user that is in group (SystemConfiguration.BashShellAdministrators) I am unable to run DCLI commands.
I get the below message:
/usr/bin/python: Error while finding module specification for 'vmware.vapi.client.dcli.cli' (ImportError: No module named 'vmware')
Is it possible for another user besides root user to access and use DCLI from SSH connection?
I have installed vCenter6.7 on ESXi 6.7 host. In the vCenter appliance I'm seeing the below log message continuously in /var/log/vmware/messages log file.
2020-07-15T08:20:01.112590-07:00 glhc-vcsa sshd 39441 - - pam_mgmt_cli(sshd:auth): authentication successful, but failed to connect to applmgmt service (254):
2020-07-15T08:20:01.029120-07:00 glhc-vcsa cli - - - vmware.vherd.linux_cli.cli Error getting authentication cookie from applmgmt service. Verify that the applmgmt service is running and that the method requested to obtain the cookie requires authentication.
However when I login into the vCenter appliance and check the status of applmgmt service it is showing as running. However I have started restarting the service and still the issue is not solved.
How to resolve this issue?
Hello,
Please, could someone help me with these basic questions?
I have two physical virtualization servers and one storage directed attached. Both servers runs ESXi with vCenter Essential Plus license (supporting HA and Fault Tolerance).
I have one virtual machine in Fault Tolerance scope (with 4 vCPUs = 4 vCPUs for shadow and 4 vCPUs for active VM).
I have one virtual machine running only in physical server 1 and I have other one virtual machine running only in physical server 2
Now I also need the virtual machine for vCenter that manages the cluster. And the doubts are:
Does the vCenter virtual machine needs to be run under HA?
Is the vCenter virtual machine used just to configure (and diagnose) the servers and all these configurations are stored on the ESXi servers? I have the doubt because if I lost the physical server 1 and the vCenter virtual machine goes down (because it was running on this server 1), then I lost my architecture, cluster management and etc. Is it?
Thank you so much! And kindly sorry for these basic doubts.
Eduardo
Has anyone successfully configured vcenter 6.7 appliance (I have update 3g) to send email to office 365? I've changed the relay server to smtp.office365.com, the mail sender to the from email address i'm using. Then under advanced settings i'm changing mail.smtp.port to 587, mail.smtp.username to the same account I used for mail sender, and mail.smtp.password to that account password.
Considerations:
anonymous relay to internal smtp server works fine. Trying to get away from it.
This username/password works. I'm using it successfully for other mail relays.
vcenter can ping smtp.office365.com and telnet to 587.
I know for this type of relay the from address has to match the authenticating user. Which is why I assumed they have the mail sender box
I've seen a lot of articles about hows its not supported on earlier versions but accounding to this it is supported after vCenter 6.7 U1 and 6.5 U2d.
Appliance TLS output
==================== Scanning vCenter Server TLS endpoints =====================
+---------------------+-------------------+----------------+
| Service Name | TLS Endpoint Port | TLS Version(s) |
+---------------------+-------------------+----------------+
| vmcam | | NOT RUNNING |
| vmware-rhttpproxy | 443 | TLSv1.2 |
| vmware-stsd | 7444 | TLSv1.2 |
| vami-lighttp | 5480 | TLSv1.2 |
| vmware-updatemgr | 8084 | TLSv1.2 |
| vmware-updatemgr | 9087 | TLSv1.2 |
| vmware-rbd-watchdog | | NOT RUNNING |
| vmdird | 636 | TLSv1.2 |
| rsyslog | 1514 | TLSv1.2 |
| VC Storage Clients | NOT APPLICABLE | TLSv1.2 |
| vmware-vpxd | 8089 | TLSv1.2 |
| vsphere-client | 9443 | TLSv1.2 |
+---------------------+-------------------+----------------+
Hello,
i tried to upgrade my vcenter 6.5 to last release available for my installation : VMware vCenter Server v6.5.0.6430.
The installation start but after few minutes stuck on this problem : "Installation of component VCSServiceManager failed with error code '1603'
Now the old installation does not start with this problem related on vmon.log
Service cm api-health command's stderr: ERROR:root:CM search failed. ProductId=com.vmware.cis, TypeId=cs.identity
2020-07-16T00:46:44.116+02:00| vthread-5| W115:
2020-07-16T00:46:44.116+02:00| vthread-5| W115: Service cm api-health command's stderr: ERROR:root:Error connecting to CM: {
2020-07-16T00:46:44.116+02:00| vthread-5| W115+ "resolution": {
2020-07-16T00:46:44.116+02:00| vthread-5| W115+ "id": "install.default.failure.resolution",
2020-07-16T00:46:44.116+02:00| vthread-5| W115+ "localized": "This is an unrecoverable error, please retry install. If you encounter this error again, please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request.",
2020-07-16T00:46:44.116+02:00| vthread-5| W115+ "translatable": "This is an unrecoverable error, please retry install. If you encounter this error again, please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request."
2020-07-16T00:46:44.116+02:00| vthread-5| W115+ },
2020-07-16T00:46:44.116+02:00| vthread-5| W115+ "detail": [
2020-07-16T00:46:44.116+02:00| vthread-5| W115+ {
2020-07-16T00:46:44.116+02:00| vthread-5| W115+ "args": [
2020-07-16T00:46:44.116+02:00| vthread-5| W115+ "CM search failed. ProductId=com.vmware.cis, TypeId=cs.identity:[Errno 10061] No connection could be made because the target machine actively refused it"
2020-07-16T00:46:44.116+02:00| vthread-5| W115+ ],
2020-07-16T00:46:44.116+02:00| vthread-5| W115+ "id": "install.ciscommon.internal.error",
2020-07-16T00:46:44.116+02:00| vthread-5| W115+ "localized": "Encountered an internal error.\n\nCM search failed. ProductId=com.vmware.cis, TypeId=cs.identity:[Errno 10061] No connection could be made because the target machine actively refused it",
2020-07-16T00:46:44.116+02:00| vthread-5| W115+ "translatable": "Encountered an internal error.\n\n%(0)s"
2020-07-16T00:46:44.116+02:00| vthread-5| W115+ }
2020-07-16T00:46:44.116+02:00| vthread-5| W115+ ],
2020-07-16T00:46:44.116+02:00| vthread-5| W115+ "componentKey": null,
2020-07-16T00:46:44.116+02:00| vthread-5| W115+ "problemId": null
2020-07-16T00:46:44.116+02:00| vthread-5| W115+ }
2020-07-16T00:46:44.116+02:00| vthread-5| W115:
Some ideas for fix this problem ?
Thank you so much
Alessandro.
hi - wondering if a guru can help a home labber?!
My VCSA update on 7.0 is spinning at 0%
if I click cancel i get this error:
with this in the applmgmt.log:
2020-07-15T05:35:14.678 [21601]ERROR:vmware.vapi.provider.local:Error in invoking com.vmware.appliance.update in cancel - [Errno 2] No such file or directory
Traceback (most recent call last):
File "/usr/lib/applmgmt/vapi/lib/vapi_runtime-2.100.0-py2.py3-none-any.whl/vmware/vapi/provider/local.py", line 277, in invoke
service_id, operation_id, input_value, ctx)
File "/usr/lib/applmgmt/vapi/lib/vapi_runtime-2.100.0-py2.py3-none-any.whl/vmware/vapi/provider/local.py", line 248, in _invoke_int
method_result = iface.invoke(ctx, method_id, input_value)
File "/usr/lib/applmgmt/vapi/lib/vapi_runtime-2.100.0-py2.py3-none-any.whl/vmware/vapi/bindings/skeleton.py", line 371, in invoke
meth_output = method(**meth_args)
File "/usr/lib/applmgmt/vapi/py/vmware/appliance/vapi/appliance_impl.py", line 78, in cancel
s.sendto(b'{"rpc": "cancel"}', MICROSERVICE_SOCKFILE)
FileNotFoundError: [Errno 2] No such file or directory
My update files staged successfully into /storage/updatemgr/software-update6yt9kjw9/
however in update_microservice.log i see:
]# tail update_microservice.log
2020-07-15 05:23:31,104 - 29269 - update_b2b:: _is_staged:2439 - DEBUG - Checking if version 7.0.0.10400 is already staged
2020-07-15 05:23:31,104 - 29269 - dbfunctions:: executeDML: 54 - DEBUG - Executing Query {SELECT _value from config where _config = ?} with parameters ('stageDir',)
2020-07-15 05:23:31,105 - 29269 - update_b2b:: install:2061 - DEBUG - Scanning stage directory /storage/updatemgr/software-update6yt9kjw9/stage
2020-07-15 05:23:31,105 - 29269 - update_functions:: readJsonFile: 224 - ERROR - Can't read JSON file /storage/updatemgr/software-update6yt9kjw9/stage/pkg_list [Errno 2] No such file or directory: '/storage/updatemgr/software-update6yt9kjw9/stage/pkg_list'
2020-07-15 05:23:31,105 - 29269 - update_b2b:: install:2065 - DEBUG - Exception occurred while checking for discrepancies [Errno 2] No such file or directory: '/storage/updatemgr/software-update6yt9kjw9/stage/pkg_list'
2020-07-15 05:23:31,105 - 29269 - update_microservice:: _runEvent: 409 - DEBUG - Event callback succeeded
2020-07-15 05:24:01,155 - 29269 - update_microservice:: waitForEvents: 473 - INFO - Exiting by timeout
2020-07-15 05:24:01,156 - 29269 - update_microservice:: __del__: 359 - DEBUG - Closing socket...
2020-07-15 05:24:01,156 - 29269 - update_microservice:: __del__: 361 - DEBUG - Removing sockfile
2020-07-15 05:24:01,156 - 29269 - update_microservice:: _deletePidFile: 297 - DEBUG - Removing pid file: /var/run/vmware/applmgmt/update_microservice.pid
Does anyone have any thoughts why this error occurs?
Can't read JSON file /storage/updatemgr/software-update6yt9kjw9/stage/pkg_list
thanks!
ps: I can successfully cancel the update using VMware Knowledge Base but wondering why it isnt working.
Message was edited by: mgillard
Hi,
I'm testing cutomization profile for Ubuntu 20.04 after upgrading vCenter to 6.7 U3g and ESXi to last critical patches.
The customization profile, executing perl commands, errors with the following error in /var/log/vmware-imc/toolsDeployPkg.log:
[...]
[Many errors removing lock '/tmp/.vmware-deploy.***** files]
[...]
INFO: Check if hostnamectl is available
[DEBUG]: Command: 'hostnamectl status 2>/tmp/guest.customization.stderr'
[DEBUG]: Result:
[DEBUG]: Exit Code: 256
[DEBUG]: Stderr: ^[[0;1;31mFailed to create bus connection: No such file or directory^[[0m
[...]
[ error] Customization command failed with stderr: '^[[0;1;31mFailed to create bus connection: No such file or directory^[[0m'.
[...]
I hace tried to apply the workarounds shown at VMware Knowledge Base with same results.
I have seen that customization tries to apply ubuntu 19.10 instance:
[...]
INFO: Customization instance Ubuntu1910Customization loaded.
[...]
If I try with Ubuntu 18.04 it works correctly.
Any clue on this? Is Ubuntu 20.04 still not working with customization in vCenter 6.7 U3g?
REgards,
Hi there,
I am seeking some help from the community for a specific case I am experiencing now.
My Current vCenter is a 6.7 appliance last version but historically it has been deployed with the SSO domain same as hostname fqdn.
It works pretty well so far but I know this is not supported by VMware and documentation warns about this case. Unfortunately I am not the one who deployed this vCenter....
Now I need to change the SSO domain to vsphere.local and link a remote vcenter to this one. Indeed there is no way I keep the current SSO domain as the configuration is not following the best practices.
So I used the command to repoint vcenter to a new sso domain and the repointing fails, after some troubleshoot, it appears that the URLs in the SSO configuration uses the new SSO domain as endpoint..... and not the hostname of the vcenter.
Doing the same thing with a vcenter that have a SSO domain different from hostname from the begining works perfectly.
Any one when through this specific case ?
Thank you !!!!!
Hi, When submitting CSR for custom certificates for vCenter Solution Users, machine, vpxd, vpxd-extension, & vsphere-webclient, does anyone know what is the correct information to submit?
Is it same type of key as for vCenter, ESXi, etc., such as 2048-bit SSL server enrollment form to include Multi-SAN with Extended Key Usage?
What would the following be for each Solution User?
Common Name
DNS Name
IP Address
URI
Also, what would be the best service type to select for Solution Users from list below?
Thank you!
I've been trying to figure this out for a little while now but I keep getting stuck. I've been trying to make a script that will update move vms then update the host but I can't get the host update part to work. I keep getting this error and I really don't know which logs to look in or what other things to try.
I did recently update from 6.7 to 7
Update-Entity : 7/16/2020 9:45:01 AM Update-Entity Remediate Inventory on entity 'esxi04' failed with following error: ''registry.proxy.' is invalid or exceeds the maximum number of characters permitted.'.
If anyone has any suggestions I'm all ears
Hi everyone,
i'am looking to get an Monitoring up for VCSA and nagios.
REST API Reference Documentation
interesting is. the only Call which works for me is
https://ip/rest/appliance/health/applmgmt
Response = 200 OK
for all the others i'am getting Response = Unauthorized (like database-storage)
But i'am authorized,..... so sounds like an Bug or something
thx
Max
