test

Solaris Container Manager 3.6 Release Notes

Chapter 2 Runtime Issues

This chapter describes runtime issues and bugs in the Solaris Container Manager 3.6 (Container Manager) software.

Container Manager Issues

These runtime issues might occur in the Solaris Container Manager 3.6 software.

CLI Installation of Solaris Container Manager 3.6 Is Not Translated

If you use the command line interface (CLI) version of the Solaris Container Manager 3.6 installation, it is only available in English. This version is not translated. The English language aspect does not affect the installation process or functionality.

Workaround: To perform the installation in your locale, use the GUI installation (es-guiinst) and setup (es-guisetup).

Utilization Graph Image Titles and Headings Appear in English

If you choose a locale other than English, the title and headings of the Utilization Graph image appear in English. These values are not localized.

SPARC: Extended Accounting Feature Is Disabled in Solaris 8 Release

The Extended Accounting feature is disabled in Container Manager on systems that run the Solaris 8 OS. As a result, the Extended Accounting Data (Exacct) column of the CSV file for a container on a Solaris 8 system will be null.

Some Projects in the /etc/project Database Might Not Be Discovered by Container Manager

If a project in an agent host's /etc/project database has the same project ID as a project in the Sun Management Center database but has a different project name, then the project will not be discovered by Container Manager. A unique project ID across all hosts in the same server context is a Container Manager requirement.

You should not use the projadd command to create projects. Use only Container Manager to manage projects.

Workaround: Delete the non-default project that was created by the projadd command from the agent host's /etc/project database and create the container by using the New Container wizard in Container Manager.

Security Privilege Error Messages Are Incomplete

Error messages displayed during failure of creation, modification, or deletion of Zone, Pool, or Project are incomplete and does not provide enough details. Following are the error messages you might encounter:

Workaround: If you encounter any of the above errors, refer to the points mentioned below. But first ensure that the user is a valid SunMC user and has the necessary administration privileges (part of esadm, esdomadm groups).

Ensure that the user is associated with the necessary profiles by running the following command:

$ profiles <username>

Following are the necessary profile:

If you find the necessary profiles missing, run the following command (as the superuser) and modify the profiles associated with a user:

# usermod -P "<comma separated list of necessary profiles>" <username>

If any profile does not exist on the system, please add the missing entries in the format mentioned below to the prof_attr file in the /etc/security directory.

Pool Management:::Resource pool management profile:help=RtPoolMgmt.html

Project Management:::Manage Solaris projects:auths=solaris.project.read,solaris.project.write;help=RtProjManagement.html

Run the following command to find if the user is a part of the local access user list for the SCM module.

<BASEDIR>/SUNWsymon/sbin/es-config -M scm-container -s

If user is not part of the access list, run the following command:

<BASEDIR>/SUNWsymon/sbin/es-config -M scm-container -l <user_name>

Container Manager Bugs

These runtime bugs might occur in Solaris Container Manager 3.6 software.

Agent Performance Becomes Degraded or Unresponsive (6247892)

An agent has crashed leaving scm-container* files in the /var/opt/SUNWsymon/cfg/ directory. When the agent restarts, it might not perform in an optimal manner. This condition might identify itself by the following error message:

Insufficient security privilege to complete the operation.

You can determine the state of the processes on the agent by typing the following command:

% ps -eaf | grep esd

Workaround: To improve performance, type the following commands:

  1. Become superuser.

    % su -

  2. Stop the agent.

    # /opt/SUNWsymon/sbin es-stop -a

  3. Delete the state files.

    # rm /var/opt/SUNWsymon/cfg/scm-container*

  4. Restart the agent.

    #/opt/SUNWsymon/sbin/es-start -a

Java Web Console Does Not Restart After Reboot (6252233)

Following a server reboot, the Java Web Console does not start automatically.

To start the Java Web Console, type the following commands:

  1. Become superuser.

    % su -

    Type root password.

  2. Restart the Java Web Console.

    # /usr/sbin/smcwebserver restart

  3. Ensure that Java Web Console restarts in the future.

    # /usr/sbin/smcwebserver enable

Workaround: None.

Zone Creation Fails When Invalid Locale Is Selected (6259233)

If an invalid locale is selected from the Locale drop-down menu in the New Zone wizard, zone creation fails. The Locale drop-down menu might contain invalid locale values.

To determine valid locales, go to “Supported Locales” in International Language Environments Guide.

Workaround: Choose a valid locale from the Locale drop-down menu in the New Zone wizard. If you are unsure of a locale value, select C for the English locale.

Tool Tip Displayed Instead of Alarm Badge (6219617)

If an alarm condition exists, the tool tip of the alarm badge might appear instead of the alarm badge itself.

If you navigate to another pane, then return to the alarmed object's icon, the badge on the icon is correctly displayed.

Workaround: None.

Exception Might Occur When Clicking the Browser Back Button (6241424)

When you click the browser back button, Container Manager might throw an exception. The browser back button is not supported in this release.

To recover from this exception, go to https://server_name:6789/containers and navigate to the appropriate page.

Workaround: None.

Some Processes Owned by User nobody Are Not Moved to a Container (5011290)

On the Solaris 9 Operating System, some processes, for example, the JavaTM application run by user nobody, are not moved to a container because of a bug in the newtask command.

Workaround: Start the applications that are run by user nobody in the appropriate container by using the newtask command.


# /usr/bin/newtask -p projectname command

projectname is the project in which the application is to be started and command is the command to start the application.

For more information, see the newtask(1) man page.

Using nscd as a Match Expression Causes Host to Hang (4975191)

If you use one of the following match expressions when creating a container definition and subsequently activate it, the agent host hangs:

Workaround: Start the nscd process in the appropriate project by using the newtask command:


# /usr/bin/newtask -p projectname command

projectname is the project in which the application is to be started and command is the command to start the application.

For more information, see the newtask(1) man page.

Agent Hosts Missing After Reinstalling or Running Setup of Server Layer (4964051)

If you plan to reinstall the Solaris Container Manager 3.6 software on the server layer, be sure to save the data when uninstalling. Similarly, if you run setup again on the server layer, be sure to answer No when asked if you want to recreate the database. Otherwise, agent hosts previously discovered might be missing from the database if the data was not saved and you then reinstall or set up again on the server layer.

Workaround: If hosts are missing after you reinstall or rerun setup, restart the Sun Management Center agent on the hosts by doing the following procedure:

  1. Log in to agent system.

  2. Become superuser.

    % su -

  3. Stop the Sun Management Center agent by typing:


    # /opt/SUNWsymon/sbin/es-stop -a

  4. Start the Sun Management Center agent by typing:


    # /opt/SUNWsymon/sbin/es-start -a