Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VIC Hostname Set Fails After Power Loss #8643

Open
KLEPTOROTH opened this issue Aug 16, 2020 · 6 comments
Open

VIC Hostname Set Fails After Power Loss #8643

KLEPTOROTH opened this issue Aug 16, 2020 · 6 comments

Comments

@KLEPTOROTH
Copy link

KLEPTOROTH commented Aug 16, 2020

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.

@KLEPTOROTH
Copy link
Author

KLEPTOROTH commented Aug 16, 2020

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?

@ChengYen-Tang
Copy link

I also encountered the same problem.

@nopbop
Copy link

nopbop commented May 24, 2021

I also have the same issue, do you finally find a way to properly fix it ? Thx

@KLEPTOROTH
Copy link
Author

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.

@nopbop
Copy link

nopbop commented May 24, 2021

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 :)

@KLEPTOROTH
Copy link
Author

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants