ESXi Host Failed to Restart the Virtual Machine

From the ESXi host, when we are trying to shut down or restart a virtual machine, it is failed with the below error message.

Failed to restart the virtual machine, cannot execute script

If the vCenter server is failed to perform any task regarding the virtual machine then we can do it directly from the host where that virtual machine is residing. If we are not able to shut down or restart the virtual machine from the vCenter server for any reason then we can do it using the ESXi host. 

We can take two types of access to the ESXi host. The first one is "Graphical Access" and the second one is "Command Line Access". Using the "vSphere Web Client", we can take access to the graphical mode. To work on the command line mode, we can use "ESXi Shell" or we can make an SSH connection from any other network computer.

But, sometimes it will also fail to perform any operation regarding virtual machines from the graphical access. That's why it is good practice to work with command line mode for any VM operation.

In this tutorial, we will stop a VM from the command line mode. We will stop the VM by killing that VM process. Three types of killing methods are available for the virtual machine. We can use any of the methods. By chance, the "Soft" and "Hard" method is failed to kill that VM process then we should use the "Force" method. It will definitely work.

To view the virtual machine list that is running on this host, we will use the below command.

esxcli vm process list

This command will output just like as the below. We will use the "World ID" number to identify the specific VM.

Now we will execute the VM process killing command using that "World ID" number. The command structure is given below.

esxcli vm process kill --type=[soft,hard,force] --world-id=[world-number]

One example for the VM process killing command is given below.

esxcli vm process kill --type=force --world-id=2188667

After executing this command, that virtual machine will be stopped whose "world-id" number is "2188667".

That's all. Using this way, we can turn off or shut down any virtual machine that can't be stopped from the vCenter server.

ESXi Host Failed to Power Off the Virtual Machine

From the ESXi host, when we are trying to shut down or restart a virtual machine, it is failed with the below error message.

Failed to power off the virtual machine, cannot execute script

If the vCenter server is failed to perform any task regarding the virtual machine then we can do it directly from the host where that virtual machine is residing. If we are not able to shut down or restart the virtual machine from the vCenter server for any reason then we can do it using the ESXi host.

 

We can take two types of access to the ESXi host. The first one is "Graphical Access" and the second one is "Command Line Access". Using the "vSphere Web Client", we can take access to the graphical mode. To work on the command line mode, we can use "ESXi Shell" or we can make an SSH connection from any other network computer.

But, sometimes it will also fail to perform any operation regarding virtual machines from the graphical access. That's why it is good practice to work with command line mode for any VM operation.

In this tutorial, we will stop a VM from the command line mode. We will stop the VM by killing that VM process. Three types of killing methods are available for the virtual machine. We can use any of the methods. By chance, the "Soft" and "Hard" method is failed to kill that VM process then we should use the "Force" method. It will definitely work.

To view the virtual machine list that is running on this host, we will use the below command.

esxcli vm process list

This command will output just like as the below. We will use the "World ID" number to identify the specific VM.

Now we will execute the VM process killing command using that "World ID" number. The command structure is given below.

esxcli vm process kill --type=[soft,hard,force] --world-id=[world-number]

One example for the VM process killing command is given below.

esxcli vm process kill --type=force --world-id=2188667

After executing this command, that virtual machine will be stopped whose "world-id" number is "2188667".

That's all. Using this way, we can turn off or shut down any virtual machine.

ESXi Host Kill VM

In this tutorial, we will stop a VM from the command line mode. We will stop the VM by killing that VM process. Three types of killing methods are available for the virtual machine. We can use any of the methods. By chance, the "Soft" and "Hard" method is failed to kill that VM process then we should use the "Force" method. It will definitely work.

To view the virtual machine list that is running on this host, we will use the below command.

esxcli vm process list

This command will output just like as the below. We will use the "World ID" number to identify the specific VM.

Now we will execute the VM process killing command using that "World ID" number. The command structure is given below.

esxcli vm process kill --type=[soft,hard,force] --world-id=[world-number]

One example for the VM process killing command is given below.

esxcli vm process kill --type=force --world-id=2188667

After executing this command, that virtual machine will be stopped whose "world-id" number is "2188667".

That's all. Using this way, we can turn off or shut down any virtual machine.

ESXi Host Shutdown VM Command Line

In this tutorial, we will stop a VM from the command line mode. We will stop the VM by killing that VM process. Three types of killing methods are available for the virtual machine. We can use any of the methods. By chance, the "Soft" and "Hard" method is failed to kill that VM process then we should use the "Force" method. It will definitely work.

