Sun Management Center Change Manager 1.0.1 Administration Guide

- Previous: Change Manager Server Installation Problems
- Next: Software Deployment Problems

# 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 –

       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:

  - Create a shared profile by using the browser interface, see How to Create a Shared Profile (Web Browser).

  - Import an existing shared profile to the repository:

    1. Create a shared profile outside of the repository. The shared profile is a text file that contains the parameters and parameter values described in Parameters Used by Shared Profiles and Host Properties.

    2. Import the shared profile to the repository. See How to Import Shared Profiles to the Change Manager Repository (Command Line).

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

- Previous: Change Manager Server Installation Problems
- Next: Software Deployment Problems

- © 2010, Oracle Corporation and/or its affiliates