Commonly-accessed directories and files on Linux servers

Last Updated : Mar 14, 2024 |

The table describes the directories and some useful log files in each that can be quick indicators of problems. These files are not useful to the general user, as much of the information is contained in SAT reports or Web interface logs and reports. However, the information is presented here for situations in which the SAT and Web interface might not be available.

Caution:

Do not directly manipulate (change) the files in the table.

Table 1: Directories and files for troubleshooting

Directory

File

Description

/etc/opt/ecs

ecs.conf

This file is the configuration file for the switch and is essential for Communication Manager Applications to run correctly. The file is populated when you configure the server through System Management Interface (SMI). Flags that are set incorrectly in this file can cause numerous problems in the switch.

servers.conf

This file contains information on the IP addresses of the servers and the control networks. This information is useful for troubleshooting possible network problems. This file is populated by using the Server Configuration  > Configure Server option on SMI.

/etc/hosts

This file contains the IP addresses of all Cajun-family devices and servers in the system. This information is useful for troubleshooting possible network problems. This file is populated by using the Server Configuration > Configure Server option on SMI.

lspList

This file is usually 0 bytes long, unless one or more Survivable Remote Servers are registered to this server. If Survivable Remote Servers are registered, this file contains the IP addresses of the Survivable Remote Servers to which Communication Manager has tried to send the translation files. This file is populated by registering Survivable Remote Servers.

/var/log/ecs
This directory contains three very useful types of files:

ecs log files

These log files are marked by the date on which the log files occur and provide information about Communication Manager and various Linux processes. However, this information might not be directly useful.

Commandhistory

This file contains the history of commands that are issued on the server. This file shows such things as when server interchanges were done, when patches were applied, and when servers were started and stopped. Note that this file does not record every command that is run at the Linux CLI but is populated by the various command interfaces.

wdlog

This file is the watchdog log, the process in Communication Manager that watches over all other processes to ensure proper behavior. This log outputs occupancy profiles on a per-process basis if the system is running at high occupancy. This file is populated by the Watchdog process.

/var/log/messages

This file contains more information about system behavior, including information on modems, security, and traps.

/var/crash

If the core-vector is set on a server that is running Communication Manager, a core dump is generated on system restarts for Linux-based servers. See Core dumps and mini-core dumps for some basic information about core dumps. This file is populated by various Linux processes.

/var/log/defty/dumps

If the core vector is not set on a server that is running Communication Manager, a mini core dump (smaller version of the core dump) might be generated on restarts. This directory contains core dumps on Linux-based servers. See Core dumps and mini-core dumps for some basic information about mini core dumps. This file is populated by various Linux processes.

Core dumps and mini-core dumps

A core dump is a file that contains a snapshot of the memory image of the server at the time that the core dump is generated. A core dump is required to debug system failures in depth. System failures can vary from a single process restart to a reload of the server. To generate a core dump, you set a flag in the low-level maintenance monitor (LMM) on legacy system (G3r, si, and csi). This flag can be enabled or disabled. When enabled, this flag can generate core dumps under various conditions. On Linux-based servers, the /var/crash directory contains core dumps.

A mini core dump is usually generated without setting any flags. However, a mini core dump generates less useful information than a core dump. On Linux-based servers the /var/log/defty/dump contains mini core dumps.