I have ESXi 6.7 running, after a funny issue with the webportal not working correctly, stuck just before the login screen, I reset the management agents, now all I presented with is
Have tried resetting the management agents again and the network agent both via ssh and on the console, I'm now at a loss please help me.
Could you please run below command and confirm if there is any services which are at stake
service-control --status --all
If vsphere-ui is stopped then use below command to start it
service-control --start vsphere-ui
Please mark this as "correct" or " Helpfull" if this answers your query.
Sadly no joy here at all
[root@ESX1:~] service-control --status --all
-sh: service-control: not found
[root@ESX1:~] service-control --start vsphere-ui
-sh: service-control: not found
Any other ideas?
ok, just installed vCenter and when I go to add the host I get this error
Cannot contact the specified host (10.1.0.15). The host may not be available on the network, a network configuration problem
Clearly the host is not in state it can be contacted other than via SSH, anyone help at all? There must be something I can do via SSH?
Oh I can add the other ESXi 6.7 host with no issues
Yes, all networking is ok, was all ok for over a month, then the browser interface went funny only getting to the blue screen prior to login, then refreshed the management agents and got this error, all rather odd and can't find another reference to it online anywhere. This is the free version as the hosted servers are for a non profit organisation, so they basically have no money, I do all my work for free as well. Obviously, I can reinstall ESXi but that would mean downtime for them or out of hours working for me and getting a member of their staff their to look after me, hence hoping there is a fix for it. I'd never run 6.7 before and I'm wishing I had stuck with 6.5 native, using the old thick client is so much nicer and easier than this nasty web interface.
I randomly have same issue. I am working on one right now is how I came across this thread. only access I have is console and SSH. tried restarted all the service and still get the 503 message and show disconnected in vcenter. VM's are still running and responding.
ESX host responds to pings and can SSH into it fine. Just stops reporting to vcenter and web client is not working. Try to connect back to vcenter and it says host is un-avaliable, as it cant connect to the host on https.
Only way I have fixed this is reboot the host and kill all the VM's. I have not found a fix to this as of yet.
This looks to have been a intermittent issue for a while now and I don't see any fix or workaround for it. not good for a production environment when I have to kill running VM's.
Along with other posts, and only resolution is reboot host, with running VM's.
Same here, ESXi host 6.5 happened after I installed updates on the server so it was in maintenance mode.
The httpd service was stopped so I started it, but still no change on the host/ui
I rebooted the host and now the ui loads.
On this link - it seems there is a bug with the esxui,
I checked from SSH
it was running, so possibly /etc/init.d/esxui start may help if it is stopped. Others reinstalled the VIB.
I got the same problem (Esxi 6.7). When I login host with SSH, try to use esxcli command to control vm I got "Connection refused/error".
I have to shutdown each vm manually, and reboot the host. Everything back to normal.
Yeah got this today. I was setting up a new server, running dell emc vmware esxi release build 14320388. Was at the point where i configure iscsi targets. So i did that but forgot to authorize the server on the array. So did that, went back and the server was just not doing anything.
Looked down and saw about 10 "rescan HBA" tasks. that were all at 0%. waited about an hour for it to resolve and when it didnt, i attempted a server restart. Server restart was locked up as well it seemed, so i used console to powercycle it.
After power cycle this message was displayed when going to the machine directly and my vcenter can not talk to the host. It is pingable though.
The last thing i did before these problems occurred was trying to set up iscsi connections to our shared storage arrays as i have done before....
will post back if i find a solution because the machine is inaccessible now.