To view the virtual machine list that is running on this host, we will use the below command.

esxcli vm process list

This command will output just like as the below. We will use the "World ID" number to identify the specific VM.

Now we will execute the VM process killing command using that "World ID" number. The command structure is given below.

esxcli vm process kill --type=[soft,hard,force] --world-id=[world-number]

One example for the VM process killing command is given below.

esxcli vm process kill --type=force --world-id=2188667

After executing this command, that virtual machine will be stopped whose "world-id" number is "2188667".

That's all. Using this way, we can turn off or shut down any virtual machine.

ESXi VM Not Shutting Down

From the ESXi host, when we are trying to shut down or restart a virtual machine, it is failed with the below error message.

Failed to power off the virtual machine, cannot execute script

If the vCenter server is failed to perform any task regarding the virtual machine then we can do it directly from the host where that virtual machine is residing. If we are not able to shut down or restart the virtual machine from the vCenter server for any reason then we can do it using the ESXi host.

 

We can take two types of access to the ESXi host. The first one is "Graphical Access" and the second one is "Command Line Access". Using the "vSphere Web Client", we can take access to the graphical mode. To work on the command line mode, we can use "ESXi Shell" or we can make an SSH connection from any other network computer.

But, sometimes it will also fail to perform any operation regarding virtual machines from the graphical access. That's why it is good practice to work with command line mode for any VM operation.

In this tutorial, we will stop a VM from the command line mode. We will stop the VM by killing that VM process. Three types of killing methods are available for the virtual machine. We can use any of the methods. By chance, the "Soft" and "Hard" method is failed to kill that VM process then we should use the "Force" method. It will definitely work.

To view the virtual machine list that is running on this host, we will use the below command.

esxcli vm process list

This command will output just like as the below. We will use the "World ID" number to identify the specific VM.

Now we will execute the VM process killing command using that "World ID" number. The command structure is given below.

esxcli vm process kill --type=[soft,hard,force] --world-id=[world-number]

One example for the VM process killing command is given below.

esxcli vm process kill --type=force --world-id=2188667

After executing this command, that virtual machine will be stopped whose "world-id" number is "2188667".

That's all. Using this way, we can turn off or shut down any virtual machine that can't be stopped from the vCenter server.

ESXi Shutdown Virtual Machine Command

In this tutorial, we will stop a VM from the command line mode. We will stop the VM by killing that VM process. Three types of killing methods are available for the virtual machine. We can use any of the methods. By chance, the "Soft" and "Hard" method is failed to kill that VM process then we should use the "Force" method. It will definitely work.

To view the virtual machine list that is running on this host, we will use the below command.

esxcli vm process list

This command will output just like as the below. We will use the "World ID" number to identify the specific VM.

Now we will execute the VM process killing command using that "World ID" number. The command structure is given below.

esxcli vm process kill --type=[soft,hard,force] --world-id=[world-number]

One example for the VM process killing command is given below.

esxcli vm process kill --type=force --world-id=2188667

After executing this command, that virtual machine will be stopped whose "world-id" number is "2188667".

That's all. Using this way, we can turn off or shut down any virtual machine.

ESXi Cli VM Shut Down

In this tutorial, we will stop a VM from the command line mode. We will stop the VM by killing that VM process. Three types of killing methods are available for the virtual machine. We can use any of the methods. By chance, the "Soft" and "Hard" method is failed to kill that VM process then we should use the "Force" method. It will definitely work.

To view the virtual machine list that is running on this host, we will use the below command.

esxcli vm process list

This command will output just like as the below. We will use the "World ID" number to identify the specific VM.

Now we will execute the VM process killing command using that "World ID" number. The command structure is given below.

esxcli vm process kill --type=[soft,hard,force] --world-id=[world-number]

One example for the VM process killing command is given below.

esxcli vm process kill --type=force --world-id=2188667

After executing this command, that virtual machine will be stopped whose "world-id" number is "2188667".

That's all. Using this way, we can turn off or shut down any virtual machine.

Failed to Restart the Virtual Machine, cannot execute script

From the ESXi host, when we are trying to shut down or restart a virtual machine, it is failed with the below error message.

Failed to restart the virtual machine, cannot execute script

If the vCenter server is failed to perform any task regarding the virtual machine then we can do it directly from the host where that virtual machine is residing. If we are not able to shut down or restart the virtual machine from the vCenter server for any reason then we can do it using the ESXi host. 

We can take two types of access to the ESXi host. The first one is "Graphical Access" and the second one is "Command Line Access". Using the "vSphere Web Client", we can take access to the graphical mode. To work on the command line mode, we can use "ESXi Shell" or we can make an SSH connection from any other network computer.

