Why is my Linux WorkSpace stuck in the starting, rebooting, or stopping status?

Resolution

WorkSpace status depends on health checks of the components from the WorkSpace, including the required WorkSpaces services. The operating system (OS) for the WorkSpace might take a long time to boot. Or, the components fail to report the actual status of the WorkSpace. These issues cause the status to become stuck in the starting, rebooting, or stopping state.

Check whether your WorkSpaces is pending updates

If the WorkSpaces console or client application sends a reboot command to the WorkSpace, then the WorkSpace might be busy applying updates. A reboot action also initiates any pending WorkSpaces component updates.

Note: You must turn on SSH password authentication on your Linux WorkSpace.

Check your antivirus software

Make sure that your antivirus software isn't blocking required WorkSpaces components or configurations.

Check whether your WorkSpace is in a Running state

Important: For an Ubuntu or Red Hat Enterprise Linux (RHEL) WorkSpace, wsp-dcv-hostadapter, dcvserver, and skylight agent must be in a Running state. For an Amazon Linux 2 WorkSpace, pcoip.service and skylight-agent.service must be in a Running state.

To verify that the required WorkSpaces services are started at the OS level, complete the following steps:

1. Use SSH to connect to the WorkSpace.

2. Open Terminal.

3. Check the status of the required agents in the WorkSpace.
   For an Amazon Linux WorkSpace, run the following commands:

   sudo systemctl status pcoip.service
   sudo systemctl status skylight-agent.service

   For an Ubuntu or RHEL WorkSpace, run the following commands:

   sudo systemctl status skylight-agent.service. 
   sudo systemctl status wspdcvhostadapter.service
   sudo systemctl status dcvserver.service

4. If the status is Stopped, then to start the service, run the following command:

   systemctl start service-name

   Note: Replace service-name with the stopped service.

If any of the preceding services isn't installed, then to automatically install the service, reboot the WorkSpace. Wait for 15 minutes. If the service still isn't installed after a reboot, then you must open a support case.

Check that the network adapters are turned on

Verify that both network adapters on the WorkSpace are turned on, complete the following steps:

1. Use SSH to connect to the Workspace.

2. Open Terminal.

3. To check whether the network interfaces (ETH 0 and ETH 1) are both running, run the following command:

   sudo ifconfig 

4. If an interface isn't running, then run the following command:

   sudo ifconfig ethernet-name up

   Note: Replace ethernet-name with the interface name.

5. To validate that both interfaces are now running, run the following command:

   sudo ifconfig

Restart the WorkSpace

If you still have issues, then wait until the status of the WorkSpace shows as Unhealthy in the console. Then, restart the WorkSpace. Wait for a few minutes for the WorkSpace to come online, and then try to connect to the WorkSpace. The status of the WorkSpace changes within 15 minutes.

Related information

Why can't I create a new WorkSpace?