Custom server template problems

lsof command is not fully functional on custom server

Problem

The lsof command is not fully functional on the custom server.

Solution

Check the logs to verify that the lsof command has the appropriate privileges. For example, the logs contain the following types of message:

• DiscoverManager [DiscoverWorker-13] GenericServerSensor-X.XX.XX.XX DEBUG os.UnixOs - lsof privilege looks good. netstat: 46 lsof: 45
• DiscoverManager [DiscoverWorker-11] GenericServerSensor-X.XX.XX.XX DEBUG os.UnixOs - lsof probably lacks privilege. netstat: 46 lsof: 39

Custom server is written to match but does not match

Problem

You write a custom server template to match a process, but the custom server template does not match.

Solution

Determine whether the process has a listening port. If it does not, TADDM ignores it. To prevent TADDM from ignoring the custom server, add the process name for the custom server as a value of one of the forcedServerList properties in the collation.properties file, as shown in the following example:

# Special servers to be recognized by OS layer
# despite having no listening ports
com.collation.platform.os.WindowsOs.forcedServerList=w3wp;nserver;amqzxma0
com.collation.platform.os.UnixOs.forcedServerList=amqzxma0;vxconfigd
com.collation.platform.os.OpenVmsOs.forcedServerList=

Custom server is matched by a previous template

Problem

The custom server is matched by a previous discover template or by an ignore template, regardless of the order of the custom server in the list.

Solution

Change the templates so that the custom server is not matched by a previous discover template or by an ignore template. To determine which template is the matching one, look in the logs.

If the matching template is not an internal template, change the matching template by using the UI.

If the matching template is an internal template, export the template, change the value within the <internal> element to false, and import the template again, according to the following instructions:

1. To export, enter the following command:

   $ api.sh -u admin -p pass find --depth -1 Template >/tmp/data/t.xml

2. Edit the XML output from the previous command, and change <internal>true</internal> to <internal>false</internal>.
3. To import, enter the following command:

   $ api.sh -u admin -p pass import /tmp/data

Discovery using custom server templates does not retrieve configuration files from Tru64 UNIX systems

Problem

Discovery of Tru64 UNIX systems fails to retrieve configuration files specified on the Config Files tab of the custom server template.

Solution

This problem occurs because TADDM uses the scp1 protocol to retrieve configuration files, but the Tru64 UNIX operating system does not support scp1 by default. The scp2 protocol, which is supported by Tru64 UNIX, is not compatible with scp1.

For more information,see http://h21007.www2.hp.com/portal/download/files/unprot/STK/Tru64_STK/impacts/i352.html.

As a workaround, you can install an scp1 package such as OpenSSH on the Tru64 UNIX system: http://www.openssh.com/portable.html.

Out of memory errors, or timeout occur when you capture too many or too large configuration files

Problem

When during a CST creation, in the Search Path for Capture File window you specify criteria to capture too many or too large configuration files, out of memory errors and timeout might occur. For example, in the Search Path, you specify / in the first field and * in the second field, and you select the Capture file content, and Recurse Directory Search options. Such combination captures too many files and TADDM is unable to handle it.

Solution

Try to limit the number of files to search and files that are large. To avoid timeout, you can modify the value of the com.collation.SshSessionCommandTimeout property. To avoid out of memory errors, you can select the Limit size of captured file to option.