D    Graphical User Interfaces

There are two interfaces that provide graphical representation of the AdvFS file system: the Logical Storage Manager Storage Administrator (LSMSA) and the AdvFS Graphical User Interface (AdvFS GUI). LSMSA allows you to manage LSM objects and perform LSM as well as the AdvFS file system administrative functions. In contrast, the AdvFS Graphical User Interface GUI provides a visual representation of the AdvFS file system. Both require utilities licenses.

LSMSA is a Java-based application that operates on local or remote (client) systems. LSMSA operations are described in detail in Logical Storage Manager.

AdvFS GUI operations are described below. The AdvFS GUI is designed to run under the Common Desktop Environment (CDE). You can use the GUI locally or as a remote system manager.

To access the AdvFS GUI, you must register the AdvFS Utilities license and you must have root user privilege. For information about license activation contact your software support organization.

D.1    Installing the AdvFS GUI

To load the AdvFS GUI, choose the AdvFS Utilities subset when you update or install the operating system.

Table D-1 contains the subset titles, names (where xxx is the subset identification number), and descriptions of the subsets that make up the AdvFS GUI. The disk space requirements for loading and running AdvFS Utilities software subsets are shown in Table D-2.

Table D-1:  AdvFS GUI Subsets

Table D-2:  Disk Space Requirements for the AdvFS GUI

D.2    Components of the GUI

There are two parts to the GUI: advfsd, the agent, and dtadvfs, the actual graphical interface. The agent must be running for the GUI to operate.

D.2.1    GUI Agent (advfsd)

The AdvFS GUI agent, advfsd, issues commands and obtains system information for the GUI. If the agent is not running, the GUI cannot operate. The agent is automatically started at boot time and when the OSFADVFSDAEMON subset is installed. It runs unseen in the background.

Under normal conditions, advfsd does not need to be run manually. If you want to start or stop the agent at any time, do so from the command line (see advfsd(8)). If you are not running Performance Manager, you can stop the agent and restart it when you run the GUI.

To stop the agent:

# /sbin/init.d/advfsd stop

To restart the agent:

# /sbin/init.d/advfsd start
 
 

Only one agent can be running on a system at a given time. If you attempt to start a second copy of advfsd, it fails.

The agent allows Simple Network Management Protocol (SNMP) clients such as NetView to request AdvFS information. This is not a two-way path: SNMP clients cannot issue system configuration commands to advfsd.

The agent periodically asks for information from the system on which it is running. It then updates the file systems and the storage device information passed to the GUI display. It also evaluates any free space alert conditions. The time interval for when the agent scans the system disks is the agent state monitor interval. To change the agent state monitor interval, see Section D.3.1. The interval is saved between restarts of the agent.

D.2.2    AdvFS GUI (dtadvfs)

Only the root user can start the AdvFS GUI, dtadvfs. It can be started in a terminal window or from a CDE icon. The file system operations that the GUI can perform are described in Section D.4.

To start the GUI from the command line, enter:

# /usr/bin/X11/dtadvfs &

To start the GUI using CDE icons:

1. Select the Application Manager on the CDE toolbar.

2. Double-click on the System_Admin icon in the Application Manager window.

3. Double-click on the Storage_Management icon in the System_Admin window.

4. Double-click on the Advanced File System icon in the Storage_Management window.

When the GUI is running, window displays are periodically updated to reflect the changing characteristics of the file system. The GUI refresh interval, the time interval between updates, is 15 minutes by default. To change the GUI refresh interval when the GUI is running, see Section D.3.1. The GUI refresh interval is not saved between restarts of the GUI.

D.2.2.1    GUI Security

Two optional security files are associated with each system that the GUI manages. The password file restricts the use of the GUI managing a particular system to administrators who know the password. The allowable hosts file allows only GUIs running on systems listed in the file to remotely manage it. These files are configured through an editor of your choice. They cannot be accessed directly from the GUI.

The root user creates the password file, /var/advfs/daemon/socket/gui.passwd, on the system for which the password is to be used. There is one password file containing one password per system. (It is not a good idea to use the root password.) The file contains the password in plain text. Only users who enter the correct password can run a GUI connected to the system. A user wanting to use the GUI to manage the system from a remote location must know this password in order to connect to the system.

