FAQ123: Troubleshooting Orbit launch issues



This article contains troubleshooting information to help if you're encountering problems running the Orbit desktop client with Athera.




There are a couple of things to check if you are experiencing issues launching an Athera application in orbit. 



First of all please ensure that you have followed the installation guide FAQ122: How to install and run apps through the Orbit desktop client in order to install Orbit 


Make sure that your host name/orbit client is set as active on your dashboard as shown below:



In order to troubleshoot the Orbit issue further you can have a look at the log files that it produces. 

Orbit generates two logs: an orbit.log and an orbit-session.log. The orbit.log file contains information about the Orbit Desktop Client's status, such as start up and close down times and client error details. The orbit-session.log contains information about sessions started in the client, such as session names and session error details.

Both types of log file are placed inside the .athera directory in your local machine's home directory, which differs by operating system:

• Windows: C:\Users\<username>\.athera\orbit
For example: C:\Users\jimmy\.athera\orbit

• Mac: /Users/<username>/.athera/orbit
For example: /Users/jimmy/.athera/orbit

• Linux: /home/<username>/.athera/orbit
For example: /home/jimmy/.athera/orbit

This is explained under the 'Viewing Orbit Logs' title of the Athera Online Help - Configuring the Orbit Desktop Client section. 


X server access:

On some Linux distributions, the Orbit Desktop Client requires access to X Server to run correctly. If this is the case, the log file contains the following error:

Failed running TurboVNC executable error=exit status 1

In order to grant access to the X server please follow the steps outlined under 'Running Orbit on Linux' title of the Athera Online Help - Configuring the Orbit Desktop Client section. 



If you are still experiencing issues please create a Support ticket with the following information:

  • Copies of both Orbit log files from your .athera directory
  • The Session ID of the session you are seeing this behaviour with (you can locate the session ID via the steps in the following article: FAQ101: What is the Session ID and where do I find it?)
  • System Specs of your machine you're running Orbit on
    • Operating System and Version
    • CPU
    • RAM
    • GPU and Driver Version

From here we will be able to look into this further

Was this article helpful?
0 out of 0 found this helpful