Sun N1 Service Provisioning System 5.1 Release Notes

Runtime Issues

This section describes known runtime issues.

Running an `execNative` Command in the Background Might Take More Than Ten Minutes to Start Execution on IBM AIX Platforms (6315401)

When executing an execNative step with the background option specified, the command might take more than ten minutes to start instead of starting immediately.

This issue occurs on IBM AIX systems that have the number of open file descriptors set to a value in excess of a million or unlimited. Unlimited equates to approximately two billion. You can determine the current soft limit on the maximum number of open file descriptors by executing the ulimit -n command.

Workaround: Set the value of the nofiles parameter to 2000 in the /etc/security/limits file for either the user that is running the agent process or all users. Following a reboot, this value persists and affects all users on the machine.

Note –

The value of the nofiles parameter must not exceed 100,000.

For more information about the /etc/security/limits file, perform the following steps:

Go to the IBM AIX Information Center at http://publib.boulder.ibm.com/infocenter/pseries/index.jsp.
Type limits file in the Search text field.
Click the GO button.
Click the limits File link in the search results.

Incorrect Permissions for the `/protect/jexec` File on SUSE Linux 9 (6313166)

After installing the Remote Agent on a system running SUSE Linux 9 which has the setuid bit set to yes, the permissions are incorrect for the /protect/jexec file.

The permissions are:

---x--x---  1 root   other 21864 2005-08-15 03:16 jexec

The permissions should be:

---s--x---  1 root   other 21864 2005-08-15 03:16 jexec

Workaround: Manually correct the file permissions after the installation completes by using the following command:

% chmod 4110 $BASEDIR/agent/bin/protect/jexec

$BASEDIR is the installation directory.

Component Cannot Be Deleted If Root Component Refers to Non-Root `autogen` Plan (6306809)

You might not be able to delete a component when different versions of the component have had direct-run component procedures run.

This situation arises if a particular direct-run component procedure was first run on a version other than 1.0 of the component and then the same direct-run component procedure was later run on version 1.0 of the component.

You will not be able to delete the 1.0 version of the component or the first direct-run component procedure that you ran. Neither direct delete of one version nor bulk delete of both versions will be possible.

Note –

As an alternative to delete, it is possible to hide the components in question to remove them from view.

Workaround: Avoid the problem by using one of the following methods:

Always run direct-run component procedures on the 1.0 version of the component first.
Do not run direct-run component procedures on the root component once the direct-run component procedure has been run on other versions.

Detail Preflight Might Fail on Solaris Systems (6313603)

When running a plan on a Solaris Remote Agent with the Detailed Preflight option selected, the plan fails during preflight and displays the following error messages:

The system was unable to create VirtualAgent for host xxx. (017009)
Unable to connect to agent at host xxx. (026000)
Unable to create an internal representation of host xxx. (017030)
Unexpected exception thrown on the server-side. (022046)
readdir_r() on "/" failed: "Unknown error [-1]". (025006)

Workaround: Do not select the Detailed Preflight option when running a plan.

Check In Current Does Not Report Errors for Components That Do Not Support Check In Current (5063014)

The Check In Current operation enables you to ensure that the version of a component in the Master Server repository is the most recent. The Master Server checks its version of the component against the version on the source host. The check is based on metadata regarding the location of the component that was gathered at the time of previous check in.

You cannot perform the Check In Current operation on all component types. Typically, component types that can be browsed using the browser interface are eligible for the Check In Current operation.

When performing a bulk Check In Current operation, if you select a component type that does not support the Check In Current operation, the operation completes with no errors. The results displayed in the Progress dialog box for component types that are not supported might be empty or might represent historical data.

Workaround: No workaround is available.

System Might Hang When Using SSL on Red Hat Linux Advanced Server 3.0 (5084676)

If you are running the Sun N1 Service Provisioning System on Red Hat Linux Advanced Server 3.0, the system might hang when using Secure Socket Layer (SSL) connections.

SSL uses SecureRandom which uses /dev/random to generate random numbers. Red Hat Linux Advanced Server 3.0 includes a bug that causes /dev/random not to collect entropy. Since /dev/random does not generate numbers unless sufficient entropy is collected, applications hang when attempting to read random data from /dev/random.

Workaround: Choose one of the following workarounds:

Red Hat plans to include a patch in Update 3 to correct the problem. Apply the patch from Red Hat to your system when the patch is available. For more information about the Red Hat patch, see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=117218.
Do not use SSL as a connection type. Choose TCP/IP or SSH.
Remove /dev/random and replace it with a symbolic link to /dev/urandom. /dev/urandom is less secure than /dev/random but the system does not hang when the provisioning system attempts an SSL connection on Red Hat Linux Advanced Server 3.0.

Notification Rules Might Cause Plans to Run Slowly (6176243)

If you create a notification rule that has few criteria or no criteria, plans might appear to run slowly. The plan does not complete slowly, but the display of the plan results might be delayed.

Workaround: When creating a notification rule, use as many criteria as possible. More criteria for a notification rule decreases the number of notification emails the provisioning system sends across the network. A lower number of notification emails is less likely to interfere with the display of plan results.