The allowable hosts file, /var/advfs/daemon/socket/hosts.allow, is also created by the root user. It contains a plain text list of all systems (hosts) on which a GUI can operate to manage the system. The hosts.allow file automatically includes the GUI running locally on the system; that is, it includes itself. If you want to allow others to remotely manage your system, you must include them in your hosts.allow file to authorize the agent to send your file system information to their system. If you have protected your system with a password in the system's gui.passwd file, remote users also have to know that password.

See advfsd(8) and dtadvfs(8) for more information.

D.2.2.2    Ignoring Disks

Create the /var/advfs/daemon/disks.ignore file to specify a list of disks that the agent does not examine. The disks.ignore file contains a plain-text list of disk drives, one per line. This file is useful because performance might be reduced when there are off-line HSZ devices or spun-down disk drives.

Since the agent processes the disks.ignore file every time the disks are checked, disks that fail can be added to the file and disks listed in the file that become available can be removed. It is not necessary to stop the agent. See advfsd(8) for more information.

You cannot ignore an LSM volume by including the LSM volume name in the disks.ignore file; you must list the disks from which the LSM volume is built. To ignore a complete disk group, you must list all disks in it. Because all partitions on the listed disks are ignored, unexpected results might occur if a disk has partitions belonging to more than one disk group.

D.2.2.3    Log Files

Entries are generated in the agent log file, /var/advfs/daemon/logs/advfsd, and the GUI log file, /var/advfs/gui/advfs_gui.log, as processing proceeds. It is a good idea to periodically check these files. Both the agent and the GUI log files are periodically renamed to prevent unrestricted consumption of disk space.

D.2.2.4    Help

The help system contains background information about the AdvFS file system as well as specific information about the GUI. Each operation is described. Detailed explanations of the dialog boxes that are used to perform file system activities are provided.

D.2.2.5    Monitoring Remote File Systems

From your system you can remotely monitor file systems that have your system listed in their hosts.allow file. You can attach to these systems through the GUI:

1. Choose Host... from the AdvFS menu of the main window.

2. The Select a Host dialog box appears, in which you can select another host system or choose to modify the host list to add or delete host systems. This list is created by you and saved on your system to identify the hosts you connect to regularly.

3. Select the host and click Connect.

If you try to connect to a host but are unsuccessful, you are no longer connected to any host so you must repeat the connection process for another system.

Note that the host list is for convenience only. It does not provide additional security. You can always type a host name in the Selection block of the Select a Host dialog box.

D.2.2.6    Managing LSM Volumes

If you are using LSM volumes, it is important to know how the GUI treats these volumes:

• An LSM volume is listed as available if it is labeled unused.

• Do not use LSM to change the size of an LSM volume that is in use by an AdvFS domain. AdvFS is unable to accommodate this change.

• If you added the LSM volume /dev/vol/volname to the domain from the command line, the AdvFS GUI does not recognize that it is the same as /dev/vol/rootdg/volname. If the volume has mounted filesets, it appears as unknown in the devices and volumes window; if it has no mounted filesets, it appears as unavailable. If you try to add it to a domain, you get an error message saying it is in use.

• If you encapsulate a volume in use by AdvFS into LSM while the GUI is running, the volume name is not updated in the GUI window. You must exit and restart the GUI to display the correct name.

• You cannot ignore an LSM volume by including the LSM volume name in the disks.ignore file; you must list the disks from which the LSM volume is built.

D.3    Displaying File System Information

The objects (components) that make up the file system (volumes, domains, filesets, and fileset clones) are viewed in the GUI windows in an object tree that shows their hierarchical relationship to each other. If an object contains other objects, a folder icon appears to its left. Clicking on the folder icon expands or collapses the object tree; that is, displays or hides the objects below it in the tree. For example, clicking on a domain folder icon displays or hides the filesets that belong to that domain.

You can change your window views and look at critical information about the objects in a number of ways. You can view:

• Main window information

  The first window that appears, the main window, provides a comprehensive view of the file system. It is the starting point for all GUI-managed tasks and the primary screen for monitoring file system status. Use the items on the View menu to display the status of domains and filesets; domains and volumes; and domains, filesets, and volumes. You can also use the View menu to change from one of these views to viewing fileset quotas and back.

• Devices and volumes

  Choose Devices and Volumes from the Configuration menu for a different detailed view. The devices and volumes window displays all the physical disks, disk groups, and logical volumes on the system and can be used to determine volume type or partition availability.

