[ Previous | Next | Table of Contents | Index | Library Home | Legal | Search ]

Distributed SMIT 2.2 for AIX: Guide and Reference

DSMIT Troubleshooting

Use the following suggestions if you encounter problems while connecting to a client, listing domain members, or defining a working collective. A Failed prompt in the Command Status field of the output screen indicates that one or more systems reported a failure.

Clean Up After Abnormal Termination

If the front end of DSMIT/crex/srex abnormally terminates, the following may not have been cleared:

Concurrent DSMIT/crex/srex sessions may have similar side effects and they must be resolved. The following information is intended as a guide for cleaning up processes that abnormally terminated:

  1. Remove the files in /tmp/dsmit that belong to the failing process.
  2. Use the dsmit-dec command to decrement by 1 the value of the counter in the /usr/share/DSMIT/security/dslock.ctr file.
  3. Remove /usr/share/DSMIT/security/dslock lock file.

If You Cannot Connect to a Client

Many of the problems associated with Distributed System Management Interface Tool (DSMIT) arise when you cannot connect to one or all of the clients. Consult the following list if you cannot connect to the DSMIT clients:

If You Cannot Establish a Secure Session

If a message such as "establishing secure session failed" is displayed, refer to the following steps:

  1. Be sure the system you are trying to establish a session with is defined as a managed machine. On the DSMIT server, do the following:
    1. Type dsmit env.
    2. Select List All Machines.


    3. Type lsdsmitm.

      Note: If the machine you are trying to establish a session with does not appear in the list of managed machines, you should add it. See Modifying DSMIT Security Configuration for more information.
  2. Install a new key on the managed machine:
    1. Remove the managed machine.
    2. Add the machine.
    3. Install the new key.

      Note: See Modifying DSMIT Security Configuration for more information.

If You Cannot List All Members of A Domain

If the output from the lsdsmitd command does not include all of the hosts that were added to a domain, check the /usr/share/DSMIT/hosts file for spaces between client names. Remove all spaces in the definition of a domain.

If You Cannot Define A Working Collective

If you cannot define a working collective because you get the message:

All the hosts should have one and the same Operating System

If You See Double Entries in the Domain Management Menus

Double entries can occur if you completed step 4 in the Database (Databases) section even though DSMIT was installed on the HostWithNewLevel. To correct this situation, remove the NewLevelDirectory and complete all the steps except step 4 in the "Database" section.

If You Cannot Connect to the File Server

If you get messages such as the following:

Cannot acquire exclusive lock


Cannot connect to the file server 

Enter the dsmit-unlock and dsmit-dec commands on the file server.

If You Cannot Run dsmit-addkey on a Client

If you cannot run the dsmit-addkey command because you get the message:

dsmit-addkey: Problems with /tmp/new-v5srvtab -- exiting.

If You Cannot Access/Open File /tmp.installp_cmd

If you get the Cannot access/open file /tmp.installp_cmd message when trying to install a software package, the version of installp on the remote machine is different than the SMIT database version on the local machine. To fix this, install the correct version of the database on the local machine. Refer to Databases .

If You Cannot Select the Next Screen

You may get the following message cause you cannot select the next:

There is a conflict in selecting the next screen - Make other selections in previous screens and/or 
exclude some hosts from the collective

The next menu to display is not exactly the same on all machines in the working collective. This indicates one of the following:

For example, for the menu Change/Show Characteristics of a Tape Drive, the working collective is defined to be M1 and M2. On M1, a 4.0 GB 4mm tape drive exists and on M2, a 2.3 GB 8mm tape drive exists. When DSMIT attempts to display a menu, you will get the above error message. This is because of the different dialog type options. On the 4.0 GB tape drive, it has the extra option Use data COMPRESSION and on the 8.0 GB, it has the Use EXTENDED file marks option. DSMIT cannot display different dialogs at once. Each dialog must be the same to work.

To correct this problem, you must work with each group of machines that have the same dialogs by temporarily excluding the machines that are different and working with them later.

If You Cannot Get Solaris Machines Into Working Collective

If you cannot get Solaris 2.3 and Solaris 2.4 machines into the same working collective, check /usr/share/DSMIT/hosts to be sure all machines are listed as Solaris and not Solaris_2.3.

Related Information

Chapter 1, Distributed System Management Interface Tool.

Installing DSMIT.

[ Previous | Next | Table of Contents | Index | Library Home | Legal | Search ]