test

Sun Management Center Change Manager 1.0.1 Administration Guide

Appendix B Troubleshooting (Reference)

This appendix lists problems, warning messages, and error messages that you might see when using Change Manager.

The information for each problem can include three sections:

Troubleshooting information is provided for the following problem areas:

For problems that have been discovered since the publication of this book, see the Sun Management Center Change Manager 1.0.1 Release Notes.

Change Manager Server Installation Problems

The following troubleshooting issues relate to the installation of Sun Management Center 3.5 and Change Manager 1.0.1 on the designated Change Manager server.

Sun Management Center Agent Cannot Communicate With the Change Manager Server After Installing a Managed Host

Description:

When you upgrade your Change Manager 1.0 server to be a Change Manager 1.0.1 server (see How to Upgrade a Change Manager 1.0 Server to Run Sun Management Center 3.5 Server Software), you might experience a problem when installing managed hosts. After you install a Solaris Flash archive on a managed host, the managed host fails to communicate with the Change Manager server.

Cause:

The custom JumpStart files that were created for the Change Manager 1.0 server are retained. So, if you install a managed host by using these old custom JumpStart files, then the Sun Management Center agent might not communicate with the Change Manager server.

This problem will occur if you change the value of the “Sun Management Center server seed” during the upgrade of the Change Manager server.

Solution:

Run Set Up for Install or changemgr setup for each managed host that you want to install. This step re-creates the custom JumpStart files for each managed host you specify.

Stale Custom JumpStart Data Not Removed When Change Manager 1.0 Server Software Is Uninstalled

Description:

If you upgrade your Change Manager 1.0 server to run Sun Management Center 3.5 server software and you do not preserve the data, then only the Change Manager 1.0 server software is uninstalled. None of the Change Manager data (the custom JumpStart data and the Change Manager repository) is removed from the Change Manager server.

Cause:

This situation occurs when Change Manager 1.0 server software is uninstalled in one of the following two ways:

  • Using the es-guiinst command or the es-inst command to upgrade from Sun Management Center 3.0 to Sun Management Center 3.5

  • Using the es-uninst command to uninstall Sun Management Center 3.0 server software

Solution:

Manually clean up entries in the /etc/dfs/dfstab file and in the /etc/bootparams file. Then, delete the Change Manager 1.0 repository. The directory that holds the Change Manager repository is specified by the value of the cmdataroot property in the /var/opt/SUNWsymon/cfg/ichange.cfg file.

Information About Managed Hosts and Host Groups Created by Change Manager Remains in the Topology Database Even After Change Manager Software Is Uninstalled

Description:

Managed hosts and host groups created by Change Manager appear in the Sun Management Center topology database even after Change Manager has been uninstalled and data has been discarded.

You can access these managed hosts and host groups from the Sun Management Center Console. If you reinstall Change Manager later, you can also access these managed hosts and host groups. However, you will be unable to run any Change Manager operations, such as an update, on them.

Cause:

Change Manager needs more information about managed hosts than Sun Management Center does. The information that remains in the Sun Management Center topology database must be augmented before such hosts can be fully managed by Change Manager.

Solution:

If you intend to reinstall Change Manager software, you must first update the host configuration for each of the existing managed hosts.

Update the configuration by setting all of the required host properties and by associating each managed host with a shared profile or Solaris Flash archive. Once these changes have been made, you can perform Change Manager operations on these managed hosts.

If you do not intend to reinstall Change Manager software, remove the managed hosts and host groups from the Sun Management Center topology database. You can perform this cleanup by using the Sun Management Center Console.

User Interface Problems

This section describes problems using the browser interface and the command-line interface. Problems seen when using both user interfaces are described first.

General User Interface Problems

Managed Host Not Added Error Appears When You Try to Add a New Host

Description:

You attempt to add a new host, and the following message appears:


Managed Host Not Added
SNMP request returned error status 6 (no access)
snmp://129.153.72.86:164/mod/topology+view-#/entityAdder#0

Other similar types of requests might yield a similar error.

Solution:

Ensure that you are an authorized Sun Management Center domain administrator by checking that you are a member of both the esadm and esdomadm groups.

Internal error: unable to establish probe connection Appears When Running Jobs on a Managed Host

Description:

When you run jobs on a managed host, you might see the following error message:


Internal error: unable to establish probe connection
Cause:

This message appears when you run jobs on a managed host that is managed by more than one Change Manager server.

Solution:

Ensure that the managed host is managed by only one Change Manager server.

To change control of a managed host to another Change Manager server, perform the following steps:

  1. Remove the managed host from the current server.

  2. Add the managed host to the new Change Manager server.

  3. Create a shared profile for the managed host.

  4. Run Set Up for Install or changemgr setup for the managed host.

  5. Type the boot net - install command at the OpenBoot prompt of the managed host to perform the initial installation.

Import of a Solaris Boot Image Fails (4733369)

Description:

When you import a Solaris boot image, you might see the following error message:


Aug 29 10:03:27 IC_1 - - 
  Failed [Execution failed [import failed: ]]
Cause:

This error usually indicates that the disk is full.

Solution:

