Product Documentation

Troubleshooting

Sep 27, 2016

Registration issue

For basic diagnostics, refer to the KB article and use XDPing.

For detailed information, refer to the Linux VDA blog

Session validation issue

For detailed information, refer to the Linux VDA blog.

Customize desktop environment per-user

Currently, the Linux VDA does not allow the user to choose the desktop environment when logging in; to workaround this issue, the user can configure a file (for example, .xsession) for the Linux distribution to set the default desktop environment for each user. Refer to the documents accompanying the Linux distribution for more information.

To set the KDE as the default environment:

command 複製

#! /usr/bin/env bash

exec startkde

To set GNOME as the default desktop envionment:

command 複製

#! /usr/bin/env bash

exec gnome-session

Verify that the Linux machine has been prepared correctly

The most common issues are a direct result of Linux machine misconfiguration, mainly around networking, NTP time server configuration or Active Directory domain membership. Fixing the Linux machine’s configuration will often resolve issues with the VDA software.

Configure logging and tracing

The Broker Agent and the HDX Service log to syslog. Citrix Support provides a set of tools that can enable additional trace during a support call.

HDX Service Logging

The HDX Service is configured to log syslog out-of-the-box messages and no further configuration is needed.

Broker Agent logging 

The Broker Agent (also known as the ctxvda service) writes log data to syslog via network sockets. This may not be configured out-of-the-box. To enable the Broker Agent logging to syslog logging, the following configuration is required:

SLED/SLES 11

Edit the /etc/syslog-ng/syslog-ng.conf file and add the following line in the s_sys section:

command 複製

udp(ip(127.0.0.1) port(514));

Save and close the syslog-ng.conf file. Restart the syslog-ng service to apply the change:

command 複製

sudo service syslog-ng restart

SLED/SLES 12

Edit the /etc/rsyslog.conf file and add the following lines:

command 複製

$ModLoad imudp

$UDPServerRun 514

Save and close the rsyslog.conf file. Restart the rsyslog service apply the change:

command 複製

sudo service rsyslog restart

What to try if HDX sessions won't start

Ensure you have no orphaned processes which might be preventing new sessions from starting:

command 複製

sudo pkill -9 ctxhdx

sudo pkill -9 ctxgfx

sudo pkill -9 ctxlogin

sudo pkill -9 ctxvfb

Restart the Linux VDA services and retry connection.

Verify ownership and permissions of key directories and files

Check the file ownership and permission of the following directories and files:

  • /var - Owner: root, Group: root, Permissions: 0755 
  • /var/xdl - Owner: ctxsrvr, Group: ctxadm, Permissions: 0755 
  • /var/xdl/.isacagent - Owner: root, Group: root, Permissions: 0666 
  • /var/xdl/.winsta - Owner: ctxsrvr, Group: ctxadm, Permissions: 0777 
  • /var/xdl/vda - Owner: root, Group: root, Permissions: 0755

Audio is not being heard

Check that the volume control on the device running the Citrix Receiver as well as the Linux desktop are not muted or set to a low level.

Check that audio is enabled on the Linux VDA. Use the ctxreg tool to query the value of the configuration item fDisableCam

command 複製

sudo ctxreg read -k "HKLM\System\CurrentControlSet\Control\Citrix\WinStations\tcp" -v fDisableCam

A value of 0x1 means audio is disabled. To enable, set fDisableCam to 0x0:  

command 複製

sudo ctxreg update -k "HKLM\System\CurrentControlSet\Control\Citrix\WinStations\tcp" -v fDisableCam  -d 0x00000000

If audio is still not being heard check that the Citrix audio sink is loaded by pulseaudio. This  PulseAudio module is loaded into the pulseaudio daemon at session start. Use the pacmd tool to check the Citrix audio sink is loaded:

command 複製

pacmd list-sinks

If the Citrix audio sink is loaded, the output should be:

ouput 複製

name: <CitrixAudioSink>

driver: <module-ctx-sink.c>

If Citrix audio sink is not loaded, kill the ctxaudio process and restart it.

Audio is not being recorded

Check that audio is enabled on the Linux VDA and audio recording is enabled on the ICA client. If audio is still not being recorded check that the Citrix audio source is loaded by pulseaudio. If audio recording is enabled on the ICA client, this PulseAudio module will be loaded into the pluseaudio daemon at session start. Use the pacmd tool to check the Citrix audio source is loaded:

command 複製

pacmd list-sources

If the Citrix audio source is loaded, the output should be:

output 複製

name: <CitrixAudioSource>

driver: <module-ctx-source.c>

If the Citrix audio source is not loaded, kill the ctxaudio process and restart it.

CDM does not work

The CDM feature includes a daemon process (ctxcdmd); if the CDM feature fails, reboot the Linux VDA machine and verify whether the daemon launched correctly:

command 複製

Ps -lef | grep ctxcdmd

The file naming in the mapped drive should follow the VDA and Receiver OS naming rules.