This section describes the various kinds of debug data that you must provide to the Sun Support Center and how to obtain debug data based on the kind of problem you are experiencing.
This section contains the following tasks:
To Collect Required Debug Data for All Secure Global Desktop Problems
To Collect Debug Data for Secure Global Desktop Installation Problems
To Collect Debug Data for Secure Global Desktop Application Launch Problems
To Collect Debug Data for Secure Global Desktop Application Emulation Problems
To Collect Debug Data for Secure Global Desktop Printing Problems
To report problems described in this technical note, you must collect some basic information. This basic information includes the Secure Global Desktop version, system details, and date and time when the problem occurred. Follow these steps to collect the basic information.
If the Secure Global Desktop is in an array, please provide the information below from the primary server and one of the secondary servers in the array. To find the primary and secondary server information:
install-dir/bin/tarantella status Array members (2): - host1.ssgd-array.com (primary): Accepting standard connections. - host2.ssgd-array.com (secondary): Accepting standard connections. - Webtop sessions (73): - Standard connections: 73 - - Emulator sessions (74): - X Protocol Engine: 74 |
Note the SGD version.
install-dir/bin/tarantella version |
Note the date and time the problem occurred.
Note the operating system.
Note the type of Webtop that is being used to connect to the Secure Global Desktop server.
Classic Webtop – Indicated by either of these situations:
The URL ends with /tarantella
The Secure Global Desktop Native Client is being used
For an example of a Classic Webtop, see Sun Secure Global Desktop Software 4.3 Using Your Webtop
Secure Global Desktop Webtop – The URL ends with /sgd
For an example of a Secure Global Desktop Webtop, see Sun Secure Global Desktop Software 4.3 Using Your Webtop
Integrated Mode Webtop – You log in to Secure Global Desktop by clicking the Login link on your desktop Start menu
For an example of an Integrated Mode Webtop, see Sun Secure Global Desktop Software 4.3 Administration Guide
Note the type of client that is being used to connect to the Secure Global Desktop server.
The Sun Secure Global Desktop Software 4.3 Release Notes provides a list of platform support for the Secure Global Desktop and for the Classic Desktop.
Collect Sun Secure Global Desktop and System information.
install-dir/bin/tarantella info -all |
Press Return when you are prompted for the Output tar filename. Please include the resulting .gz file in the handoff package.
This command can fail or cause system stress on systems where stability of the entire array is already an issue. If the command fails, run the following commands as root:
script /tmp/ssgd_info.txt install-dir/bin/tarantella config list install-dir/bin/tarantella license list ifconfig -a netstat -rn hostname cat /etc/hosts cat /etc/resolv.conf nslookup localhost nslookup hostname |
Press CTRL+D to end the script. Include the resulting /tmp/ssgd-info.txt file in the debug data.
Collect the Secure Global Desktop Log files into a compressed tar file.
install-dir/bin/tarantella archive install-dir/var/log/1 |
Note any customization to the Secure Global Desktop installation, for example, a modified Webtop, or custom binaries.
If an array is being used, list the current server times on each server in the array.
If you are unable to complete the installation or if an upgrade fails, complete the following steps.
Collect as much of the required debug information as possible.
For more information, see To Collect Required Debug Data for All Secure Global Desktop Problems.
Note the disk space available:
df -kv |
Note whether this installation is a new installation or an upgrade.
If this installation is an upgrade, supply the original version, upgrades to any intermediate versions, and the final version.
Note any specific error messages that are received at the time of failure.
If you are running Secure Global Desktop on the Solaris platform or running versions up to version 4.20.959, create an installation debug log.
If you are unable to launch any application, complete the following steps.
Collect as much of the required debug data as possible.
For more information, see To Collect Required Debug Data for All Secure Global Desktop Problems.
Note the attributes of the application failing to launch.
install-dir/bin/tarantella object list_attributes --name "obj" |
For example:
install-dir/bin/tarantella object list_attributes --name " .../_ens/o=organization/cn=dtterm (ttahost)" |
For more details about this command, see Sun Secure Global Desktop Software 4.3 Administration Guide.
Collect the connection details from the launch window from a failed launch, and one from a successful launch if possible.
Access SunSolve document #15493. (You can search for the document number if you do not have direct access.)
Enable Launch debugging through the SunSolve document.
Include the resulting files in the debug files provided to Sun Support.
If an application launches successfully but the application exhibits unusual behavior, such as slow processing, incorrect window size, unusual coloring, and the like, complete the following steps.
Collect as much of the required debug data as possible.
For more information, see To Collect Required Debug Data for All Secure Global Desktop Problems.
Note the attributes of the application with the emulation problems.
install-dir/bin/tarantella object list_attributes --name "obj" |
For example:
install-dir/bin/tarantella object list_attributes --name " .../_ens/o=organization/cn=dtterm (ttahost)" |
For more details about this command, see Sun Secure Global Desktop Software 4.3 Administration Guide.
Provide a description of the behavior or appearance that is different than what you expected.
For example, a screenshot in PNG or JPEG format is helpful.
Capture a Spy session of the application.
Windows applications: http://sunsolve.sun.com
X applications: http://sunsolve.sun.com
If you are experiencing problems when printing, for example, the print job is not appearing or is not formatted correctly, complete the following steps to collect debug data from the Secure Global Desktop server and client.
Collect as much of the required debug data as possible.
For more information, see To Collect Required Debug Data for All Secure Global Desktop Problems.
In the file install-dir/bin/scripts/lp_interface.en, change TRACE="" to TRACE="t".
In the file install-dir/bin/scripts/tta_print_converter, change TRACE="" to TRACE="t".
If you are running a version of Secure Global Desktop prior to version 4.4 and the Client is using the Classic Webtop:
In the file install-dir/var/docroot/resources/webtops/sco/tta/standard/locale=en-us/print.html, find the section that starts with:
<!-- printer applet --> |
and change the text at the end of the section to:
<param name="ProxyFrame" value="OptFrame"> <param name="DebugMask" value="255"> </ttaapplet> |
On the client, enable the Java Console for the browser being used.
Refer to the browser documentation for details.
Reproduce the print problem by, if possible, having the user print from a client using the Classic Webtop.
Collect the Print debug data:
If the problem is related to printing from Windows applications, on the Windows Terminal Server, capture any print-related messages logged in the Windows Event Viewer.