But, sometimes it will also fail to perform any operation regarding virtual machines from the graphical access. That's why it is good practice to work with command line mode for any VM operation.

In this tutorial, we will stop a VM from the command line mode. We will stop the VM by killing that VM process. Three types of killing methods are available for the virtual machine. We can use any of the methods. By chance, the "Soft" and "Hard" method is failed to kill that VM process then we should use the "Force" method. It will definitely work.

To view the virtual machine list that is running on this host, we will use the below command.

esxcli vm process list

This command will output just like as the below. We will use the "World ID" number to identify the specific VM.

Now we will execute the VM process killing command using that "World ID" number. The command structure is given below.

esxcli vm process kill --type=[soft,hard,force] --world-id=[world-number]

One example for the VM process killing command is given below.

esxcli vm process kill --type=force --world-id=2188667

After executing this command, that virtual machine will be stopped whose "world-id" number is "2188667".

That's all. Using this way, we can turn off or shut down any virtual machine that can't be stopped from the vCenter server.

Failed to Power Off the Virtual Machine, Cannot Execute Script

From the ESXi host, when we are trying to shut down or restart a virtual machine, it is failed with the below error message.

Failed to power off the virtual machine, cannot execute script

If the vCenter server is failed to perform any task regarding the virtual machine then we can do it directly from the host where that virtual machine is residing. If we are not able to shut down or restart the virtual machine from the vCenter server for any reason then we can do it using the ESXi host. 

We can take two types of access to the ESXi host. The first one is "Graphical Access" and the second one is "Command Line Access". Using the "vSphere Web Client", we can take access to the graphical mode. To work on the command line mode, we can use "ESXi Shell" or we can make an SSH connection from any other network computer.

But, sometimes it will also fail to perform any operation regarding virtual machines from the graphical access. That's why it is good practice to work with command line mode for any VM operation.

In this tutorial, we will stop a VM from the command line mode. We will stop the VM by killing that VM process. Three types of killing methods are available for the virtual machine. We can use any of the methods. By chance, the "Soft" and "Hard" method is failed to kill that VM process then we should use the "Force" method. It will definitely work.

To view the virtual machine list that is running on this host, we will use the below command.

esxcli vm process list

This command will output just like as the below. We will use the "World ID" number to identify the specific VM.

Now we will execute the VM process killing command using that "World ID" number. The command structure is given below.

esxcli vm process kill --type=[soft,hard,force] --world-id=[world-number]

One example for the VM process killing command is given below.

esxcli vm process kill --type=force --world-id=2188667

After executing this command, that virtual machine will be stopped whose "world-id" number is "2188667".

That's all. Using this way, we can turn off or shut down any virtual machine that can't be stopped from the vCenter server.

vCenter VM Not Restarting

From the vCenter when we are trying to shut down or restart a virtual machine, it is failed with the below error message.

A General System Error Occurred: Invalid Fault

One snapshot for this error message is given below.

If the vCenter server is failed to perform any task regarding the virtual machine then we can do it directly from the host where that virtual machine is residing. If we are not able to shut down or restart the virtual machine from the vCenter server for any reason then we can do it using the ESXi host. 

We can take two types of access to the ESXi host. The first one is "Graphical Access" and the second one is "Command Line Access". Using the "vSphere Web Client", we can take access to the graphical mode. To work on the command line mode, we can use "ESXi Shell" or we can make an SSH connection from any other network computer.

But, sometimes it will also fail to perform any operation regarding virtual machines from the graphical access. That's why it is good practice to work with command line mode for any VM operation.

In this tutorial, we will stop a VM from the command line mode. We will stop the VM by killing that VM process. Three types of killing methods are available for the virtual machine. We can use any of the methods. By chance, the "Soft" and "Hard" method is failed to kill that VM process then we should use the "Force" method. It will definitely work.

To view the virtual machine list that is running on this host, we will use the below command.

esxcli vm process list

This command will output just like as the below. We will use the "World ID" number to identify the specific VM.

Now we will execute the VM process killing command using that "World ID" number. The command structure is given below.

esxcli vm process kill --type=[soft,hard,force] --world-id=[world-number]

One example for the VM process killing command is given below.

esxcli vm process kill --type=force --world-id=2188667

After executing this command, that virtual machine will be stopped whose "world-id" number is "2188667".

That's all. Using this way, we can turn off or shut down any virtual machine that can't be stopped from the vCenter server.

vCenter VM Not Shutting Down

