System Administration Bugs

rcm_daemon Error Message (4386436)

When the system boots the following error message may be logged to the system log file located in /var/adm/messages:

open(/var/run/rcm_daemon_lock) - No such file or directory
  rcm_daemon exit: errno = 2

This occurs only if /var is a separate partition.

Workaround: Ignore the message. It does not harm the system.

Obsolete Files Still Present in Help System (4339515)

After selecting Help -> Information from the Front Panel, a list of obsolete files is returned. The correct file is S8FCSreleasenotes.

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

Workaround: To reset the CIM Object Manager Repository:

1. Become superuser.

2. Stop the CIM Object Manager.

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

3. Remove the JavaSpaces log directory.

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

4. Restart the CIM Object Manager.

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

   ---

   Note -

   You will lose any proprietary definitions in your datastore. You must recompile the MOF files that contain those definitions using the mofcomp command. For example:

   # /usr/sadm/bin/mofcomp -u root -p root_password your_mof_file

   ---

WBEM Common Information Model Object Manager Crashes When Solaris_FileSystem Instances Are Requested (4301275)

If you enumerate instances of the Solaris_FileSystem class by using CIM WorkShop or the WBEM APIs, then the CIMOM no longer runs and the following error message is displayed:

Attempted to complete RMI action
enumInstances and received exception 
java.rmi.UnmarshalException: Error 
unmarshaling return header; nested 
exception is:
java.io.EOFException

Workaround: In superuser mode, restart the CIMOM by typing the following command:

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