• Object characteristics

  Choose Show... from the Configuration menu to display more complete information about the object that you have highlighted in the main window display.

  You can usually select Show... as an alternate way of performing the file system management tasks described in the following sections. For example, highlight the domain and choose Show... to see an object dialog box that includes the creation date and number of log pages for that domain.

Note that double-clicking a domain, fileset, clone, or volume in the object tree is the same as choosing Show... for that object. Double-clicking does not work for hosts, devices, or partitions or for the volume icon in the devices and volumes window. Single-clicking an object in an object tree only highlights it. No new information is presented.

Clicking the right mouse button on an object brings up a list of commands appropriate for that object.

If you attempt to access a menu item and find it unavailable (grayed out), check that the appropriate object is highlighted. For example, you need to select a fileset before you can create a clone for it.

D.3.1    Choosing Units for Displaying Information

You can customize the display of your file system information by choosing Options from the AdvFS menu. All options except the agent state monitor interval are reset each time the GUI is restarted.

• Units

  Choose to display disk space usage in 512-kilobyte blocks, kilobytes, megabytes, gigabytes, or terabytes.

• Update Interval

  Choose the GUI refresh rate.

  Choose the Agent state monitor interval.

• Free Space Alert

  Choose between space used > and free space <.

  Choose to display space available as a percent or in the units you have chosen for the display.

• Fileset quotas

  Choose to calculate quotas by percent of space or by the amount of space used.

D.3.2    Main Window

When the main window first displays, disk-space usage information is shown for the host and for domains. Options on the View menu let you display domains, filesets, and volumes in different combinations.

From the main window you can also view fileset quota information by choosing Fileset Quotas from the View menu. You can return to viewing domain, fileset, and volume information by selecting the items you want to view from the same View menu.

The main window has menu selections that you can use to accomplish file system management tasks for domains, filesets, clones, and volumes. Menu commands call up dialog boxes to help you accomplish these tasks.

D.3.3    Devices and Volumes Window

The devices and volumes window displays disk groups and logical volumes. It identifies the size and type of disks and what each partition is used for. This view is particularly useful if you want to enlarge your domain and need to locate a volume to use. From the View menu of the devices and volumes window, you can sort your objects, choose to display only available volumes, or choose to display overlapped volumes.

D.4    Performing File System Operations

You can perform file system management tasks on domains, filesets, AdvFS fileset clones, and volumes directly from the GUI. In general, you must select the appropriate object before you can proceed. In the following sections, file domain and domain are synonymous.

D.4.1    Operations on a Domain

File system management tasks for domains are initiated from the main window by selecting Show or File Domain on the Configuration menu. In addition, from the devices and volumes window you can create a new domain and add volumes to an existing domain.

D.4.1.1    Creating a Domain

To create a domain, you must assign a name and select an initial volume. You can set a free space alert.

A domain is not completely defined until you have created at least one fileset. A domain is not active unless there is a mounted fileset. To create a domain using the main window:

1. Choose File Domain from the Configuration menu.

2. Choose New from the File Domain menu.

3. In the New File Domain dialog box, enter the domain name and highlight an available volume in the object tree. You might need to expand the device list by clicking on the folder to the left of the device name. You can also set the free space alert.

If you are not certain what storage device to use for the new domain, work from the devices and volumes window (on the Configuration menu) to get a complete view of the storage on your system:

1. Choose Devices and Volumes from the Configuration menu of the main window.

2. In the devices and volumes window, choose Show available volumes only from the View menu.

3. Choose a volume that is labeled as available.

4. Choose New File Domain from the Configuration menu.

5. In the New File Domain dialog box, create the domain and set the free space alert. If you are monitoring a file system prior to Version 4.0E, see the main window instructions for directions on using the Advanced button.

Creating a domain automatically generates an entry in the /etc/fdmns directory.

D.4.1.2    Setting a Free Space Alert for a Domain

Set a free space alert to inform you when the free space threshold in the domain is reached or passed. When you set the alert, you can choose to automatically run a script when the alert threshold is crossed. See /usr/advfs/daemon/scripts for examples of scripts used by the agent to execute commands.

To set the free space alert from the main window:

1. In the object tree, highlight the domain.

2. Choose File Domain from the Configuration menu.

