test

Sun Management Center Change Manager 1.0 Administration Guide

Appendix B Troubleshooting (Tasks)

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 Release Notes.

Change Manager Server Installation Problems

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

patchadd -p Issues PatchArrElem Error on Solaris 8


/usr/sbin/patchadd[177]: PatchArrElem: subscript out of range

Description:

This message appears when you run the patchadd -p command on the Solaris 8 2/02 operating environment.

Solution:

You can ignore this message.

To avoid seeing this message, add patch 108987-09 to your Solaris 8 2/02 system.

  1. Become superuser.

  2. Download the patch to your system from the SunSolve Patch Portal.

  3. Use the unzip command to expand the patch from the ZIP archive.


    # unzip 108987-09.zip

  4. Change to the patch directory.


    # cd 108987-09

  5. Install the patch.


    # patchadd `pwd`/108987-09

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 ensuring that you are a member of both the esadm and esdomadm groups.

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


Internal error: unable to establish probe connection

Description:

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

Solution:

Ensure that the managed host is a client of 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.

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: ]]

This error might indicate that the disk is full.

Solution:

Check to see if the file system that contains the Change Manager repository is full.

Import of Shared Profile Fails if Specified Solaris Flash Archive Does Not Exist in the Repository (4738382)

Description:

If you import a shared profile in to the repository and the operation fails, you might see the following error message:


Execution failed [import failed: record not found:
  /archive_name.flar]
/templ_name.cmsp: import failed.
Cause:

Change Manager validates the archive specified in the shared profile. If the archive is invalid (it does not exist), then the import fails.

Solution:

Make sure that the Solaris Flash archive exists in the repository before importing the shared profile.

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

This error message might indicate that /tmp is full.

Solution:

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

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 by typing:


# /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 by typing:


# /opt/SUNWsymon/sbin/es-restart -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 by typing:


# /usr/sadm/bin/smcwebserver restart

Netscape Communicator Reports That Certificate Has an Invalid Signature


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.

The Browser Interface Behaves Unpredictably When Handling Large Numbers of Host Groups (4685706, 4707804, 4738647)

Description:

When a large number of host groups, namely, 200, are manipulated, the browser interface might behave unpredictably. This situation occurs when creating large numbers of host groups or renaming a host group that contains a large number of host groups.

Solution:

Avoid creating a topology hierarchy with large numbers of host groups.

If the browser interface becomes unusable, restart the Sun Management Center server and the web server by running:


# /opt/SUNWsymon/sbin/es-restart -S
# /usr/sadm/bin/smcwebserver restart

If restarting the Sun Management Center server and web server fails, you might want to reinitialize the Sun Management Center database.

Caution - Caution -

Reinitializing the database removes all the topology and Change Manager data from the Change Manager server. So, use this only as a last resort.

  1. Remove the data and recreate the Sun Management Center database.


    # /opt/SUNWsymon/sbin/es-setup -F

  2. Recreate the Change Manager database.


    # /opt/SUNWsymon/sbin/es-setup -p ichange

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 publically 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.

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 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.

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. The 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, Creating 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, Creating 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 hanged 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

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(1M) command to identify the network boot servers on which your managed host is a client.

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

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

    1. Use the browser interface or the command-line interface to remove your managed host from the Change Manager topology.

    2. Log in to the boot server as superuser.

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

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


      # ./rm_install_server hostname

  2. Run the hostconfig command to determine whether your managed host is a client of 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 a client of 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 a client of a boot server. Go to Step 7.

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

    If you use the NIS naming service, for example, use ypmatch(1) 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

  5. Repeat Step 1b to Step 4 to remove your managed host entries from the /etc/bootparams file on the boot server.

  6. Repeat Steps 2-4 to find additional boot servers.

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

Interactive Installation Program Launched When Files For Non-Existent Managed Hosts Not Cleaned Up (4721489)

Description:

When the last reference to a managed host is removed from the Change Manager topology, the custom JumpStart data is not deleted.

The /etc/bootparams file still contains entries corresponding to the managed hosts.

The /var/opt/ichange/jsdata/hostname directories still contain boot environment information and custom JumpStart configuration files.

Extraneous /etc/bootparams entries for a managed host can cause problems. For example, if more than one Change Manager server has the same managed host registered, each server answers the call from that managed host. This situation produces excess traffic and unknown results on the managed host.

Solution:

Manually clean up the following files on the Change Manager server:

  • Find a Solaris miniroot, which might be located in the Change Manager repository under /var/opt/ichange/root. Change directory to the Tools subdirectory, for example, /var/opt/ichange/root/s9.miniroot/Solaris_9/Tools. Then, as superuser, type:


    # ./rm_install_client hostname

  • Delete the host-specific directories from the /var/opt/ichange/jsdata directory.