test

Solaris 9 8/03 Release Notes

System Administration Bugs

x86: Unable to Establish Sun4U Diskless Client (4878696)

If you try to add the Sun4UTM diskless service on an x86 server, the following error is displayed:


Jun  12 17:02:48 s12-9 WBEM_Logging_Service[1810]: Failed to create clone area 
/export/root/clone/Solaris_9/sun4u.
Failed to create clone area /export/root/clone/Solaris_9/sun4u.


	The wbem_log had the following error:


strings  /var/sadm/wbem/log/wbem_log | grep SUNWidecr
 Solaris_OsService@#@0@#@0@#@root@#@s12-9@#@s12-9@#@1054856467079@#@System 
command return value.@#@System command, /usr/sbin/pkgadd -S -n -R 
/export/root/clone/Solaris_9/sun4u -a /tmp/admin.Qwayvg -d 
/export/root/templates/Solaris_9/SUNWidecr_4.1, REV=2001.03.02.13.55_sparc.sun4u
all, returned value of: 
/export/root/clone/Solaris_9/sun4u/var/sadm/pkg/SUNWidecr/install/postinstall:
test: argument expected
Installation of SUNWidecr failed.
Note –

It is possible to add a Sun4U diskless client to a SPARC server.

Workaround: None.

/etc/named.conf File Causes Solaris Management Console Operations on User and Group Accounts to Fail (4777931)

If you use Solaris Management Console to perform operations on a User or Group account on a system that serves as a Domain Name Service (DNS) server, and the /etc/named.conf file exists on that system, errors occur.

The following errors occur when you perform these operations from the GUI or when you use smuser and smgroup, which are command-line interfaces for the console.

The console launches a new dialog box or the smuser command exits with the following error messages when operated on a User:


"The attempt to view Users or Roles has failed due to an unexpected
error.
        This was caused by the following error: CIM_ERR_FAILED."

The console launches a new dialog box or the smgroup command exits with the following error message when operated on a Group:


"Attempted Read of Group IDs failed with unexpected CIM error:
        CIM_ERR_FAILED."operations from the GUI or command-line interface.

Workaround: Choose from one of the following workarounds:

For more information, see the smuser(1M) and the smgroup(1M) man pages.

x86: Pressing the F4 Key During BIOS Bootup Fails to Boot the Service Partition (4782757)

You are booting a Sun LX50 which has a Service partition and the Solaris 9 8/03 (x86 Platform Edition) operating environment is installed. You are given the option of pressing the F4 function key to boot the Service partition. However, pressing F4 causes the screen to go blank and the system 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 and press the Return key. The system boots the Service partition.

UltraSPARC II CP Event Message in Solaris 9 8/03 Operating Environment Not Always Produced (4732403)

In the Solaris 9 8/03 operating environment, on UltraSPARC II based systems, the CP Event message that accompanies some Uncorrectable Memory Error messages is not always produced. These include the following systems:

The result is that some information needed to identify a failing CPU might not always be present.

Workaround: For the latest information regarding this issue, check the SunSolveSM Web site at http://sunsolve.sun.com.

Solaris WBEM Services 2.5 Daemon Cannot Locate com.sun Application Programming Interface Providers (4619576)

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.

Some com.sun Application Programming Interface Method Invocations Fail Under XML/HTTP Transport Protocol (4497393, 4497399, 4497406, 4497411)

If you choose to use the com.sun application programming interface rather than the javax application programming interface to develop your WBEM software, only 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:

Method Invocation 

Error Message 

CIMClient.close()

NullPointerException

CIMClient.execQuery()

CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED

CIMClient.getInstance()

CIM_ERR_FAILED

CIMClient.invokeMethod()

XMLERROR: ClassCastException

Cannot Modify File-System Mount Properties With Solaris Management Console Mounts and Shares Tool (4466829)

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:

CIM_ERR_LOW_ON_MEMORY Error Occurs When Trying to Add Data With WBEM (4312409)

The following error message is displayed when memory is low:


CIM_ERR_LOW_ON_MEMORY

You cannot add more entries when the Common Information Model (CIM) Object Manager is low on memory. You must reset the CIM Object Manager Repository.

Workaround: To reset the CIM Object Manager Repository, follow these steps:

  1. Become superuser.

  2. Stop the CIM Object Manager.


    # /etc/init.d/init.wbem stop

  3. Remove the JavaSpacesTM log directory. 


    # /bin/rm -rf /var/sadm/wbem/log

  4. Restart the CIM Object Manager. 


    # /etc/init.d/init.wbem start
    Note –

    When you reset the CIM Object Manager Repository, you lose any proprietary definitions in your data store. You must recompile the MOF files that contain those definitions by using the mofcomp command. See the following example:


    # /usr/sadm/bin/mofcomp -u root -p root-password your-mof-file