Table of Contents
Log Files
At runtime, uTel, uLite, uPilot, and uOne create log files in C:\CiscoSystems\uOne\logs path. The log files are periodically cleaned out of this directory by the interval settings in the uLogRemover.ini file.
uLite logs can be found at the C:\CiscoSystems\uOne\logs directory. The files are listed as uLite.XXXXXXXX.out and can be viewed using Wordpad. The following information discusses the uLite logging process which can be helpful when reviewing uLite logs.
- When uLite initializes, it does a login to the Messaging Server. If the login fails, check to see if the Messaging Server is running. If it is not, start the Messaging Server and then restart uLite.
- uLite periodically does an inventory of messages in the "notifier" mailbox. If the inventory fails, check to see if the Messaging Server is running.
- If there is a message in the "notifier" mailbox, uLite reads the header and sends a set indicator command to uTel. Check for failure messages from uTel.
The following table reflects the particular fields of information shown in a log file.
Table 4-1:
| Time Stamp
| Server
| Log Designation
| Log Data
|
The time stamp of the log message from the NT server.
| The server the uOne application is interacting with for the log message.
The servers include: uTel, Directory Server, and Messaging Server.
| The LOG tag designator.
| Any information that is being sent between servers is logged. It includes: API calls, commands, queries, acknowledgements, error messages, and so forth.
|
uLite Log File Format
Figure 4-1: Sample uLite Log File:
14:07:01.812000|NOTIFY|LOG| [* OK Netscape IMAP4rev1 Service 3.62 on
estfeat3.cisco.com at Wed, 8 Dec 1999 14:07:01 -0500 (Eastern Standard
Time)]
14:07:01.812000|NOTIFY|LOG| [00000000 CAPABILITY]
14:07:01.812000|NOTIFY|LOG| [* CAPABILITY IMAP4 IMAP4rev1 SCAN QUOTA
LITERAL+ AUTH=LOGIN XSENDER X-NETSCAPE]
14:07:01.968000|NOTIFY|LOG| [00000000 OK CAPABILITY completed]
14:07:01.968000|NOTIFY|LOG| [00000001 LOGIN notifier 1234]
14:07:01.984000|NOTIFY|LOG| [00000001 OK LOGIN completed]
14:07:01.984000|NOTIFY|LOG| [00000002 SELECT INBOX]
14:07:01.984000|NOTIFY|LOG| [* 0 EXISTS]
14:07:02.171000|NOTIFY|LOG| [* OK [UIDVALIDITY 944145963] UID validity
status]
14:07:02.171000|NOTIFY|LOG| [* FLAGS (\Answered \Flagged \Deleted \Draft
\Seen)]
14:07:02.171000|NOTIFY|LOG| [* OK [PERMANENTFLAGS (\Answered \Flagged
\Deleted \Draft \Seen)] Permanent flags]
...
14:13:29.109000|NOTIFY|LOG| [0000000a NOOP]
14:13:29.109000|NOTIFY|LOG| [* 1 EXISTS]
14:13:29.250000|NOTIFY|LOG| [* 1 RECENT]
14:13:29.250000|NOTIFY|LOG| [0000000a OK NOOP completed]
14:13:29.250000|NOTIFY|LOG| [0000000b FETCH 1 (ENVELOPE
BODY.PEEK[HEADER.FIELDS (X-Priority X-Sensitivity X-AmtevaBcast
X-AmtevaExp)] BODYSTRUCTURE UID INTERNALDATE RFC822.SIZE FLAGS)]
14:13:29.453000|NOTIFY|LOG| [* 1 FETCH (ENVELOPE ("Wed, 8 Dec 1999
14:13:26 -0500 (Eastern Standard Time)" "Voice Message From Test Phone"
(("Test Phone" NIL "tphone" "estfeat3.cisco.com")) (("Test Phone" NIL
"tphone" "estfeat3.cisco.com")) (("Test Phone" NIL "tphone" "e]
14:13:29.453000|NOTIFY|LOG| [ BODYSTRUCTURE (("AUDIO" "WAV" NIL NIL
"Amteva Voice Message (1 seconds)" "BASE64" 16708 NIL ("INLINE" ("VOICE"
"Voice-Message" "FILENAME" "message.wav")) NIL)("AUDIO" "WAV" NIL NIL
"Originator's Spoken Name" "BASE64" 7450 NIL ("INLINE" ("VOI]
...
17:31:11.515000|NOTIFY|LOG| [Set MWI ON for 8047625641]
uOne log files can be found at the C:\CiscoSystems\uOne\logs directory. The files are listed as uOne.XXXXXXXX.out and can be viewed using Wordpad. There is a separate uOne.out file for every instance of uOne. The log file shows the client/server interaction between the uOne application and uTel, the Directory Server, and the Messaging Server. The following table reflects the particular fields of information shown in a log file.
Table 4-2: uOne Log File Format
| Time Stamp
| Server
| Sent/Response
| Log Data
|
The time stamp from the NT server of the log message.
| The server the uOne application is interacting with for the log message.
The servers include: uTel, Directory Server, and Messaging Server.
| Tagged as "Sent" if uOne is sending to the server.
Tagged as "Resp" if uOne is receiving a response from the server.
| Any information that is being sent between servers is logged. It includes: API calls, commands, queries, acknowledgements, error messages, etc.
|
Figure 4-2: Sample uOne Log File
14:13:00.859000|TEL|SENT| [1 LOGIN UM4 pass]
14:13:00.875000|TEL|SENT| [2 CREATESESSION]
14:13:00.890000|TEL|RESP| [2 OK CREATESESSION Complete|{SesId6}]
14:13:00.890000|TEL|SENT| [3 SesId6 {REQUESTGROUP UM4 INCREMENT}]
14:13:00.890000|TEL|RESP| [3 OK REQUESTGROUP
Complete|{SCR_UNRECEIVEDCOUNT 1} ]
14:13:00.890000|TEL|SENT| [4 NOOP]
14:15:30.203000|TEL|SENT| [5 DESTROYSESSION SesId6]
uPilot log files can be found at C:\CiscoSystems\uOne\logs directory. The files are listed as uPilot.XXXXXXXX.XXX.out and can be viewed using Wordpad.
The uTel.ini file indicates at what level logging is being performed. The uTel logs can be found at the C:\CiscoSystems\uOne\logs directory. The files include uTel.dbg, uTel.XXXXXXXX.out and uTel.XXXXXXXX.err, and can be viewed using Wordpad.
Figure 4-3: Sample uTel.XXXXXXXX.out File
[--w- 12:47:37.671000 scp_run.c 98 ? ?] - Call[SCPCall18] disconnected
[--w- 12:47:37.671000 scp_run.c 98 ? ?] - Call[SCPCall19] disconnected
[--w- 12:47:39.531000 scp_run.c 98 ? ?] - Call[SCPCall16] disconnected
[--w- 12:49:23.218000 rad_rtp.c 767 ? ?] - RTPSession[RadRtpSes00] connection is NULL - removing callback
[--w- 12:50:15.406000 rad_rtp.c 767 ? ?] - RTPSession[RadRtpSes01] connection is NULL - removing callback
[-i-e 12:55:06.625000 response.c 729 ? ?] - Response block[RespId130] timeout. Timer handle[154], Command[ANSWERCALL]
[--w- 12:56:06.281000 rad_rtp.c 767 ? ?] - RTPSession[RadRtpSes00] connection is NULL - removing callback
[---e 12:57:31.765000 scr_cmds.c 1167 SesId7 ?] - Incomplete DIALMAP parameter list
[--w- 12:57:43.437000 rad_rtp.c 767 ? ?] - RTPSession[RadRtpSes00] connection is NULL - removing callback
[--w- 12:58:04.125000 rad_rtp.c 767 ? ?] - RTPSession[RadRtpSes00] connection is NULL - removing callback
[--w- 12:59:51.015000 rad_rtp.c 767 ? ?] - RTPSession[RadRtpSes00] connection is NULL - removing callback
[---e 13:03:07.859000 scr_cmds.c 1167 SesId10 ?] - Incomplete DIALMAP parameter list
[---e 13:07:32.359000 schemefile.c 424 ? ?] - error creating
The level of logging for uTel is determined by settings in the [DBG] section of the uTel.ini file. See "The .ini Files" chapter of this guide for more information on setting the logging level for the uTel.ini file.
There are two tools in Windows NT which are used to gather and control information on the performance and logging of the NT system. They are the Event Viewer and the Task Manager.
Event Viewer
The Event Viewer is the tool you can use to monitor NT events in your system. You can use Event Viewer to view and manage System Security and Application event logs. It can be accessed by the following steps.
Step 1 Click the Start button in the Windows task bar to get the Start popup menu.
Step 2 Select Programs, then Administrative Tools (Common).
Step 3 Select Event Viewer.
Task Manager
The Task Manager enables you to monitor and control your computer and the processes running on it. The various features you can access from the Task Manager are listed below.
- The Application tab shows the status of the programs (also known as tasks) that are currently running on your computer. From this window you can end, switch to, or start a program.
- The Processes tab shows information about the processes that are currently running on your computer. From this window, you can end a process.
- The Performance tab displays a dynamic overview of your computer's performance, including graphs for CPU and memory usage. The number of items running includes handles, threads, and processes. Information about physical, kernel, and commit memory is also included.
You can access the Task Manager by performing the following steps.
Step 1 Simultaneously press Control + Alt + Delete while the system is running.
Step 2 Then select Task Manager.
Error logs are used to record error messages generated by the Directory Server, specifically ns-slapd. These messages can describe error conditions, but more often they contain informative conditions such as server startup and shutdown times, and the port number the server uses. This log contains differing amounts of information depending on the current setting of the Log Level parameter. The error log is located at:
C:\Netscape\SuiteSpot\slapd-<Server ID>\logs\errors
Access Logs are used to record each database access. The following information is recorded in the log file: IP of the client machine that accessed the database, operations performed (for example, search, add, modify), result of the access (for example, the number of entries returned). The access log is located at:
C:\Netscape\SuiteSpot\slapd-<Server ID>\logs\access







Posted: Thu Jun 29 06:16:37 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.