test

N1 Grid Console - Container Manager 1.0 Release Notes

Chapter 1 Runtime Issues

This chapter describes runtime issues and bugs in the N1 Grid Console - Container Manager 1.0 (Container Manager) software.

Container Manager Issues

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 Operating System (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 Oracle® 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.

Container Manager Bugs

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

If Container Manager is installed on a Solaris 8 system and projects exist in the /etc/project database with project names that do not conform with the naming convention (user.username), these projects will be 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 will be identified as a user-based container. The container will function 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 Do Not Display Correctly (5020762)

Occasionally, utilization graphs do not display 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 due to 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 due to a bug in the newtask command.

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


# /usr/bin/newtask -p projectname command

where 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

where 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 N1 Grid Console - Container Manager 1.0 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 setup 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 into 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