test

Sun N1 Service Provisioning System 5.2.1 Release Notes

Chapter 3 Sun N1 Service Provisioning System 5.2 Issues

This chapter describes Sun N1 Service Provisioning System 5.2 issues that are known to be problems.

Installation Issues

This section describes known issues with installation.

Windows: Resource Check Ins Might Be Rejected (6396403)

Per a recent change in the way resource space is managed, the variable used to configure the Master Server resource repository size has changed in name and function. Therefore, the default configuration files need to be changed.

The new variable, rsrc.minMSRepoVolFreeSpace, specifies the minimum number of bytes of disk space that should remain available before further resource check ins are rejected. If a value is not given to rsrc.minMSRepoVolFreeSpace, the Master Server can use as much disk space as needed, up to the entire disk.

Workaround: On Windows Master Servers, manually delete configuration variable rsrc.maxMSRepoSize and add the new configuration variable rsrc.minMSRepoVolFreeSpace. Both variables pertain to the management of resource disk space on the Master Server.

Windows: Windows 2000 Installation Might Fail When Configuring HTTPS (6398475)

While installing the Sun N1 Service Provisioning System 5.2 Master Server on Windows, the installation fails when selecting the I Am Ready to Specify the HTTPS configuration now option. When choosing this option, the installer prompts for keystore file path and keystore password. The installation might fail by throwing the following error:

Error 1720: There is a problem with this windows installer package. A script required for this install to complete could not be run. Contact your support personnel or package vendor.

The possible causes for this error are:

Workaround: To prevent an error, verify the following:

As an alternative, you can also select the I will specify the HTTPS configuration after the install option instead of the I am ready to specify the HTTPS configuration now option and perform keystore configuration later.

For more information, see Creating a Keystore File and Keystore Password for HTTPS Connections in Sun N1 Service Provisioning System 5.2 Installation Guide.

Problems Starting the Master Server on Solaris Systems That Do Not Meet Minimum System Configuration Requirements (6395197)

The N1 SPS Master Server uses the PostgreSQL database. PostgreSQL requires a shared memory segment when it is started. If the PostgreSQL's request for a shared memory segment exceeds available memory, then database startup fails with the following error message on the console:

Error! Failed to initialize the database (exit value was 1). Exiting..

The installation of the Master Server is incomplete. It can be removed by using the following command:

# pkgrm SUNWspsms SUNWspsc1

Also the db error log would contain a message similar to the following:

IpcMemoryCreate: shmget(key=5432001, size=426688512, 03600) failed: Not enough space

It is recommended, to stop all other processes that might be using shared memory during master server installation. If the master server could not be installed even after upgrading the physical RAM, refer to Chapter 10, Upgrading to the Sun N1 Service Provisioning System 5.2, in Sun N1 Service Provisioning System 5.2 Installation Guide. This chapter describes the steps required to migrate the Master Server from this machine to a different one that meets the minimum system requirements.

Workaround: The workaround for this issue is to increase the physical RAM on the system. The Master Server cannot be installed on systems that do not meet the minimal system configuration requirements.

The minimal system configuration requirements for Master Server are documented at Master Server Hardware Requirements in Sun N1 Service Provisioning System 5.2 Installation Guide.

Also, if Master Server installation was successful, but fails to start up due to shared memory constraints, the shared memory requirement of the Master Server could be reduced by using one, or both, of the following methods:

Windows: Installation Fails When User Does Not Have Correct Privileges or Incorrect Password Is Entered (6394017)

The user is installing a Master Server, Remote Agent, or Local Distributor on a Windows system. If the user chooses to run the Windows Service as Other Account, the user needs to provide a username that has Log on as a service privileges. If the user types an invalid password or the username does not have Log on as a service privileges, the installed services fail to start.

When the services fail to start, one of the following error messages is displayed:

This error occurs because the user typed an invalid password or the username does not have Log on as a service privileges. Username validation only validates the existence of the user on that computer. The credentials are not checked to see if the password is valid for that user or if the username has "Log on as a service" privileges.

Workaround: To prevent this error, implement one of the following workarounds:

Uninstallation Issues

This section describes known issues with uninstallation.

Side-by-Side Upgrade of a Windows Master Server Uninstall Fails (6188943)

When you are performing a side-by-side upgrade of a Windows Master Server, immediate uninstallation fails. Uninstallation might require manual intervention and reboot to complete.

Workaround: Stop the Master Server service from the Services application in the Windows Control Panel before running the Master Server uninstallation. After the uninstallation completes, the Master Server services are still present. Reboot the machine to remove the Master Server services entries in the Services application in the Windows Control Panel.

Uninstallation Window Displays Previous Sun N1 Service Provisioning System Version Value (6189043)

After upgrading a Sun N1 Service Provisioning System Windows version of the Local Distributor or Remote Agent to the next version, if you uninstall that Local Distributor or Remote Agent, the title of the uninstallation window displays the previous version.