3. Choose Set free space alert from the File Domain menu.

4. In the File Domain dialog box, set the free space alert.

You must reset the free space alert when the size of a domain changes. Free space alert values are evaluated using actual size (for example, kilobytes), not percentage of space.

D.4.1.3    Enlarging a Domain

Add volumes to transform a single-volume domain (except the root domain, which can only have one volume) into a multivolume domain or to enlarge a multivolume domain (see Section 1.6.6).

To add a volume to a domain:

1. In the object tree, highlight the domain.

2. Choose File Domain from the Configuration menu.

3. Choose Add Volume from the File Domain menu.

4. In the Add Volume dialog box, highlight an available volume to add. You might need to expand the view of the volumes by clicking the folder icon to the left of the device name.

If you do not know which volume to add to your domain, work from the devices and volumes window to get a complete view of the storage on your system:

1. Choose Devices and Volumes from the Configuration menu of the main window.

2. In the devices and volumes window, choose Show available volumes only from the View menu.

3. Click a volume that is labeled available.

4. Choose Add to domain from the Configuration menu.

5. In the Add Volume dialog box, choose the domain to which the new volume is added.

It is a good idea to balance your domain after you have added a volume. This distributes existing files to the new volume.

D.4.1.4    Removing a Domain

You can delete a domain only after all filesets and fileset clones in the domain are unmounted. You get an error message if you try to remove a domain with mounted filesets. When you remove a domain in order to delete all filesets, its entry in the /etc/fdmns directory is removed. However, this can present a security hole since only pointers are changed and no data on the volume is removed. It could be possible to access the fileset data from the command line by using the salvage utility (see Section 5.8.4). If you need the increased security, remove each fileset individually.

The deleted domain name remains in the /etc/fstab file unless you modify the file by choosing the Modify /etc/fstab option in the dialog box or change it from the command line. If you do not update this file, you will get error messages when you reboot the system or when you enter a mount -a command from the command line. If you do not delete the file name from the /etc/fstab file, you can do so at a later time from the command line.

To remove a domain:

1. In the object tree, highlight the domain.

2. Choose File Domain from the Configuration menu.

3. Choose Delete from the File Domain menu.

4. In the Delete File Domain dialog box, delete the domain and back up and modify the /etc/fstab file.

Note

When you unmount your filesets and fileset clones, you must choose to modify the /etc/fstab file. If you do not do so at that time, you must manually edit the /etc/fstab file. After you delete the domain you no longer have access to the filesets.

D.4.1.5    Renaming a Domain

You can assign a new name to an existing domain (see Section 1.6.9). The old name remains in the /etc/fstab file unless you modify the file by choosing the Modify /etc/fstab option in the dialog box or change it from the command line. If you do not update the /etc/fstab file, the filesets in this domain do not mount when you reboot the system or when you enter the mount -a command from the command line. If you must update the /etc/fstab file at a later time, do so from the command line.

Unmount all filesets before renaming the domain. You get an error if you try to rename a domain with mounted filesets. You cannot rename a domain with the name of an existing domain.

To rename a domain:

1. In the object tree, highlight the domain.

2. Choose File Domain from the Configuration menu.

3. Choose Rename from the File Domain menu.

4. In the Rename File Domain dialog box, enter the new name and back up and modify the /etc/fstab file.

D.4.2    Operations on a Fileset

File system management tasks for filesets are initiated from the main window by selecting Show... or Fileset from the Configuration menu after you have highlighted the fileset on which you want to operate. It is important that you choose to modify and back up the /etc/fstab file as you perform fileset operations. If you do not, there is a chance that the /etc/fstab file will not be correct for subsequent operations. If you must update the /etc/fstab file at a later time, do so from the command line.

D.4.2.1    Creating a Fileset

You cannot create a fileset until you have a domain with which to associate it (see Section D.4.1.1).

To create a fileset:

1. In the object tree, highlight the domain for which the fileset will be created.

2. Choose Fileset from the Configuration menu.

3. Choose New from the Fileset menu.

4. In the New Fileset dialog box, create the fileset, mount the fileset, back up and modify the /etc/fstab file, set a free space alert, and set fileset quotas (as desired).

Note that when you create a fileset, you can set the free space alert only as a percentage of the available space.

D.4.2.2    Mounting a Fileset

