Troubleshooting Linux/Unix/Mac OS Discovery

Some of the more common discovery issues and resolutions are described below.

Sudo Issues

With Linux/Unix/Mac OS discovery, CAM uses certain commands in data collection that require the use of the sudo command. This means that the credentials you enter when you configure Linux/Unix/Mac OS discovery must be for a user who is authorized to execute sudo. For example, Services on Mac OS requires using the sudo command. If you set up discovery using credentials that don't allow for executing sudo, services information cannot be collected during discovery.

To ensure you can collect all data:

  • Verify that your Linux/Unix/Mac OS machines are set up to allow use of sudo.
  • If you are using a private key instead of a password, the user must be able to run sudo commands without being prompted for a password.
  • With some operating systems, you may also need to check the secure_path value for commands run using sudo. This value should include those directories that are normally used to store administrative commands. In most cases, this information is stored in the /etc/sudoers file and should read as follows: 
    Defaults secure_path =/sbin:/bin:/usr/sbin:/usr/bin

Generated Files

Machines discovered via Linux/Unix/Mac OS discovery must have a file associated with each GUID returned by the discovery process. When the discovery process does not find such a file for a GUID, it creates one with the following characteristics:

  • File name = <guid>.<platform>

where <platform> = linux, unix, or app (Mac OS)

  • Path = "/"
  • File size = 500 (Linux), 600 (Unix), or 100 (Mac OS)

Can't Connect to a Machine

If you can't connect to a known machine (for example, if you receive an error when you select Test to validate your credentials, or discovery fails to find a known machine), check whether the machine supports SSH connections. You can do this by using a tool like PuTTY. If you can connect via PuTTY, but not from CAM Administrator, contact technical support for assistance.

Inventory Information Missing from Some Machines

If the discovery process completes successfully but some inventory information is missing, check the following:

  • Operating system. Supported operating systems are listed in Linux/Unix/Mac OS Machines. If you want to discover machines on other operating systems, please contact technical support for assistance.
  • Commands used. If one or more commands for collecting data were unsuccessful, contact technical support.
  • Whether the commands used require sudo. See Sudo Issues above.

Previously Successful Discovery Fails

If discovery for a particular configuration previously succeeded but now fails, check whether you are running discovery from the same CAM Administration Service machine where the configuration was saved, or if you are on a machine that uses a shared certificate (see ../../cam_certificate_manager/Cert_Welcome_to_the_CAM_Certificate_Manager.xml#concept1743).

Default Shell

When discovering Mac OS devices, the Login Shell for the user running discovery must be Bash. This can be set in System Preferences on the Mac machine.