Workaround: The uninstallation program proceeds properly. Ignore the erroneous title.

Runtime Issues

This section describes known runtime issues.

Windows: Database Optimization Should Be Performed On a Regular Basis

If database optimization is not performed on a regular basis, performance deteriorates.

Workaround: Manually schedule a database optimization task.

This is a two phase process.

Note –

The following steps are performed on the Master Server.

  1. Creation of Database Optimization Script

    Create a new Windows command file called file_name.cmd in the server\bin\ directory of the Master Server installation. Copy the following text to the file_name.cmd file.


    REM No changes need to be made to the script after this line
cd %SPS_MS_DIR%\bin
..\cygwin\bin\bash.exe roxdbcmd vacuumdb -d rox

  2. Scheduling

    1. Choose Start ⇒ Settings ⇒ Control Panel ⇒ Scheduled Tasks.

    2. Start the Task Scheduler Wizard by double-clicking Add Scheduled Task in the Scheduled Tasks folder. Click Next.

    3. Click Browse to open the Select Program To Schedule dialog box. Navigate to the optimizedb.cmd file.

    4. Choose the frequency of task runs.

      It is recommended that you run the task daily. Your options in subsequent screens will depend on your choices. The following steps assume that the user selected the daily option.

    5. Enter the time when the task should be run. Click Next.

      Note –

      It is advisable to run the database optimization task when the system is not being used. Choose the scheduling time accordingly.

    6. Type the name and password of the user who is associated with this task. Click Next.

      Make sure that you choose a user with sufficient permissions to run the program. By default, the wizard selects the name of the user who is currently logged on.

    7. Click Finish.

      The task is scheduled.

    8. For confirmation of successful task scheduling, it is advisable to choose Start ⇒ Settings ⇒ Control Panel ⇒ Scheduled Tasks and check the Task Exit Status Code. A successful task run is indicated by code 0x0.

      Note –

      Please note that the scheduled run of the task should be completed before observing the exit status code.

      For more information on Windows task scheduling options, see http://www.microsoft.com/technet/scriptcenter/guide/sas_man_lpja.mspx.

Backup and Restore Commands Fail To Restart Master Server (6398090)

When the backup and restore scripts are run, the Master Server with an SSL configuration fails to restart after the execution of these commands.

Workaround: Perform one of the following options:

Folder Add Command Fails With Permission Problems (6382198)

When a user tries to create a folder by using the fdb.f.add command, folder creation fails despite the parents argument being set to true.

Setting -parents true, only creates the new folder and its immediate parent. The following example fails because folder f1 does not exist.


r_cli -cmd fdb.f.add  -parents true -fullname /group1/f1/f2/f3 -u user1 -p user1

The following error message is displayed:

Unable to save folder /group1/f1/f2/ due to permissions problem. (013011) access denied (com.raplix.rolloutexpress.systemmodel.userdb.FolderPermission folder:129159219047-1139319070874-31478-1381549121 write)

This happens when a user does not have administrator rights, but is a member of the group that owns the folder.

Workaround: When using the -parents true option, do not require the command to create more than the new folder and its immediate parent.

Container Component Creation Fails When Platform Is Not Equal To system#any (6408383)

If you attempt to create a component of type system#container and platform is not equal to system#any, component creation fails. The following error message is displayed:

Unable to perform the requested operation An unexpected error occurred. Try using the menu on the left or other links on the page to navigate to the page you want and try again.

Workaround: Perform one of the following:

Snapshot Data For Nested Components Might Not Be Purged When the Nested Components Get Reinstalled

If a nested component that is installed by way of the installation of a container component, creates snapshots, the snapshot data on the Remote Agent might not get purged when the nested component is uninstalled by the reinstall of the container component. This might lead to the Remote Agent, on which the nested component was installed, to consume more disk space than it should since the orphaned snapshot data was not purged.

Workaround: The orphaned snapshot data might be purged by installing and then uninstalling a simple component that creates snapshots on the Remote Agent with orphaned snapshot data. The install and uninstall cause the Remote Agent to compare its snapshot data with the Master Server. The result is that the snapshot data is purged for all the components that are no longer installed on the Remote Agent.

System Might Hang When Using SSL on Red Hat Linux Advanced Server 3

If you are running the Sun N1 Service Provisioning System on Red Hat Linux Advanced Server 3, 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 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:

Plan Execution Pauses for 10 Minutes on execJava in Preflight on IBM AIX Remote Agents (6313197)

On an IBM AIX remote agent, the plan execution for CreateManagedServerPlan might pause for 10 minutes on an execJava step.

Workaround: None.

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:

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.

Issues Interacting With the Windows 2000 Plug-In

This section describes known issues with the Windows 2000 plug-in.

