Configuration of LCDaemonStatusTest

A daemon is a program that runs in the background without requiring any user interaction. It is activated by the occurrence of a specific event or condition. A daemon supervises the system or provides functionality to other processes. Daemon ensures that the operating system runs properly. When a daemon is not active or is not enabled, then, a few processes could not be started/stopped or user requests could not be processed. This may lead to processing lag and also largely affect the functioning of the Linux system. To avoid such processing lag and to ensure the smooth functioning of the Linux system, it is imperative to proactively monitor the status of each daemon on the target Linux cluster. The LCDaemonStatusTest helps administrators in this regard!

This test auto-discovers the daemons on the target Linux cluster and for each daemon, this test reports the current status. This test also reveals if the daemon is enabled or disabled. Using this test, administrators can identify inactive daemons and initiate troubleshooting well before users complain of issues on the Linux cluster.

The default parameters associated with this test are:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, specify the HOST for which this test is to be configured.

• Specify the port at which the specified host listens to in the PORT text box. By default, this is NULL.

• If the REPORT BY OWNER NODE ONLY flag is set to Yes, then this test will report metrics only for the owner node and not for the other nodes in the cluster. On the other hand, if the flag is set to No, then, it indicates that the test will report metrics for all the nodes in the cluster. By default, this flag is set to No.

• By default,USE SUDO flag is set to Yes, indicating that the test uses sudo command to collect the daemon-related metrics. If this flag is set to No, then the test will not collect the metrics using sudo command.

• The SUDO PATH parameter is relevant only when the USE SUDO parameter is set to Yes. By default, the SUDO PATH is set to none. This implies that the sudo command is in its default location - i.e., in the /usr/bin or /usr/sbin folder of the target host. In this case, once the USE SUDO flag is set to Yes , the eG agent automatically runs the sudo command from its default location to allow access to the daemon process. However, if the sudo command is available in a different location in your environment, you will have to explicitly specify the full path to the sudo command in the SUDO PATH text box to enable the eG agent to run the sudo command.

• The DD FREQUENCY refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS button will appear in this page. Clicking on this button will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.