From the vCenter when we are trying to shut down or restart a virtual machine, it is failed with the below error message.

A General System Error Occurred: Invalid Fault

One snapshot for this error message is given below.

If the vCenter server is failed to perform any task regarding the virtual machine then we can do it directly from the host where that virtual machine is residing. If we are not able to shut down or restart the virtual machine from the vCenter server for any reason then we can do it using the ESXi host.

 

We can take two types of access to the ESXi host. The first one is "Graphical Access" and the second one is "Command Line Access". Using the "vSphere Web Client", we can take access to the graphical mode. To work on the command line mode, we can use "ESXi Shell" or we can make an SSH connection from any other network computer.

But, sometimes it will also fail to perform any operation regarding virtual machines from the graphical access. That's why it is good practice to work with command line mode for any VM operation.

In this tutorial, we will stop a VM from the command line mode. We will stop the VM by killing that VM process. Three types of killing methods are available for the virtual machine. We can use any of the methods. By chance, the "Soft" and "Hard" method is failed to kill that VM process then we should use the "Force" method. It will definitely work.

To view the virtual machine list that is running on this host, we will use the below command.

esxcli vm process list

This command will output just like as the below. We will use the "World ID" number to identify the specific VM.

Now we will execute the VM process killing command using that "World ID" number. The command structure is given below.

esxcli vm process kill --type=[soft,hard,force] --world-id=[world-number]

One example for the VM process killing command is given below.

esxcli vm process kill --type=force --world-id=2188667

After executing this command, that virtual machine will be stopped whose "world-id" number is "2188667".

That's all. Using this way, we can turn off or shut down any virtual machine that can't be stopped from the vCenter server.

A General System Error Occurred: Invalid Fault

From the vCenter when we are trying to shut down or restart a virtual machine, it is failed with the below error message.

A General System Error Occurred: Invalid Fault

One snapshot for this error message is given below.

If the vCenter server is failed to perform any task regarding the virtual machine then we can do it directly from the host where that virtual machine is residing. If we are not able to shut down or restart the virtual machine from the vCenter server for any reason then we can do it using the ESXi host. 

We can take two types of access to the ESXi host. The first one is "Graphical Access" and the second one is "Command Line Access". Using the "vSphere Web Client", we can take access to the graphical mode. To work on the command line mode, we can use "ESXi Shell" or we can make an SSH connection from any other network computer.

But, sometimes it will also fail to perform any operation regarding virtual machines from the graphical access. That's why it is good practice to work with command line mode for any VM operation.

In this tutorial, we will stop a VM from the command line mode. We will stop the VM by killing that VM process. Three types of killing methods are available for the virtual machine. We can use any of the methods. By chance, the "Soft" and "Hard" method is failed to kill that VM process then we should use the "Force" method. It will definitely work.

To view the virtual machine list that is running on this host, we will use the below command.

esxcli vm process list

This command will output just like as the below. We will use the "World ID" number to identify the specific VM.

Now we will execute the VM process killing command using that "World ID" number. The command structure is given below.

esxcli vm process kill --type=[soft,hard,force] --world-id=[world-number]

One example for the VM process killing command is given below.

esxcli vm process kill --type=force --world-id=2188667

After executing this command, that virtual machine will be stopped whose "world-id" number is "2188667".

That's all. Using this way, we can turn off or shut down any virtual machine that can't be stopped from the vCenter server.

Mikrotik EoIP Tunnel Step by Step

In networking, the broadcast domain is a logical part or division. Through this, an entire network is divided into smaller sections. Generally, these divisions are logical. That means, physically they will be connected to the same network, but they still stay in separate networks. Those who are in the same logical division or the same broadcast domain can only communicate themselves. A single broadcast domain may have a wide range of locations. It can be in the same building as well as in a different city. For example, let's say, a company has two offices. The first one is head-office and another one is the factory Office. Both offices are connected to the internet. Our network scenario looks like the following:-

Now head-office and factory office must be in the same broadcast domain. We will discuss this issue in this tutorial.

The EOIP (Ethernet over Internet Protocol) usually works to keep two remote offices in the same broadcast domain. This protocol creates a tunnel between the remote offices through the internet. We are assuming that "Mikrotik" has been used as a router for internet connection in the offices.

At first, we will create a tunnel between the router. We assume that the WAN IP of our head-office router (Router-1) is 1.1.1.1 and the WAN IP of the factory router (Router-2) is 2.2.2.2. At the same time, we also assume there are two LAN segments at head-office and there are also two LAN segments in the factory. The LAN segments network of head-office is 192.168.1.0/24 and 192.168.2.0/24. Similarly, the network of LAN segments in the factory is 192.168.3.0/24 and 192.168.4.0/24. Notice the diagram below.

