To enable trace logging for ctxjproxy
Follow the steps below to enable trace logging for ctxjproxy:
1. Find the /etc/xdl/ctx-jproxy.conf file. The file is generated after you configure the Linux VDA by ctxsetup.sh.
2. Uncomment the line and change the following setting.
3. Open the /etc/xdl/log4j.xml file, find the following content, change the level value to trace, and save the file
<root><level value=”info”/><appender-ref ref=”file”/><appender-ref ref=”syslog”/></root>
4. Restart the ctxjproxy service.
sudo service ctxjproxy restart
Trace level logs will be found in /var/log/xdl/jproxy.log
Each log level defines the minimum rank of messages to log:
1. ALL - The lowest possible rank. Intended to log all.2. TRACE - Designates finer-grained informational events than the DEBUG level.3. DEBUG - Designates fine-grained informational events that are most useful to debug an application.4. INFO - Designates informational messages that highlight the progress of an application at coarse-grained level.5. WARN - Designates potentially harmful situations.6. ERROR - Designates error events that might still allow an application to continue to run.7. FATAL - Designates very severe error events that will presumably cause an application to abort.8. OFF - The highest possible rank.
To enable trace logging for ctxvda
1. The trace file of .NET ctxvda service is under /var/log/xdl/ with file name vda.*.log. The file to configure tracing is /etc/xdl/brokeragent.conf, open this file to change logging level.
2. Trace modules in ctxvda are listed as following:
<add key="TraceProvider.BrokerAgent.CategoryFilter" value="Error" /> <add key="TraceProvider.BrokerAgentAoTracing.CategoryFilter" value="Error" /> <add key="TraceProvider.BrokerAgentEvents.CategoryFilter" value="Error" /> <add key="TraceProvider.BrokerAgentPluginProxy.CategoryFilter" value="Error" /> <add key="TraceProvider.CBP.CategoryFilter" value="Error" /> <add key="TraceProvider.LaunchStore.CategoryFilter" value="Error" /> <add key="TraceProvider.LoadBalancing.CategoryFilter" value="None" /> <add key="TraceProvider.MonitorManager.CategoryFilter" value="Error" /> <add key="TraceProvider.NTEvent.CategoryFilter" value="Error" /> <add key="TraceProvider.PerfCounter.CategoryFilter" value="Error" /> <add key="TraceProvider.Plugin.CategoryFilter" value="Error" /> <add key="TraceProvider.Registry.CategoryFilter" value="Error" /> <add key="TraceProvider.SessionMonitoring.CategoryFilter" value="Error" /> <add key="TraceProvider.SessionParameters.CategoryFilter" value="Error" /> <add key="TraceProvider.ShortcutEnumerator.CategoryFilter" value="Error" />
Trace levels for each tracing module include Error, Warning, Information and EntryExit. By default, the trace level is Error which means only error message will be output to trace file. Modifying the value parameter will change the tracing level for certain tracing module.
3. After updating the configuration, ctxvda service should be restarted to let those change take effect.
sudo service ctxvda restart
To enable trace logging for ctxhdx and all other services
The Linux VDA has been using a new log system since version 1.2. Log messages are sent directly to syslog and trace messages are sent to a new optional component – the ctxLog daemon (ctxlogd).
The setdbg utility is replaced with the new setlog utility, which offers more intuitive control over trace output.
The setlog utility and ctxlog daemon are included in the trace package. For the relevant trace and symbol packages, contact Citrix Escalation engineers.
Follow the steps below to enable trace logging for ctxhdx and all other services:
1. Install the proper version of the trace and symbol packages.
2. Enable the ctxlog daemon.
sudo service ctxlogd start
3. Restart corresponding services to enable the trace log for each services.
sudo service ctxhdx restartsudo service ctxcdm restart // For CDMsudo service ctxpolicyd restart //For policysudo service ctxusbsd restart //For usb
4. Change log levels using the setlog utility.
Logs will be found in /var/log/xdl/hdx.log.
Trace logging is configured using the setlog utility, which is packaged alongside the ctxlog daemon.
Log classes are now organized into a hierarchy, allowing settings to be inherited. You can set each log class to allow a minimum message priority, to be disabled entirely, or to inherit settings from its parent. The flags to control what metadata is printed with trace messages have returned.
The setlog utility allows you to configure the path that trace output will be written to and to configure log rollover based on a threshold file size. It also now has basic command line options so that you can control trace flags and levels over SSH or in any other circumstances where a graphical environment is not available. For more information, type setlog help
For the log classes required, contact Citrix technical support.