Joining Esxi to doamin fails with the below message:
[root@esx:~] ./usr/lib/vmware/likewise/bin/domainjoin-cli join ntitta.in
Joining to AD Domain: ntitta.in
With Computer DNS Name: esx.
adm@ntitta.in's password:
Error: LW_ERROR_INVALID_MESSAGE [code 0x00009c46]
The Inter Process message is invalid
Cat /etc/hosts show below:
Cat /etc/hosts
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
::1 localhost.localdomain localhost
192.168.1.104 esx. esx <------------------notice the "esx."In some cases, the hostname on the /etc/hosts file might not match to that of the host. (look for the message on domainjoin-join “With Computer DNS Name: esx.”
In order to sort this out, correct the /etc/host file (in my case, I had to suffix the DNS suffix)
Cat /etc/hosts:
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
::1 localhost.localdomain localhost
192.168.1.104 esx.ntitta.in esx
restart lwsmd
/etc/init.d/lwsmd startRe-attempt doamin join CLI
Note: In some cases after performing the change to /etc/hosts, joining the host via powerCLI will fail with error “‘ vmwauth InvalidHostNameException: The current hostname is invalid: hostname cannot be resolved”
Hostd.log:
2019-01-07T19:20:16.288Z error hostd[DEC1B70] [Originator@6876 sub=ActiveDirectoryAuthentication opID=500fc81b-b5-602f user=vpxuser:IKIGO\nik] vmwauth InvalidHostNameException: The current hostname is invalid: hostname cannot be resolved
The management agents/host will need a restart to sort this out.
services.sh restart
Hello Nick,
did you find out what is causing this issue?
Thanks in advance.
Martin
In the scenario I was working on, the /etc/host file had an invalid hostname (it was ending with an “.” instead of just having the computer name or the FQDN)
Eg:
192.168.1.xx esxi123.
Yes understand, but by default it should be populated by dns domain settings. I’ve tried to fix it with esxcli system hostname set –domain=lab.local and it put an entry to /etc/hosts file automatically. I just would like to know if you was checking why the domain wasn’t populated, because I believe that this is the route cause.
Thanks.
Martin