8.3. GUI Issues

8.3. GUI Issues
Prev	Chapter 8. Known Issues	Next

8.3.1. Unable to log in to Admin GUI after upgrade (Oracle Linux)

If you enabled Admin GUI access for additional UNIX users beyond the default admin account, access for those users is not preserved during an upgrade. The Sun Ray Software upgrade program does not preserve PAM configurations, and it reconfigures the default setting for admin during the upgrade.

Workaround: Modify the PAM configuration as follows based on the operating system running on the Sun Ray server:

For Oracle Linux, modify the /etc/pam.d/utadmingui file by replacing the current utadmingui PAM stack with the following auth include system-auth entry:
```
#%PAM-1.0
# BEGIN: added to utadmingui by SunRay Server Software -- utadmingui
auth include system-auth
# END: added to utadmingui by SunRay Server Software -- utadmingui 
```

For Oracle Solaris, modify the /etc/pam.conf file by replacing the current utadmingui PAM stack with the following entries:

# BEGIN: added to utadmingui by SunRay Server Software -- utadmingui
utadmingui auth requisite pam_authtok_get.so.1
utadmingui auth required pam_dhkeys.so.1
utadmingui auth required pam_unix_cred.so.1
utadmingui auth required pam_unix_auth.so.1

Reference: CR 14340529

8.3.2. Admin GUI Upgrade

The Admin GUI requires a Web container that supports the Java Servlet and Java Server Pages (JSP) standards; earlier versions did not. Due to this change, Apache Tomcat 5.5 (or higher) has to be installed on the system, and the utconfig script has therefore been extended to ask for the location of an existing Tomcat instance.

If you perform an upgrade from a previous Sun Ray Software version (using a preserve file, for example), you must run utconfig -w after you have completed the upgrade. The utconfig -w command will prompt you for the Admin GUI settings, including the location of the Tomcat installation, after which the Admin GUI will be started automatically.

Reference: CR 12204639

8.3.3. Remote Access

Disabling remote access can result in an empty page.

The utconfig -w command allows you to enable or disable remote access to the Admin GUI. If remote access is disabled (the default), you must access the Admin GUI via http://localhost:1660 or http://127.0.0.1:1660.

Accessing the Admini GUI via http://servername:1660 will not work in this case and will result in an empty browser page. If you want to access the Admin GUI via http://servername:1660, you must enable remote access.

Reference: CR 12188689

8.3.4. Self-Registration GUI

If the wrong username or password is entered, the self-registration GUI does not allow text to be entered.

Workaround: Press the Exit button to relaunch the self-registration GUI.

Occasionally, use of the self-registration GUI can result in a Java core dump, although registration continues to work as expected, and no other adverse side effects are observed. However, if coreadm is configured to name core dumps uniquely, disk space usage should be monitored.

Reference: CRs 12195258, 12196361

8.3.5. Multiple Authentication (Solaris)

Sometimes multiple authentications are required when the session is disconnected using a hot key sequence (the default is Shift-Pause).

Reference: CR 12249130

Prev	Up	Next
8.2. General Issues	Home	8.4. Login Issues