Then, as in the diagram above, we have four LAN segments in our two locations. And we know that each LAN segment is a different broadcast domain. Now we merge the factory's 192.168.4.0/24 LAN segment with the head-office's 192.168.1.0/24 LAN segment so that the LAN segment of the factory comes under the head-office LAN segment or broadcast domain. That is, both of them are under the 192.168.1.0/24 network. That LAN segment of the factory will have no separate network or broadcast domain. Just like the diagram below.

According to the diagram, we did not assign any type of network information in the LAN segment of the factory (Router-2) even without assigning an IP in the router LAN interface. Because this segment will be merged with the head-office's 192.168.1.0/24 segment or broadcast domain. This factory segment will connect itself to the 192.168.1.0/24 network.

A LAN segment from head-office and one from the factory will be in the same broadcast domain.

The details of how to make the tunnel are given below:-

At first, we will create the tunnel in our head-office's router. Click on the "Interface" option from the winbox menu and then navigate to the "EoIP Tunnel" tab. Their click on the (+) sign to add a new EoIP tunnel.

Now provide a descriptive name for this tunnel in the "Name" field. Here, we named it "EoIP_Tunnel_to_Factory". Write the head-office's public IP address or the WAN address in the "Local Address" field. According to the example, this address will be 1.1.1.1. Write the factory's public IP address or the WAN address in the "Remote Address" field. According to the example, this address will be 2.2.2.2. Now provide a tunnel ID in the "Tunnel ID" field. Please keep in mind that, this ID must be the same at both offices otherwise the tunnel won't be established. If we want we can secure this tunnel with a secret password. This password will use to encrypt the tunnel traffic that will be forwarded within this tunnel. In the "IPsec Secret" field, we can provide this encryption password. This IPsec Secret password must be the same at both sites also otherwise the tunnel won't be up. That's it. The rest of the things keep the default. Now click on the "Apply" and "Ok" button to save this tunnel and close this window.

Our head-office's site tunnel configuration has been done. Now we will move to our factory-office. There, in the same way, we will create the tunnel. But there will be some changes in some places.

In the same manner, we will provide the descriptive name for this tunnel. The name will be the "EoIP_Tunnel_to_Head Office". At this time, in the "Local Address" field, we will write the factory's public IP address or the WAN IP address and in the "Remote Address" field, we will write the head-office's public IP address or the WAN IP address. According to our example, at this time, the local address will be 2.2.2.2 and the remote address will be 1.1.1.1. The "Tunnel ID" value and the "IPsec Secret" value must be the same as the head-office router one. Otherwise, the link won't be established.

Now the tunnel should be up and running. We will find that the "running" text will be highlighted.

Our tunnel configuration has been done at both offices. Now we have to create the virtual bridge interface at both of the routers. In the head-office router, the bridge port will be the "EoIP Tunnel" interface and the "Ether-2" interface. At the same time, in the factory router, the bridge port will be the "EoIP Tunnel" interface and the "Ether-1" interface.

In the head-office router, we will make a bridge between the "EoIP Tunnel" and the "Ether-2" interface because we want to merge the factory's segment with this "Ether-2" network. And in the factory router, we will make a bridge between the "EoIP Tunnel" and the "Ether-1" interface because we want to connect this "Ether-1" segment with the head-office's "Ether-2" network.

Now we will create the bridge interface in the head-office router. To create a bridge interface, just click on the "Bridge" option from the Winbox Menu list. Their click on the (+) sign to add a new virtual bridge interface. 

Now we will provide a descriptive name for this bridge interface. Here, we name it "EoIP_Bridge_Factory".

Now we will add the "EoIP_Tunnel_to_Factory" interface and the "Ether-2" interface as bridge ports with this Bridge interface. To add a bridge port, navigate to the "Ports" tab and click on the (+) sign to add a new bridge port.

At first, we will add the EoIP tunnel interface. Select the EoIP tunnel interface from the interface field. According to this example, this will be the "EoIP_Tunnel_to_Factory". Then we will select the bridge interface from the "Bridge" field with which we want to add. According to this example, this will be the "EoIP_Bridge_Factory". Then click on the "Apply" and "OK" button to save and close this window.

After adding the EoIP tunnel interface then we will add the "Ether-2" interface as a bridge port with our bridge interface.

Our head-office router configuration has been done. Now we will move to our factory router. Here, in the same way, we will create a bridge. We will name it "EoIP_Bridge_Head Office".