When you mount a fileset, you make its files available. The display in the main window indicates which filesets are mounted. A domain is active when at least one fileset is mounted.

To mount a fileset:

1. In the object tree, highlight the fileset.

2. Choose Fileset from the Configuration menu.

3. Choose Mount from the Fileset menu.

4. In the Mount Fileset dialog box, create a mount point if it does not exist and back up and modify the /etc/fstab file.

D.4.2.3    Unmounting a Fileset

When you unmount a fileset, its files are no longer available. You must unmount the fileset before you can remove it or remove the domain to which it belongs. The display in the main window indicates whether filesets are mounted or not mounted.

To unmount a fileset:

1. In the object tree, highlight the fileset.

2. Choose Fileset from the Configuration menu.

3. Choose Unmount from the Fileset menu.

4. In the Unmount Fileset dialog box, unmount the fileset and back up and modify the /etc/fstab file.

D.4.2.4    Setting a Free Space Alert for a Fileset

Set a free space alert to warn when the free space threshold in the fileset is reached or passed. You must mount the fileset before you can set the alert. After you set the alert, you can choose to automatically run a script when the alert threshold is crossed.

To set the free space alert:

1. In the object tree, highlight the fileset.

2. Choose Fileset from the Configuration menu.

3. Choose Set free space alert from the Fileset menu.

4. In the Fileset dialog box, set the free space alert.

You must reset the free space alert when the size of a fileset changes. Free space alert values are evaluated using actual size (for example, kilobytes), not percentage of space.

D.4.2.5    Setting Fileset Quotas

Set fileset quotas to limit the amount of space the fileset can consume. If you do not set quotas, any fileset can use all the available space in the domain. You can only set quotas on mounted filesets.

To set fileset quotas:

1. In the object tree, highlight the fileset.

2. Choose Fileset from the Configuration menu.

3. Choose Set fileset quotas from the Fileset menu.

4. In the Fileset dialog box, set the fileset quotas.

You can view fileset quota information from the main window by choosing Fileset Quotas from the View menu. To return to viewing disk usage, choose the items you want to view from the View menu.

D.4.2.6    Removing a Fileset

You must unmount a fileset before you can delete it. You can unmount as part of the removal process. If the fileset has a clone, you must remove the clone first. Removing a fileset removes all files in that fileset.

To remove a fileset:

1. In the object tree, highlight the fileset.

2. Choose Fileset from the Configuration menu.

3. Choose Delete from the Fileset menu.

4. In the Delete Fileset dialog box, unmount the fileset, delete it, and back up and modify the /etc/fstab file.

If all the filesets are unmounted, the fastest way to remove all filesets is to remove the domain to which they belong. However, this might present a security hole because it might be possible to access the data by using the salvage utility (see Section 5.8.4).

D.4.2.7    Renaming a Fileset

You must unmount a fileset before you can rename it. You can do this as part of the renaming process. The new fileset name must be unique within the domain.

To rename a fileset:

1. In the object tree, highlight the fileset.

2. Choose Fileset from the Configuration menu.

3. Choose Rename from the Fileset menu.

4. In the Rename Fileset dialog box, unmount the fileset, enter a new name, and back up and modify the /etc/fstab file.

Note

If you rename a fileset that has never been mounted (does not already have an /etc/fstab file entry) and check the modify /etc/fstab box, you do not get a new entry for the fileset name. You must manually edit the /etc/fstab file to add the new entry.

If you rename a fileset, its clone can no longer track it. You must delete the old clone and create a new one because clones cannot be renamed.

D.4.3    Operations on an AdvFS Fileset Clone

When you operate on a clone, it is important to modify and back up the /etc/fstab file as you perform clone operations. If you do not, there is a chance that the /etc/fstab file will not be correct in subsequent operations. If you must update the /etc/fstab at a later time, do so from the command line.

D.4.3.1    Creating an AdvFS Fileset Clone

Creating a fileset clone allows you to back up files while the file system is on line (see Section 3.3). You can create only one clone for a fileset.

To create a clone:

1. In the object tree, highlight the fileset that you want to clone.

2. Choose Clone from the Configuration menu.

3. Choose New from the Clone menu.

4. In the New Clone dialog box, enter a clone name, create a mount point, and back up and modify the /etc/fstab file.

D.4.3.2    Mounting a Clone

