This section describes system administration bugs in Solaris 10 OS.
The smosservice or smdiskless command might not work because of a dependency on JDK 1.5 release.
The following error message is displayed:
/usr/sadm/bin/smosservice list -u <user> -p <password> Exception in thread "main" java.lang.UnsupportedClassVersionError: com/sun/management/viperimpl/console/BaseConsoleOptionsManager (Unsupported major.minor version 49.0) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:539) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123) at java.net.URLClassLoader.defineClass(URLClassLoader.java:251) at java.net.URLClassLoader.access$100(URLClassLoader.java:55) at java.net.URLClassLoader$1.run(URLClassLoader.java:194) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) at java.lang.ClassLoader.loadClass(ClassLoader.java:289) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
Set the JAVA_HOME variable to point to a JDK 1.5 installation.
A system that runs the Sun Patch Manager Tool 2.0 can manage remote systems that run Patch Manager Tool, including Sun Patch Manager Tool 1.0.
However, a system with an earlier version of Patch Manager Tool cannot manage remote systems that run Patch Manager Tool 2.0. Earlier versions include the following:
Sun Patch Manager Base Software 1.x
Sun Patch Manager Tool 1.0
Note - Common Information Model/Web Based Enterprise Management (CIM/WBEM) support for Patch Manager Tool does not exist in the Solaris 8 OS. Consequently, remote management with Patch Manager does not apply to Solaris 8 systems.
Sun Remote Services (SRS) Net Connect is supported only in the global zone. Error messages are displayed if you perform one of the following actions:
You install SRS Net Connect in a local zone.
SRS Net Connect is installed in the global zone at the time a local zone is created.
The error messages are as follows:
*** package SUNWcstu failed to install - interactive administration required: Interactive request script supplied by package pkgadd: ERROR: request script did not complete successfully Installation of SUNWcstu was suspended (interaction required). No changes were made to the system. *** package SUNWfrunc failed to install - interactive administration required: Interactive request script supplied by package pkgadd: ERROR: request script did not complete successfully Installation of SUNWfrunc was suspended (interaction required). No changes were made to the system.
Workaround: Ignore the error messages.
While installing a non-global zone by using the zoneadm command, error or warning messages might be displayed during package installation. The messages are similar to the following example:
Preparing to install zone zone1. Creating list of files to copy from the global zone. Copying 2348 files to the zone. Initializing zone product registry. Determining zone package initialization order. Preparing to initialize 790 packages on the zone. Initialized 790 packages on zone. Zone zone1 is initialized. Installation of the following packages generated errors: SUNWjhrt SUNWmcc SUNWjhdev SUNWnsb SUNWmcon SUNWmpatchmgr Installation of the following packages generated warnings: SUNWj3rt SUNWmc SUNWwbmc SUNWmga SUNWdclnt SUNWlvma SUNWlvmg SUNWrmui SUNWdoc SUNWpl5m SUNWpmgr
Problems about package installation are also recorded in /export/zone1/root/var/sadm/system/logs/install_log which contains a log of the zone installation.
Note - The non-global zone can still be used even though these messages have been reported. Issues with package installation existed in earlier Solaris Express and Solaris 10 Beta releases. However, no notification about these problems was being generated. Beginning with this Solaris release, these errors are now properly reported and logged.
The function to add regions in the localeadm command no longer works if you create a new configuration file. The Language CD is not detected when you add the following regions:
The following error message is displayed:
No langcd image has been found in /cdrom/sol_10_1005_x86_4/Solaris_10/Product No langcd image has been found in /cdrom/sol_10_1005_x86_4 /cdrom/sol_10_1005_x86_4 /cdrom/sol_10_1005_x86_4 /cdro m/sol_10_1005_x86_4 /cdrom/sol_10_1005_x86_4 Please enter the path to this image/disk, or enter 'q' to quit:
Workaround: When you are prompted to create a new configuration file, select No. Instead, use the configuration file that was installed in the system.
During dynamic reconfiguration (DR), error messages might be displayed. The messages are displayed if you perform DR while input and output operations are active on devices that are in the DR path. After the messages are displayed, the input and output operations are retried and eventually succeed. The following is a sample that is displayed:
Jul 28 12:23:19 qame10-a scsi: [ID 107833 kern.warning] WARNING: /ssm@0,0/pci@19,700000/SUNW,qlc@2,1/fp@0,0/ssd@w2100000c5056fa13,0 (ssd6): Jul 28 12:23:19 qame10-a transport rejected fatal error Jul 28 12:22:08 qame10-a scsi: [ID 107833 kern.warning] WARNING: /ssm@0,0/pci@19,700000/SUNW,qlc@2,1/fp@0,0/ssd@w2100000c5056f9a7,0 (ssd36): Jul 28 12:22:08 qame10-a SCSI transport failed: reason 'timeout': retrying command
Workaround: None. Ignore the error messages.
The command luxadm -e forcelip to reinitialize a link on one server causes the logical unit number (LUN) to reset on all servers in the Storage Area Network (SAN). The following sample error message is displayed on the console of one or more servers in a zone within the same SAN environment.
Aug 16 13:34:07 ontario-a last message repeated 5 times Aug 16 13:34:07 ontario-a scsi_vhci: [ID 734749 kern.warning] WARNING: vhci_scsi_reset 0x0
Workaround: None. Ignore the error messages.
The patchadd and patchrm commands work improperly in non-global zones with inherited file systems. Consequently, in those zones, the pkgchk command might generate error messages about packages under the following circumstances:
In the global zone, you apply patches for the Solaris 10 zone system by using the patchadd command.
You use the patchrm command to remove patches that you just recently applied.
In a non-global zone with inherited file systems, you check with the pkgchk command for information about a package in any of the removed patches.
The following sample message is displayed when the pkgchk command is used on SUNWcsu under the circumstances previously listed.
# pkgchk SUNWcsu ERROR: /usr/lib/inet/certdb modtime <04/26/05 10:55:26 PM> expected <01/23/05 01:48:24 AM> actual file size <36012> expected <42152> actual file cksum <37098> expected <19747> actual ERROR: /usr/lib/inet/certlocal modtime <04/26/05 10:55:26 PM> expected <01/23/05 01:48:24 AM> actual file size <44348> expected <84636> actual
Workaround: None. The errors are harmless. Ignore the error messages.
Systems with the Solaris 10 3/05 HW1 release might cause problems with IPsec. This problem might occur on a freshly installed system or a system that imports a large number of new Service Management Facility (SMF) manifests during the boot. After these booting conditions, IPsec, which is part of svc:/network/initial:default, might be initialized prior to the encryption framework, which is part of svc:/system/cryptosvc:default. Because authentication or encryption algorithms are not available, creation of IPsec security associations might fail with an error message such as the following:
PF_KEY error: type=ADD, errno=22: Invalid argument, diagnostic code=40: Unsupported authentication algorithm
For example, this error might occur when using DR on a Sun Fire E25K system, which involves IPsec services.
Workaround: Before performing operations that use IPsec services, perform the following steps after a boot that imports a large number of new SMF manifests:
Issue this command after booting:
If /etc/inet/secret/ipseckeys exists on the system, also issue this command:
ipseckey -f /etc/inet/secret/ipseckeys
Now you can perform actions that create IPsec security associations, such as using DR on a Sun Fire E25K system.
This procedure needs to be repeated only when a large number of new SMF manifests are imported during the boot.
If you attempt to launch the Solaris Product Registry administration utility in a zone, the attempt fails. During the zone installation, productregistry, the Solaris Product Registry database, is not duplicated in the zone. Consequently, the utility cannot run in a zone.
Workaround: As superuser, copy the productregistry database to the zone.
# cp /var/sadm/install/productregistry zone_path/var/sadm/install/
In the previous command, zone_path is the path to the root directory of the zone that you created.
If you use the smdiskless command to delete a diskless client, the command fails. The diskless client is not removed from the system databases. The following error message is displayed:
Failing with error EXM_BMS.
Workaround: Unshare the /export partition before adding the client.
Installation of Net Connect 3.1.1 fails if you select the product at the beginning of a full Solaris 10 installation. This failure occurs when you are installing by using the Solaris 10 Operating System DVD. At the completion of the OS installation, the following error message is recorded in the Net Connect install log in /var/sadm/install/logs/:
Installation of SUNWSRSPX failed. Error: pkgadd failed for SUNWsrspx Install complete. Package: SUNWsrspx
Workaround: After the OS installation is completed, follow these steps:
Insert the Solaris 10 Operating System DVD or the Solaris 10 Software - CD 4.
Change to the directory of the Net Connect product.
Run the Net Connect installer.
Note - To download the latest version of the Sun Net Connect software and release notes, go to the Sun Net Connect portal at https://srsnetconnect.sun.com.
A boot failure that involves the Solaris Flash archive might occur under the following circumstances:
You create a Solaris Flash archive on a system that is using a libc C library with certain hardware-support capabilities.
You install the archive on a clone system that has different hardware-support capabilities.
When you attempt to boot the clone system, the following error message is displayed:
WARNING: init exited with fatal signal 9; restarting.
Workaround: Follow these steps.
Before you create the archive, unmount the /lib/libc.so.1 library on the master system.
# umount /lib/libc.so.1
This command enables the master system to use the basic version of the libc C library.
Create the Solaris Flash archive on the master system.
For more information about how to create Solaris Flash archives, see the Solaris 10 6/06 Installation Guide: Solaris Flash Archives (Creation and Installation).
Mount the /lib/libc.so.1 library on the master system.
# mount -O -F lofs /lib/libc.so.1 /usr/lib/libc/libc_hwcap2.so.1
Install the Solaris Flash archive on the clone system.
For more information about how to install Solaris Flash archives, see the Solaris 10 6/06 Installation Guide: Solaris Flash Archives (Creation and Installation).
If you use the smosservice delete command to remove a diskless client service, the command does not successfully remove all the service directories.
Workaround: Follow these steps.
Make sure that no clients exist that use the service.
# unshare /export/exec/Solaris_10_sparc.all # rm -rf /export/exec/Solaris_10_sparc.all # rm -rf /export/exec/.copyofSolaris_10_sparc.all # rm -rf /export/.copyofSolaris_10 # rm -rf /export/Solaris_10 # rm -rf /export/share # rm -rf /export/root/templates/Solaris_10 # rm -rf /export/root/clone/Solaris_10 # rm -rf /tftpboot/inetboot.sun4u.Solaris_10
Remove the following entry from the /etc/bootparams file.
Note - Remove this entry only if this file server does not provide functions or resources for any other services.
Remove the following entry from the /etc/dfs/dfstab file.
share -F nfs -o ro /export/exec/Solaris_8_sparc.all/usr
Modify the /var/sadm/system/admin/services/Solaris_10 file.
If the file server is not Solaris_10, delete the file.
If the file server is Solaris_10, remove all entries after the first three lines. The deleted lines indicate the service USR_PATH and SPOOLED ROOT packages in /export/root/templates/Solaris_10 and the supported platforms.
If you use the patchadd command to install patches across the NFS from another system, the command fails. The following example shows a patchadd operation that failed and the error message that is displayed:
Validating patches... Loading patches installed on the system... [...] Loading patches requested to install. [...] Checking patches that you specified for installation. [...] Approved patches will be installed in this order: [...] Checking local zones... [...] Summary for zones: [...] Patches that passed the dependency check: [...] Patching global zone Adding patches... Checking installed patches... Verifying sufficient filesystem capacity (dry run method)... Installing patch packages... Patch Patch_ID has been successfully installed. See /var/sadm/patch/Patch_ID/log for details Patch packages installed: SUNWroute [...] Adding patches... The patch directory /dev/.SUNW_patches_0111105334-1230284-00004de14dcb29c7 cannot be found on this system. [...] Patchadd is terminating.
Workaround: Manually copy all of the patches to be installed from the NFS server to the local system first. Then use the patchadd command to install the patches from the directory on the local system where the patches were copied.
If you use the lucreate command to create RAID-1 volumes (mirrors) that do not have device entries in the /dev/md directory, the command fails. You cannot mirror file systems with the lucreate command unless you first create the mirrors with Solaris Volume Manager software.
Workaround: Create the mirrored file systems with Solaris Volume Manager software, then create the new boot environment with the lucreate command.
For more information about the lucreate command, see the lucreate(1M) or Solaris 10 6/06 Installation Guide: Solaris Live Upgrade and Upgrade Planning.
For more information about how to create mirrored file systems with Solaris Volume Manager software, see Solaris Volume Manager Administration Guide.
When a fabric zone in a storage area network (SAN) is created dynamically, that zone's devices might be unavailable at the host side. If you use the command luxadm -e dump_map to display data for such devices or host bus adapters, an error message is displayed. See the following example:
# luxadm -e dump_map /dev/cfg/c5 Pos Port_ID Hard_Addr Port WWN Node WWN Type ERROR: Unable to retrieve target port details (QLogic Corp-2312-3)ERROR
Listing the status of all the attachment points yields information similar to the following example. In this example, the fabric devices include a tape drive, but no device is indicated in c5.
# cfgadm -al Ap_Id Type Receptacle Occupant Condition : : c5 fc-fabric connected unconfigured unknown usb0/1 unknown empty unconfigured ok : :
Workaround: After configuring the fabric-connected devices, reinitialize the link to the devices by using the luxadm -e forcelip command. For the previous example, you would type the following:
# luxadm -e forcelip /dev/cfg/c5
If you attempt to stop the system by pressing keyboard sequences such as Stop-A or L1-A, the system might panic. An error message similar to the following example is displayed:
panic[cpu2]/thread=2a100337d40: pcisch2 (pci@9,700000): consistent dma sync timeout
Workaround: Do not use keyboard sequences to force the system to enter OpenBoot PROM.
The ipfs command saves and restores information about the state of the Network Address Translation (NAT) and packet-filtering state tables. This utility prevents network connections from being disrupted if the system reboots. If you issue the command with the -W option, ipfs fails to save the kernel state tables. The following error message is displayed:
state:SIOCSTGET: Bad address
After modifying the contents of snmpd.conf, you can issue the command kill -HUP snmp Process ID. This command stops the snmp process. The command then sends a signal to the System Management Agent's master agent (snmpd) to reread snmpd.conf and implement the modifications that you introduced. The command might not always cause the master agent to reread the configuration file. Consequently, using the command might not always activate modifications in the configuration file.
Instead of using kill -HUP, restart the System Management Agent after adding modifications to snmpd.conf. Perform the following steps:
Type the following command:
# /etc/init.d/init.sma restart
You are booting a Sun LX50 which has a Service partition and Solaris 10 OS on x86 is installed. Pressing the F4 function key to boot the Service partition, when given the option, causes the screen to go blank. The system then fails to boot the Service partition.
Workaround: Do not press the F4 key when the BIOS Bootup Screen is displayed. After a time-out period, the Current Disk Partition Information screen is displayed. Select the number in the Part# column that corresponds to type=DIAGNOSTIC. Press the Return key. The system boots the Service partition.
The Solaris WBEM Services 2.5 daemon cannot locate providers that are written to the com.sun.wbem.provider interface or to the com.sun.wbem.provider20 interface. Even if you create a Solaris_ProviderPath instance for a provider that is written to these interfaces, the Solaris WBEM Services 2.5 daemon does not locate the provider.
Workaround: To enable the daemon to locate such a provider, stop and restart the Solaris WBEM Services 2.5 daemon.
# /etc/init.d/init.wbem stop # /etc/init.d/init.wbem start
Note - If you use the javax API to develop your provider, you do not need to stop and restart the Solaris WBEM Services 2.5 daemon. The Solaris WBEM Services 2.5 daemon dynamically recognizes javax providers.
If you choose to use the com.sun application programming interface rather than the javax application programming interface to develop your WBEM software, only Common Information Model (CIM) remote method invocation (RMI) is fully supported. Other protocols, such as XML/HTTP, are not guaranteed to work completely with the com.sun application programming interface.
The following table lists examples of invocations that execute successfully under RMI but fail under XML/HTTP:
The Solaris Management Console Mounts and Shares tool cannot modify mount options on system-critical file systems such as root (/), /usr, and /var.
Workaround: Choose one of the following workarounds:
Use the remount option with the mount command.
# mount -F file-system-type -o remount, additional-mount-options \ device-to-mount mount-point
Note - Mount property modifications that are made by using the -remount option with the mount command are not persistent. In addition, all mount options that are not specified in the additional-mount-options portion of the previous command inherit the default values that are specified by the system. See the man page mount_ufs(1M) for more information.
Edit the appropriate entry in the /etc/vfstab file to modify the file-system mount properties, then reboot the system.