13 Troubleshooting DMS

This chapter contains information to assist you in troubleshooting problems with DMS. If a DMS client has trouble booting, you can check several aspects of server operation to ensure that the server's end of the network connection is functioning properly. These are grouped into the following categories:

Removing DMS lock files (Section 13.1)

Checking NFS server status (Section 13.2)

Checking network daemon status (Section 13.3)

Checking directory exports (Section 13.4)

Checking server-client compatibility (Section 13.5)

Correcting swap device problems (Section 13.6)

Reconfiguring for a hardware update release (Section 13.7)

13.1 Removing DMS Lock Files

To prevent multiple users from performing simultaneous operations on DMS areas, the dmu utility creates two lock files in the /tmp directory, dmslock and dms.tty.lock when you are installing or deleting software in a DMS area. If another user (or the same user on a different terminal) runs the dmu utility and attempts to install or delete software from the DMU Main Menu, they see a message similar to the following:

The dmu utility is currently locked while j_smith on /dev/ttyp3
is installing software.  Try again later.

If the dmu utility is stopped prematurely, these lock files may not be removed and you see this message even though no other user is using DMS. You must delete the lock files from the /tmp directory.

Caution

Before deleting the lock files, ensure that no other user is using the dmu utility.

13.2 Checking NFS Server Status

Some DMS client boot problems occur if the DMS server is not a Network File System (NFS) server. To check whether or not a DMS server is an NFS server, enter the following command on the DMS server:

# rcmgr get NFSSERVING

If the response is a 1, the system is an NFS server. If the response is a 0, the system is not an NFS server. Run nfsconfig to configure the server to be an NFS server. Refer to the nfsconfig(8X) reference page for more information about this utility.

13.3 Checking Network Daemon Status

Some DMS client boot problems occur if the network daemons are not running on the DMS server. This condition is indicated on the DMS client with a message similar to the following:

panic: vfs_mountroot: cannot mount root

If you see this message on the DMS client, check to make sure that the following daemons are running on the DMS server:

portmap

mountd

nfsd

nfsiod

Enter the following command on the DMS server to see if the network daemons are running:

# ps ax | grep -E "portmap|mountd|nfsd|nfsiod"

You see process status for any of those daemons that are running, as well as a line showing your grep command. If the daemons are not all running, you must start the inoperative ones.

13.4 Checking Directory Exports

Some DMS client boot problems occur if the client's directories are not exported correctly. If the DMS client boots to single-user mode but will not boot to multiuser mode, check the entries in the DMS server's /etc/exports file and ensure that the /usr file system and dmsN root area entries in /etc/exports are correct, similar to the following example for a DMS client named client1 registered to the /var/adm/dms/dms0.alpha DMS area:

/clients/client1 -r=0 client1
/var/adm/dms/dms0.alpha/root/usr -r=0 -ro

Refer to the exports(4) reference page for information about the /etc/exports file.

13.5 Checking Version Compatibility

If you cannot execute commands on the DMS client and the DMS server and client are running different versions of the operating system, check to see if you copied the client's dmu version to the server. Refer to Section 11.1 for more information.

13.6 Correcting Swap Device Problems

If there is a problem with the disk or disk partition that was designated as the swap device when the client was registered, you may see a message similar to the following:

WARNING: /dev/device/name swap partition has unused fstype, failed to add swap.
       : Swap is being set to lazy (over commitment) mode. The system will
       : come up to single-user mode. Set fstype for swap partition to
       : "swap" using "disklabel -s  swap" command and reboot.

Use one of the following procedures to correct this problem:

If you are using an older version of the operating system that uses traditional device naming conventions (/dev/rrzNc), follow these steps:
1. Log in to the DMS client as root or use the su command to gain superuser privileges.
2. Change directory to /dev.
```
# cd /dev
```
3. Run the MAKEDEV utility on the disk or disk partition designated as the swap device.
```
# ./MAKEDEV swapdev
```
4. Set the file system type for the swap device by running the disklabel utility. Remember to specify swapdev as a raw device.
```
# disklabel -sF /dev rswapdev swap
```
5. Shut down and reboot the DMS client.

If you are using a later version of the operating system that uses newer device naming conventions (/dev/disk/cdromNc), follow these steps:
1. Log in to the DMS client as root or use the su command to gain superuser privileges.
2. Change directory to /dev/rdisk.
```
# cd /dev/rdisk
```
3. Set the file system type for the swap device by running the disklabel utility.
```
# disklabel -sF /dev/rdisk swapdev swap
```
4. Shut down and reboot the DMS client.

13.7 Reconfiguring for a Hardware Update Release

If you are installing a hardware update release and you configure the DMS environment before you add the operating system hardware update, you must connect to the root directory in the DMS environment and issue the following two commands to undo the configuration:

# rm -rf usr/sys/conf/DATALESS
# rm -rf usr/sys/DATALESS

Refer to Appendix D for information about hardware update releases in DMS.