You must mount a clone in order to access it. An unmounted clone tracks changes to a fileset but cannot be read. Clones are mounted as read-only.

To mount a clone:

1. In the object tree, highlight the clone.

2. Choose Clone from the Configuration menu.

3. Choose Mount from the Clone menu.

4. In the Mount Clone dialog box, create a mount point if it does not exist and back up and modify the /etc/fstab file.

D.4.3.3    Unmounting a Clone

You cannot access an unmounted clone, but it still tracks fileset changes.

To unmount a clone:

1. In the object tree, highlight the clone.

2. Choose Clone from the Configuration menu.

3. Choose Unmount from the Clone menu.

4. In the Unmount Clone dialog box, unmount the clone and back up and modify the /etc/fstab file.

D.4.3.4    Removing a Clone

You must unmount a clone before you can remove it. You can do this as part of the removal process.

To remove a clone:

1. In the object tree, highlight the clone.

2. Choose Clone from the Configuration menu.

3. Choose Delete from the Clone menu.

4. In the Delete Clone dialog box, unmount the clone, delete it, and back up and modify the /etc/fstab file.

D.4.4    Operations on a Volume

File system management tasks for volumes are initiated from the main window by selecting Show or Volume from the Configuration menu after you have highlighted the volume on which you want to operate. (In order to view volumes, the View menu must be set to Domains and volumes or Domains, filesets, and volumes.)

D.4.4.1    Setting a Free Space Alert for a Volume

Set a free space alert to inform you when the free space threshold in the volume is reached or passed.

To set the free space alert:

1. In the object tree, highlight the volume.

2. Choose Volume from the Configuration menu.

3. Choose Set free space alert from the Volume menu.

4. In the Volume dialog box, set the free space alert.

When you set the alert, you can choose to automatically run a script when the threshold is crossed.

D.4.4.2    Adding a Volume

Adding a volume is the same as enlarging a domain (see Section D.4.1.3). See Section 1.5 for detailed information about volumes.

D.4.4.3    Removing a Volume

You can remove a volume from a domain at any time without interrupting the logical structure of the filesets in the domain (see Section 1.6.7). The data that was stored on that volume is moved to other volumes in the domain. In order to complete successfully, there must be room on the remaining volumes.

Before you can remove a volume from a domain, all filesets in that domain must be mounted. You cannot remove a volume while you are balancing or defragmenting a domain associated with that volume.

To remove a volume:

1. In the object tree, highlight the volume.

2. Choose Volume from the Configuration menu.

3. Choose Remove from the Volume menu.

4. In the Remove Volume dialog box, confirm the removal.

D.4.5    Maintaining AdvFS

File system maintenance tasks are initiated from the main window through the Maintenance menu. The maintenance tools improve read/write performance by altering the way files are mapped on the disk. They can be run while the system is on line, and their operation is transparent to system users and to applications. The maintenance tasks can be stopped without harm to the domain. The activity that has already taken place remains.

D.4.5.1    Balancing a Multivolume Domain

You can use the GUI to initiate the balance process to evenly distribute files among volumes (see Section 4.10). You cannot balance a domain while you are defragmenting, adding or removing volumes, or removing filesets on the same domain. You can choose to abort the operation at any time. The domain you want to balance must have all filesets mounted. If you try to balance a domain that includes unmounted filesets, you get an error message.

To balance a domain:

1. In the object tree, highlight the domain.

2. Choose Balance from the Maintenance menu.

3. In the Balance dialog box, start the balance process.

D.4.5.2    Defragmenting a Domain

You can make files in a domain more contiguous by defragmenting the domain. Defragmenting also consolidates free space so files created later are also less fragmented (see Section 4.8). You cannot defragment a domain while you are balancing, adding or removing volumes, or removing filesets on the same domain. You can choose to abort the defragment operation at any time. The domain you want to defragment must have all filesets mounted. If you try to defragment a domain that includes unmounted filesets, you get an error message.

To defragment a domain:

1. In the object tree, highlight the domain.

2. Choose Defragment from the Maintenance menu.

3. In the Defragment dialog box, start the defragment process and specify how long it is to operate.

D.5    GUI Operation

Table D-3 presents some GUI problems and solutions. Check dtadvfs(8) and advfsd(8) for additional information.

Table D-3:  GUI Troubleshooting