Sun Management Center Change Manager 1.0.1 Administration Guide

- Previous: Change Manager Server Installation Problems
- Next: Browser Interface Problems

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

- Previous: Change Manager Server Installation Problems
- Next: Browser Interface Problems

- © 2010, Oracle Corporation and/or its affiliates