-
Notifications
You must be signed in to change notification settings - Fork 92
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 Management randomly failed to start. It won't recover. #2578
Comments
Again, not a programmer here, but Hopefully it doesn't freaks out later and I shorts circuit again. In the console I shortly saw the |
Summary
After authentication, vSphere Integrated Containers Management fails to load with error
{"message":"Service not found: https://127.0.0.1:8282/","statusCode":404,"documentKind":"com:vmware:xenon:common:ServiceErrorResponse","errorCode":-2147483648}
.Restarting individual services fails,
systemctl reset-failed
appears to work,systemctl is-system-running
will showrunning
but it's really not.Details
Doing
systemctl
without arguments showedsystemd-modules-load.service
to be failing, thenjournalctl
showed:harbor.service
,armiral.service
,fileserver.service
andvic-machine-server.service
are all active though onlyfileserver.service
doesn't have red insystemctl status <service>.service
. The plugin in vSphere appears to be working except that it won't deploy VCHs, doing it from a random computer still works and the Appliance's config help on port 9443 still is showing up. So at least Re-Initializing the appliance is probably an option. I'm not a programmer so that's my best bet I guess.Appliance is running on vSphere 7 which has been a hassle deploying as setting any of the options in the OVA will prevent the appliance from starting. This was fixed by manually adding the vApp Options in the VM's Configure tab. Before vSphere 7 there were no issues deploying the OVA.
I attached a few screenshots.
See Also
The text was updated successfully, but these errors were encountered: