Chapter 2 Late-Breaking Installation and Runtime Bugs
This chapter covers issues related to the installation of the Solaris 8 Admin Pack software or that may arise while you are using Solaris 8 Admin Pack software.
Solaris Management Console Bugs
The known issues with Solaris Management Console (SMC) are listed in the following sections.
SMC Servlet May Crash Due to Insufficient Swap [4166571]
If the machine on which the SMC server is running does not have sufficient swap space and the Java garbage collector is not given enough time to release allocated memory, the servlet may run out of memory and cause a segmentation fault.
As a result, all client machines disappear and the initial server remains with a red slash through it, indicating that it is not available.
Workaround: To resume, become superuser and restart the SMC servlet by executing these commands:
/etc/init.d/ehttpd stop
/etc/init.d/ehttpd start
This problem can be avoided by spacing authentication requests far enough apart to allow the Java garbage collector to do its work, adding sufficient swap space, or periodically restarting the servlet or rebooting the machine.
SMC Clients on the Same Server Do Not Update Each Other When Registry Changes [4168704]
If multiple clients are accessing the same SMC server, and one of the clients updates the SMC registry on the server, the others will not be notified of the change. SMC displays only the old registry information in the Applications View and SMC Server View. This display causes Already exists errors to be reported to the older clients when they attempt to manually add the same registry changes.
Workaround: Log out and log in again to refresh the SMC client display.
No Default SMC pam Entry in /etc/pam.conf file [4168726]
SMC uses smc_console as its pam service name when SMC calls pam_start(). The default /etc/pam.conf file does not have an entry for the smcconsole service. This causes pam to correctly use the pam module other in pam.conf, which refers to the pam_unix module.
SMC Applications Can Be Modified by Any User [4169897]
Applications that are registered with Solaris Management Console to be launched with user, root, or group 14 permission can have their SMC registry information modified or removed by any user.
Workaround: None
Launched Applications May Not Display When Running SMC Client Via Remote xhost [4171154]
When running SMC client on a remote xhost, launched applications may not be displayed.
Workaround: Add each remote server to your X authorization list, for example xhost + .
Solaris Adminsuite 3.0.1 Issues
The known issues with Adminsuite are listed in the following section.
The User Properties List of Rights Is Not Translated
The Rights tab of the User Properties dialog box lists all possible user rights for the domain you are currently managing. This list is in English because the rights shown are obtained from tables that cannot be translated in this version of the product. To learn more about the rights, refer to the context-sensitive help provided when clicking on each Right shown in the Rights tab.
No Multi-Byte Characters Are Accepted in AdminSuite Dialog Boxes
You cannot enter multi-byte characters in any of the AdminSuite dialog boxes, and specifically in the description fields.
Workaround: Click anywhere in the HTML renderer pane in the left side of the dialog box. Then press the Ctrl and Space keys (or whatever control sequence is configured). Note that the pre-edit status window opens; by default, it is at the bottom of the dialog box. Toggle the control sequence until it is in the input mode that you want, and then click on the field in which you want to enter multi-byte characters. If the pre-edit status window disappears, try the workaround again, starting with clicking anywhere in the HTML renderer pane.
Out-of-Memory Error -- Troubleshooting Solution Unsuccessful
If you receive java.lang.OutOfMemory errors, first follow the directions in the Out-of-Memory Error section of AdminSuite's online Troubleshooting guide. That should solve the problem, but if it does not then you might have insufficient "descriptors" (open files). Insufficient descriptors is more likely to be the cause of the out-of-memory errors if you have one server with multiple clients.
To view the number of descriptors, type "limit" in a c shell window:
% limit
cputime unlimited filesize unlimited datasize 2097148 kbytes stacksize 8192 kbytes coredumpsize unlimited descriptors 64 memorysuze unlimited
In this case, the default is set to 64, which may be fewer than you need. Try increasing the number of descriptors to 1024 by issuing the limit descriptors command.
% limit descriptors 1024
AdminSuite Cannot Handle NFS Mounts with /dev= Option [4279439]
Mounts on file systems that contain the /dev= option in the /etc/mnttab file are displayed incorrectly by AdminSuite. When a user selects on a Mounts node or attempts any Mount administration operation, the following error is displayed:
Invalid or unsupported mount option, dev, for mount file_sys mounted at mount point mount_point. This mount cannot be managed by this application.
All such mounts are displayed with a Mount Status of At Boot.
AdminSuite Cannot Manage High Sierra File System [4284522]
AdminSuite cannot manage the High Sierra File System (HSFS). An attempt to view a mount of HSFS CD-ROM will generate an error similar to the following:
Invalid or unsupported mount option maplcase for mount /vol/dev/dsk/c0t6d0/network_client_3_2. This mount cannot be managed by this application.
Sun Enterprise Authentication Mechanism 1.0.1 Issues
The known issues with SEAM 1.0 are listed in the following section.
Sun Enterprise Authentication Mechanism Does Not Accept Extended Characters in Passwords [4250805]
Password fields in Sun Enterprise Authentication Mechanism (SEAM) do not accept Extended (8-bit) characters. SEAM documentation does not document this restriction.
Must Upgrade SEAM on Solaris 8
When upgrading to the Solaris 8 operating environment, you must also upgrade SEAM to the 1.0.1 version contained in the Solaris 8 Admin Pack. Otherwise, you will not be able to use Kerberos V5 security with NFS. This could cause NFS sharing to fail on the server, which would prevent clients from gaining access to filesystems shared with strong security. A machine sharing or using Kerberos V5 security for NFS should not upgrade to Solaris 8 without a simultaneous upgrade to the Solaris 8 Admin Pack.
Kerberos V5 Not Working with NFS [4278857]
After installation, several lines in the /etc/nfssec.conf file are left commented, thus preventing use of Kerberos V5 with NFS.
Workaround: Remove comment indicator (#) at the beginning of the following lines in the /etc/nfssec.conf file:
#krb5 390003 kerberos_v5 default - #RPCSEC_GSS
#krb5i 390004 kerberos_v5 default integrity #RPCSEC_GSS
/etc/pam.conf File Installed Incorrectly [4278862]
After installation, several lines in the /etc/pam.conf file are left commented, which prevents Kerberos security from being applied to the applications indicated in the commented lines.
Workaround: Remove comment indicator (#) at the beginning of all lines in /etc/pam.conf that begin with SEAM.
- © 2010, Oracle Corporation and/or its affiliates