Changing a Microsoft IIS Setting and Then Resetting It Might Result in Differences Being Found (6189034)

When performing model to install comparisons that include snapshots of IIS settings, if an IIS setting is changed and then changed back to its original value on the target server, comparison results might indicate differences when no difference exists. In particular, IIS metabase properties that are inherited from parent nodes, such as read/write web site permissions or default document settings, are prone to this behavior.

Workaround: Ignore the differences that are found in these cases.

Cannot Uninstall Windows IIS Application (6197564)

When you uninstall a Windows IIS Application, the Master Server browser interface displays that the uninstallation was successful. However, the COM+ applications are not completely removed. The COM+ applications remain in the Add/Remove Software Programs in the Control Panel.

Workaround: Manually remove the remaining COM+ applications.

To prevent this problem, when you install the application, increase the value of the shutdownDelaySecs variable.

Issues Interacting With the BEA WebLogic Plug-In

This section describes known issues with the WebLogic plug-in.

EJB Component Is Not Uninstalled (5109783)

If you run the default uninstall procedure for an EJB component that was deployed to more than one virtual WebLogic managed server and select only one of the managed servers to be uninstalled, the EJB component does not appear to be uninstalled from the managed server.

After the uninstall, if you click the tab on the WebLogic console for the managed server from which you uninstalled the EJB, the console correctly reports that the EJB is no longer deployed. Also, when you click the EJB tab, the console reports that the EJB is no longer targeted at the managed server from which it was uninstalled.

However, on the EJB tab, the console reports that the EJB is deployed on the managed server.

If you uninstall the EJB from all managed servers, the EJB is removed from the WebLogic console correctly.

Workaround: The WebLogic Plug-In is uninstalled correctly. Ignore the erroneous display.

Comparison Fails With Snapshot Error When WebLogic Application Was Deleted From the WebLogic Console (6186456)

If you deploy a WebLogic web application that contains a web application container with a WAR file and web application settings and include a snapshot and then delete the web application from the WebLogic Console, the following error displays if you run a model to install comparison on the web application component:


Could not complete operation on webapp domain.
No such webapp exists on domain /domain/. (310101)

The comparison should report a difference between the model and what is installed on the server. However, the comparison fails.

Workaround: No workaround is available.

Comparison Does Not Report Differences For Undeployed Components (6186457)

If you use the WebLogic Console to undeploy a WebLogic WAR or EJB component from a managed server or cluster, the WebLogic Console reports that the WAR or EJB component is still targeted to that managed server or cluster. Consequently, if you run a model to install comparison on the managed server or cluster, the comparison reports no differences. The model to install comparison checks the WebLogic Console and reports targeted applications as deployed.

Workaround: No workaround is available.

Comparison Results Incorrect for Content Changes Made to the On Disk Representation of WebLogic Application Archives (6196108)

If a WebLogic application is installed using the Sun N1 Service Provisioning System 5.2 and then content changes are made to the on disk WAR archive on the administration server, the changes are not reported in comparison results. The problem does not occur when configuration changes are made.

Workaround: Comparisons can be customized using the generate and prepare extensions with more capabilities to preprocess the on disk representation prior to running the comparison. This type of customization might require some advanced scripting.

SSL Connections to WebLogic Administration Servers Are Not Supported (6203385)

When setting up a WebLogic administration server in the Sun N1 Service Provisioning System 5.2, clicking the Secure checkbox will attempt to set up connectivity using SSL. This selection causes an error when attempting to perform actions that require access to the WebLogic administration server.

Workaround: Always setup WebLogic administration server connections with requiring SSL connectivity. Do not select the Secure checkbox.

Localization Issues

This section describes issues encountered when using the Sun N1 Service Provisioning System 5.2 in locales other than the English locale.

Search Pattern With Non-ASCII Latin-1 Characters Does Not Work Correctly (6302462)

In the Latin-1 locale environment, non-ASCII characters should not be used in the search pattern. For example, umlauts in German and accents in French. The desired match might not be in the returned set when the find operation is executed.

Workaround: Latin-1 locale users should not use non-ASCII characters as the input to the find command. Using non-ASCII characters might not return the desired result. Use only ASCII characters in these locales.

Locale Sensitive Sorting Is Not Supported

String–based data within the Sun N1 Service Provisioning System is sorted using the standard dictionary lexicon. Locale-specific collation is not performed. Consequently, accented versions of characters appear in a different position than the same unaccented characters.

Upgrading Issue

Update Hosts Progress Dialog Box Does Not Continuously Refresh (6383815)

If you click the Update Entire Host Network button during an upgrade of remote agents or local distributors where the database has thousands of hosts, the Update Host Progress dialog box might not continuously refresh. The dialog box provides the current status for approximately 20 minutes. Although the dialog box stops refreshing, the upgrade continues.

Workaround: Go to the Hosts List page and click the View Current Host Updates link.