test

Solaris Container Manager 1.1 Release Notes

Container Manager Bugs

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

Unselected Processes Move to New Project (6268412)

When you move processes by using the Move Processes feature, unselected processes might also be moved. Hence, do not use the Move button on the Processes tab.

Workaround: To ensure that processes are not inadvertently moved, perform the following steps:

  1. Become superuser.

  2. Move processes to the correct project by using the following command:

    % newtask -c <pid>

Performance Degrades When Alarms Are Present (6255145)

If an alarm condition exists, performance might be degraded. To remedy this situation, perform one of the following:

Incorrect Error Message When Agent Moved to Different Server Context (5034900)

If an object on an agent which is now in a different server context is accessed, the following error message is displayed:

There was an error while retrieving the Container data.

Choose one of the following actions:

Workaround: None.

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.

Cumulative Utilization Graphs Do Not Display for Particular Object and Time Interval Combinations (6256467)

If you select the Cumulative Utilization by Object option, graphs do not display for the following objects and time intervals:

Workaround: None.

Updated Resource Change Job Fails (6258383)

A Resource Change Job has been previously scheduled, executed, and completed normally. If you update the Resource Change Job, the job fails.

Workaround: Instead of updating the Resource Change Job, delete it and create a new job.

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.

Application Error Occurs When Starting Wizard After Clicking Breadcrumb (5038524)

If you use a breadcrumb to navigate to any pane and then start a wizard, an Application Error occurs.

Workaround: Do not start a wizard immediately after clicking a breadcrumb.

Action Buttons Are Not Being Activated After Change in Zone State (6247882)

You have selected a zone and clicked one of the action buttons at the top of the table. Hereafter, the action buttons might not be correctly activated relative to the zone state.

To ensure that the action buttons are properly activated, navigate to another pane and return to the Zones table.

Workaround: None.

Zones Table Is Not Immediately Updated When Zone Is Deleted (6247898)

If you delete a zone, the row in the Zones table is not immediately deleted. The Zone entry in the Zones table is not removed until Zone deletion has been completed. This process might take a few minutes.

To view an updated Zones table, perform one of the following steps:

Workaround: None.

Resource Pools With Associated Zones Can Be Deleted (6240756)

If you attempt to delete a resource pool that contains zones, the resource pool is deleted and the zones are moved to the pool_default resource pool.

Workaround: None.

Project Status Might Not Update in the Projects Table (6252494)

If the project status is changed, the Status field in the Projects table might not update with the correct status.

To display the correct status, navigate to another pane and return to the Projects table.

Note –

Do not use the browser Reload button to refresh the Projects table. This behavior is not supported.

Workaround: None.

Updated Resource Change Job Fails (6258383)

A Resource Change Job has been previously scheduled, executed, and completed normally. If you update the Resource Change Job, the job fails.

Workaround: Instead of updating the Resource Change Job, delete it and create a new job.

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.

Additional Attributes Might Not Be Displayed in Zone - Properties Pane (6247877)

If you navigate to the Zone - Properties pane, the Additional Attributes values might not be displayed.

If you encounter this situation, leave this pane and navigate back to the Zone by using the links in the left pane and click the Properties tab.

Workaround: None.

Resource Pool Creation Fails When the First Character of the Name Is Not Alphabetic (6253063)

If you attempt to create a resource pool with a name that starts with any character other than an alphabetic, creation fails.

If the host does not appear to be respond after a failure, you might need to restart the host:

  1. Become superuser on the host.

    % su -

  2. Stop and restart the host.

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

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

Valid characters are the following:

Workaround: Begin all resource pool names with an alphabetic character.

Project Status Might Not Update in the Status Column of the Projects Table (6252494)

If the project status is changed, the Status field in the Projects table might not update with the correct status.

To display the correct status, navigate to another pane and return to the Projects table. Using the Reload button is not supported.

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.

Existing Projects on Solaris 8 OS Might Be Discovered as Application-Based Container (5026619)

On a Solaris 8 system with Container Manager installed, projects might exist in the /etc/project file with project names that do not conform with the naming convention (user.username). These project are discovered as an application-type container. This assignment can be confirmed in the properties sheet for the container.

If an lnode of username and a project name of user.username exist for this project, the container is identified as a user-based container. The container then functions normally in Container Manager.

If no lnode is associated with this project, you can deactivate the project. The entry in the /etc/project database is deleted. If you subsequently attempt to activate the container, the following error message is displayed:


There was an error while activating the Container.
Container activation failed.

Workaround: To re-create the container definition through Container Manager, perform the following steps:

  1. Delete the container definition.

  2. Re-create the container definition through Container Manager.

Utilization Graphs Are Not Displayed Correctly (5020762)

Occasionally, utilization graphs are not displayed correctly. All data points relative to the x-axis appear as a single line on the y-axis.

Workaround: To reload the frame in which the utilization graph appears, perform one of the following workarounds:

Note –

Do not click the Reload or Refresh button in the browser's toolbar. You might return to the Hosts navigation window.

SPARC: Container Manager Agent Module Causes Memory Leak on Solaris 8 (4982743)

When the Container Manager module is loaded, the module refreshes the container table by reading the /etc/project database. On agent hosts that run the Solaris 8 OS, a memory leak occurs because of a bug in the APIs of the libproject library.

Workaround: To resolve the memory leak problem, perform one of the following workarounds:

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.

Help Is Not Context Sensitive (4970176)

Clicking the Help button displays the Help Table of Contents. Context-sensitive help is not currently available.

Workaround: Use one of the following options to access Help for a specific panel:

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 1.1 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 re-create 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