Check to see if the file system that contains the Change Manager repository is full. If it is, see File System That Contains Change Manager Repository Is Full.

File copy did not run Error Message Issued During Import Operation (4753374)

Description:

When you perform an import operation, you might see the following error message:


File copy did not run
Cause:

This error message might indicate that /tmp is full.

Solution:

Free space in /tmp to make room for the file that you want to import.

File System That Contains Change Manager Repository Is Full

Description:

Change Manager issues errors if the file system that contains the repository is full and you perform tasks that write to the repository. Such tasks include importing files to the repository or performing some Change Manager operations such as an audit.

Solution:

If the file system that contains the repository is full, do one of the following:

  • Create more space by deleting unneeded file objects from the repository, using either of the Change Manager user interfaces.

  • Move the repository to a file system on a local disk that has sufficient space. Do the following as superuser on the Change Manager server:

    1. Stop the Sun Management Center services.


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

    2. Disable the custom JumpStart configuration for the existing managed hosts.

      1. Remove entries from the /etc/dfs/dfstab file that represent directories that are exported from the repository.

      2. Remove entries for all managed hosts that are registered in the /etc/bootparams file.

    3. Copy the Change Manager repository to the new location.

      For example, if the full repository is /var/opt/ichange and the new repository is called /export/cm101, do the following:


      # cd /var/opt/ichange
# find root hostdata jobdata -print | cpio -pudm \
/export/cm101
...
#

    4. Update the value of the cmdataroot parameter to point to the new repository location.


      # cd /var/opt/SUNWsymon/cfg
# cp ichange.cfg ichange.cfg.orig
# /bin/sed -e '/^cmdataroot/s/=.*$/=\/export\/cm101/' \
ichange.cfg.orig >ichange.cfg
#

    5. Restart the Sun Management Center services.


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

    6. Recreate the custom JumpStart data for all your managed hosts.

      • If you use the browser interface, run the Set Up for Install operation.

      • If you use the command-line interface, run the changemgr setup command.

      Caution – Caution –

      If the ichange_db directory exists in the original repository location, do not remove it. This situation occurs if you specify the same location for the repository and the Change Manager database. The information in this directory is required for Change Manager database operations.

    7. Verify that you can access files and manage files in the new repository before removing the repository from its original location.

Browser Interface Problems

The following troubleshooting issues relate to the browser interface.

Unable to Reach the Change Manager Login Page

Description:

You provide the correct Change Manager URL, but you are unable to reach the login page. Following is the correct form of the URL:


https://server_name.domain:6789/changemgr
Solution:

Try restarting the web server.


# /usr/sadm/bin/smcwebserver restart

Unable to Log In to the Change Manager Browser Interface With Valid User Name and Password

Description:

You type a valid Change Manager user name and password on the Change Manager login page, but the login attempt fails.

Solution:

Try restarting the Sun Management Center server.


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

Change Manager Does Not Appear in the Application List or Not Authorized to Use Requested Application Is Displayed When You Try to Log In

Description:

You provide a valid Solaris user name and password, but are unable to start the Change Manager application.

Solution:

Ensure that you are an authorized Sun Management Center user by inspecting the file /var/opt/SUNWsymon/cfg/esusers.

Note –

To access all areas of Change Manager, you need to be an authorized Sun Management Center domain administrator. Ensure that you are a member of both the esadm and esdomadm groups.

document contained no data Error Appears When Trying to Access the Change Manager URL

Description:

You provide the correct Change Manager URL, but the following error message appears in a dialog box:


document contained no data.
Solution:

Verify that the URL is correct.

The following example shows the correct form of the Change Manager URL:


https://server_name.domain:6789/changemgr

Ensure that the URL begins with https, not http.

If the URL is correct, try restarting the web server.


# /usr/sadm/bin/smcwebserver restart

Netscape Communicator Reports That Certificate Has an Invalid Signature

Description:

Netscape Communicator Version 4 produces this message:


The server's certificate has an invalid signature. You will
not be able to connect to this site securely.
Solution:

Restart the Netscape Communicator, then access the page again.

Cannot Browse Directories in the File Chooser Wizards That Are Not Publicly Readable (4735785)

Description:

The browser interface cannot display the contents of directories that are not publicly readable. This problem prevents the file browser from accessing private directories even though the user has appropriate permissions.

Solution:

Directly specify files in such a directory by supplying a full path name to the file.

JavaScript and Request-Handling Errors Occur When You Access the Web Application After You Upgrade Your Server From Change Manager 1.0 to Change Manager 1.0.1

Description:

The Sun Management Center Web Console server continues to use the cached Change Manager 1.0 JSP classes instead of recompiling them from the new Change Manager 1.0.1 JSP sources.

Cause:

This happens because the JSP classes have a later timestamp than the JSP source files.

Solution:

Stop the Sun Management Center Web Console server, remove the cached Change Manager 1.0 JSP classes, then restart the web console server.

The procedure differs, depending on the version of Solaris you are running on the Change Manager server.

  • If you are running Solaris 9 12/02, or an earlier release of Solaris, run these commands:


    # /usr/sadm/sbin/smcwebserver stop