Now we will add the "EoIP_Tunnel_to_Head Office" interface and the "Ether-1" interface with this bridge interface.

At first, we will add the EoIP tunnel interface.

Now we will add the "Ether-1" interface.

That's it. All the configuration has been done. From now on, the factory segment will be merged with the head-office's 192.168.1.0/24 network. It will be the same broadcast domain.

NSX Controller Failed to Start the File System Check

NSX Controller is running on the VMware  Photon Operating System. The time when the Photon operating system is starting, it will check all the devices that are connected with it. If it found any devices that are inaccessible by the operating system, then it will directly boot into the emergency mode.

Also, it will display information about failed devices. Use "Shift+PageUp" and "Shift+PageDown" to scroll the console screen.

According to this snapshot, the operating system is failed to check the file system for the "/dev/sda4" device. That's why it was directly booted into the emergency mode. Due to failed file system checking process, it can't take access into the "/dev/sda4" device. It won't boot into the normal mode until it can take access the "/dev/sda4" device. To resolve this issue we have to run the file system checking process for that "/dev/sda4" device. Please execute the below command from the emergency mode:-

" e2fsck  -y  /dev/sda4 "

To enter the emergency mode, please provide your root password. Then apply that command and restart the appliance after completing the file system checking process. Hope, this time it will boot into the normal mode. To restart the appliance, please use the below command:-

" reboot -f "

According to this snapshot, we found one failed issue only that interrupt our normal booting process. If you found multiple failed issues in your production environment, then you have to resolve every failed issue otherwise it won't boot into the normal mode. To find out the failed issues, please use the "Shit+PageUp" key combination to scroll the upper screen.

Thank you.

NSX Controller Automatically Boot Emergency Mode

NSX Controller is running on the VMware  Photon Operating System. The time when the Photon operating system is starting, it will check all the devices that are connected with it. If it found any devices that are inaccessible by the operating system, then it will directly boot into the emergency mode.

Also, it will display information about failed devices. Use "Shift+PageUp" and "Shift+PageDown" to scroll the console screen.

According to this snapshot, the operating system is failed to check the file system for the "/dev/sda4" device. That's why it was directly booted into the emergency mode. Due to failed file system checking process, it can't take access into the "/dev/sda4" device. It won't boot into the normal mode until it can take access the "/dev/sda4" device. To resolve this issue we have to run the file system checking process for that "/dev/sda4" device. Please execute the below command from the emergency mode:-

" e2fsck  -y  /dev/sda4 "

To enter the emergency mode, please provide your root password. Then apply that command and restart the appliance after completing the file system checking process. Hope, this time it will boot into the normal mode. To restart the appliance, please use the below command:-

" reboot -f "

According to this snapshot, we found one failed issue only that interrupt our normal booting process. If you found multiple failed issues in your production environment, then you have to resolve every failed issue otherwise it won't boot into the normal mode. To find out the failed issues, please use the "Shit+PageUp" key combination to scroll the upper screen.

Thank you.

NSX Controller Booting Emergency Mode

NSX Controller is running on the VMware  Photon Operating System. The time when the Photon operating system is starting, it will check all the devices that are connected with it. If it found any devices that are inaccessible by the operating system, then it will directly boot into the emergency mode.

Also, it will display information about failed devices. Use "Shift+PageUp" and "Shift+PageDown" to scroll the console screen.

According to this snapshot, the operating system is failed to check the file system for the "/dev/sda4" device. That's why it was directly booted into the emergency mode. Due to failed file system checking process, it can't take access into the "/dev/sda4" device. It won't boot into the normal mode until it can take access the "/dev/sda4" device. To resolve this issue we have to run the file system checking process for that "/dev/sda4" device. Please execute the below command from the emergency mode:-

" e2fsck  -y  /dev/sda4 "

To enter the emergency mode, please provide your root password. Then apply that command and restart the appliance after completing the file system checking process. Hope, this time it will boot into the normal mode. To restart the appliance, please use the below command:-

" reboot -f "

According to this snapshot, we found one failed issue only that interrupt our normal booting process. If you found multiple failed issues in your production environment, then you have to resolve every failed issue otherwise it won't boot into the normal mode. To find out the failed issues, please use the "Shit+PageUp" key combination to scroll the upper screen.

Thank you.

The Process Cannot Access the File Because Another Process has Locked a Portion of the File

Sometimes, we failed to start or power on our virtual machines and it displays the below error message.

 

" The process cannot access the file because another process has locked a portion of the file. "

