TOC & Recently Viewed

Recently Viewed Topics

General Client Information

Running LCE Clients Directly on the LCE Server

Some LCE clients can be installed and operated on the same host as the LCE server. The clients must be configured to connect to either localhost (127.0.0.1) or the IP address of the LCE server. Multiple LCE client types (such as the primary LCE Client and the Tenable NetFlow Monitor) can be run at the same time as well.

Caution: While using the LCE Client to watch LCE log files, be extremely careful to avoid feedback loops. For example, choosing to monitor lce.log would cause any log saved by the LCE server to be captured by the LCE Client, sent back to the LCE server, and repeated indefinitely.

Running Multiple LCE Clients on One Host

Remote systems can run multiple LCE clients. When using the LCE Client Manager and various LCE clients and versions, each client type is identified and managed appropriately upon connection to the LCE server.

Maximum Number of LCE Clients

A maximum of 8,192 individual LCE clients can be connected simultaneously to the LCE server. Once 8,192 clients have connected, the LCE server will stop accepting new connections.

LCE Client Types and Platforms

There are a number of different LCE client types available. All LCE clients report performance statistics (memory, disk space, and CPU usage) on their host regardless of the platform. The LCE clients that support 32-bit platforms will operate on 64-bit systems as long as the 32-bit libraries are installed. However, native 64-bit support is only available for certain platforms.

Diagnosing Connection Problems

If an LCE client cannot connect to the LCE server:

  • View the most recent LCE client log file located in that client's install directory to determine if any error messages exist. The log has a file name in the following format: <YearMon>.log, where <YearMon> is a value such as 2016Mar. In the case of the LCE Client for Windows, the file is named lce_client.log.
  • Check that the LCE server daemon is running and correctly licensed by running “service lce status”. If the process is running, output similar to the following is displayed:

    # service lce status

    lced (pid 26868 26864) is running...

    lce_queryd (pid 26876 26874) is running...

    lce_indexerd (pid 26892) is running...

  • Check to see if there is a local firewall, network firewall, or other network issue that would prevent the LCE client connecting to the LCE server. On the LCE server host, monitor connections to TCP port 31300 (default port). If no connections attempts by the LCE client are observed, something is blocking the connection. Check the LCE client host for potential configuration issues.
  • Using the Clients page of the LCE interface, confirm that the LCE client is authorized to connect to the server.
  • Verify that the IP addresses of the LCE client and LCE server are correct. The client will not connect to the LCE server if it has the wrong IP address or cannot correctly resolve the hostname, and the LCE server will not accept a random client unless it is specifically configured in the LCE Client Manager.

Copyright 2017 Tenable, Inc. All rights reserved. Tenable Network Security, Nessus, SecurityCenter, SecurityCenter Continuous View and Log Correlation Engine are registered trademarks of Tenable, Inc.  Tenable, Tenable.io, Assure, and The Cyber Exposure Company are trademarks of Tenable, Inc.  All other products or services are trademarks of their respective owners.