|
|
This chapter contains descriptions of the various log files used by the uOne system, procedures for viewing them, and information that will help you interpret log file messages. The chapter also provides information about of how log files are removed on the Gateserver, and about managing log files on the backend servers.
The following log files provide information about the uOne application environment on the Gateservers:
 |
Note The Attrib.Global and the Attrib.<hostname> files, located in $PARMLIB/parms/<Agent> or $PARMLIB/parms/BASE, contain the parameter settings for all logging detail and debug levels. The parameters can be set to enable or disable logging. Default settings can be over-ridden at the ACB (BASE) / agent level. Typically, any modification to the default settings is handled during configuration with the Quick Configuration tool. You can dynamically change current logging settings of running server agents only with the umcli tool or SNMP. |
To view any of the log files:
Step 2 Log in as spmaster.
Step 3 View the log file in one of the following ways:
Table 5-1 contains the pathnames for all the uOne log files on the Gateserver.
| Log File | Directory in Which It Resides |
|---|---|
ACB and agent log files | $PARMLIB/logs/logfiles and $PARMLIB/logs/netlogs |
stderrout files | $PARMLIB/logs/stderrout |
umsa_pma.log file | $HOME/ADMIN/logs |
SNMP agent log files | $PARMLIB/logs/logfiles |
Step 2 At the command line, type:
umcli -s set loglevel <variable> <value>
| Variable | Value | Description |
|---|---|---|
acb error | off local | Sets the ACB error level logging. |
acb warning | off local | Sets the ACB warning level logging. |
acb info | off local | Sets the ACB informational level logging. |
acb debug | off local | Sets the ACB debug level logging. |
cma error | off local | Sets the CMA error level logging. |
cma warning | off local | Sets the CMA warning level logging. |
cma info | off local | Sets the CMA informational level logging. |
cma debug | off local | Sets the CMA debug level logging. |
<PID> error | off local | Sets the <PID> error level logging, where the <PID> is the PID of any scheduled agent. |
<PID> warning | off local | Sets the <PID> warning level logging, where the <PID> is the PID of any scheduled agent. |
<PID> info | off local | Sets the <PID> informational level logging, where the <PID> is the PID of any scheduled agent. |
<PID> debug | off local | Sets the <PID> debug level logging, where the <PID> is the PID of any scheduled agent. |
|
Note The local setting for the loglevel command means to direct messages logged at the specified level to log files in the $PARMLIB/logs/logfiles directory on the local machine. |
|
Note You can't set remote, event, and resource logging on/off dynamically. |
The uOne logging process provides central log management services to server and application agents. The ACB and agents generate log files.
ACB and agent log files contain messages generated from the ACB and server or application agents. The three types Agent log files are:
|
Note ACB and agent logging can be configured in the BASE/Attrib.Global, <agent>/Attrib.Global, or <agent>/Attrib.<hostname> files. For additional information, refer to the uOne Gateserver Installation and Configuration Manual. |
The ACB and agent log files are identified by their file type as illustrated in Figure 5-1.
There are five types of software messages:
Software log files display the format illustrated in Figure 5-2. Table 5-3 describes the fields in the Sof messages.
Refer to "Software Log File Messages Descriptions" in this manual for descriptions of the Sof log file messages.
| Message Field | Description |
|---|---|
Date | Date when the message was issued (automatically generated). |
Time | Time when the message was issued (automatically generated). |
Module | C-language file name from which the message was issued (automatically obtained during the compilation process). |
Line Number | Line number in the file above where the message was issued (automatically obtained during the compilation process). |
Message Name | Descriptive name of the type of message generated. The name includes the severity and version of the message. These message names can be associated with SNMP traps via trap file configuration. |
Detail | The specific message. |
Resource log messages are used to indicate resource utilization, such as agent instance allocation and deallocation. They can be used for capacity planning.
The sample in Figure 5-3 shows the fields in a Res log file. Refer to Table 5-3 for specific field descriptions.
| Message Field | Description |
|---|---|
Date | Date when the message was issued (automatically generated). |
Time | Time when the message was issued (automatically generated). |
Machine Name | Host name of the machine from which the message was issued (automatically generated). |
Component and Key | Name of the component (e.g., CMA, ACB, etc.) that generated the message (automatically generated). The two sets of numbers that represent the key are UNIX time stamps. (The number of seconds since 12 AM Jan., 1 1970 GMT.) The first part of the key is when Base cane up for this component; the second part is when the application agent came up. |
Process | The name of the process that issued the message (automatically generated). |
PID | Number of the process (process ID) that issued the message (automatically generated). |
Module Name | C-language file name from which the message was issued (automatically obtained during the compilation process). |
Line Number | Line number in the file above where the message was issued (automatically obtained during the compilation process). |
Message Category | Category of resource logging message. The currently used category is Billing |
Resource Type | Type of resource accessed. The currently used type is Application Program. |
Resource Action | Action performed on the resource. The currently used actions are: Allocated and Freed |
ID | A numeric code (often an event or command ID) modifying the resource action above, e.g. a code indicating a "STARTAPP" command ID was used to allocate a Application Program agent resource. These codes are not published. |
Max | Maximum number of resources of the resource type that can be allocated. (independent of current utilization). |
Level | Current allocation of resources of this type. |
User PID | ID number of the process requesting the resource action. |
User Host | Name of the host requesting the resource action. |
User Component | Name of the server agent requesting the resource action. |
Resource Name | Name of the specific resource accessed. |
Application agents use Event Log File messages to log important events or traces, such as information required for call detail records, or errors. Application agents log these messages through the ACB so they are associated with the ACB name. Event logging trace information allows administrators to recreate user problems, enabling enhanced problem resolution abilities. The event logging also supplies billing information.
The following application agents output messages to the Event Log File:
The uOne application agents have several types of event logging:
The format for the event messages generated by the uOne application agents has two parts. The first part of the message is common to all types of event logging. The second part is specific to the type of logging, which is fatal error, warning, informational, or call detail record logging. The sample message in Figure 5-4 identifies the common part of an Event Log Message. See Table 5-5 for descriptions of the message fields.
Refer to the following sections in this chapter for descriptions of the fields that are specific to the logging type:
The UM application Agent logs Fatal Error messages when errors occur that cause UM to exit with the phrases AUD_SORRY_GOODBYE or AUD_SYSTEM_ERROR_GOODBYE. This level of logging is not configurable and is always turned on.
Figure 5-5 is an example of a Fatal Error Message from the Event Log File. Table 5-6 describes the message fields that are specific to Fatal Error Messages.
The UM application agent logs warning messages when non-fatal problems occur, such as failure to play a phrase or retrieve DTMF. This level of logging is not configurable and is always turned on. Table 5-6 describes the message fields that are specific to Warning Messages.
| Field Number | Message Field | Description |
|---|---|---|
11 | Type | Valid access type is: Warning. |
12 | Mailbox ID | Subscriber's mailbox identification. |
13 | Blank | Not applicable. |
14 | Code | Return code. |
15 | Error | Description of the non-fatal problem that occurred. |
16, 17 | Blank | Not applicable. |
Subscriber Informational Messages provide information about subscriber sessions other than billing information and FaxPrint processing and MWI processing. This includes events such as IMAP and LDAP accesses, DTMF keys pressed, and phrases played.
Figure 5-6 is an example of a Informational Message from the Event Log File. Table 5-8 describes the message fields that are specific to Informational Messages.
| Field Number | Message Field | Description |
|---|---|---|
11 | Type | Valid types are: DTMF, Play, Record, IMAP, LDAP, MWI. |
12 | Mailbox ID | Subscriber's mailbox identification or blank. |
13 | Usage Type | The type of usage that this message represents. Valid types are: RetrieveSignals, GetDigits, DateNTime, Number, Phrase, Record, Open, Close, ChangeFolder, Bind, DeleteDistList, AddList, Modify, SetIndicator, SendPage. |
14 | Code | Error code. |
15, 16,17 | Variable | Variable information based on Type. See "Event Log FileInformational Messages". |
Call Detail Records provide information required to bill for subscriber activity. Figure 5-7 shows a sample Call Detail Record from the Event Log File.
|
Note These logs are located on each host that is running uOne application agents. In a distributed system, the information contained in these logs will have to be gathered from multiple hosts for a billing application to get complete and accurate data. Use of the central logging feature is recommended for this purpose. Central logging is covered in the area of uOne Manager. |
See Table 5-9 for descriptions of the message fields that are specific to Call Detail Records. See Appendix C for detailed descriptions of usage information logged in Call Detail Records.
| Field Number | Message Field | Description |
|---|---|---|
11 | Access Type | Valid access types are: Subscriber, SNR, SNA, and Caller. |
12 | Mailbox ID | Subscriber's mailbox identification. |
13 | Usage Type | The type of usage which this record represents. Valid types are: Login, LogOut, MakeCallStart, MakeCallConnect, MakeCallStop, MakeCallFailed Sent (smtp), Broadcast, Cancelled, Failed, LockOut PageSent, PageFailed, FaxReceive, FaxFailed, Transfer, TransferFailed TransferAtt, TransferAttFailed. |
14 | Code | Return Code. |
15, 16, 17, 18 | Variable | Variable information based on Type. See "Event Log FileInformational Messages". |
Figure 5-8 illustrates an interpretation of the log records for a subscriber making a brief phone call.
If there is activity on multiple hosts, the easiest way to trace what is occurring is to turn on centralized logging. Centralized logging only works for Event and Resource logs. The content is the same locally and remotely. When centralized logging is on, all logs are posted to a central log server. Refer to the Gateserver Installation and Configuration Manual for information on setting up centralized logging.
The stderr and stdout files contain information sent to the stderr and stdout streams of the uOne software. Under normal conditions, minimal or no output will be sent to these files. Instead, output should go to the ACB and agent log files. The stderr and stdout files hold string output and log messages that could not be logged normally because of an unavailable local LOGSUB.
When you are troubleshooting a problem, TAC may request copies of these files to help them resolve the problem.
All uOne Administration/PMA log messages are written to the umsa_pma.log file in the home2/spmaster/ADMIN/logs directory. Figure 5-9 provides an example of this file.
The loggingData.ini file defines the types of information and activities that will be logged for uOne Administration and PMA
The uOne SNMP agent log file contains error, warning, informational, and debug output from the uOne SNMP agent. It has the following format:
<date>.<time>.<host>.snmpd.<pid>.<rollover>.log
The logging features are configurable. The settings are generally set during the configuration process by the Quick Configuration tool. Logging settings can, however, be modified at any time to meet your needs. For information on configuring Event Log detail levels, refer to the uOne Administration Manual. Logging settings can be changed dynamically using the umcli tool. Other logging reconfiguration requires restarting processes.
The LogRemover utility constantly monitors logs and moves or deletes them as defined by the rules in the LogRemover.ini file. By default, Log Remover acts on Cisco generated logs. LogRemover runs on the Gateserver only. LogRemover rules can be defined for individual log files. For example, you might want to delete one log file and move another. You can configure periodic delays during rules processing to minimize LogRemover's impact on CPU and I/O usage. You can also configure a time period that must elapse before the LogRemover utility can start rules processing again.
The files specified and the rules for removal are set up in the LogRemover.ini file during system configuration by the Quick Configuration tool. If necessary, you may change the rules at any time.
See the uOne Administration Manual for additional information about the LogRemover.ini file.
Be sure to manage and monitor third party log files on your backend servers. Refer to your vendor documentation for information on log files.
MWI_PlugIn.so, notify.so, and MWI_PassOff logging occurs on the Netscape Messaging Server via the syslog user facility. See the /etc/syslog.conf file for information about where the logs are configured and the severity that is logged.
Posted: Mon Sep 25 20:14:58 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.