This article provides general guidance to troubleshoot Session Shadowing feature of Linux VDA.
 

Instructions

1. Check if Session Shadowing is enabled correctly – refer to Introduction - Session Shadowing for Linux VDA sessions and How to configure Session Shadowing for Linux VDA sessions.
2. Perform troubleshooting steps for further investigation

1. You can use developer tools of a web browser, check the output logs on the Console tab, or check the response of the ShadowLinuxSession API on the Network tab. Below is an example of Firefox web developer tool:

2. If the shadow request window pop up in session user end yet the connection fails, manually ping the FQDN of the Linux VDA to make sure that Citrix Director Client host can resolve the FQDN correctly.
3. If you’re using an SSL encrypted connection, check the certificate settings, make sure the CA certificate is correctly imported.

On the Citrix Director Server

1. Check system event viewer of Citrix Director Server for Warning or Error messages on Citrix Director Service. Below is an example of SSL failure:

2.  Enable debug logging to get more detailed logging, you can refer to How to Enable Logging for Desktop Director for instructions.

On the Linux VDA
 You can get more detailed logging by following steps:

• Get more detailed vda.log:
  1. Locate the /etc/xdl/ctx-vda.conf file. Uncomment the following line to enable the vda.log configuration:

Log4jConfig=”/etc/xdl/log4j.xml”

2. Open /etc/xdl/log4j.xml, locate the com.citrix.dmc part, and change “info” to “trace” as follows:

<!-- Broker Agent Plugin - Director VDA plugin Logger -->
<logger name="com.citrix.dmc">
    <level value="trace"/>
  </logger>

3. Run the sudo service ctxvda restart command to restart the ctxvda service.

• Get debug logging for sessionshadowing.sh:
  1. Locate /var/xdl/sessionshadowing.sh file, uncomment the following line:

logFile="/dev/null"

2. Add a line to set log file, for example:

logFile="/var/log/xdl/shadowing.log"

The generated shadowing.log will contain some debug information for shadowing request popup window, starting or killing a VNC server.

1. If the shadowing confirmation windows didn’t prompt, check the vda.log and hdx.log under /var/log/xdl/ for clues.
2. In case of an error during connection setting up:
   • Check for any firewall limitation that stops Session Shadowing from opening the port.
   • Verify that the certificates and key files are named properly and put under the right path in case of the SSL scenario.
   • Verify that there are enough ports left between 6001-6099 for new shadowing requests.