In this tutorial, we will know how to resolve that issue. Every virtual machine is made of some configuration files and those files are stored in that virtual machine's home directory. If any of the configuration files are being blocked by the VMware Workstation program then that virtual machine will fail to start and will show up the below error message. 

If any configuration files are being blocked then a new folder will be created with that file name. That folder name will have an extension called ".lck". For example, the folder name will be " TestVM.vmx.lck ". One snapshot is given below as an example. Those are all the lock folders that are created with the same file name that is being locked by the program.

To resolve this issue we have to have removed or deleted that locked folder from the virtual machine home directory. That's it. Now the virtual machine should run without any issues. If you find any locked files with the .lck extension like the locked folder that also have to be deleted.

If you have doubts about the virtual machine home directory path or the locked folder or file path then you can find it from that error message.

That's all. Please make sure that if any lock files (filename with .lck extension) are available those are also deleted.

VMware Failed to Start the Virtual Machine

Sometimes, we failed to start or power on our virtual machines and it displays the below error message.

 

" The process cannot access the file because another process has locked a portion of the file. "

In this tutorial, we will know how to resolve that issue. Every virtual machine is made of some configuration files and those files are stored in that virtual machine's home directory. If any of the configuration files are being blocked by the VMware Workstation program then that virtual machine will fail to start and will show up the below error message. 

If any configuration files are being blocked then a new folder will be created with that file name. That folder name will have an extension called ".lck". For example, the folder name will be " TestVM.vmx.lck ". One snapshot is given below as an example. Those are all the lock folders that are created with the same file name that is being locked by the program.

To resolve this issue we have to have removed or deleted that locked folder from the virtual machine home directory. That's it. Now the virtual machine should run without any issues. If you find any locked files with the .lck extension like the locked folder that also have to be deleted.

If you have doubts about the virtual machine home directory path or the locked folder or file path then you can find it from that error message.

That's all. Please make sure that if any lock files (filename with .lck extension) are available those are also deleted.

VMware Workstation Module Disk Power on Failed

Sometimes, we failed to start or power on our virtual machines and it displays the below error message. 

"The process cannot access the file because another process has locked a portion of the file."

In this tutorial, we will know how to resolve that issue. Every virtual machine is made of some configuration files and those files are stored in that virtual machine's home directory. If any of the configuration files are being blocked by the VMware Workstation program then that virtual machine will fail to start and will show up the below error message. 

If any configuration files are being blocked then a new folder will be created with that file name. That folder name will have an extension called ".lck". For example, the folder name will be " TestVM.vmx.lck ". One snapshot is given below as an example. Those are all the lock folders that are created with the same file name that is being locked by the program.

To resolve this issue we have to have removed or deleted that locked folder from the virtual machine home directory. That's it. Now the virtual machine should run without any issues. If you find any locked files with the .lck extension like the locked folder that also have to be deleted.

If you have doubts about the virtual machine home directory path or the locked folder or file path then you can find it from that error message.

That's all. Please make sure that if any lock files (filename with .lck extension) are available those are also deleted.

vCloude Director Failed to Start

In this article, we are going to discuss an error message that is appearing during login to the vCloud Director web interface. We got the following error message when we are trying to take access to the vCloud Director interface.

" An error occurred during the initialization. Accessing the application through an unsupported public URL or poor connectivity might cause this error "

One snapshot for this error message is given below:-

The URL which we are using to access the vCloud Director provider interface, it must be registered to the vCloud Director. There is a property available in the vCloud Director which name is "webapp.allowed.origins". All the URL information that can use to access the vCloud Director Provider interface, is listed in this property. We have to have used these listed URLs if we want to take access to the vCloud Provider web interface. If we are using an URL address that is not registered or listed on the "webapp.allowed.origins" property then we can't take access to the vCloud Director Provider interface. In that case, that error message will appear. If we want to take access to the vCloud Director Provider interface using a new URL address, we must register or enlist it to the "webapp.allowed.origins" property. Only then it is possible to take access to the vCloud Director Provider interface using that new URL address.

To view the list of enlisted or registered URL information that is available on the "webapp.allowed.origins" property, we have to execute the below command on the vCloud Director appliance.

" /opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n webapp.allowed.origins -l "

After executing this command, it will show us the enlisted or registered URL information that is currently available on the "webapp.allowed.origins" property.

If we want to update this "webapp.allowed.origins" property or we want to add a new URL address in this property, then we have to execute the below command on the vCloud Director appliance.

" /opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n webapp.allowed.origins -v <comma_separated_list_without_space> "

