VMware Cloud Community
virtualvikram2
Contributor
Contributor

Unable to access " Direct console access has been disabled by the administrator for ESXi host"

Hi Everyone,

One of my colleague was trying to configure Syslog server for ESXi host and has run the command "/usr/lib/vmware/vmsyslog/bin/shutdown.sh" after which we are not able to connect to the ESXi server through vSphere client or Direct console". But, all the VMs are working fine.

Does the Direct console service stop when we run the command "/usr/lib/vmware/vmsyslog/bin/shutdown.sh" and if all the services are stop? is there any other way to make services up without rebooting the server.

Regards,

Vikram.

5 Replies
Anish_007
Contributor
Contributor

You can try this command

./sbin/services.sh restart

This will restart all services


0 Kudos
krish290785
Enthusiast
Enthusiast

Hi Vikram

Looks like you are in trouble now. It would disable the DCUI login, SSH login, vpxa communication and also the vpshere client wouldn't connect.

  • If your ESXi shell is enabled before, you may use the TSM by ALT+F1 from the DCUI. You should be able to start the services by running "/sbin/services.sh start"
  • If you still have the SSH session alive from where you executed the command, you may try "/sbin/services.sh start" to get the access back to the server.

Even the Powercli also doesn't work in this scenario. You may plan for reboot in case if the above options are not available.

-Bala Krishna Gali If the above info is useful, please mark answer as correct or helpful.
0 Kudos
virtualvikram2
Contributor
Contributor

Hi Krish,

Thanks alot for your reply.


We have Esxi 5.0 U1. we had call with VMware they confirmed that we cannot use it TSM using ALT+F1.So, only option is to restart the ESXi hos

Regards,

Vikram

0 Kudos
krish290785
Enthusiast
Enthusiast

So, the ESXi Shell is not enabled in your case.? That's the reason why VMware recommended to reboot.?

-Bala Krishna Gali If the above info is useful, please mark answer as correct or helpful.
Marimuthuvmware
Contributor
Contributor

I tried to restart the Physical host from console the issue been fixed.

0 Kudos