Troubleshooting Volution Manager Clients

• To check if the Volution Manager Client daemon, volutiond, is running:
  
  ps -ef | grep volutiond

• If the VM Client is not contacting the Volution Manager computer creation daemon (volutonccd) to populate your directory, check the following:

  • The VM Client might not be using the correct certificate if the VM Server has been reinstalled. If this is the case, run the following commands to remove the certificate and restart the VM Client:
    
    rm -rf /etc/opt/volution/cacert
    
    rm /etc/opt/volution/volutiond.conf
    
    /etc/init.d/volutiond restart

  • If the VM Client is running but is not contacting the VM Server, run the voldiag tool.

• If a VM Client is unable to complete a hardware inventory, or the health monitoring function is not working properly, the Practical Extraction and Reporting Language (Perl) might be installed in an unexpected location. The VM Client is dependent on Perl, and looks to find it first in /usr/bin, and then in /usr/local/bin.

  If Perl is installed in a different location on your system, you will need to modify the following files to specify the correct location:

  • the /opt/volution/bin/os5hwinfo2xml file for hardware inventory

  • the /opt/volution/bin/os5tsmod.pl file for health monitoring

See also:

• ``Getting diagnostic information on Volution Manager Clients''

• ``Troubleshooting the Volution Manager Client daemon''

• See the Caldera Volution Manager documentation for more extensive troubleshooting information.

Getting diagnostic information on Volution Manager Clients

Use the voldiag tool to get diagnostic information on VM Clients. This tool provides information about:

• System information, such as platform and architecture data

• Network analysis, including basic network functioning and name service resolution

• SLP analysis, including availability of services and system scope

• the volutiond configuration file and current volutiond functions

To use voldiag:

1. Log onto the SCO OpenServer system that you want to analyze as root.

   You must have root privileges to run this command because it displays passwords that allow the VM Client to access LDAP and the software repository (the organizational unit in your LDAP directory that includes objects that represent software packages you plan to distribute). In addition, many of the actions you might take as a result of voldiag output (such as re-starting a system) require this permission level.

2. Run:
   
   /opt/volution/bin/voldiag [-option]

Troubleshooting the Volution Manager Client daemon

The VM Client Analysis section of the voldiag tool's output contains information read from the volutiond configuration file (/etc/opt/volution/volutiond.conf), as well as real-time status of the volutiond daemon and the services it detects.

• If volutiond.conf is unreadable because it has been corrupted or is not present, VM Client Configuration Information fails and the daemon does not run correctly. In this case, you need to re-authenticate the VM Client to the server by removing the file (if present) and then stopping and starting volutiond:
  
  /etc/init.d/volutiond stop
  
  /etc/init.d/volutiond start

  The VM Server's computer creation daemon, volutionccd, then creates the configuration file automatically.

• If the volutiond daemon is not running, you need to re-start the daemon from the client by entering /etc/init.d/volutiond start.

• If the daemon is running, voldiag checks to see if it can contact the following services: CCD, DENS, LDAP, and SLP. This is primarily a cross-check at this point, as these systems were located and verified as functional earlier in the diagnostic process.

• Based on it's ability to access the required services, voldiag reports the system's health. This is simply a quick view of the sum of all diagnostic information.