Here, this "<comma_separated_list_without_space>" means, we can add multiple URLs one by one using comma without using any space. Suppose we want to add the "test1.vlcoud.com", "test2.vcloud.com", and "test3.vcloud.com" to the "webapp.allowed.origins" property. Then our command will be as follows:-

" /opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n webapp.allowed.origins -v test1.vlcoud.com,test2.vcloud.com,test3.vcloud.com "

That's it. After registering our new URL address, then we can use it to take access to the vCloud Director interface. No more errors will be shown.

Thank you.

vCloud Director Web Login Failed

In this article, we are going to discuss an error message that is appearing during login to the vCloud Director web interface. We got the following error message when we are trying to take access to the vCloud Director interface.

"An error occurred during the initialization. Accessing the application through an unsupported public URL or poor connectivity might cause this error"

One snapshot for this error message is given below:-

The URL which we are using to access the vCloud Director provider interface, it must be registered to the vCloud Director. There is a property available in the vCloud Director which name is "webapp.allowed.origins". All the URL information that can use to access the vCloud Director Provider interface, is listed in this property. We have to have used these listed URLs if we want to take access to the vCloud Provider web interface. If we are using an URL address that is not registered or listed on the "webapp.allowed.origins" property then we can't take access to the vCloud Director Provider interface. In that case, that error message will appear. If we want to take access to the vCloud Director Provider interface using a new URL address, we must register or enlist it to the "webapp.allowed.origins" property. Only then it is possible to take access to the vCloud Director Provider interface using that new URL address.

To view the list of enlisted or registered URL information that is available on the "webapp.allowed.origins" property, we have to execute the below command on the vCloud Director appliance.

" /opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n webapp.allowed.origins -l "

After executing this command, it will show us the enlisted or registered URL information that is currently available on the "webapp.allowed.origins" property.

If we want to update this "webapp.allowed.origins" property or we want to add a new URL address in this property, then we have to execute the below command on the vCloud Director appliance.

" /opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n webapp.allowed.origins -v <comma_separated_list_without_space> "

Here, this "<comma_separated_list_without_space>" means, we can add multiple URLs one by one using comma without using any space. Suppose we want to add the "test1.vlcoud.com", "test2.vcloud.com", and "test3.vcloud.com" to the "webapp.allowed.origins" property. Then our command will be as follows:-

" /opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n webapp.allowed.origins -v test1.vlcoud.com,test2.vcloud.com,test3.vcloud.com "

That's it. After registering our new URL address, then we can use it to take access to the vCloud Director interface. No more errors will be shown.

Thank you.

vCloud Director An Error Occurred During the Initialization

In this article, we are going to discuss an error message that is appearing during login to the vCloud Director web interface. We got the following error message when we are trying to take access to the vCloud Director interface.

"An error occurred during the initialization. Accessing the application through an unsupported public URL or poor connectivity might cause this error"

One snapshot for this error message is given below:-

The URL which we are using to access the vCloud Director provider interface, it must be registered to the vCloud Director. There is a property available in the vCloud Director which name is "webapp.allowed.origins". All the URL information that can use to access the vCloud Director Provider interface, is listed in this property. We have to have used these listed URLs if we want to take access to the vCloud Provider web interface. If we are using an URL address that is not registered or listed on the "webapp.allowed.origins" property then we can't take access to the vCloud Director Provider interface. In that case, that error message will appear. If we want to take access to the vCloud Director Provider interface using a new URL address, we must register or enlist it to the "webapp.allowed.origins" property. Only then it is possible to take access to the vCloud Director Provider interface using that new URL address.

To view the list of enlisted or registered URL information that is available on the "webapp.allowed.origins" property, we have to execute the below command on the vCloud Director appliance.

" /opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n webapp.allowed.origins -l "

After executing this command, it will show us the enlisted or registered URL information that is currently available on the "webapp.allowed.origins" property.

If we want to update this "webapp.allowed.origins" property or we want to add a new URL address in this property, then we have to execute the below command on the vCloud Director appliance.

" /opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n webapp.allowed.origins -v <comma_separated_list_without_space> "

Here, this "<comma_separated_list_without_space>" means, we can add multiple URLs one by one using comma without using any space. Suppose we want to add the "test1.vlcoud.com", "test2.vcloud.com", and "test3.vcloud.com" to the "webapp.allowed.origins" property. Then our command will be as follows:-

" /opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n webapp.allowed.origins -v test1.vlcoud.com,test2.vcloud.com,test3.vcloud.com "

That's it. After registering our new URL address, then we can use it to take access to the vCloud Director interface. No more errors will be shown.

Thank you.