Collect Logs Tool - Novell DATA SYNCHRONIZER - ADMINISTRATION GUIDE 07-2010 Administration Manual

By using the Flatfile Connector, you can determine which log files are most likely to provide useful
data for resolving the problem.

3.4.8 Collect Logs Tool

As shown in the Section 3.4.1, "Log File Overview," on page
in a variety of directories. The Collect Logs tool collects the most recent log files into a
for convenience when submitting log files to Support. You can collect all log files:
default.pipeline1.groupwise-AppInterface.log
default.pipeline1.groupwise.log
default.pipeline1.mobility-AppInterface.log
default.pipeline1.mobility.log
engine.log
configengine.log
connectorManager.log
PySQLPool.Query.log
Or you can collect just the first five files in the list. The files are collected into a file named
datasync_logs_yyyy-mm-ddThh.mm.ss.tar.gz
To run the Collect Logs tool:
1 In a terminal window, become the
2 Change to the following directory:
/opt/novell/datasync/tools
3 Run the following command:
python CollectLogs.pyc
4 Enter
if you want to collect all log files.
yes
or
Enter if you want only the five most useful log files.
no
5 Enter
for the GroupWise Connector.
1
6 Enter for the Mobility Connector.
1
The collected logs are listed in the terminal window. A
which lists the files that have been included in the resulting
When you submit the set of log files to Support, you also need to provide a GroupWise message ID
of a message that has failed to synchronize, so that Support can use the Trace Log tool
( ) to trace the problem message. The output of the Trace Log tool includes the
traceLog.pyc
following sections to help Support diagnose the problem:
Starting from GroupWise...
===================================
From GroupWise Connector into Engine...
=======================================
Inside Engine...
25, Synchronizer log files are created
.
user.
root
manifest.txt
.tar.gz
file is also created,
file.
.tar.gz
Managing Your Synchronizer System
file
29