# Log File Report

## Overview

The log file is a record of any detected module or system errors and the date and time of any system resets. An excerpt from a sample Log File Report for a single-module system is shown here.

Note: Support for multiple-module servers (e.g. NPM UM 640) was discontinued with NuPoint Release 6.0.

>>> Mitel Corporation <<< SYSTEM ERROR LOGFILE Wed Nov 11 12:32:52 20xx 1 16365(ipPhone ) (ip_phone_han 409 ) 11/11 10:54:51: Ch 49 extension 147321224: Error receiving data, expected 176, received 0 1 16365(ipPhone ) (ip_phone_han 527 ) 11/11 10:54:51: Ch 49: [x.6250] detected a closed socket 1 16314(ipPhone ) (ip_phone_han 409 ) 11/11 10:54:51: Ch 47 extension 164487560: Error receiving data, expected 176, received 0 1 16314(ipPhone ) (ip_phone_han 527 ) 11/11 10:54:51: Ch 47: [x.6248] detected a closed socket 1 16301(ipPhone ) (ip_phone_han 409 ) 11/11 10:54:51: Ch 46 extension 161661320: Error receiving data, expected 176, received 0 1 16301(ipPhone ) (ip_phone_han 527 ) 11/11 10:54:51: Ch 46: [x.6247] detected a closed socket 1 16258(ipPhone ) (ip_phone_han 409 ) 11/11 10:54:51: Ch 43 extension 138531208: Error receiving data, expected 176, received 0 1 16258(ipPhone ) (ip_phone_han 527 ) 11/11 10:54:51: Ch 43: [x.6244] detected a closed socket 1 05766(recorder) (recorder.c 497 MINOR ) 11/11 10:54:51: Logfile size rea ched 800000. Previous log file has been moved to /usr/vm/log/logfile_8. 1 16298(mitaiMon) (mtaimonitor. 363 ) 11/11 10:54:51: Ch 45, Resilient /usr/vm/log/logfile

You are advised to view or print and clear this report on a weekly basis.

### Reading the Logfile Report

The logfile maintains the following format:

<sitecode><m> <tid>(task_name>) <date> <time>: <error message> <code>

<sitecode> | Site code assigned to module (serial output only)
<m> | Module where failure occurred
<tid> | Task ID of program reporting problem
<task_name> | Name of system resource
<date> | Date of occurrence
<time> | Time of occurrence
<error message> | Type of error that occurred (may also indicate resets and other system activity)
<code> | Failure code

If you are unsure of the meaning or importance of any logfile message, do not clear the logfile until you consult with the system technician or your distributor.

## Run the Logfile Report

The Logfile Report can be extensive and, therefore, time-consuming to scroll through. You are advised to review and clear all logfiles on a weekly basis. The Logfile Report can become extensive and, therefore, time-consuming to scroll through.

### View the Logfile

1. From the Main Menu, select (R) Reports and then (L) Log File.

2. Select (V) View Log File Content.

3. The log file is displayed. Press Page Down to scroll through the report.

4. Press Q to exit the report. The system returns to the Log File Menu.

CAUTION: If you are unsure of the meaning or importance of any logfile message, do not clear (delete) the logfile until you consult with the system technician or your distributor.

### Configure the Log File

1. From the Main Menu, select (R) Reports and then (L) Log File.

2. Select (C) Configure Primary Log Output.

3. To enable console output for this module, select (E) Enable Console Output. To disable logging to this module's console, select (D) Disable Console Output.

4. To change the name of the log file (default is "logfile"), select (N) Specify Disk Log File Name and then enter a new name for the log file.

5. Exit from the Log File menu to save your changes.

### To Delete the Log File Report

1. From the Main Menu, select (R) Reports and then (L) Log File.

2. Select (D) Delete Log File.

3. The system prompts you to confirm the deletion. If you are unsure of the meaning or importance of any log file message, do not clear the log file until you consult with the system technician or your administrator.

4. Enter Y to continue and delete the log file OR enter N to keep the log file.

### Access Log File help

1. From the Main Menu, select (R) Reports and then (L) Log File.

2. Select (H) Help.