This chapter describes N1 Grid Service Provisioning System 5.0 issues that are known to be problems.
This section describes known issues with installation.
The N1 Grid Service Provisioning System 5.0 Master Server is not supported when running on Red Hat Linux Advanced Server 3.0. However, the Master Server installation program allows you to install a Master Server on Red Hat Linux Advanced Server 3.0.
Workaround: Do not install the N1 Grid Service Provisioning System 5.0 Master Server on Red Hat Linux Advanced Server 3.0. Installing the provisioning system on unsupported operating systems might result in undefined and unexpected behavior.
If you attempt to install the CLI Client on a Solaris 10 server with a Solaris 10 local zone, the installation might fail. The following error message displays:
pkginstall: ERROR: unable to create package object </N1SPS5.0-home/cli>. pathname does not exist group name <group> not found in group table(s) owner name <user> not found in passwd table(s) Installation of <SUNWspscl> on zone <xxxx> partially failed. Error! Failed to install SUNWspscl. Exit value was 2 Exiting.. |
The installation fails because the provisioning system installation program creates the N1SPS5.0-home/cli directory in the global zone, but not in the local zone. Also, the installation fails if the user and group you created to own the provisioning system are not served by the name service.
Workaround: To prevent the CLI Client installation failure, before you begin the installation, complete the following steps:
Create the N1SPS5.0-home/cli directory in the local zone. N1SPS5.0-home is the home directory in which you plan to install the N1 Grid Service Provisioning System.
If the name service does not serve the user and group, create the user and the group that will own the N1 Grid Service Provisioning System in the global zone and in all local zones.
This section describes known issues with uninstallation.
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.
After upgrading an N1 Grid Service Provisioning System 4.1 Windows version of the Local Distributor or Remote Agent to the N1 Grid Service Provisioning System 5.0 version, if you uninstall that Local Distributor or Remote Agent, the title of the uninstallation window displays N1 Service Provisioning System 4.1.
Workaround: The uninstallation program proceeds properly. Ignore the erroneous title.
On a Solaris 10 server that contains one local Solaris 10 zone, if you use the cr_uninstall.sh script to uninstall the CLI Client, the uninstallation fails. The following error messages display in the log file:
N1 Grid SPS Uninstaller Log. Uninstall started on Fri Nov 12 10:51:36 PST 2004 Attempting to remove: SUNWspscl SUNWspsc1 pkgrm: ERROR: cannot use -A option when non-global zones exist pkgrm: ERROR: cannot use -A option when non-global zones exist |
Workaround: To uninstall the CLI Client, complete the following steps:
Change to the root user.
% su root |
Use the pkgrm command without the -A option to manually remove the SUNWspscl, SUNWspsc1, and SUNWspsj1 packages.
# pkgrm SUNWspscl SUNWspsc1 SUNWspsj1 |
This section describes known runtime issues.
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.
If you are running the N1 Grid 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.
From the browser interface on the Plug-Ins page, if you attempt to import a file that is larger than 40 MBytes, the import fails.
Workaround: To import plug-in files larger than 40 MBytes, use the plg.p.add command from the CLI Client . For instructions, see Chapter 11, plg: CLI Commands for Plug-ins, in N1 Grid Service Provisioning System 5.0 Command-Line Interface Reference Manual.
If you create a new file component using the browser interface and perform a Check In Current operation on the component to create version 1.1, if you attempt to delete both versions of the component at the same time, the following error message displays:
The 1.0 version of the object cannot be deleted as long as other versions of the same object exist. |
Workaround: Do not use bulk delete to delete the two components. Delete the components individually.
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.
Some APIs that are available on the Master Server do not check for any permissions. Without permission checks, an unauthenticated user might invoke these services and possibly compromise the Master Server.
Workaround: You can set up the Master Server and CLI Clients to prevent unauthorized access. The following security options are available for the Master Server and the CLI Clients:
Configure the Master Server to use SSL to connect to the CLI Clients.
Install the CLI Client on servers that are accessible only to users who are authorized to access the N1 Grid Service Provisioning System.
On Solaris OS, Red Hat Linux, and IBM AIX servers, install the CLI Client within a user group that contains only authorized provisioning system users as its members.
Set the permissions for the CLI Client private keystore in N1SPS5.0-CLI-home/cli/data/private.store to 640. This permissions setting allows only authorized provisioning system users access to the CLI Client private keys to be able to connect to the Master Server.
On Windows 2000 systems, ensure that the CLI Client private keystore has read permissions granted only to authorized provisioning system users.
If you attempt to restore data to a Master Server that is installed in a different path than the path to the Master Server that you used to create the backup file, the restore fails. The following message appears:
ERROR! Failed to restore the database successfully. The following fatal errors were encountered ERROR: stat failed on file 'N1SPS5.0-MS-home/': No such file or directory |
N1SPS5.0-MS-home is the home directory of the Master Server that you used to create the backup.
Workaround: On the server where you want to restore the Master Server data, reinstall the Master Server into the same directory as the Master Server that you used to create the backup.
This section describes known issues with the Windows 2000 plug-in.
You can create a component with a single resource of type registry key where the entry you capture is a single default value. However, without the accompanying registry key, you can deploy that value but you cannot uninstall it or delete it. A message indicating an invalid path appears.
Workaround: Ensure that registry keys that you capture include more than just a single default value. For example, include the key and the default value.
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.
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.
This section describes known issues with the WebLogic plug-in.
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.
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.
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.
If a WebLogic application is installed using the N1 Grid Service Provisioning System 5.0 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.
If you are using WebLogic 7.0 Service Pack 3 or later, you cannot deploy WebLogic EAR components. During an attempt to deploy an EAR component, the following message appears:
Execution ended abnormally. (025075) |
Workaround: No workaround is available.
When setting up a WebLogic administration server in the N1 Grid Service Provisioning System 5.0, 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.
This section describes issues encountered when using the N1 Grid Service Provisioning System 5.0 in locales other than the English locale.
String–based data within the N1 Grid 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.