vmware
VIC Hostname Set Fails After Power Loss
Summary
Lost power to the host running VIC - now I cannot get to the container management page.
Details
Had a power outage due to the heat in California, and as a result the VIC web interface is no longer functioning. Seems for some reason it cannot properly set the host name, which makes the vSphere PSC saml token request fail, I get this when trying to open the webpage:
This site can’t be reachedThe webpage at https://192.168.11.48:8282/auth/psc/callback/token might be temporarily down or it may have moved permanently to a new web address. ERR_INVALID_RESPONSE
journalctl -xe shows this when it's trying to set the host name:
Aug 16 01:58:58 localhost systemd[1]: Started permit root login by ssh based on user provided parameter. Aug 16 01:58:58 localhost dbus-daemon[163]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.2' (uid=0 pid=260 comm="hostnamectl set-hostname error: EOF ") Aug 16 01:58:58 localhost systemd[1]: Starting Hostname Service... Aug 16 01:58:58 localhost dbus-daemon[163]: [system] Successfully activated service 'org.freedesktop.hostname1' Aug 16 01:58:58 localhost systemd[1]: Started Hostname Service. Aug 16 01:58:58 localhost systemd-hostnamed[261]: Changed pretty host name to 'error: EOF' Aug 16 01:58:58 errorEOF systemd-hostnamed[261]: Changed static host name to 'errorEOF' Aug 16 01:58:58 errorEOF systemd-hostnamed[261]: Changed host name to 'errorEOF' Aug 16 01:58:59 errorEOF network-config.sh[162]: [Match] Aug 16 01:58:59 errorEOF network-config.sh[162]: Name=eth0 Aug 16 01:58:59 errorEOF network-config.sh[162]: [Network] Aug 16 01:58:59 errorEOF network-config.sh[162]: Address=error: EOF/16 Aug 16 01:58:59 errorEOF network-config.sh[162]: Gateway=error: EOF Aug 16 01:58:59 errorEOF network-config.sh[162]: DNS=error: EOF Aug 16 01:58:59 errorEOF network-config.sh[162]: Domains=error: EOF Aug 16 01:58:59 errorEOF network-config.sh[162]: [DHCP] Aug 16 01:58:59 errorEOF network-config.sh[162]: UseDNS=false Aug 16 01:58:59 errorEOF network-config.sh[162]: UseDomains=false Aug 16 01:58:59 errorEOF network-config.sh[162]: UseHostname=false Aug 16 01:58:59 errorEOF systemd[1]: Started Network customization based on user provided parameter.
I was able to restore functionality by running: hostnamectl set-hostname 192.168.11.48 Then rebooting the VIC VM. however I don't feel this is necessarily proper.... not only because this also has the effect of changing the root prompt to "root@192" (previously was "root@localhost", then it changed to "root@errorEOF" due to this issue) but shouldn't this be set from the OVF environment and not something within the VM?
I also have the same issue, do you finally find a way to properly fix it ? Thx
I have not found a proper fix for this yet, but it's been running in this manner for a while now and I haven't had any issues thus far. Would be nice to see this bug fixed however.
Ok, my VIC host was completely unaccessible for a reason I still ignored. errorEOF was also present in VIC log file ... I finally apply the same fix you did on the VIC host :
hostnamectl set-hostname "vic server ip" reboot
now everything works fine !
Thank you very much :)
Ok, my VIC host was completely unaccessible for a reason I still ignored. errorEOF was also present in VIC log file ... I finally apply the same fix you did on the VIC host :
hostnamectl set-hostname "vic server ip" reboot
now everything works fine !
Thank you very much :)
I'm glad to see my work figuring this one out helped someone!