# rm -rf /var/sadm/webconsole/work/localhost/changemgr
# /usr/sadm/bin/smcwebserver start

  • If you are running at least Solaris 9 4/03, run these commands:


    # /usr/sadm/bin/smcwebserver stop
# rm -rf /var/sadm/webconsole/work/Standalone/localhost/changemgr
# /usr/sadm/bin/smcwebserver start

Command-Line Interface Problems

The following troubleshooting issues relate to the command-line interface.

Cannot Use the Command-Line Interface to Create Shared Profiles

Description:

You cannot use the command-line interface to create a shared profile.

Solution:

To create a shared profile, do one of the following:

After the shared profile is in the repository, you can modify property values by using the changemgr fileset command. See How to Modify File or Folder Properties (Command Line).

Software Deployment Problems

The following troubleshooting issues relate to the deployment of software to managed hosts.

Custom JumpStart Installation Launches the Interactive Installation Program

Description:

If the installation program detects an invalid parameter or invalid parameter value in a shared profile or in host properties, the hands-off installation terminates. Then, the interactive installation program launches so you can correct the problem or otherwise continue with the installation.

Note that the questions asked by the interactive installation program provide clues as to which parameters caused the problem.

This scenario occurs if you provide an invalid parameter value. For information about custom JumpStart keywords, see “Preconfiguring System Configuration Information (Tasks)” in Solaris 9 Installation Guide.

Note –

The custom JumpStart keywords correspond to the Change Manager parameters, but the names are different. Change Manager parameters begin with the base_config_ string, but the content part of the string matches closely to the custom JumpStart keyword names. To see a description of the Change Manager parameters, see Chapter 10, Parameters for Shared Profiles and Host Properties (Reference).

Cause:

The installation program detects the parameter problem, but cannot correct it. The custom JumpStart installation cannot continue, so it launches the interactive installation program.

Solution:

To correct the problem, review the parameters and parameter values for the managed host that failed to perform the custom JumpStart installation.

Ensure that the parameters and parameter values are correct. See Chapter 10, Parameters for Shared Profiles and Host Properties (Reference) for a description of the parameters specified in shared profiles and by host properties.

Note –

Be careful when copying the encrypted root password from /etc/shadow to the shared profile. Do not include the colon (:) field delimiters as part of the base_config_sysidcfg_rootpw property value.

If you find the problem and correct it, restart the initial installation.

If you do not find the problem, review the parameters and parameter values in the shared profile or in the host properties.

Note –

If you are installing only one managed host, you might continue with the interactive installation. This solution is not advisable unless you are installing just one managed host with a simple software stack.

Managed Host Hangs While Booting From the Network (4656587)

Description:

While loading the bootstrap, the managed host hangs. You can tell when the bootstrap is being loaded because of the hex count to 24000.

This problem might occur more often when the network is heavily loaded.

Cause:

An in.tftpd bug causes this intermittent failure. As a result of this bug, the transfer hangs.

Solution:

Reset the hung managed host. Try the network boot again.

Panic: unable to mount file systems Message Appears While Booting From the Network

Description:

The network boot of your managed host might fail with an error message such as:


Panic: unable to mount file systems
Cause:

If such a message appears, then your managed host is probably being served by more than one network boot server.

You must first identify all network boot servers on which your managed host is registered, other than the Change Manager server.

Solution:

Use the hostconfig command to identify the network boot servers that manage your managed host.

Perform the following steps to determine whether your managed host is managed by more than one network boot server:

  1. Remove your managed host from the Change Manager server from which you want to boot.

    Use the browser interface or the command-line interface to remove your managed host from the Sun Management Center topology.

  2. Run the hostconfig command to determine whether your managed host is managed by another network boot server.


    $ hostconfig -p bootparams -f hostname -n -v

  3. See if the hostconfig command identifies a network boot server for your managed host.

    • If an IP address appears in square brackets on the first line of output, your managed host is managed by another boot server. The IP address represents the boot server.


      From [192.153.72.132]: hostname = host1
	ypdomain = yourCompany.COM
	router = 192.153.72.1

    • If no IP address appears, then your managed host is not managed by a boot server. Go to Step 7.

    See the hostconfig(1M) man page.

  4. Determine the name of the boot server specified by the IP address.

    If you use the NIS naming service, for example, use ypmatch to associate the IP address with the host name of the boot server.


    $ ypmatch 192.153.72.132 hosts.byaddr
129.153.72.132  cmserver

    See the ypmatch(1) man page.

  5. Remove your managed host entries from the /etc/bootparams file on the boot server.

    1. Log in to the boot server as superuser.

    2. Change to the Tools directory of the Solaris boot image associated with the Solaris version you want to install.

    3. Run the rm_install_client command to remove the entries for your managed host from the /etc/bootparams file.


      # ./rm_install_server hostname

  6. Repeat Steps 2-4 to find additional boot servers. Then, perform Step 5 for any boot servers found.

  7. When no more boot servers are indicated by the hostconfig command, add your managed host to the Sun Management Center topology of the Change Manager server. Set up the files for installation. Then, restart the boot net - install from your managed host's console.